Problem: Editing a deployment descriptor of an EJB or WAR inside of an EAR sends things to hell

Hello,
I've got an EAR with utility classes in lib/ (like log4j and some other
goodies).
Inside my EJBs, I have manifests that have class-path entries that reference
this and they all work upon initial load (I when they don't work because my
beans don't load).
When I edit my descriptors using the WebLogic console and persist my
changes, my EJBs crap out because they can no longer load log4j. When I
shutdown WebLogic and looked at the manifest inside the EJB inside of the
EAR, sure enough, the class-path entry that kept the whole thing working was
gone. WebLogic decided to instead detail a bunch of classes.
Any workaround for this (other than to include all classes in all EJBs)?
This prevents customers and deployers from doing their jobs. :(
How do I report this to BEA? I poked around the website and could nary find
a "report bug" link.
thanks,
greg

Yes - getting to support should be easier ...
www.bea.com -> Services -> Customer Support Services -> Learn More about WebSupport
-> Register for Web Account
Then you can follow the WebSupport link at the bottom of any page.
Mike
"Gregory Gerard" <[email protected]> wrote:
Hello,
I've got an EAR with utility classes in lib/ (like log4j and some other
goodies).
Inside my EJBs, I have manifests that have class-path entries that reference
this and they all work upon initial load (I when they don't work because
my
beans don't load).
When I edit my descriptors using the WebLogic console and persist my
changes, my EJBs crap out because they can no longer load log4j. When
I
shutdown WebLogic and looked at the manifest inside the EJB inside of
the
EAR, sure enough, the class-path entry that kept the whole thing working
was
gone. WebLogic decided to instead detail a bunch of classes.
Any workaround for this (other than to include all classes in all EJBs)?
This prevents customers and deployers from doing their jobs. :(
How do I report this to BEA? I poked around the website and could nary
find
a "report bug" link.
thanks,
greg

Similar Messages

Problems in configuring deployment descriptors to use EJB in JSP

          Hello,
          I've been trying to use an EJB in a JSP on Weblogic 8.1. The relevent part of
          my web.xml and weblogic.xml look like this:
          =====================================
          web.xml -
          <ejb-ref>
          <description>Purchase order bean deployed</description>
          <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>mypackage2.PurchaseorderHome</home>
          <remote>mypackage2.Purchaseorder</remote>
          <ejb-link>/PO.jar#Purchaseorder</ejb-link>
          </ejb-ref>
          <ejb-local-ref>
          <description>purchase order</description>
          <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <local-home>mypackage2.PurchaseorderLocalHome</local-home>
          <local>mypackage2.PurchaseorderLocal</local>
          <ejb-link>/PO.jar#Purchaseorder</ejb-link>
          </ejb-local-ref>
          =====================================
          weblogic.xml -
          <ejb-reference-description>
          <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
          <jndi-name>Purchaseorder</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          =================================
          My ejb-jar.xml file looks like this (this EJB jar is already deployed on Weblogic):
          <description>Entity Bean ( CMP )</description>
          <display-name>Purchaseorder</display-name>
          <ejb-name>Purchaseorder</ejb-name>
          <home>mypackage2.PurchaseorderHome</home>
          <remote>mypackage2.Purchaseorder</remote>
          <local-home>mypackage2.PurchaseorderLocalHome</local-home>
          <local>mypackage2.PurchaseorderLocal</local>
          <ejb-class>mypackage2.PurchaseorderBean</ejb-class>
          ==============================================
          Finally, my weblogic-ejb-jar.xml looks like this:
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>Purchaseorder</ejb-name>
          <jndi-name>Purchaseorder</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ===============================================
          But despite many many efforts, I keep getting the following error:
          Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException:
          [J2EE:160101]Error: The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref
          or ejb-local-ref 'ejb/Purchaseorder' in the application module 'public_html' could
          not be resolved. The target EJB for the ejb-ref could not be found. Please ensure
          the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error:
          The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref or ejb-local-ref
          'ejb/Purchaseorder' in the application module 'public_html' could not be resolved.
          The target EJB for the ejb-ref could not be found. Please ensure the link is correct.
          at
          I have changed around a lot of things. I've a classes directory under web-inf
          where I have mypackage2\all-the-class-files. I've also made available PO.jar file
          (which contains Purchaseorder) at various levels to ensure that the class can
          be found. I've changed the "/PO.jar#Purchaseorder" value of <ejb-link> tag accordingly
          to try various things. (e.g ejb/Purchaseorder, mypackage2.Purchaseorder, and a
          lot of other things) but of no avail. I keep getting the same error over and over
          again. (Do you think banging my head on the wall would do the trick?)
          Any help would be greatly appreciated. Thanks.


          Sam, thanks for the explanation. It makes sense now that why it's not working.
          But is this specific to Weblogic? I'm actually using JDevloper to develop my
          EJB (CMP) and JSP. Within JSP, I can use the tag library ejbtag provided by Oracle
          to specify home, create instance, and get collection back from an EJB. I've specify
          the tag lib URI in the web.xml but I kept getting the error message in Weblogi
          when running the test to load JSP saying that it could not find the EJB (Purchaseorder)
          specified. That led me to do some research and I came accross the <ejb-ref> and
          <ejb-link> tags.
          If it is a restriction only posed by Weblogic then I guess I'll have to create
          a JavaBean to interact with EJB first and then get the collection.
          Thanks.
          Sam Pullara <[email protected]> wrote:
          >You can only use ejb-links when connecting to EJBs that are in the same
          >
          >application (ear). If you want to have them separate you will have to
          >
          >use a global JNDI name for the EJB and look up that.
          >
          >Sam
          >
          >A Roman wrote:
          >> Michael,
          >>
          >> I'm not deploying EJB as an .ear application that'd include web app
          >and .jar.
          >> Instead I have deployed .jar as stand alone EJB and want to deploy
          >.war (exploded
          >> directory structure) as a seperate web app. Both .jar and .war will
          >be deployed
          >> on the same server. That's exactly why I cannot use the syntax that's
          >used in
          >> the samples.
          >>
          >> Thanks.
          >>
          >> "Michael Kovacs" <[email protected]> wrote:
          >>
          >>>I guess to start off with I'm making the assumption that your PO.jar
          >>>is your
          >>>EJB module
          >>>and that it is contained in the same EAR as your webapp module, looking
          >>>something like
          >>>this:
          >>>
          >>>myEAR.ear
          >>> |_ PO.jar
          >>> |_ webapp
          >>> |_ jspCallingEJB.jsp
          >>>
          >>>If this is correct, the first thing I'd suggest trying is to remove
          >your
          >>>"/"
          >>
          >>>from the front of your <ejb-link> and
          >>
          >>>just make the value <ejb-link>PO.jar#Purchaseorder</ejb-link>
          >>>
          >>>The EJB example that ships with 8.1 platform makes use of an EJB from
          >>>a jsp
          >>>page so you could
          >>>look to that example for some guidance, which references the EJB in
          >this
          >>>same way in the web.xml ejb-local-ref element.
          >>>hope that helps.
          >>>--
          >>>Michael Kovacs
          >>>Senior Software Engineer
          >>>BEA Systems
          >>>"ARoman" <[email protected]> wrote in message
          >>>news:[email protected]...
          >>>
          >>>>Hello,
          >>>>
          >>>>I've been trying to use an EJB in a JSP on Weblogic 8.1. The relevent
          >>>
          >>>part
          >>>of
          >>>
          >>>>my web.xml and weblogic.xml look like this:
          >>>>=====================================
          >>>>web.xml -
          >>>>
          >>>> <ejb-ref>
          >>>> <description>Purchase order bean deployed</description>
          >>>> <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
          >>>> <ejb-ref-type>Entity</ejb-ref-type>
          >>>> <home>mypackage2.PurchaseorderHome</home>
          >>>> <remote>mypackage2.Purchaseorder</remote>
          >>>> <ejb-link>/PO.jar#Purchaseorder</ejb-link>
          >>>>
          >>>> </ejb-ref>
          >>>>
          >>>> <ejb-local-ref>
          >>>> <description>purchase order</description>
          >>>> <ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
          >>>> <ejb-ref-type>Entity</ejb-ref-type>
          >>>> <local-home>mypackage2.PurchaseorderLocalHome</local-home>
          >>>> <local>mypackage2.PurchaseorderLocal</local>
          >>>> <ejb-link>/PO.jar#Purchaseorder</ejb-link>
          >>>> </ejb-local-ref>
          >>>>=====================================
          >>>>
          >>>>weblogic.xml -
          >>>><ejb-reference-description>
          >>>><ejb-ref-name>ejb/Purchaseorder</ejb-ref-name>
          >>>><jndi-name>Purchaseorder</jndi-name>
          >>>></ejb-reference-description>
          >>>></reference-descriptor>
          >>>>=================================
          >>>>My ejb-jar.xml file looks like this (this EJB jar is already deployed
          >>>
          >>>on
          >>>Weblogic):
          >>>
          >>>>
          >>>> <description>Entity Bean ( CMP )</description>
          >>>> <display-name>Purchaseorder</display-name>
          >>>> <ejb-name>Purchaseorder</ejb-name>
          >>>> <home>mypackage2.PurchaseorderHome</home>
          >>>> <remote>mypackage2.Purchaseorder</remote>
          >>>> <local-home>mypackage2.PurchaseorderLocalHome</local-home>
          >>>> <local>mypackage2.PurchaseorderLocal</local>
          >>>> <ejb-class>mypackage2.PurchaseorderBean</ejb-class>
          >>>> ==============================================
          >>>>Finally, my weblogic-ejb-jar.xml looks like this:
          >>>>
          >>>><weblogic-ejb-jar>
          >>>> <weblogic-enterprise-bean>
          >>>> <ejb-name>Purchaseorder</ejb-name>
          >>>> <jndi-name>Purchaseorder</jndi-name>
          >>>> </weblogic-enterprise-bean>
          >>>></weblogic-ejb-jar>
          >>>>===============================================
          >>>>
          >>>>But despite many many efforts, I keep getting the following error:
          >>>>
          >>>>Could not setup environment - with nested exception:
          >>>
          >>>[weblogic.deployment.EnvironmentException:
          >>>
          >>>>[J2EE:160101]Error: The ejb-link '/PO.jar#Purchaseorder' declared
          >in
          >>>
          >>>the
          >>>ejb-ref
          >>>
          >>>>or ejb-local-ref 'ejb/Purchaseorder' in the application module
          >>>
          >>>'public_html' could
          >>>
          >>>>not be resolved. The target EJB for the ejb-ref could not be found.
          >>>
          >>>Please
          >>>ensure
          >>>
          >>>>the link is correct.] weblogic.deployment.EnvironmentException:
          >>>
          >>>[J2EE:160101]Error:
          >>>
          >>>>The ejb-link '/PO.jar#Purchaseorder' declared in the ejb-ref or
          >>>
          >>>ejb-local-ref
          >>>
          >>>>'ejb/Purchaseorder' in the application module 'public_html' could
          >not
          >>>
          >>>be
          >>>resolved.
          >>>
          >>>>The target EJB for the ejb-ref could not be found. Please ensure the
          >>>
          >>>link
          >>>is correct.
          >>>
          >>>>at
          >>>>
          >>>>I have changed around a lot of things. I've a classes directory under
          >>>
          >>>web-inf
          >>>
          >>>>where I have mypackage2\all-the-class-files. I've also made available
          >>>
          >>>PO.jar file
          >>>
          >>>>(which contains Purchaseorder) at various levels to ensure that the
          >>>
          >>>class
          >>>can
          >>>
          >>>>be found. I've changed the "/PO.jar#Purchaseorder" value of <ejb-link>
          >>>
          >>>tag
          >>>accordingly
          >>>
          >>>>to try various things. (e.g ejb/Purchaseorder, mypackage2.Purchaseorder,
          >>>
          >>>and a
          >>>
          >>>>lot of other things) but of no avail. I keep getting the same error
          >>>
          >>>over
          >>>and over
          >>>
          >>>>again. (Do you think banging my head on the wall would do the trick?)
          >>>>
          >>>>Any help would be greatly appreciated. Thanks.
          >>>>
          >>>
          >>>
          >>
          >
          >

Problem with Missing deployment descriptor [J2EE:160043]

Hi,
I am having a problem deploying an *.ear into weblogic 8.1. I get the error
J2EE:160043]Missing deployment descriptor "META-INF/application.xml" at "C:\bea\weblogic81\samples\domains\examples\applications\ejb20_dataLoadMgr.ear"
even though the application.xml file is in the *.ear file. This *.ear file is
built using the following
ant script:
Note: I am integrating a Message Driven EJB with Documentum Content Server
DFC API calls (3rd party jars)
Thanks, Craig
<project name="ejb20-message" default="all" basedir=".">
     
     <property environment="env"/>
     <property file="../../../examples.properties"/>
     <property name="build.compiler" value="${compiler}"/>
     <property name="source" value="."/>
     <property name="build" value="${source}/build"/>
     <property name="dist" value="${source}/dist"/>
     <property name="dummy" value="${source}/dummy"/>
     
     <target name="all" depends="clean, init, compile_ejb, jar.ejb, appc, ear_app3"/>
     
     <target name="init">
          
          <tstamp/>
          
          <mkdir dir="${build}"/>
          <mkdir dir="${build}/META-INF"/>
          <mkdir dir="${dist}"/>
          <copy todir="${build}/META-INF">
               <fileset dir="${source}">
                    <include name="*.xml"/>
                    <exclude name="build.xml"/>
                    <exclude name="application.xml"/>
               </fileset>
          </copy>
          
          <copy todir="${dist}/META-INF">
               <fileset dir="${source}">
                    <include name="application.xml"/>
               </fileset>
          </copy>
          
     </target>
     
     <target name="compile_ejb">
          <javac srcdir="${source}" destdir="${build}" includes="DataLoadMgrBean.java"
excludes="DSSCommand.java,GetDSSCommand.java,ImportXMLHelper.java" classpath="dfc.jar"/>
     </target>
     
     <target name="jar.ejb" depends="compile_ejb">
          <jar jarfile="${dist}/ejb20_dataLoadMgr.jar" basedir="${build}" update="yes">
</jar>
     </target>
     <target name="appc" depends="jar.ejb">
          <wlappc debug="${debug}" source="${dist}/ejb20_dataLoadMgr.jar" classpath="dfc.jar"
verbose="true"/>
     </target>
     
     <target name="ear_app" depends="jar.ejb">
          <ear earfile="${apps.dir}/ejb20_dataLoadMgr.ear" appxml="${source}/application.xml">
               
               <fileset dir="${dist}" includes="ejb20_dataLoadMgr.jar"/>
          </ear>
     </target>
     
     <target name="ear_app3" depends="jar.ejb">
          <jar destfile="${apps.dir}/ejb20_dataLoadMgr.ear" basedir="${dist}"/>
     </target>
     <target name="ear_app2" depends="jar.ejb">
          <wlpackage toFile="${apps.dir}/ejb20_dataLoadMgr.ear" srcdir="${dist}" destdir="${dummy}"/>
     </target>
     
     <target name="compile_client">
          <javac srcdir="${source}" destdir="${client.classes.dir}" includes="Client.java"/>
     </target>
     <target name="clean">
          <delete dir="${build}"/>
     </target>
     
     <target name="run">
          <java classname="examples.ejb20.dataLoadMgr.Client" fork="yes" failonerror="true">
               <arg value="t3://localhost:${port}"/>
               <classpath>
                    <pathelement path="${ex.classpath}"/>
               </classpath>
          </java>
     </target>
</project>

Can you show me the output of jar tvf
C:\bea\weblogic81\samples\domains\examples\applications\ejb20_dataLoadMgr.ear
-- Rob
Craig Ahtye wrote:
Hi,
I am having a problem deploying an *.ear into weblogic 8.1. I get the error
J2EE:160043]Missing deployment descriptor "META-INF/application.xml" at "C:\bea\weblogic81\samples\domains\examples\applications\ejb20_dataLoadMgr.ear"
even though the application.xml file is in the *.ear file. This *.ear file is
built using the following
ant script:
Note: I am integrating a Message Driven EJB with Documentum Content Server
DFC API calls (3rd party jars)
Thanks, Craig
<project name="ejb20-message" default="all" basedir=".">
     
     <property environment="env"/>
     <property file="../../../examples.properties"/>
     <property name="build.compiler" value="${compiler}"/>
     <property name="source" value="."/>
     <property name="build" value="${source}/build"/>
     <property name="dist" value="${source}/dist"/>
     <property name="dummy" value="${source}/dummy"/>
     
     <target name="all" depends="clean, init, compile_ejb, jar.ejb, appc, ear_app3"/>
     
     <target name="init">
          
          <tstamp/>
          
          <mkdir dir="${build}"/>
          <mkdir dir="${build}/META-INF"/>
          <mkdir dir="${dist}"/>
          <copy todir="${build}/META-INF">
               <fileset dir="${source}">
                    <include name="*.xml"/>
                    <exclude name="build.xml"/>
                    <exclude name="application.xml"/>
               </fileset>
          </copy>
          
          <copy todir="${dist}/META-INF">
               <fileset dir="${source}">
                    <include name="application.xml"/>
               </fileset>
          </copy>
          
     </target>
     
     <target name="compile_ejb">
          <javac srcdir="${source}" destdir="${build}" includes="DataLoadMgrBean.java"
excludes="DSSCommand.java,GetDSSCommand.java,ImportXMLHelper.java" classpath="dfc.jar"/>
     </target>
     
     <target name="jar.ejb" depends="compile_ejb">
          <jar jarfile="${dist}/ejb20_dataLoadMgr.jar" basedir="${build}" update="yes">
</jar>
     </target>
     <target name="appc" depends="jar.ejb">
          <wlappc debug="${debug}" source="${dist}/ejb20_dataLoadMgr.jar" classpath="dfc.jar"
verbose="true"/>
     </target>
     
     <target name="ear_app" depends="jar.ejb">
          <ear earfile="${apps.dir}/ejb20_dataLoadMgr.ear" appxml="${source}/application.xml">
               
               <fileset dir="${dist}" includes="ejb20_dataLoadMgr.jar"/>
          </ear>
     </target>
     
     <target name="ear_app3" depends="jar.ejb">
          <jar destfile="${apps.dir}/ejb20_dataLoadMgr.ear" basedir="${dist}"/>
     </target>
     <target name="ear_app2" depends="jar.ejb">
          <wlpackage toFile="${apps.dir}/ejb20_dataLoadMgr.ear" srcdir="${dist}" destdir="${dummy}"/>
     </target>
     
     <target name="compile_client">
          <javac srcdir="${source}" destdir="${client.classes.dir}" includes="Client.java"/>
     </target>
     <target name="clean">
          <delete dir="${build}"/>
     </target>
     
     <target name="run">
          <java classname="examples.ejb20.dataLoadMgr.Client" fork="yes" failonerror="true">
               <arg value="t3://localhost:${port}"/>
               <classpath>
                    <pathelement path="${ex.classpath}"/>
               </classpath>
          </java>
     </target>
</project>

Weblogic Deployment Descriptor for CMP EJB

Hi all,
Am new to EJB, CMP. Pls help me how to write deployment descriptors for the CMP EJB for Weblogic.
Give me the list of the Deployment descriptors needed and also pls give me some samples
thanks in advance
rgds
Ravi Bharathi

The easiest way is to go through some tutorial or refer the code samples. If you have installed weblogic, there are examples provided in the weblogic installation folder itself for each type of bean. Basically for cmp you have to provide the table names and mapping between the class variables to db fields in weblogic_cmp_rdbms.xml deployment descriptor.

How To Define Security in the deployment descriptor for an ejb

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Problem with weblogic deployment descriptor tool (DDInit)

Hi,
I'm just playing with weblogic ... following their tutorual but I can't seem to run their deployment descriptor tool:
java weblogic.ant.taskdefs.war.DDinit <folderName> gives me a NoClassDefFoundError.
I have weblogic6.0sp1 installed with an evaluation license which has not yet expired. I have d:\bea\wlserver6.0sp1\lib in mt classpath so weblogic.jar is n there.
When I check out the contents of the weblogic.jar file .. I can't seem to find this tool.
Can anyone give me a clue as to what I am doing wrong?

Here's a link describing the process. If this is what you are doing then your problem may be that 6.0 doesn't support this.
http://edocs.bea.com/wls/docs61/programming/packaging.html#pack004

Common JAR file between EJB and WAR inside an EAR

Hi,
I'm trying to deploy an EAR application outside the development environment and I have the following problem.
My EAR has the following structure :
application.ear
|-- ejbs.jar
|-- web.war
Inside the WAR, in /WEB-INF/lib/, I have a set of JAR files that are used by the Web app and also, of course, by the EJB.
During the deployment step, EJB module cannot be deployed because it miss some classes into the classpath.
I think it is a common problem in J2EE development, so does someone has a solution for this problem ?
Please note I'm using Macromedia JRun 4 SP1 on Windows XP.
Regards,
Damien.

Ok,
I have found a solution that seems elegant to me. I'm going to try and explain...
My appli.jar EJB module and my appli.war Web module are using both two JAR, let's say common.jar and util.jar.
The way to share those JAR between the two modules is to have the following structure for the EAR :
appli.ear
|-- appli.jar
|-- appli.war
|-- common.jar
|-- util.jar
|-- META-INF
|-- application.xml
|-- manifest.mfIn this structure :
* the common.jar and the util.jar are not part of the WAR (/web-inf/lib)
* the manifest.mf file has the following content :
Manifest-Version: 1.0
Created-By: My Application
Class-Path: common.jar util.jarPlease note that space is used as separator for the classpath entry to allow independancy from OS.
And you know what ? It works ! Well, on Macromedia JRun 4.0 SP1 and on Windows XP but I hope it works on other platforms.
I hope it will help a lot of people because I spent a lot of time before to find a solution !
Regards,
Damien.

Unable to Edit Deployment Descriptor

Hi,
I am currently using weblogic 6.1 sp4 and am having some problem while trying
to edit the deployment descriptors through the weblogic console.
I get the following error message:
There was an error while loading the descriptor for component:
UserRegistrationMDB
Please fix the error in the component descriptor file(s), redeploy the component
and then press continue to attempt to edit this components descriptor.
The following error(s) occurred:
String index out of range: -1
I dont get this error with weblogic 6.1 sp3.
Please let me know what the reason might be.
Thanks,
JS.

I have attached the ejb jar xml and the weblogic ejb jar xml
Thanks!
- JS
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>UserRegistrationBean</ejb-name>
<ejb-class>UserRegistrationTopicListenerBean</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>dups-ok-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>UserRegistrationBean</ejb-name>
<method-intf>Remote</method-intf>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd" >
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>UserRegistrationBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>200</max-beans-in-free-pool>
<initial-beans-in-free-pool>20</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>dss.UserRegistrationTopic</destination-jndi-name>
     <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
     <provider-url>t3://localhost:7000</provider-url>
     <connection-factory-jndi-name>iag.jms.billing.TopicConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
"SP" <[email protected]> wrote:
It seems that the deployment descriptor has a value less than 3 chars
or
more than the maximum chars.
If I can see the deployment descriptor, then I may tell exactly what
the
reason is
SP
"JS" <[email protected]> wrote in message
news:[email protected]...
Hi,
I am currently using weblogic 6.1 sp4 and am having some problem whiletrying
to edit the deployment descriptors through the weblogic console.
I get the following error message:
There was an error while loading the descriptor for component:
UserRegistrationMDB
Please fix the error in the component descriptor file(s), redeploythe
component
and then press continue to attempt to edit this components descriptor.
The following error(s) occurred:
String index out of range: -1
I dont get this error with weblogic 6.1 sp3.
Please let me know what the reason might be.
Thanks,
JS.

How to edit deployment descriptor in weblogic 9.0?

Hi ,
I need to edit the values of certain environment variables mentioned in the deployment descriptor of a ejb module.
In weblogic 7,its a straight forward method in which we have the option to edit the deployment descriptor in weblogic console.
But I'm not sure how the same can be done in weblogic 9.0.
Please guide me..!!! its urgent...
Thanks,
Smita

If you want to edit the actual deployment descriptor (ie as a developer) than using any text editor or using an IDE like WebLogic Workshop/Eclipse etc would be the way to go.
If you're trying to change values in an already deployed application, then configuration and tunables can be changed in the admin console. These write the changes to a separate file called a deployment plan. It allows you to change performance and environment settings without disturbing the original EAR file.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Deployment descriptor "weblogic.xml" is malformed. in managed server

Hi All,
          Appreciate if anyone can help.
          I have set up a cluster containing two nodes - one local and other
          remote machine on weblogic 8.1.4
          then i install my application this cluster setup its working fine.
          for my requirement i upgrade the the weblogic version from 8.1.4 to
          8.1.6 .
          i upgrade through the smart update from the bea site . i upgraded both
          the node.
          i started the admin server.it started with no issue.
          my problem comes when i start the my managed server on the cluster .it
          gives me this exception.
          <HTTP> <BEA-101296> <Unable to load the default compiler class
          "com.sun.tools.javac.Main". Using the default javac compiler to compile
          JSPs.>
          i checked the classpath it has the same jdk that i used for 8.1.4
          (jdk1.4.05 from sun.)
          should i used new jdk that comes with the upgrade package of 8.1.6 like
          (jdk1.4.11)
          my class path having the weblogic jar also.
          this is my class path.:
          E:\bea\weblogic81\server\lib\weblogic.jar and other my application
          jars.
          complete exception it is shown like :
          <Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
          <Application:
          'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
          Module: 'Nexaweb': Public ID references the old version of the Servlet
          DTD. You must change the public ID in web.xml file to "-//Sun
          Microsystems, Inc.//DTD Web Application 2.3//EN".>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
          <[Application:
          'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?br>Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
          Check against the DTD: org.xml.sax.SAXParseException: The content of
          element type "weblogic-web-app" must match
          "(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?t*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?ontainer-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?ap?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
          (line 26, column 20).>
          Compiler class: 'com.sun.tools.javac.Main', not found
          java.lang.ClassNotFoundException: com.sun.tools.javac.Main
          at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
          at java.security.AccessController.doPrivileged(Native Method)
          at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
          at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
          at java.lang.Class.forName0(Native Method)
          at java.lang.Class.forName(Class.java:141)
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?6)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
          <Call-by-reference is not enabled for the EJB 'JMSBean'. The server
          will have better performance if it is enabled. To enable
          call-by-reference, set the enable-call-by-reference element to True in
          the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
          <Failed to initialize the application Xellerate due to error
          weblogic.management.ApplicationException: prepare failed for
          xlBackOfficeBeans.jar
          Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
          EJBModule(xlBackOfficeBeans.jar,status=NEW)
          Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
          Compiler class: 'com.sun.tools.javac.Main', not found
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
          found
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          weblogic.management.ApplicationException: prepare failed for
          xlBackOfficeBeans.jar
          Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
          EJBModule(xlBackOfficeBeans.jar,status=NEW)
          Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
          Compiler class: 'com.sun.tools.javac.Main', not found
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
          found
          at
          weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?1)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
          at
          weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
          at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
          at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
          at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
          at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
          at
          weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?>
          at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
          at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?va:3212)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1628)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          at
          weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?r.java:1658)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ava:1584)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?3)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?6)
          at
          weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?)
          at
          weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?.java:3058)
          at
          weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?yer.java:985)
          at
          weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?r>
          at
          weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?tManagerServerLifeCycleImpl.java:229)
          at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
          at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
          at weblogic.Server.main(Server.java:32)
          ><Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
          <BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
          to initialize due to failed deployments.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
          <The deployment framework was unable to resume accepting requests.>
          <Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
          <BEA-000342> <Unable to initialize the server: [Deployer:149601]The
          deployment framework was unable to resume accepting
          requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
          is unable to initialize due to failed deployments.>
          hope the scope of the questions is not too broad. Kindly let me know
          if you need more information.
          Thanks a lot.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

