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

Similar Messages

  • Weblogic.xml: jsp-descriptor element (working-dir)

    Hi all,
    In order to define correct deployment directory, we want to modify the weblogic.xml with jsp-descriptor as followed (e.g.):
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
    <security-role-assignment>
    <role-name>PrivilegedUser</role-name>
    <principal-name>Administrators</principal-name>
    </security-role-assignment>
    <jsp-descriptor>
    <page-check-seconds>60</page-check-seconds>
    <precompile>false</precompile>
    <precompile-continue>false</precompile-continue>
    <keepgenerated>true</keepgenerated>
    <verbose>true</verbose>
    *<working-dir>D:\Oracle\Middleware</working-dir>*
    </jsp-descriptor>
    <charset-params>
    <input-charset>
    <resource-path>/*</resource-path>
    <java-charset-name>UTF-8</java-charset-name>
    </input-charset>
    </charset-params>
    </weblogic-web-app>
    My questions:
    1- Is the solution (using weblogic.xml and modify working-dir) correct?
    2- What is the best approach:
    a- preparing <working-dir>D:\Oracle\Middleware</working-dir> via development phase and responsiblity of developer team?
    b- adjust and modify application(s) via adminstrators
    3- I find the following doc:
    http://docs.tpu.ru/docs/Oracle/en/fmw/11.1.1.6.0/web.1111/e13712/weblogic_xml.htm#i1038490
    Is there more doc/sample/info available regarding this matter?
    Regards,
    Moh

    Hi all,
    In order to define correct deployment directory, we want to modify the weblogic.xml with jsp-descriptor as followed (e.g.):
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
    <security-role-assignment>
    <role-name>PrivilegedUser</role-name>
    <principal-name>Administrators</principal-name>
    </security-role-assignment>
    <jsp-descriptor>
    <page-check-seconds>60</page-check-seconds>
    <precompile>false</precompile>
    <precompile-continue>false</precompile-continue>
    <keepgenerated>true</keepgenerated>
    <verbose>true</verbose>
    *<working-dir>D:\Oracle\Middleware</working-dir>*
    </jsp-descriptor>
    <charset-params>
    <input-charset>
    <resource-path>/*</resource-path>
    <java-charset-name>UTF-8</java-charset-name>
    </input-charset>
    </charset-params>
    </weblogic-web-app>
    My questions:
    1- Is the solution (using weblogic.xml and modify working-dir) correct?
    2- What is the best approach:
    a- preparing <working-dir>D:\Oracle\Middleware</working-dir> via development phase and responsiblity of developer team?
    b- adjust and modify application(s) via adminstrators
    3- I find the following doc:
    http://docs.tpu.ru/docs/Oracle/en/fmw/11.1.1.6.0/web.1111/e13712/weblogic_xml.htm#i1038490
    Is there more doc/sample/info available regarding this matter?
    Regards,
    Moh

  • DPL8007: Unsupported deployment descriptors element message-destination?

    Hi All,
    I am not able to run a working Java EE 5 JMS tutorial in jdk1.6.0_25, GF3.1 (bundled with Netbeans 7.0 on Windows XP) despite having re-created the whole project from scratch. Below is the code snippets of various components of the project:
    C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\src\java\com\ensode\mdb\MessageReceiverBean.java
    @MessageDriven(mappedName = "jms/myQueue", activationConfig = {
        @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
        @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    public class MessageReceiverBean implements MessageListener {
        @Override
        public void onMessage(Message message) {
            TextMessage textMessage = (TextMessage) message;
            try {
                System.out.println("Received message:" + textMessage.getText());           
            } catch (JMSException ex) {
                Logger.getLogger(MessageReceiverBean.class.getName()).log(Level.SEVERE, null, ex);
    C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProjectApplicationClient\src\java\com\ensode\jms
    public class Main {
        @Resource(name = "jms/myQueue")
        private static Queue myQueue;
        @Resource(name = "jms/myQueueConnectionFactory")
        private static ConnectionFactory myQueueConnectionFactory;
        public static void main(String[] args) throws JMSException {
            new Main().sendJMSMessageToMyQueue("NetBeans makes JMS trivial!");
        private Message createJMSMessageForjmsMyQueue(Session session,
                Object messageData) throws JMSException {
            TextMessage textMessage = session.createTextMessage();
            textMessage.setText((String) messageData);
            return textMessage;
        private void sendJMSMessageToMyQueue(Object messageData) throws
                JMSException {
            Connection connection = null;
            Session session = null;
            try {
                connection = myQueueConnectionFactory.createConnection();
                session = connection.createSession(false,
                        javax.jms.Session.AUTO_ACKNOWLEDGE);
                MessageProducer messageProducer = session.createProducer(myQueue);
                messageProducer.send(createJMSMessageForjmsMyQueue(session,
                        messageData));
            } finally {
                if (session != null) {
                    session.close();
                if (connection != null) {
                    connection.close();
    C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE resources PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 3.1 Resource Definitions//EN" "http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
    <resources>
      <admin-object-resource enabled="true" jndi-name="jms/myQueue" object-type="user" res-adapter="jmsra" res-type="javax.jms.Queue">
        <property name="Name" value="myQueue"/>
      </admin-object-resource>
      <connector-resource enabled="true" jndi-name="jms/myQueueConnectionFactory" object-type="user" pool-name="jms/myQueueConnectionFactory">
        <description/>
      </connector-resource>
      <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.QueueConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueFactoryPool" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
      <connector-resource enabled="true" jndi-name="jms/myQueueFactory" object-type="user" pool-name="jms/myQueueFactoryPool"/>
      <connector-connection-pool associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-definition-name="javax.jms.ConnectionFactory" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="true" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="jms/myQueueConnectionFactory" ping="false" pool-resize-quantity="2" pooling="true" resource-adapter-name="jmsra" steady-pool-size="8" validate-atmost-once-period-in-seconds="0"/>
    </resources>Yet it was met with the following exception which appears to be an unsupported deployment descriptor generated by Netbeans 7.0:
    _GF3.1 server log_
    WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
    _Application Client Outpu
    t_10/05/2011 2:59:45 AM com.sun.enterprise.deployment.util.ComponentValidator accept
    WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
    com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
    Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]glassfish-resources.xml used to reside in C:\Documents and Settings\jack\JMSEnterpriseProject\ setup\ sun-resources.xml back in GF2.1.
    Deployment was successful which resulted in the following resources created:
    Connector Resources => jms/myQueueConnectionFactory, jms/myQueueFactory.
    Connector Connection Pools => jms/myQueueFactoryPool, jms/myQueueConnectionFactory.
    Admin Object Resources => jms/myQueue.
    Your assistance would be very much appreciated.
    Thanks,
    Jack

    Hi,
    The same unsupported deployment descriptor persists despite having removed C:\Documents and Settings\jack\JMSEnterpriseProject\JMSEnterpriseProject-ejb\setup\glassfish-resources.xml with the following exception:
    10/05/2011 11:41:22 PM com.sun.enterprise.deployment.util.ComponentValidator accept
    WARNING: DPL8007: Unsupported deployment descriptors element message-destination value null
    10/05/2011 11:41:28 PM org.hibernate.validator.util.Version <clinit>
    INFO: Hibernate Validator 4.1.0.Final
    10/05/2011 11:41:28 PM org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA
    INFO: Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
    10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
    INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter: Version:  4.5  (Build 29-b) Compile:  Wed Feb  9 22:53:30 PST 2011
    10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
    INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter starting: broker is REMOTE, connection mode is TCP
    10/05/2011 11:41:29 PM com.sun.messaging.jms.ra.ResourceAdapter start
    INFO: MQJMSRA_RA1101: GlassFish MQ JMS Resource Adapter Started:REMOTE
    com.sun.enterprise.container.common.spi.util.InjectionException: Exception attempting to inject Unresolved Message-Destination-Ref jms/[email protected]@null into class com.ensode.jms.Main
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:698)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.inject(InjectionManagerImpl.java:468)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:215)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl.injectClass(InjectionManagerImpl.java:207)
         at org.glassfish.appclient.client.acc.AppClientContainer$ClientMainClassSetting.getClientMainClass(AppClientContainer.java:619)
         at org.glassfish.appclient.client.acc.AppClientContainer.getMainMethod(AppClientContainer.java:511)
         at org.glassfish.appclient.client.acc.AppClientContainer.completePreparation(AppClientContainer.java:405)
         at org.glassfish.appclient.client.acc.AppClientContainer.prepare(AppClientContainer.java:319)
         at org.glassfish.appclient.client.AppClientFacade.prepareACC(AppClientFacade.java:278)
         at org.glassfish.appclient.client.acc.agent.AppClientContainerAgent.premain(AppClientContainerAgent.java:76)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
         at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
    Caused by: javax.naming.NamingException: Lookup failed for 'java:comp/env/jms/myQueue' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.url.pkgs=com.sun.enterprise.naming, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl} [Root exception is javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]]
         at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
         at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.sun.enterprise.container.common.impl.util.InjectionManagerImpl._inject(InjectionManagerImpl.java:597)
         ... 15 more
    Caused by: javax.naming.NameNotFoundException: No object bound for java:comp/env/jms/myQueue [Root exception is java.lang.NullPointerException]
         at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:242)
         at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:498)
         ... 18 more
    Caused by: java.lang.NullPointerException
         at javax.naming.InitialContext.getURLScheme(InitialContext.java:269)
         at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:318)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at com.sun.enterprise.naming.util.JndiNamingObjectFactory.create(JndiNamingObjectFactory.java:82)
         at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:772)
         at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.lookup(GlassfishNamingManagerImpl.java:740)
         at com.sun.enterprise.naming.impl.JavaURLContext.lookup(JavaURLContext.java:172)It is running on Windows 7 as opposed to XP earlier on.
    Is it possible that this is a bug since all JMS resources have been declared without using deployment descriptor at all?
    Thanks,
    Jack

  • 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.

  • Weblogic EJB Deployment Descriptor

    Hi,
    Can someone help me in learning how to write weblogic specific deployment descriptors for EJBs ??? Where can I find good tutorial or help. I am new to EJB.
    Thank you in advance

    Why not search http://bea.com and see what pops up. I searched their site for "EJB deployment descriptors" and got quite a few hits.

  • 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

  • Weblogic.xml - reference-descriptor

    Hello All,
              When ever I put "reference-descriptor" element directly under root element "weblogic-web-app" in weblogic.xml, I get this message during server startup..
              "weblogic.xml" is malformed. Check against the DTD: org.xml
              .sax.SAXParseException: The content of element type "weblogic-web-app" must matc h "(description?,weblogic-version?,security-role-assignment*,run-as-role-assignm
              ent*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filter?,cont
              ainer-descriptor?,charset-params?,virtual-directory-mapping*,url-match-map?,prep
              rocessor*,preprocessor-mapping*,security-permission?,context-root?,wl-dispatch-p
              olicy?,servlet-descriptor*,init-as*,destroy-as*)". (line 60, column 20).
              XMLSpy also complains that "Unexpected child element 'reference-descriptor'. Can somebody point me what is wrong here?
              My weblogic.xml looks like this..
              <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
              <weblogic-web-app>
                   <jsp-descriptor>
                   </jsp-descriptor>     
                   <reference-descriptor>
                        <resource-description>
                             <res-ref-name>jdbc/myDataSource</res-ref-name>
                             <jndi-name>MyDataSource</jndi-name>
                        </resource-description>
                   </reference-descriptor>
              </weblogic-web-app>
              Any help will be deeply appreciated..
              Thanks,
              Ranjith Pillai

    Hello All,
              When ever I put "reference-descriptor" element directly under root element "weblogic-web-app" in weblogic.xml, I get this message during server startup..
              "weblogic.xml" is malformed. Check against the DTD: org.xml
              .sax.SAXParseException: The content of element type "weblogic-web-app" must matc h "(description?,weblogic-version?,security-role-assignment*,run-as-role-assignm
              ent*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filter?,cont
              ainer-descriptor?,charset-params?,virtual-directory-mapping*,url-match-map?,prep
              rocessor*,preprocessor-mapping*,security-permission?,context-root?,wl-dispatch-p
              olicy?,servlet-descriptor*,init-as*,destroy-as*)". (line 60, column 20).
              XMLSpy also complains that "Unexpected child element 'reference-descriptor'. Can somebody point me what is wrong here?
              My weblogic.xml looks like this..
              <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
              <weblogic-web-app>
                   <jsp-descriptor>
                   </jsp-descriptor>     
                   <reference-descriptor>
                        <resource-description>
                             <res-ref-name>jdbc/myDataSource</res-ref-name>
                             <jndi-name>MyDataSource</jndi-name>
                        </resource-description>
                   </reference-descriptor>
              </weblogic-web-app>
              Any help will be deeply appreciated..
              Thanks,
              Ranjith Pillai

  • 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                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • 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

  • Web.xml vs weblogic.xml

    i have an application :(ijust joined the production team)
    and the web.xml is empty .. do i need a weblogic.xml file for the webapp or not and also if the web.xml is empty like the only tag it has is <webapp> </web-app>
    what should the content of weblogic.xml be:
    i am guessing it will follow the web.xml and will have <weblogic> </weblogic> tags or is there anything mandatory for the weblogic.xml

    As a minimum you will need a web.xml and it should not be empty if you use any servlets in your webapp, I think you can probably get away with an empty web.xml if you only use JSPs. You can configure Servlet mappings, security roles etc in the web.xml file. If your application uses none of these thats probably why your web.xml is a bit sparse.
    see
    http://e-docs.bea.com/wls/docs81/webapp/weblogic_xml.html
    for info on weblogic.xml deployment descriptor.

  • 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
              >
              

  • 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.

Maybe you are looking for

  • Ipod wont sync - Says library is being used by another version

    I try to open iTunes and it keeps giving me an error message saying my library is connected to a different version of Itunes (or something to that effect). I do not have another Itunes program. Last night I did install media Sync for blackberry I tho

  • Prevent Printing of Web Accessible pdf created with Acrobot Pro X

    I posted this elsewhere but have not had an reply so wondered if I asked in the wrong place. Hello, Could I get brief answers to the following three questions... Question 1: Do the prevent printing advanced options in Adobe Acrobat Pro X work reliabl

  • ITunes Library Keeps Disappearing (database files get deleted)

    Hello Everyone, I have seen quite a few discussions regarding this problem, but the majority of the threads are resolved as the source of the error was a program loaded on a Sony Vaio computer.  However, I have an HP, so that doesn't apply to me. My

  • Creating a vignette in Premiere Pro CC 2014

    In another thread, I was criticised for the way I chose to create a frame vignette in Premiere Pro. I've always created a vignette using the circle effect on a transparent video layer, inverting it and applying a feather.  The result can be made fair

  • Dear Adobe, where is Adobe AIR 1.5.2 Update

    For Flash CS4 Professional??? You promised us we will be able to develop in Flash. I can't purchase flex now. thankx.