MANIFEST not deployed to Weblogic server

I have an EAR project in IDEA that deploys to a weblogic 9.0 server using
exploded deployment. (Run/Debug Configurations->Weblogic
Instance->Deployment) I also build this project into an exploded directory.
(Module Settings->J2EE Build Settings->Application Exploded Directory)

This EAR file contains an EJB Project. Now, the EJB project includes a bunch
of JAR file dependencies which are marked as being linked via manifest and
copied. In the exploded directory IDEA dutifully places these JAR files in
the root directory and generates a MANIFEST.MF which includes a classpath
entry for these JAR files. However, when I deploy the EAR file to Weblogic,
the MANIFEST.MF file is not copied into the META-INF directory of the EJB
directory of the deployment:

Exploded:

exploded
EcsReference
EcsCoreEjb
META-INF
ejb-jar.xml
MANIFEST.MF
weblogic-ejb-jar.xml
.
.
.

Deployment

autodeploy
EcsReference
EcsCoreEjb
META-INF
ejb-jar.xml
weblogic-ejb-jar.xml <- no manifest!!!
.
.
.

The missing classpath entries of course wreak havac when the application
tries to run. I've tried rebuilding and redeploying but it doesn't help.

-- Les Walker


2 comments

Is there some kind of white paper that describes how this is supposed to
work? I find it incredibly confusing. Why do I need a "deployment source"
for autodeploy. Why can't IDEA just autodeploy to the weblogic autodeploy
directory???

-- Les Walker

"Les Walker" <jlwa1ker@yahoo.com> wrote in message
news:dtiip1$cim$1@is.intellij.net...
>I have an EAR project in IDEA that deploys to a weblogic 9.0 server using
>exploded deployment. (Run/Debug Configurations->Weblogic
>Instance->Deployment) I also build this project into an exploded directory.
>(Module Settings->J2EE Build Settings->Application Exploded Directory)
>

This EAR file contains an EJB Project. Now, the EJB project includes a
bunch of JAR file dependencies which are marked as being linked via
manifest and copied. In the exploded directory IDEA dutifully places these
JAR files in the root directory and generates a MANIFEST.MF which includes
a classpath entry for these JAR files. However, when I deploy the EAR file
to Weblogic, the MANIFEST.MF file is not copied into the META-INF
directory of the EJB directory of the deployment:

>

Exploded:

>

exploded
EcsReference
EcsCoreEjb
META-INF
ejb-jar.xml
MANIFEST.MF
weblogic-ejb-jar.xml
.
.
.

>

Deployment

>

autodeploy
EcsReference
EcsCoreEjb
META-INF
ejb-jar.xml
weblogic-ejb-jar.xml <- no manifest!!!
.
.
.

>

The missing classpath entries of course wreak havac when the application
tries to run. I've tried rebuilding and redeploying but it doesn't help.

>

-- Les Walker

>



0

Hello Les,

I cannot reproduce this bug in IDEA. Perhaps it has been already fixed.

Is there some kind of white paper that describes how this is supposed
to work?


Try to see IDEA Help | Compiling/Running/Debugging in IDEA | Run/debug options
| WebLogic Server options.

I find it incredibly confusing. Why do I need a "deployment
source" for autodeploy. Why can't IDEA just autodeploy to the weblogic
autodeploy directory???


"Deployment source" specifies that should be copied in the weblogic autodeploy
directory: EAR or exploded directory.

---
Nikolay Chashnikov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.