Deployment descriptor "weblogic.xml" is malformed.

Hi All,
Appreciate if anyone can help.
I have set up a cluster containing two nodes - one local and other
remote machine on weblogic 8.1.4
then i install my application this cluster setup its working fine.
for my requirement i upgrade the the weblogic version from 8.1.4 to
8.1.6 .
i upgrade through the smart update from the bea site . i upgraded both
the node.
i started the admin server.it started with no issue.
my problem comes when i start the my managed server on the cluster .it
gives me this exception.
<HTTP> <BEA-101296> <Unable to load the default compiler class
"com.sun.tools.javac.Main". Using the default javac compiler to compile
JSPs.>
i checked the classpath it has the same jdk that i used for 8.1.4
(jdk1.4.05 from sun.)
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
complete exception it is shown like :
<Dec 19, 2006 12:44:58 PM GMT+05:30> <Warning> <HTTP> <BEA-101247>
<Application:
'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLNexaweb.ear',
Module: 'Nexaweb': Public ID references the old version of the Servlet
DTD. You must change the public ID in web.xml file to "-//Sun
Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <HTTP> <BEA-101248>
<[Application:
'E:\bea\user_projects\domains\wlupgdomain\XLApplications\WLXellerateFull.ea?r',
Module: 'xlWebApp']: Deployment descriptor "weblogic.xml" is malformed.
Check against the DTD: org.xml.sax.SAXParseException: The content of
element type "weblogic-web-app" must match
"(description?,weblogic-version?,security-role-assignment*,run-as-role-assi?gnment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filt?er?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-ma?tch-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-r?oot?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
(line 26, column 20).>
Compiler class: 'com.sun.tools.javac.Main', not found
java.lang.ClassNotFoundException: com.sun.tools.javac.Main
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:406)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Warning> <EJB> <BEA-010202>
<Call-by-reference is not enabled for the EJB 'JMSBean'. The server
will have better performance if it is enabled. To enable
call-by-reference, set the enable-call-by-reference element to True in
the weblogic-ejb-jar.xml deployment descriptor for this EJB.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149205>
<Failed to initialize the application Xellerate due to error
weblogic.management.ApplicationException: prepare failed for
xlBackOfficeBeans.jar
Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
EJBModule(xlBackOfficeBeans.jar,status=NEW)
Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
Compiler class: 'com.sun.tools.javac.Main', not found
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
found
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
weblogic.management.ApplicationException: prepare failed for
xlBackOfficeBeans.jar
Module Name: xlBackOfficeBeans.jar, Error: Exception preparing module:
EJBModule(xlBackOfficeBeans.jar,status=NEW)
Unable to deploy EJB: xlBackOfficeBeans.jar from xlBackOfficeBeans.jar:
Compiler class: 'com.sun.tools.javac.Main', not found
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:274)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
java.io.IOException: Compiler class: 'com.sun.tools.javac.Main', not
found
at
weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.ja?va:411)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
at
weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:270)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:498)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:793)
at
weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:708?)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1431)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:496)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContain?er.java:3212)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1628)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
at
weblogic.j2ee.J2EEApplicationContainer.tryPrepareModules(J2EEApplicationCon?tainer.java:1658)
at
weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContai?ner.java:1584)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1243)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:1076)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.jav?a:829)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDep?loyer.java:3058)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(Slave?Deployer.java:985)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:34?2)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Depl?oymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <Deployer>
<BEA-149229> <Server xlManagedServer_1 in cluster xlCluster is unable
to initialize due to failed deployments.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Error> <Deployer> <BEA-149601>
<The deployment framework was unable to resume accepting requests.>
<Dec 19, 2006 12:45:00 PM GMT+05:30> <Emergency> <WebLogicServer>
<BEA-000342> <Unable to initialize the server: [Deployer:149601]The
deployment framework was unable to resume accepting
requests.[Deployer:149229]Server xlManagedServer_1 in cluster xlCluster
is unable to initialize due to failed deployments.>
hope the scope of the questions is not too broad. Kindly let me know
if you need more information.
Thanks a lot.

