5 Replies Latest reply on Apr 17, 2003 5:05 PM by Juha Lindfors

    Porting to Jboss from Orion or Oracle 9ias

    zboss Newbie

      Does anyone have experience porting to Jboss from Orion or Oracle Application Server? it seems that the all of the xml tabs for ejb beans / ejb-jar.xml need to be completely rewritten?
      thanks

        • 1. Re: Porting to Jboss from Orion or Oracle 9ias
          Juha Lindfors Master

          why would you need to rewrite ejb-jar.xml? That should be a standard DTD for all J2EE app servers.

          • 2. Re: Porting to Jboss from Orion or Oracle 9ias
            zboss Newbie

            Here's just a small sample from a working Oracle9ias/Orion ejb-jar.xml file compared to JBOSS (info from 'jboss 3.0 deplyment & administration handbook' - they appear to be very different - hope I'm wrong:

            ORACLE 9IAS / ORION
            <entity-deployment name="Booking" copy-by-value="false" data-source="jdbc/OracleDS" exclusive-write-access="false" table="BOOKING">
            <primkey-mapping>
            <cmp-field-mapping>

            <cmp-field-mapping name="booking_id" persistence-name="BOOKING_ID" persistence-type="NUMBER(22)"/>

            </cmp-field-mapping>
            </primkey-mapping>
            <cmp-field-mapping name="booking_id" persistence-name="BOOKING_ID" persistence-type="NUMBER(22)"/>
            <cmp-field-mapping name="repeat_booking_id" persistence-name="REPEAT_BOOKING_ID" persistence-type="NUMBER(22)"/>
            <cmp-field-mapping name="room_id" persistence-name="ROOM_ID" persistence-type="NUMBER(22)"/>

            JBOSS
            orion version is <entity-deployment
            <pk-constraint-template> orion version is <primkey-mapping>etc etc
            <cmp-field><field-name>room_id</field-name></cmp-field> orion version is <cmp-field-mapping name="room_id"
            jboss - don't see any tags called persistence-name or persistence-type

            • 3. Re: Porting to Jboss from Orion or Oracle 9ias
              Juha Lindfors Master

              Yes, the application specific deployment descriptors are ... well, specific to their own servers. This is not ejb-jar.xml though. Ejb-jar.xml file is standard. The functionality it covers should be the same across all J2EE app servers. Obviously the features that are not part of J2EE (like the ones you've shown above) needs to be transformed to a working document instance. In JBoss's case it means jboss.xml and jbosscmp-jdbc.xml files.

              If you decide to do it via XSL, please donate ;-)

              • 4. Re: Porting to Jboss from Orion or Oracle 9ias
                zboss Newbie

                Porting this ejb-jar.xml file is a major major pain - the printout is over 9 pages.
                Do know of any easier way to do this other than xdoclet/ant etc etc, or manually?
                sorry about the multiple posts - it's a symptom of desperation...

                • 5. Re: Porting to Jboss from Orion or Oracle 9ias
                  Juha Lindfors Master

                  no, if its app server specific config then it really is app server specific