- This topic has 5 replies, 3 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
After modification of our project code to accomodate some shortcomings with weblogic 8, I have been able to deploy our application using MyEclipse. I have found though, that the EAR’s application.xml file is not copied correctly to the deployment directory. Our EJB project is saved under EJB.jar project name the URI in the application dir references this. When it is deployed to app server, MyEclipse changes the URI to EJB. Is this intentional, is this a bug?
Eclipse V3.0 build 200310101454
MyElipse V3.6.4 build 200311041200
Windows XP
JDK1.4.1_02Actually, that’s the correct behavior for WebLogic. WLS doesn’t like the directories to be named with a .jar suffix so the deployer modifies them and then updates the application.xml file to compensate when using exploded deployment. However, it will not do this for packaged deployment; those archives are built exactly as specified.
Is everything working OK?
–Scott
MyEclipse SupportI have not experienced an issue with Weblogic not deploying EJBs as directories ending with the .Jar extension. I can modify the application.xml file that was created in the deployment by MyEclipse and rename the ejb component to ejb.jar and weblogic will boot and deploy the EJB.
The other issue with regards to your comment is that there is a discrepency that is not being addressed by the change in the EJB component name. I have named my EJB project as EJB.jar. The deployment copies the project to the deployment folder as EJB.jar. It then creates an application.xml which does not match the deployment structure. So there should be a change that either doesn’t allow you to create a project with the .JAR name, or it should deploy the project so that it will match the application.xml, or it should create the application.xml with the .JAR extension.
So there should be a change that either doesn’t allow you to create a project with the .JAR name, or it should deploy the project so that it will match the application.xml, or it should create the application.xml with the .JAR extension.
I believe that actually naming the project with a .jar extension is what is causing the problem. It’s simply an edge condition we hadn’t considered in the deployer design. I’ve entered a bug report so that we can address this oversight in a subsequent release. As a workaround, I’d suggest renaming the project, if that’s at all possible at this point. Thanks for reporting it.
–Scott
MyEclipse SupportScott,
There is the converse problem with WAR projects. The application.xml is generated with a “.war” extension even if the project doesn’t have that in the name. Weblogic, and most app servers as far as I know, allow you to deploy a web app as part of an EAR in exploded format without the .war extension.