ram ram <> wrote:
should i used new jdk that comes with the upgrade package of 8.1.6 like
(jdk1.4.11)
my class path having the weblogic jar also.
this is my class path.:
E:\bea\weblogic81\server\lib\weblogic.jar and other my application
jars.
Add tools.jar from your Java installation to the classpath.
Bart
Schelstraete Bart
http://www.schelstraete.org
http://www.mqseries.be

Deployment descriptor configuration tool

Hi,
My company delivers a weblogic server based product.
We have the following problem: when we deliver a new version of the product
(basically, a new .ear), we overwrite the previous deployment descriptor of
each EJB, Connector, etc... This means that if our customers need to
remember their previous settings (particularly concerning caches and pools).
Is there a way to merge those descriptors (I really don't see how a program
could decide what's old, new, modified, and so on...) or at least automate
the configuration?
The only solution I see for now is having descriptor templates and creating
an ant script (would work on windows and unix) that would basically do the
following:
. extract the descriptors templates (unear, unjar, unwar, unrar)
. configure the new descriptors using an existing (previous version)
properties file
. replace the descriptors (jar, war, rar, ear)
I realize that this could be a pain to do and maintain, so I wonder if there
is not already a tool for that...
Thank you,
Patrick.
PS: we are still on WLS 6.1 for now...

Patrick:
There is a feature in 8.1 called alt-dd that allows you to specify an
alternate DD to the DD's in the EAR and modules. This would allow you to
replace externally without have to over-write.
Additionaly in our next release, code named Diablo (named for a State Park),
we are working on feature in conjunction with JSR88 of J2EE 14 whereby
Descriptor values that are bindables and tunables can be over-ridden by a
Deployment Plan that sits external to the ear.
Cheers
mbg
"Patrick Martin" <[email protected]> wrote in message
news:[email protected]..
Hi,
My company delivers a weblogic server based product.
We have the following problem: when we deliver a new version of theproduct
(basically, a new .ear), we overwrite the previous deployment descriptorof
each EJB, Connector, etc... This means that if our customers need to
remember their previous settings (particularly concerning caches andpools).
>
Is there a way to merge those descriptors (I really don't see how aprogram
could decide what's old, new, modified, and so on...) or at least automate
the configuration?
The only solution I see for now is having descriptor templates andcreating
an ant script (would work on windows and unix) that would basically do the
following:
. extract the descriptors templates (unear, unjar, unwar, unrar)
. configure the new descriptors using an existing (previous version)
properties file
. replace the descriptors (jar, war, rar, ear)
I realize that this could be a pain to do and maintain, so I wonder ifthere
is not already a tool for that...
Thank you,
Patrick.
PS: we are still on WLS 6.1 for now...

Failed to save deployment descriptor - cause: com.sun.enterprise.deploymen

I have a CMP EJB that will not deploy. I've been able to compile, run the capture-schema, complete the EJBC, but then I get a failure with the message below. I have used the ASMT to migrate from Weblogic 6.1 to Sun One 7. Any help would be userful.
ERROR:
Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: Tracker-EJB cause: com.sun.enterprise.deployment.EjbExternalDescriptor
The exception in the admin log file really doesn't help me.
Thanks in advance.

Please check the xml files by running verifier. It seems like there is some problem with the sun-ejb-jar file. Check the packaging of the EJB. Set the log level to fine or above and give the log to know more details about the error.

Deployment Descriptor defaults for clustering

          If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
          Darko Bohinc
          Synergy International Limited
          www.synergy.co.nz


          Darko,
          All EJB "homes" are clusterable by default (a request for a home interface can be routed to any server in the cluster).
          In the case of stateless session beans, you also achieve load-balancing by default (method calls can be sent to any server in the cluster). Failover is achieved by default only BETWEEN method calls and not DURING method calls. In other words, the stub will retry a method call on another server in the cluster only if the stub is absolutely sure that the method call did not reach the server in the cluster during the first try. If the stub cannot determine this, it will not retry by default and you should eventually get an error. If you would like the server to retry all method calls even if the server failed in the middle of a call, then you need to write your EJB methods to be idempotent (calling any method in the EJB many times with the same parameters should achieve the same result with no side effects such as duplicate inserts in the database etc). You will then have to explicitly set the "stateless-bean-methods-are-idempotent" element in the deployment descriptor for the EJB to let WL know that all methods can be retried without any worries.
          Please see the following link for additional information:
          http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#1046391
          Hope this answers your questions.
          Giri
          "Darko Bohinc" <[email protected]> wrote:
          >
          >If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
          >
          >Darko Bohinc
          >Synergy International Limited
          >www.synergy.co.nz

Deployment descriptor error for an EJB 3.0 entity bean module

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Hi all,
i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
The application is composed as follows:
WASEnterprise.ear
|-META-INF
|-application.xml
|-WAS.jar
|-META-INF
|-persistence.xml
In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
<Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
The persistence.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<persistence>
<persistence-unit name="CNT4">
<non-jta-data-source>cnt5ds</non-jta-data-source>
<class>it.eni.italgas.was.db.entity.AsiDisco</class>
<class>it.eni.italgas.was.db.entity.AsiErrori</class>
<class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
<class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
<class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
</persistence-unit>
</persistence>
and the application.xml deployment descriptor is:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
<display-name>WASEnterprise</display-name>
<module id="myeclipse.1188512259959">
<ejb>WAS.jar</ejb>
</module>
</application>
I don't use any other weblogic specific deployment descriptor.
Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
Thanks inadvance.
Denis Maggiorotto

Problem: Editing a deployment descriptor of an EJB or WAR inside of an EAR sends things to hell

Similar Messages

Maybe you are looking for