As per the EJB 2.0 (pfd2) specifications it is possible to pacakge an EJB 1.1 Container mananged persistence bean in a EJB 2.0 compliant jar using the cmp-version tag. In my opinion this might not serve any useful purpose because: 1) A EJB 1.1 CMP cannot have local interfaces and hence cannot participate in Relationships. 2) It is mandatory for the EJB 2.0 container to support jars which conform to EJB 1.1 specification. It made sense to have this tag in the previous version ( public drafts and pfd) because they allowed EJB 1.1 Bean to be the target of a relationships. With that removed in the proposed final Draft 2 the cmp-verison tag does not have much relevance. Providing suport for cmp-version tag would be trivial if the container supports EJB 1.1 version but I feel that would be better to keep the EJB 1.1 beans in seprate jars. Amit Khanna, Pramati Technologies =========================================================================== 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".
