Now that the EJB jar MANIFEST file is deprecated in the EJB1.1
specification, what are the intended semantics of the standard MANIFEST
Class-path: header? That is, how do I indicate that my beans in an EJB
jar will make use of certain non-EJB classes that it assumes are
present? Previously, since a MANIFEST file was required, I put the
Class-path: header in there (although most app servers don't recognize
it, thus violating the jar specification). Is a MANIFEST file
containing this header still permitted?
Cheers,
Laird
===========================================================================
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".
