[ http://issues.apache.org/jira/browse/JS1-542?page=comments#action_63114 ]
     
David Sean Taylor commented on JS1-542:
---------------------------------------

> 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

The jar is in the remote repo, should work as is

>> 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? 


Well thats the whole point. 
There needs to be one jar per database.
So you change the torque-om/project.properties:

torque.database = oracle

and then rebuild

For the 1.6 release, I was planning on prebuilding each and every database (and 
signing), ... i know


> 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 database:
> + 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to