This isn't a flaw; it's intentional. Keep in mind that EJB need only provide persistence mechanisms; EBs could just as easily be stored in flat files, for example, as in a database. Thus, the decision as to how to persist them is vendor-specific. This is why you need to generate information specific to weblogic, such as connection pools, in a separate file. It just happens that WL uses XML for this as well, because it is easy to do so. -Jake At 03:27 PM 6/16/00 -0400, you wrote: >Converting from WL 4.5.1 to WL 5.1.0 so I have to change my DD from text >format to XML. I find with WL that instead of one XML file, I have to >create 3 XML files when have CMP beans, or 2 XML files if no CMP. The >only explanation for this, that I can think of, is that the spec for EJB >1.1 left out important DD info from the XML. For example, where is JNDI >name in ejb-jar.xml, where are pool size parameters in ejb-jar.xml, in >CMP where is the mapping from variable name to dbms-column in >ejb-jar.xml? > >Am I missing something here? Or is the definition of the XML file >seriously flawed? > >-- >tcp > >Thomas Preston >Vacation.com, Inc. >Engineering Department >617.210.4850 x 124 > >=========================================================================== >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". ---------------------------------------------------------------------------------- Jake Reichert email: [EMAIL PROTECTED] Technical Lead Phone: (415) 876-7500 Allpredict Fax: (240) 250-5593 =========================================================================== 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".
