Ok, I'll give that a try.fine
toI was thinking of something like <class-descriptor><sequence-manager/></class-descriptor> Then persistence broker will check class-descriptor before defaulting
jdbc-connection's sequence manager. Are there any plans to introduce this/these feature(s)? Probably too late for 1.0?
It's never too late for new features ;-) I thought about that and add this on my todo list, but priority set within the scope of 1.1
regards, Armin
----- Original Message ----- From: "Durham David Contr 805 CSPTS/SCBE" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]>; "Armin Waibel" <[EMAIL PROTECTED]> Sent: Wednesday, October 01, 2003 4:03 PM Subject: RE: Can I use multiple Sequence Managers
####### Currently it's not supported (you can only
define SequenceManager implementations on a per jdbc-connection-descriptor level), but you can easy write your own SequenceManager implementation to manage different SM implementations. Use custom 'attribute' elements in your field-descriptor to specify the different SM implementation classes and let your SM implementation manage the different instances.
regards, Armin
Ok, I'll give that a try.
I was thinking of something like <class-descriptor><sequence-manager/></class-descriptor>
Then persistence broker will check class-descriptor before defaulting to jdbc-connection's sequence manager.
Are there any plans to introduce this/these feature(s)? Probably too late for 1.0?
Thanks,
Dave
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
