portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <jetspeed-...@jakarta.apache.org>
Subject [jira] Commented: (JS1-542) Torque OM jar generation per backend database
Date Mon, 18 Apr 2005 20:46:48 GMT
     [ http://issues.apache.org/jira/browse/JS1-542?page=comments#action_63107 ]
Ate Douma commented on JS1-542:

> The Torque build is set as a pregoal to java:compile.
> Wonder why that isn't enough, since it does a jar:install
Because the jar is defined as dependency in the main project.xml and maven first it to be
resolved before it even starts with the java:compile

>> I tested this with Oracle9i and can confirm it working.
> The big gotcha here is when you go to create a new user.
> Thats when Torque fails miserably: since the generated code for Oracle
> requires sequences.
Sorry, I only tested it out yet with the buildin users so I missed that one! It certainly
is a killer...
Do already have an idea how to handle that?

> Torque OM jar generation per backend database
> ---------------------------------------------
>          Key: JS1-542
>          URL: http://issues.apache.org/jira/browse/JS1-542
>      Project: Jetspeed
>         Type: New Feature
>   Components: Database
>     Versions: 1.6-dev
>     Reporter: David Sean Taylor
>     Assignee: David Sean Taylor
>      Fix For: 1.6-dev

> Creates torque specific bindings for the selected database.
> Goal: end users will no longer have to recompile the source to get support for a different
database than hypersonic. This requirement has been the source to a large number of problems
reported on the user list.
> on the distribution site, I'd like to provide several small jars for each torque-supported
> + 1.6-binary
>   + torque
>       + hypersonic
>           jetspeed-torque-om-1.6.jar
>       + mysql
>           jetspeed-torque-om-1.6.jar
>       + axion
>           jetspeed-torque-om-1.6.jar
>       + sybase
>           jetspeed-torque-om-1.6.jar
> ...
> prefer to have all the jars named the same to lessen the chance of someone accidently
having 2 jars installed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message