WAR and EJB-JAR in Seperated Server

[steven]

Hi, group

In the sample of Sun's J2EE 1.3 tutorial, WAR and EJB-JAR are combined
into an EAR and deployed. For some reasons, however, I have to deploy
the EJBs part of a application into Sun's J2EE RI while deploy the
WARs part of the same application into another server such as TomCat.
Of course, the classes in WARs need to communicate with EJBs in J2EE
RI.

My questions are,

1, Is it possible to deployee only EJBs onto the J2EE RI? In this
case, what file form I need to creat, a EJB-JAR or a EAR in which an
EJB-JAR is hold?

2, Should I write a two seperated runtime descriptor, one of which in
the WAR, another of which in the EJB-JAR?

Thanks in advance.

 

[Dobromir Gaydarov]

Hi, group

In the sample of Sun's J2EE 1.3 tutorial, WAR and EJB-JAR are combined
into an EAR and deployed. For some reasons, however, I have to deploy
the EJBs part of a application into Sun's J2EE RI while deploy the
WARs part of the same application into another server such as TomCat.
Of course, the classes in WARs need to communicate with EJBs in J2EE
RI.

My questions are,

1, Is it possible to deployee only EJBs onto the J2EE RI? In this
case, what file form I need to creat, a EJB-JAR or a EAR in which an
EJB-JAR is hold?
EAR

2, Should I write a two seperated runtime descriptor, one of which in
the WAR, another of which in the EJB-JAR?

Deployment descriptor you mean?
You already have web.xml for the WAR file and ejb-jar.xml for the EJB,
and you will need 2 application.xml files, one for the EAR containing the
WAR, another for the EAR containing the EJB.

Most of the servers will allow you to deploy WAR or EJB without being inside
EAR, although I believe this is against the spec.
To compesate for the missing application.xml they will force you to add some
server specific deployment descriptor to the WAR or EJB.
Just for example if you deploy a WAR file by itself there is no standard way
to specify context root - it normally comes from the application.xml.

Regards,
Dobromir

 

[steven]

Thank you!

Deployment descriptor you mean?
You already have web.xml for the WAR file and ejb-jar.xml for the EJB,
and you will need 2 application.xml files, one for the EAR containing the
WAR, another for the EAR containing the EJB.

Most of the servers will allow you to deploy WAR or EJB without being inside
EAR, although I believe this is against the spec.
To compesate for the missing application.xml they will force you to add some
server specific deployment descriptor to the WAR or EJB.
Just for example if you deploy a WAR file by itself there is no standard way
to specify context root - it normally comes from the application.xml.

Regards,
Dobromir