Hi, My opinion is that in this case a helper class is the right solution. I see the use of the session ejb-s only for business logic that needs/requires the advantages of the ejb container. I usually put such things in a helper class added to the jar file that contains the ejb-s. Anyway, in case that you have to call it also from a servlet (so the war file), here an ejb approach fits better, otherwise please help, a common helper for both jar and war files seems a little bit complex; it's possible to mix in an .ear file this helper (via config files, ...)?
Regards, Ionel. "Katz, Guy" wrote: > 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".
