What information must be included in the ejb jar file, as opposed to included on the server's classpath? In 17.3, the ejb specification states that the ejb jar file must include the class files of the following: bean class, home and remote interfaces, primary key class if the bean is an entity bean, superclasses and interfaces for the bean, home, and remote interfaces, classes for method parameters, results, and exceptions. Clearly, this is not accurate. If you pass a java.lang.String as a parameter to a method, you don't then include java.lang.String in your deployable jar. It seems obvious to me that 17.3 is only mandating that classes be AVAILABLE for method parameters, results, exceptions, and primary keys. However, I wonder to which other elements 17.3's literal interpretation does apply. In my case, can I legally have superclasses and interfaces for beans and remote interfaces deployed outside the ejb jar file? Or will this deployment method reduce my beans' portability? Thanks in advance- Dan =========================================================================== 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".
