hello all; i am having a hard time figuring something out. i have to write a component(in a J2EE environment but i dont have a constraint on its implementation. meaning that its not nessecarily an EJB). this component is stateless and as a part of the service it provides, it should call another service that was implemented as a statefull session bean. now, i dont know why but it feels wierd, if i implement my service as a staeless bean and inside it i am calling a statefull bean. is this ok? is something wrong with the architecture? also, if i implement the service as a regular class that just sits in the AS classpath than do i have to deploy it as a client cause its not a J2EE component or can i just get the JNDI context and do whatever i want - this would break the J2EE architecture right? we need a lot of helper classes in our application some are EJB specific(so i can package them in the ejb.jar) and some are just an infrastructure for the application and i never seem to understand where i should put these general classes and if i should package them or just put them in the classpath. what i am sure of is that i want to follow the spec fully. please give me your comments sorry if the mail is confusing.
__________________ 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".
