Transaction attribute in XML deployment descriptor

Hi,
I just want to know the use of transaction attributes like (Required, notSuuport etc..) are in the EJB.
What is Bean managed and container managed transaction.
How we use the transaction attributes in BMP and CMP.
and in similar fashion, the use of the same in Session beans.
..Aman

modification to the above quesion::
There are 5 different beans named as
CMP, BMP, Stateless, Stateful and MDB.
I want to know that which all transactions (CMT or BMT) can be applied for which bean?
I just got some feedback from some ppl that i cant apply BMT for CMP and BMP. if that is true then why???
if i can apply CMT for CMP and BMP then how i will modify the EJB-jar for the
method definitiion for CMP and BMP. I mean to say the method name and parameter definition. as there are only call back methods.
..Aman

Similar Messages

XML Deployment Descriptor question

I am upgrading from WebLogic 4.5.1 to WebLogic 5.1 on Solaris 2.6. I
have several entity beans. I created XML deployment descriptors by
running the DDConverter, then splicing the resulting files together (I
had several entity beans in one directory). I've gotten past all the
problems except this last one. I get the following errors from ejbc
when I try to compile:
ERROR: Error from ejbc: Bean provided to WebLogic RDBMS CMP system is
invalid.
Please examine the following exceptions for specific problems:
0: An unknown error occurred while parsing the Weblogic CMP RDBMS
deployment descriptor. Check that the deployment descriptor contains
well-formed and valid XML.
I've checked the weblogic-cmp-rdbms-jar.xml file, compared it to the
examples, and can't find anything wrong with it. However, the WebLogic
examples don't have an example with multiple entity beans in a jar (can
this be done?). Here is the resulting xml file:
<!DOCTYPE weblogic-rdbms-bean PUBLIC
"-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN"
"http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd">
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Address</table-name>
<attribute-map>
<object-link>
<bean-field>entity</bean-field>
<dbms-column>Entity</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>File_Cabinet</table-name>
<attribute-map>
<object-link>
<bean-field>folderContainer</bean-field>
<dbms-column>Folder_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>maxCapacity</bean-field>
<dbms-column>Max_Capacity</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list>
<finder>
<method-name>findByHomeDomain</method-name>
<method-params>
<method-param>Long</method-param>
</method-params>
<finder-query><![CDATA[(= homeDomain $0)]]></finder-query>
</finder>
</finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Folder</table-name>
<attribute-map>
<object-link>
<bean-field>documentContainer</bean-field>
<dbms-column>Document_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>parentFolder</bean-field>
<dbms-column>Parent_Folder</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
<object-link>
<bean-field>fileCabinet</bean-field>
<dbms-column>File_Cabinet</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Origination_Activity</table-name>
<attribute-map>
<object-link>
<bean-field>homeInterface</bean-field>
<dbms-column>Home_Interface</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>packageSpec</bean-field>
<dbms-column>Package_Spec</dbms-column>
</object-link>
<object-link>
<bean-field>url</bean-field>
<dbms-column>Url</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>displayable</bean-field>
<dbms-column>Displayable</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list>
<finder>
<method-name>findByName</method-name>
<method-params>
<method-param>String</method-param>
</method-params>
<finder-query><![CDATA[(= name $0)]]></finder-query>
</finder>
</finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Package</table-name>
<attribute-map>
<object-link>
<bean-field>forwardIndicator</bean-field>
<dbms-column>Forward_Indicator</dbms-column>
</object-link>
<object-link>
<bean-field>archiveFlag</bean-field>
<dbms-column>Archive_Flag</dbms-column>
</object-link>
<object-link>
<bean-field>beenReadFlag</bean-field>
<dbms-column>Been_Read_Flag</dbms-column>
</object-link>
<object-link>
<bean-field>deleteTimestamp</bean-field>
<dbms-column>Delete_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>sentBy</bean-field>
<dbms-column>Sent_By</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>patientName</bean-field>
<dbms-column>Patient_Name</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>folderName</bean-field>
<dbms-column>Folder_name</dbms-column>
</object-link>
<object-link>
<bean-field>importanceLevel</bean-field>
<dbms-column>Importance_Level</dbms-column>
</object-link>
<object-link>
<bean-field>creationTimestamp</bean-field>
<dbms-column>Creation_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>sentTimestamp</bean-field>
<dbms-column>Sent_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>sentOnBehalfOf</bean-field>
<dbms-column>Sent_On_Behalf_Of</dbms-column>
</object-link>
<object-link>
<bean-field>sentToAddrContainer</bean-field>
<dbms-column>Sent_To_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>ccToAddrContainer</bean-field>
<dbms-column>CC_To_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>subject</bean-field>
<dbms-column>Subject</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>parentFolder</bean-field>
<dbms-column>Parent_Folder</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
<object-link>
<bean-field>readBy</bean-field>
<dbms-column>Read_By</dbms-column>
</object-link>
<object-link>
<bean-field>modifiedTimestamp</bean-field>
<dbms-column>Modified_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>readTimestamp</bean-field>
<dbms-column>Read_Timestamp</dbms-column>
</object-link>
<object-link>
<bean-field>packageSize</bean-field>
<dbms-column>Package_Size</dbms-column>
</object-link>
<object-link>
<bean-field>creator</bean-field>
<dbms-column>Creator</dbms-column>
</object-link>
<object-link>
<bean-field>lastModifier</bean-field>
<dbms-column>Last_Modifier</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Package_Spec</table-name>
<attribute-map>
<object-link>
<bean-field>templateContainer</bean-field>
<dbms-column>Template_Container</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>destinationAddrContainer</bean-field>
<dbms-column>Destination_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Service_Activity</table-name>
<attribute-map>
<object-link>
<bean-field>serviceContainer</bean-field>
<dbms-column>Service_Container</dbms-column>
</object-link>
<object-link>
<bean-field>homeInterface</bean-field>
<dbms-column>Home_Interface</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>type</bean-field>
<dbms-column>Type</dbms-column>
</object-link>
<object-link>
<bean-field>url</bean-field>
<dbms-column>Url</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Service</table-name>
<attribute-map>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>packageSpec</bean-field>
<dbms-column>Package_Spec</dbms-column>
</object-link>
<object-link>
<bean-field>name</bean-field>
<dbms-column>Name</dbms-column>
</object-link>
<object-link>
<bean-field>destAddrContainer</bean-field>
<dbms-column>Dest_Addr_Container</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Default_Doc</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Doc_Template</table-name>
<attribute-map>
<object-link>
<bean-field>dtdOid</bean-field>
<dbms-column>DTD_OID</dbms-column>
</object-link>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>viewStyleSheetOid</bean-field>
<dbms-column>View_Style_Sheet_OID</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>defaultDocOid</bean-field>
<dbms-column>Default_Doc_OID</dbms-column>
</object-link>
<object-link>
<bean-field>editStyleSheetOid</bean-field>
<dbms-column>Edit_Style_Sheet_OID</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Dtd</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>version</bean-field>
<dbms-column>Version</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
<weblogic-rdbms-bean>
<pool-name>H2HPool</pool-name>
<table-name>Xml_Stylesheet</table-name>
<attribute-map>
<object-link>
<bean-field>title</bean-field>
<dbms-column>Title</dbms-column>
</object-link>
<object-link>
<bean-field>docSize</bean-field>
<dbms-column>Doc_Size</dbms-column>
</object-link>
<object-link>
<bean-field>homeDomain</bean-field>
<dbms-column>Home_Domain</dbms-column>
</object-link>
<object-link>
<bean-field>version</bean-field>
<dbms-column>Version</dbms-column>
</object-link>
<object-link>
<bean-field>owner</bean-field>
<dbms-column>Owner</dbms-column>
</object-link>
<object-link>
<bean-field>text</bean-field>
<dbms-column>Text</dbms-column>
</object-link>
<object-link>
<bean-field>oid</bean-field>
<dbms-column>OID</dbms-column>
</object-link>
</attribute-map>
<finder-list></finder-list>
<options>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</options>
</weblogic-rdbms-bean>
Have Fun!
Lea Anne Troeger
Software Engineer
Telesynthesis, Inc.
[email protected]

