- This topic has 5 replies, 5 voices, and was last updated 18 years, 7 months ago by
.
-
Posts
-
It would be very nice if MyEclipse supported JCA connectors as enterprise application’s modules (rar).
Question: Is it possible to mark (and deploy) a project to be a module of J2EE application? I’ll check possibility of adding EJB project properties without validation builders.
But rar modules consist of descriptor in META-INF and several jar’s.
Is it possible to create structure similar to this:
App.ear
App.ear/META-INF/…
App.ear/AppWeb.war/…
App.ear/AppWeb.war/WEB-INF/…
App.ear/AppWeb.war/WEB-INF/classes/…
App.ear/AppWeb.war/WEB-INF/lib/…
App.ear/AppEJB.jar/…
App.ear/AppEJB.jar/META-INF/…
App.ear/AppJCA.rar/…
App.ear/AppJCA.rar/META-INF/…
App.ear/AppJCA.rar/AppJCA.jar/… (as compiled project code)
App.ear/AppJCA.rar/(additional jar’s for connector, just like AppWeb/WEB-INF/lib/…)Best wishes,
Piotr SmolinskiPiotr,
If I am understanding you correctly, this is typically done by creating a new Enterprise Application Project, and then adding all the EJB MOdule Projects and Web Module Projects to it as modules. When you deploy it, it will be packaged appropriately to run… I”m not sure how this is different than tha RAR requirement you gave above? Is using a EAP not working for you?Well, according to 17.2.0.3 of JCA 1.5 specification, JCA classes are NOT placed directly in *.rar file.
They are placed in a jar file (or files) in main directory of rar module.
If they were placed directly in rar, it would be ok using EJB module deployment without EJB validation.
The difference is that there is one more level of packaging, see App.ear/AppJCA.rar/AppJCA.jar/… (as compiled project code)Piotr,
Good suggestions. Right now we don’t support RAR projects but are considering the capability for a future release of MyEclipse.
