> There are quite a few issues with the Security service
> that aim to be fixed with newer versions.
Good to know, thank you.
> Curious, why are you not liking them?
Nah, it's not that I don't like them (it's a good solution to an irritating
problem). It's just that using Oracle sequences for _my_ tables and
idbroker for the turbine tables messes w/ my finely-tuned sense of
anal-retentive code aesthetics. :)
Here's a real question, however - how, in my schema tables, can I have a
foreign key to a row in TURBINE_USER? Obviously one cannot put a
foreign-key reference to tables that don't exist in one's own schema and in
a vain attempt to circumvent this I deleted the turbine-schema.xml file and
placed the table definitions directly into my own PROJECT-schema.xml file.
This, however, seems to cause ant to crash during the 'schema-sql' target:
<error>
build-torque.xml:198: Generation failed. For more information consult the
velocity log, or
invoke ant with the -debug flag.
at
org.apache.velocity.texen.ant.TexenTask.execute(TexenTask.java:579)
at org.apache.tools.ant.Task.perform(Task.java:319)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
at
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java:319)
...
</error>
Is the only hope to manually insert the foreign-key declaration into the
resulting .sql file? Definitely not ideal, anyone have a better idea?
Regards,
-j
"Chris K Chew"
<[EMAIL PROTECTED] To: "Turbine Users List"
om> <[EMAIL PROTECTED]>
cc:
12/04/2002 11:21 Subject: RE: TURBINE_* using native
seqs?
AM
Please respond to
"Turbine Users
List"
Your best bet would be to live with it for the time being. There are quite
a few issues with the Security service that aim to be fixed with newer
versions. Curious, why are you not liking them?
You can alternatively check out the source from cvs, install maven, change
the PeerClasses (org.apache.turbine.om) to use the native id generation and
recompile. Read up on Torque to see how Peer classes are affected
depending
on the id scheme you select.
Good luck,
Chris
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 03, 2002 4:45 PM
> To: Turbine Users List
> Subject: TURBINE_* using native seqs?
>
>
>
> I've recently begun a project using Turbine and am quite impressed. I am,
> however, currently struggling with how to convince the turbine
> user/group/role objects to use 'native' id brokering rather than the
> ID_TABLE/idBroker system. It seems to me that this behavior is compiled
> into the .jar distributed as part of the tdk (I'm using 2.2rc2) and that
> I'm simply stuck and should learn to enjoy using native sequences for my
> tables and ID_TABLE for the TURBINE_* classes.
>
> Is this the case? Obviously not a huge deal; I'm simply curious.
> -j
>
> -------------------------------------------------
> James Diggans
> Bioinformatics Programmer
> Gene Logic, Inc.
> Phone: 301.987.1756
> FAX: 301.987.1701
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