There is one pool per RA (ra.xml/weblogic-ra.xml). One way to get almost what I think you
          are after is to use the <ra-link-ref> facility in WLS 6.1.
          HTH.
          YiQing Yang wrote:
          > Hi there,
          >
          > I have a question about connector. In weblogic-ra.xml Deployment Descriptor, you
          > define the parameters for connection factory and connection pool. Can you only
          > define one connection factory and connection pool or you can define more than
          > one? In other words, for each deployed connector, can it have more than one connection
          > pool?
          > Your help is appreciated.
          >
          > Thanks,
          >
          > YiQing Yang
          Tom Mitchell
          [email protected]
          Very Current Beverly, MA Weather
          http://www.tom.org:8080

The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing

Hello,
I want to create web service from ejb but everytime I want to do it, I get the following error:
I'm using NWDS 7.2 and JDK 1.6
[004]Deployment aborted
Settings
SDM host : XXX
SDM port : 50118
URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
Result
=> deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is: com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Can anyone tell me why am I getting this error.
Thnx for your help.
Best regards.

Hello Decio Junior,
Actually yes, I resolved my problem.
I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
The problem is that my server was using JDK 1.4 and that was the problem.
EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
Check your server JDK Version. It should be JDK 1.5 or higher.
Something else that you should check, in your project properties :
In the Build PATH : Use JDK 1.5
In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
Hope it would help.
If you need more explanations, I'm here
Good luck.

