> >>Other question : We are using Long as our pk in > all > >>EJB's, is there any > >>advantadge in using string instead? if not, is > there > >>a way to inform > >>xdoclet to use Long as pk? > > > > > > I think it would depend on app server, or database > > used as persistence store, or even on underlying > > processor architecture. > > > > You can say @ejb.bean <blabla> primkey-field="foo" > - > > if > > foo happens to be Long, then Long would be used as > PK > > > > i mean, the PK generated by Util object will take > this in account...
Util object does not generate PK classes. You surely mean GUID generation which is hex string. How do you intend to stuff 32 byte hex string into long? IMHO, using this generation is better than to depend on separate ejb or counter services which you will lookup via jndi and such stuff. Most modern databases would compare strings fast enough. regards, ===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ > __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
