I'm sure you'll get other opinions, but in my view, this translator class is a "utility" object, not a business object as such (it doesn't represent a use case or an entity). So I'd make it a mnormal Java class, and not put it into an ejb-jar file but make it a class reachable by all EJBs on the classpath. That resolves versioning issues across ejb-jar files. Hope that helps.
Ken Litwak >hi; >here is another point i have been strugling with. >for an application in the J2EE environment. i need to provide a component >that provides multi-lingual support. as usual i am stuck deciding whether to >implement this service as a staeless session bean with a traslate(...) >method or to write a regular class doing this. if i write it as a regular >class then how should i package it? it serves several ejbs and servlets so >is it good to package it as a helper class in all ejb.jar and war files? >what else can i do? >is writing a singelton regular class that gives this functionality a >solution? in such a case how should this be packaged? >thanks > >__________________ >Guy Katz >Comverse >[EMAIL PROTECTED] >+972 3 7663686 > >=========================================================================== >To unsubscribe, send email to [EMAIL PROTECTED] and include in the body >of the message "signoff EJB-INTEREST". For general help, send email to >[EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