XML deployment descriptor generation

How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
Thanks.

How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
Thanks. Hi,
there is no way (so far as I know) that an J2EE Application server (what oc4j is) makes the deployment descriptors, that's why they are called deployment descriptors, without them you can't deploy on any Application server.
I personally use JDeveloper, but most current JAVA IDE's support generation of deployment descriptors.
Basically my approach is to define the architecture within Rational Rose, which generates for me the stubs for the classes and for every ejb a deployment descriptor, later I copy all of them into one ejb-jar.xml and open the whole bunch with JDeveloper, it works fine with 903 preview, although there are some problems with the 902 version of JDeveloper.
Which IDE are you using?
--hery

How to edit web.xml deployment descriptor from console in weblogic 8.1?

In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
console, but on weblogic 8.1 I can't find a way to do so.
Is this function taken out? Why is it taken out? Do I have an alternative to edit
it without unpacking and packing the EAR or WAR?
Thanks in advance.
Bill

In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
console, but on weblogic 8.1 I can't find a way to do so.
Is this function taken out? Why is it taken out? Do I have an alternative to edit
it without unpacking and packing the EAR or WAR?
Thanks in advance.
Bill

Disappearing weblogic.xml deployment descriptor elements

Using WebLogic 8.1 SP1
We have an application that we deploy with a weblogic.xml file. This file has
half-a-dozen deployment descriptor elements, and for some reason I'm unaware of,
several of the parameters specified by these elements are set to their default
values, and these elements don't show up in the weblogic.xml deployment decriptor
when displayed from within the WebLogic Server console. When deploying an exploded
EAR, I can change the value to something non-default , look at the deployment
descriptor and the element appears; change it back and the element is gone.
Is this expected behavior? Is there any configuration setting to display all
the elements no matter the value?
Thanks.

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

How to get rid of Default Transaction Attribute warning at deployment

Hi,
When I deploy Entity and Session Beans on BEA 8.1 SP3,
I get warings about Default Trabsaction setting.
I need to know which @XDoclet Tags to insert in my Entity or Session Beans in order
to get rid of this Deployment waring: The Default Transaction is set to Supported...
with kind regards,
Harry van Rijn

I think @ejbgen:entity 'default-transaction ' should avoid the warning.
http://e-docs.bea.com/wls/docs81/ejb/EJBGen_reference.html#1126084
--Sathish
<Harry van RIjn> wrote in message news:[email protected]..
Hi,
When I deploy Entity and Session Beans on BEA 8.1 SP3,
I get warings about Default Trabsaction setting.
I need to know which @XDoclet Tags to insert in my Entity or Session Beans
in order
to get rid of this Deployment waring: The Default Transaction is set to
Supported...
with kind regards,
Harry van Rijn

Error in Sun XML schema for servlet2.4 deployment descriptor?

Hi,
I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
This error is on line 744, and is caused by the snippet:
<xsd:simpleContent>
<xsd:extension base="j2ee:nonEmptyStringType"/>
</xsd:simpleContent>
Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

XMLSpy is known to be flawed. From my own experience of implementing
validators and data-binding tools, and from my experience of working in the
W3C Schema working group, I can tell you that there are countless cases
where XMLSpy violates the schema specification.
I checked the corresponding part of the schema, but it looks correct to me.
So I suspect that this is another bug in XMLSpy.
Try Xerces. That's probably the best in terms of conformance to the spec.

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 weblogic.xml

I'm not sure what this file is either and how it relates to the web.xml
          deployment descriptor. However, I got my web app to run fine out of a
          directory that included a web.xml file. I did see the warning about the
          weblogic.xml file but it didn't seem to have any effect on my app. I
          haven't tried a WAR file yet though...
          -brian
          "John Collins" <[email protected]> wrote in message
          news:[email protected]...
          > Sean -
          >
          > That is the documentation for the weblogic-ejb-jar.xml file. What I think
          Song
          > is looking for, and so am I, is the weblogic.xml file that goes in the
          .war
          > file. I can't get a web app loaded without it, and haven't a clue how to
          build
          > it. Is there a tool? Is it documented? Is there at least a DTD? The
          > deployer tool won't load a .war file.
          >
          > Thanks.
          >
          > John Collins
          > University of Minnesota
          >
          > Sean Scott wrote:
          >
          > >
          http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_reference.html#1026457
          > >
          > > "Song" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > I can't find any documentation for the weblogic.xml on weblogic's
          website.
          > > > Could someone tell me where I can an example of weblogic.xml or the
          dtd
          > > for
          > > > it?
          > > > Thanks ,
          > > > Song
          >

EJB Deployment Descriptors not deploying to WLS

Hi,
We're using Eclipse 3.4.1 with the OEPE to target WLS 10.3 with Java 6/JEE 1.4 on a Windows XP Professional development machine.
We have an EJB 2.1 project as part of a larger EAR. The beans (all stateless session beans) and associated interfaces and deployment descriptors within are maintained manually for internal reasons; we do not rely on EJBGen or XDoclet or anything like that to manage these. We are NOT using any annotations in these EJBs, as is the default when you create a bean. Instead we rely on weblogic-ejb-jar.xml and ejb-jar.xml.
We're having an issue where deploying to the local Weblogic server instance fails with the following error displaying in the Eclipse console:
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'xxxxxxx'.>
<Dec 19, 2008 9:21:13 AM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(xxxxxxxEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation..
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     Truncated. see log file for complete stacktrace
java.io.IOException: No EJBs found in the ejb-jar file {0}. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
     at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:199)
     at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
     at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     Truncated. see log file for complete stacktrace
We DO have multiple beans defined, but it seems that WLS just isn't aware of them due to the lack of a deployment descriptor. It appears that Eclipse/OEPE is not copying the ejb-jar.xml and weblogic-ejb-jar.xml files to the build directory when the project is build:
xxxxxEJB
|-- ejbModule
|.....|-- META-INF
|.....|.....|-- ejb-jar.xml
|.....|.....|-- MANIFEST.MF
|.....|.....|-- weblogic-ejb-jar.xml
|.....|-- com (etc., .java files)
|-- build
......|-- classes
............|-- META-INF
............|......|-- MANIFEST.MF
............|-- com (etc, .class files)
Other notes:
- Cleaning the project does not help.
- Starting a new workspace does not help.
- It works under Eclipse 3.3.2 with the Europa version of OEPE.
- Explicitly exporting an EJB Jar file DOES include the two deployment descriptors (just not deploying to the embedded test server we've defined in our Servers view)
Any ideas? This seems like either a bug in the OEPE, or maybe WTP.

Yes, I have a simple EJB2.1 project with hand-crafted EJB remote/home interfaces/classes and deployment descriptors. Also tried Clean/Rebuild and manually delete
files under /build/classes.
Here are my descriptors files:
ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
     <display-name>TestEJB</display-name>
<enterprise-beans>
<session>
<display-name>HelloSessioin</display-name>
<ejb-name>HelloSession</ejb-name>
<home>sessions.HelloSessionHome</home>
<remote>sessions.HelloSession</remote>
<ejb-class>sessions.HelloSessionBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<security-identity>
<use-caller-identity/>
</security-identity>
</session>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>HelloSession</ejb-name>
<stateless-session-descriptor>
</stateless-session-descriptor>
<jndi-name>ejb.HelloSessionRemoteHome</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Did you check if there is any error/warning in Error Log view?

How do I read the Deployment descriptor throw my application?

Hi
There is a need for me to read attributes in the Deployment descriptor through my application.
How may I do that? I don't want to use a Parsa to read the XML file and get the attributes..
Is there any other way?
thanks
Sanesh

All attributes or just the context parameters?
For example:
<context-param>
<param-name>dbDriverName</param-name>
<param-value>org.gjt.mm.mysql.Driver</param-value>
<description>The database driver being used</description>
</context-param>
Could be read from your servlet with:
String dbDriverName = servletContext.getInitParameter("dbDriverName");
But if you'd like to get out the servlet mappings or anything else I guess you have to read and parse the file. There was a method called getServletNames() in the servlet context but that's deprecated now.

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

Challenges in deployment descriptors

We currently have an EJB (called CD) that is contacted "remotely" by a web service
(called CA) for some processing. The two (CD and CA) are deployed on different
WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar) whereas
CA is part of an EAR file and is deployed as an application. We ran into the necessity
of making CD as part of EAR (much like CA). However, as part of the CA package,
there is currently an initialization class (we're using a servlet) that saves
some entries in JNDI for both CA and CD. We want to mimic the functionality of
that class in CD when we create the ear for it.
I just ran into some settings that could be made in the weblogic-application.xml
deployment descriptor as follows:
<startup-class>startup class name</startup-class>
We're hoping this can help us mimic CA's init process. However, we need to pass
that class some parameters upon load (which in the case of CA was done by using
the <init-param> in its web.xml). We came across the following tag:
<application-param>
     <param-name>someparam</param-name>
     </param-value>somevalue</param-value>
</application-param
However, we have the following questions:
1. How do we make the startup class fetch those param values at load time? (for
CA, the servlet was using the appPropLoc = getInitParameter("someparam") in its
init method
2. We needed to perform the remote lookup from CA to CD. Would enclosing CD in
an EAR affect our ability to do so? If so, then how do we go about doing that?
Thanks much,
Sami

Hi sami,
Enclosing the EJB (CD) in an EAR file is not going to stop you from Remotely accessing
it.
As CD and CA are in different application package and moreover in different JVM,
you have to package the interface classes as client jar with in CA for type casting.
Joe
"sami titi" <[email protected]> wrote:
>
We have resolved the first part of this problem by using a startup servlet
much
like we do in CA. However, we still face the issue of question number
2 below.
Please provide some feedback.
Thanks,
Samir
"sami titi" <[email protected]> wrote:
We currently have an EJB (called CD) that is contacted "remotely" by
a web service
(called CA) for some processing. The two (CD and CA) are deployed on
different
WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar)
whereas
CA is part of an EAR file and is deployed as an application. We raninto
the necessity
of making CD as part of EAR (much like CA). However, as part of the
CA package,
there is currently an initialization class (we're using a servlet) that
saves
some entries in JNDI for both CA and CD. We want to mimic the functionality
of
that class in CD when we create the ear for it.
I just ran into some settings that could be made in the weblogic-application.xml
deployment descriptor as follows:
<startup-class>startup class name</startup-class>
We're hoping this can help us mimic CA's init process. However, weneed
to pass
that class some parameters upon load (which in the case of CA was done
by using
the <init-param> in its web.xml). We came across the following tag:
<application-param>
     <param-name>someparam</param-name>
     </param-value>somevalue</param-value>
</application-param
However, we have the following questions:
1. How do we make the startup class fetch those param values at load
time? (for
CA, the servlet was using the appPropLoc = getInitParameter("someparam")
in its
init method
2. We needed to perform the remote lookup from CA to CD. Would enclosing
CD in
an EAR affect our ability to do so? If so, then how do we go about doing
that?
Thanks much,
Sami

Transaction attribute in XML deployment descriptor

Similar Messages

Maybe you are looking for