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

Similar Messages

  • 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

  • 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

  • Web.xml + jsp-config element missing in definition?

    Hi,
    I have problem with jsp-config element definition in web.xml - I checked web-app_2_5.xsd it's reffering to javaee_5.xsd - but it's missing there
    from web xsd:
    <xsd:element name="jsp-config"
              type="javaee:jsp-configType"/>
    There is no javaee:jsp-configType. Is jsp-config deprecated? I couldnt find it in 1.4 as well. Please advice.
    Thanks
    Y

    ok - there are includes in web-add_2_5.xsd to jsp_2_1.xsd ... missed that - sorry
    <xsd:include schemaLocation="javaee_5.xsd"/>
    <xsd:include schemaLocation="jsp_2_1.xsd"/>
    Y

  • Namespaces in plan.xml - can't override weblogic.xml

    So, we've tried every combination we can think of, but we can't seem to get a plan.xml that successfully overrides items in weblogic.xml. It seems to be an issue around namespaces:
    <May 19, 2009 10:40:57 AM MDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor /nas/scart/domain_tmps/tcatshopDomain/servers/tcatshop1/tmp/_WL_user/MasterEar/v99i42/MasterWebPortal.war/WEB-INF/weblogic.xml of module MasterWebPortal.war. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
    /nas/scart0/prod_ecom2/local/apps/apps92/tcatshop/THUNDER_01.09.06.004/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected elements 'description@http://www.bea.com/ns/weblogic/90 weblogic-version@http://www.bea.com/ns/weblogic/90 security-role-assignment@http://www.bea.com/ns/weblogic/90 run-as-role-assignment@http://www.bea.com/ns/weblogic/90 resource-description@http://www.bea.com/ns/weblogic/90 resource-env-description@http://www.bea.com/ns/weblogic/90 ejb-reference-description@http://www.bea.com/ns/weblogic/90 service-reference-description@http://www.bea.com/ns/weblogic/90 message-destination-descriptor@http://www.bea.com/ns/weblogic/90 session-descriptor@http://www.bea.com/ns/weblogic/90 jsp-descriptor@http://www.bea.com/ns/weblogic/90 auth-filter@http://www.bea.com/ns/weblogic/90 container-descriptor@http://www.bea.com/ns/weblogic/90 charset-params@http://www.bea.com/ns/weblogic/90 virtual-directory-mapping@http://www.bea.com/ns/weblogic/90 url-match-map@http://www.bea.com/ns/weblogic/90 security-permission@http://www.bea.com/ns/weblogic/90 context-root@http://www.bea.com/ns/weblogic/90 wl-dispatch-policy@http://www.bea.com/ns/weblogic/90 servlet-descriptor@http://www.bea.com/ns/weblogic/90 work-manager@http://www.bea.com/ns/weblogic/90 logging@http://www.bea.com/ns/weblogic/90 library-ref@http://www.bea.com/ns/weblogic/90' instead of *'session-descriptor@http://www.w3.org/2001/XMLSchema-instance' here in element weblogic-web-app@http://www.bea.com/ns/weblogic/90:<nullplan.xml>*
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:229)
    at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:216)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
    at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)
    at weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)
    This is in WLP 9.2...
    Plan:
    <?xml version='1.0' encoding='UTF-8'?>
    <deployment-plan xmlns="http://www.bea.com/ns/weblogic/90">
    <application-name>MasterEar.ear</application-name>
    <variable-definition>
    <variable>
    <name>ThundercatCookieName</name>
    <value>JSESSIONID_THUNDERCAT_PLAN_XML</value>
    </variable>
    <variable>
    <name>ThundercatCookieDomain</name>
    <value>.qwest.com</value>
    </variable>
    </variable-definition>
    <module-override>
    <module-name>MasterWebPortal.war</module-name>
    <module-type>war</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-web-app</root-element>
    <uri>WEB-INF/weblogic.xml</uri>
    <variable-assignment>
         <name>ThundercatCookieName</name>
         <xpath>/weblogic-web-app/session-descriptor/cookie-name</xpath>
    </variable-assignment>
    <variable-assignment>
         <name>ThundercatCookieDomain</name>
         <xpath>/weblogic-web-app/session-descriptor/cookie-domain</xpath>
    </variable-assignment>
    </module-descriptor>
    </module-override>
    </deployment-plan>
    We've tried a lot of combinations of namespaces and such to try and get it to work, and it always spits out the same error....
    Thanks,
    Tim

    Hi Folks -
    Below is the weblogic.xml (or at least one version of it).
    We're trying to override the session-descriptor cookie-name and cookie-domain ...
    Thanks!!
    Tim
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-web-app xmlns="http://www.bea.com/ns/weblogic/90">
    <context-root>home</context-root>
    <jsp-descriptor>
    <page-check-seconds>-1</page-check-seconds>
    <precompile>true</precompile>
    <precompile-continue>true</precompile-continue>
    <verbose>false</verbose>
    <print-nulls>false</print-nulls>
    </jsp-descriptor>
    <session-descriptor>
         <cookie-name>JSESSIONID_THUNDERCAT</cookie-name>
         <cookie-domain>.tservicesq.com</cookie-domain>
    </session-descriptor>
    <library-ref>
    <library-name>wlp-tools-visitor-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-commonui-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-services-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-framework-full-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>p13n-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>beehive-controls-1.0-war</library-name>
    <specification-version>1.0</specification-version>
    <implementation-version>1.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>weblogic-controls-1.0-war</library-name>
    <specification-version>1.0</specification-version>
    <implementation-version>1.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-wsrp-producer-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-lookandfeel-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-light-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-framework-common-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wlp-framework-struts-1.2-web-lib</library-name>
    <specification-version>9.2.0</specification-version>
    <implementation-version>9.2.1</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>struts-1.2</library-name>
    <specification-version>1.2</specification-version>
    <implementation-version>1.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>wls-commonslogging-bridge-war</library-name>
    <specification-version>1.0</specification-version>
    <implementation-version>1.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>jstl</library-name>
    <specification-version>1.1</specification-version>
    <implementation-version>1.1.2</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>beehive-netui-resources-1.0</library-name>
    <specification-version>1.0</specification-version>
    <implementation-version>1.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>beehive-netui-1.0</library-name>
    <specification-version>1.0</specification-version>
    <implementation-version>1.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>QwestCmsLibrary</library-name>
    <specification-version>1.0</specification-version>
    <implementation-version>1.3.4.2</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>SIWebPortal.war</library-name>
    </library-ref>
    <library-ref>
    <library-name>StylesWebPortal.war</library-name>
    <specification-version>2.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>ShopWebPortal.war</library-name>
    <specification-version>1.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>ProfileWebPortal.war</library-name>
    <specification-version>1.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>CommonsWebPortal.war</library-name>
    <specification-version>1.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>EBillWebPortal.war</library-name>
    <specification-version>1.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>EPayWebPortal.war</library-name>
    <specification-version>1.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    <library-ref>
    <library-name>AdminWebPortal.war</library-name>
    <specification-version>2.0.0</specification-version>
    <implementation-version>1.0.0</implementation-version>
    </library-ref>
    </weblogic-web-app>

  • Using Axis2 webservices in WebLogic 10.3 - weblogic.xml

    Hi,
    I am facing an issue while trying the following:
    I am using a webservices webapp in WebLogic 10.3. The web-app uses Axis2 for the webservices. To fix a logging issue, I had to add the following to my weblogic.xml:
    <weblogic-web-app>
    <container-descriptor>
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    </weblogic-web-app>
    After adding this change to the weblogic.xml- I am now getting an error in weblogic server log files, which is as follows -
    ]] Root cause of ServletException.
    java.lang.LinkageError: loader constraint violation: when resolving interface method "org.apache.xmlbeans.SchemaTypeLoader.parse(Ljavax/xml/stream/XMLStreamReader;Lorg/apache/xmlbeans/SchemaType;Lorg/apache/xmlbeans/XmlOptions;)Lorg/apache/xmlbeans/XmlObject;"
    the class loader (instance of org/apache/axis2/deployment/DeploymentClassLoader) of the current class, com/arcot/schemas/regfort/v2/types/GetArcotIdDocument$Factory, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, org/apache/xmlbeans/SchemaTypeLoader, have different Class objects for the type javax/xml/stream/XMLStreamReader used in the signature
    I have tried over 6 hours of debugging but to no avail. If there are any suggestions anyone came make- as to the possible cause of this problem, it would be much appreciated!
    thank you,
    ronak

    hi david,
    thank you for the suggestion. The interesting thing is the error goes away as soon as I remove the weblogic.xml entry- and everything works fine. Except, when I dont have the prefer-web-inf-classes I get a log4j issue where my logs from different apps merge into a single file. That problem got resolved by adding the weblogic.xml change, but now it is this error.
    Do you think there is anything that can be done in the weblogic-application.xml <prefer-application-packages> that might help in solving this problem?
    thank you

  • resource-env-description can't be set in weblogic.xml

    hi guys , i've been troubled with this configuration problem. i am trying a very simple example to send messages from a servlet to a weblogic queue, but i cant configure the weblogic.xml properly. i've been reading a lot of information but i cant find it.:
    this is my web.xml
    <resource-ref>
              <res-ref-name>jms/ConnectionFactory1</res-ref-name>
              <res-type>javax.jms.QueueConnectionFactory</res-type>
              <res-auth>Container</res-auth>
              <res-sharing-scope>Shareable</res-sharing-scope>
         </resource-ref>
         <resource-env-ref>
              <resource-env-ref-name>jms/colaIN</resource-env-ref-name>
              <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
         </resource-env-ref>
         <resource-env-ref>
              <resource-env-ref-name>jms/colaOUT</resource-env-ref-name>
              <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
         </resource-env-ref>
    this work fine, but when i try to create the weblogic.xml , it doesn;t work:
    <weblogic-web-app>
         <reference-descriptor>
                   <resource-description>     
                        <res-ref-name>jms/ConnectionFactory1</res-ref-name>
                        <jndi-name>weblogic.jms.ConnectionFactory</jndi-name>
                   </resource-description>
         </reference-descriptor>
         <resource-env-description>
                        <res-ref-name>jms/colaIN</res-ref-name>
                        <jndi-name>weblogic.jms.Queue</jndi-name>
                   </resource-env-description>
    </weblogic-web-app>
    what am i doing wrong? . i try to set resource-env-description in weblogic-ejb-jar.xml but it didn't work either? some ideas?

    Is your workflow looking for publishing infrastructure to be turned on at site collection and site level?
    Is this a 2013 WF? is WF management service connected?
    Stacy Simpkins | MCSE SharePoint | www.sharepointpapa.com

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

  • Jsp-descriptor jsp-param jspCheckSeconds weblogic.xml?

    For some reason I can't get weblogic to recompile my jsp's when I change
              them. I am using Weblogic 6sp1 on NT4. I place my weblogic.xml in the
              d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam\Web-inf
              directory.
              When I change one of the jsps I copy it into the
              d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam directory
              and expect weblgoic to notice it changed. I use ant to copy the jsp's and I
              confirmed that it is actually copying correctly.
              The jsp's use custom tags, but I tried a simple jsp, not using custom tags,
              that doesn't get recompiled either. What could I be doing wrong? Has
              anybody else run into this problem? Restarting weblogic on every change to
              a jsp takes way too long.
              please help.
              -Scot
              <-------here is my weblogic.xml--------------------------->
              <?xml version="1.0" encoding="ISO-8859-1"?>
              <!DOCTYPE weblogic-web-app
              PUBLIC "-//BEASystems, Inc.//DTD Web Application 6.0//EN"
              "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
              <weblogic-web-app>
              <description>
              CAM - Customer Account Management
              </description>
              <session-descriptor>
              <session-param>
              <param-name>
              TimeoutSecs
              </param-name>
              <param-value>
              900
              </param-value>
              </session-param>
              <session-param>
              <param-name>
              URLRewritingEnabled
              </param-name>
              <param-value>
              false
              </param-value>
              </session-param>
              </session-descriptor>
              <jsp-descriptor>
              <jsp-param>
              <param-name>
              pageCheckSeconds
              </param-name>
              <param-value>
              1
              </param-value>
              </jsp-param>
              <jsp-param>
              <param-name>
              verbose
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              <jsp-param>
              <param-name>
              keepgenerated
              </param-name>
              <param-value>
              true
              </param-value>
              </jsp-param>
              </jsp-descriptor>
              </weblogic-web-app>
              

    This is correct. I started my web-app under a new directory which was not
              the default web-app originally and was not able to refresh the jsp's upon a
              change to the jsp. Next I tried it as the default web-app and I was able to
              refresh the jsp's as described in the weblogic.xml. Thank you for your
              help.
              Is this a known bug? Or should you not be able to use the weblogic.xml
              properites in a web application that is not the default application?
              "cheenle" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Are you start a new server for you own application?
              > I met the same problem, but I found it only appear under a new server
              >
              > "Scot Hale" <[email protected]> wrote:
              > >For some reason I can't get weblogic to recompile my jsp's when I change
              > >them. I am using Weblogic 6sp1 on NT4. I place my weblogic.xml in the
              > >d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam\Web-inf
              > >directory.
              > >
              > >When I change one of the jsps I copy it into the
              > >d:\weblogic6.0sp1\wlserver6.0sp1\config\mydomain\applications\cam
              directory
              > >and expect weblgoic to notice it changed. I use ant to copy the jsp's
              > >and I
              > >confirmed that it is actually copying correctly.
              > >
              > >The jsp's use custom tags, but I tried a simple jsp, not using custom
              > >tags,
              > >that doesn't get recompiled either. What could I be doing wrong? Has
              > >anybody else run into this problem? Restarting weblogic on every change
              > >to
              > >a jsp takes way too long.
              > >
              > >please help.
              > >
              > >-Scot
              > >
              > >
              > ><-------here is my weblogic.xml--------------------------->
              > >
              > ><?xml version="1.0" encoding="ISO-8859-1"?>
              > >
              > ><!DOCTYPE weblogic-web-app
              > > PUBLIC "-//BEASystems, Inc.//DTD Web Application 6.0//EN"
              > > "http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
              > >
              > ><weblogic-web-app>
              > > <description>
              > > CAM - Customer Account Management
              > > </description>
              > >
              > > <session-descriptor>
              > > <session-param>
              > > <param-name>
              > > TimeoutSecs
              > > </param-name>
              > > <param-value>
              > > 900
              > > </param-value>
              > > </session-param>
              > > <session-param>
              > > <param-name>
              > > URLRewritingEnabled
              > > </param-name>
              > > <param-value>
              > > false
              > > </param-value>
              > > </session-param>
              > > </session-descriptor>
              > >
              > > <jsp-descriptor>
              > > <jsp-param>
              > > <param-name>
              > > pageCheckSeconds
              > > </param-name>
              > > <param-value>
              > > 1
              > > </param-value>
              > > </jsp-param>
              > >
              > > <jsp-param>
              > > <param-name>
              > > verbose
              > > </param-name>
              > > <param-value>
              > > true
              > > </param-value>
              > > </jsp-param>
              > >
              > > <jsp-param>
              > > <param-name>
              > > keepgenerated
              > > </param-name>
              > > <param-value>
              > > true
              > > </param-value>
              > > </jsp-param>
              > > </jsp-descriptor>
              > >
              > ></weblogic-web-app>
              > >
              > >
              >
              

  • 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

  • Weblogic 6.1 and xml parser empty elements

    FYI, It looks like Weblogic changed there xml parser in the transition from
    6.0sp2 to 6.1. Example : The empty Extra Info Class produced and error,
    because it is empty. Where in 6.0sp2 it did not produce and error:
    <taglib>
    <tag>
    <name>indexProperty</name>
    <info>
    some info..
    </info>
    <tagclass>com.pssg.jsp.tags.IndexPropertyTag</tagclass>
    <teiclass></teiclass>
    </tag>
    </taglib>
    ####<Aug 20, 2001 12:20:52 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101047>
    <[WebAppServletContext(7008653,cam,/cam)] resolved taglib uri '/pssglibtags'
    to taglib-location /WEB-INF/tlds/pssgtaglib.tld:>
    ####<Aug 20, 2001 12:20:53 PM PDT> <Info> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101160> <Deployment
    descriptor is malformed, check against the DTD:
    org.xml.sax.SAXParseException: The content of element type "tag" must match
    "(name,tagclass,teiclass?,bodycontent?,info?,attribute*)"..>
    ####<Aug 20, 2001 12:20:53 PM PDT> <Error> <HTTP> <devlwebejb1> <camserver>
    <ExecuteThread: '14' for queue: 'default'> <> <> <101020>
    <[WebAppServletContext(7008653,cam,/cam)] Servlet failed with Exception>
    weblogic.servlet.jsp.JspException: (line 1): Error in using tag library
    uri='/pssglibtags' prefix='pssglibtag': For tag 'indexProperty', cannot load
    extra info class ''
    at
    weblogic.servlet.jsp.StandardTagLib.tld_jspException(StandardTagLib.java:901
    -Scot

    hi,
    there are two versions of ldap supported in wls6.1 , ldapv1 and ldavp2
    ldap v1 only has the functionality of listing groups.
    but where ldapv2 doesn't have that functionality,
    by looking at your config , it seems you are using ldap v2..
    if u need that functionality u can use ldapv1.
    thanks
    kiran
    "Bert Cliche" <[email protected]> wrote in message
    news:[email protected]..
    Per a proof of concept, I am having trouble getting WL6.1 to see
    group members as defined in iPlanet LDAP. I can see the groups,
    but modifies to create groups only create them in the local DB.
    Created users also only get placed in the local DB. I can bind
    for searches as Directory Manager via ldapsearch and run queries,
    and the DS gateway works fine. I can dump the LDIF file and the
    entries look fine.
    I copied and modified the template for the Netscape server and
    have the realm setup per the GUI.
    For sanity, everything is very generic as:
    the Root DN is "o=test.org"
    and my "Configuration" part from the config.xml looks like:
    server.authprotocol=simple;
    server.host=localhost;
    membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));
    server.port=390;
    group.dn=o=test.org;
    group.filter=(&(cn=%g)(objectclass=groupofuniquenames));
    server.principal=cn=Directory Manager;
    user.dn=o=test.org;
    server.groupiscontext=false;
    user.filter=(&(uid=%u))
    I added the "authprotocol" as a guess. Note that the server is
    running on port 390, this is not a typo.
    Any ideas what is going wrong?

  • Parsing in Weblogic/jsp doesn't work; application-mode (command-line) works

    Hello-
    Parsing my XML file in Weblogic/jsp doesn't work, whereas it works
    in application-mode... (albeit on two different machines)
    Here are the parameters:
    server1:
    weblogic 6.0
    win2k server
    jre1.3
    my personal machine:
    ***no weblogic***
    win2k server
    jre1.3
    When I run my code as an application (command-line style) on my machine,
    parsing in my xml file works fine, and I can do a root.toString() and it
    dumps out the entire xml file, as desired.
    However, running my code inside weblogic (on server1) in JSP, parsing in
    my file and doing a root.toString() results in the following: [dmui: null]
    (where dmui is my root)
    (even though i'm running it on two different machines, i'm positive its the
    same code (the servers share a mapped drive)...
    So, I think its probably because I'm using a different parser, as
    specified by weblogic? There are no exceptions being thrown. Here's my
    (abbreviated) code, which is called either command line style or in a JSP:
    // Imports
    import org.w3c.dom.*;
    import org.w3c.dom.Document;
    import javax.xml.parsers.*;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.DocumentBuilder;
    import org.xml.sax.SAXException;
    import org.xml.sax.SAXParseException;
    DocumentBuilderFactory docBuilderFactory =
    DocumentBuilderFactory.newInstance();
    DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
    mDocument = docBuilder.parse (inFile);
    myRoot.toString()
    -END
    Doing a System.getProperty("javax.xml.parsers.DocumentBuilderFactory")
    results in:
    server1 (weblogic/jsp):
    "weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
    my machine (application-mode):
    null
    Does anyone have any ideas about how to get this work? Do I try to set it
    up so that they both use the same parser? Do I change the Weblogic parser?
    If so, to what? And how?
    Am I even close?
    Any help would be appreciated..
    Thanks, Clint
    "[email protected]" <[email protected]> wrote in message
    news:[email protected]...
    No problem, glad you got it worked out :)
    ~Ryan U.
    Jennifer wrote in message <[email protected]>...
    I completely missed setting the property(:-o), foolish mistake. That wasit. Thanks.
    "j.upton" <[email protected]> wrote:
    Jennifer,
    Personally I would get rid of import com.sun.xml.parser.* and use xerces
    which comes with WLS 6.0 now, unless like I said earlier you have a need
    to
    use the sun parser :) Try something like this with your code --I've put
    things to watch for as comments in the code.
    import javax.xml.parsers.*;
    import org.xml.sax.SAXException;
    import org.w3c.dom.*;
    import java.io.FileInputStream;
    public class BasicDOM {
    public BasicDOM (String xmlFile) {
    try{
    FileInputStream inStream;
    Document document;
    /*You must specify a parser for jaxp. You can in a simple view
    think
    of this as being analogous to a driver used by JDBC or JNDI. If you are
    using this in the context of a servlet or JSP and have set an XML
    registry
    with the console this happens automatically. You can also invoke it in
    the
    context of an application on the command line using the -D switch. */
    System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
    >>>
    "weblogic.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
    // create a document factory
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
    // specify validating or non-validating parser
    dbf.setValidating(true);
    // obtain a factory
    DocumentBuilder db = dbf.newDocumentBuilder();
    // create a document from the factory
    inStream = new FileInputStream(xmlFile);
    document = db.parse(inStream);
    }//try
    catch (Exception e)
    System.out.println("Unexpected exception reading document!"
    +e);
    System.exit (0);
    }//catch
    }//BasicDom
    // Main Method
    public static void main (String[] args) {
    if (args.length < 1)
    System.exit(1); file://or you can be more verbose
    new BasicDOM(args[0]);
    }//class
    =============================================
    That will give you a basic DOM you can manipulate and parse it fromthere.
    BTW this code
    compiled and ran on WLS 6.0 under Windows 2000.
    Let me know if this helped or you still are having trouble.
    ~Ryan U.
    "Jennifer" <[email protected]> wrote in message
    news:[email protected]...
    Actually I included com.sun.xml.parser.* as one last febble attempt toget
    it working.
    And as for source code, I included the code. If I just put that oneline
    of code
    in, including the imports, it fails giving me an error listed above inthe
    subject
    line. Here is the code again:
    package examples.xml.http;
    import javax.xml.parsers.*;
    import org.xml.sax.SAXException;
    import org.xml.sax.SAXParseException;
    import org.w3c.dom.*;
    import java.util.*;
    import java.net.*;
    import org.xml.sax.*;
    import java.io.*;
    public class BasicDOM {
    static Document document;
    public BasicDOM (String xmlFile) {
    try {
    DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
    } catch (FactoryConfigurationError e){
    System.err.println(e.getException());
    e.printStackTrace();
    // Main Method
    public static void main (String[] args) {
    BasicDOM basicDOM = new BasicDOM (args[0]);

    Hi, Rob
    Does it work in WL9.2?
    It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
    I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
    <weblogic-web-app>
    <container-descriptor>     
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    </weblogic-web-app>
    Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
    <weblogic-application>
    <classloader-structure>
    <module-ref>
    <!-- reminder: this webapp contains
    prefer-web-inf-classes -->
    <module-uri>webapp</module-uri>
    </module-ref>
    <classloader-structure>
    <module-ref>
    <module-uri>mdb.jar</module-uri>
    </module-ref>
    </classloader-structure>
    </classloader-structure>
    </weblogic-application>
    Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all.

  • How to set working-dir for precompiled jsp pages to some where under tmp

    If my weblogic application gets exploded into this tmp directory:
    D:\bea_domains\my_wl_domain\servers\SERVER001\tmp\_WL_user\mywebapp\wxyzzz\war
    where "wxyzzz" is a random directory name generated by weblogic 9.2, how would I set my working-dir in weblogic.xml to store the precompiled jsp classes under:
    D:\bea_domains\my_wl_domain\servers\SERVER001\tmp\_WL_user\mywebapp\wxyzzz\war\WEB-INF\classes\jsp_servlet\_jsp directory?
    Is there an "expression" or "variable" that will hold the value of the tmp directory? Thanks.

    If my weblogic application gets exploded into this tmp directory:
    D:\bea_domains\my_wl_domain\servers\SERVER001\tmp\_WL_user\mywebapp\wxyzzz\war
    where "wxyzzz" is a random directory name generated by weblogic 9.2, how would I set my working-dir in weblogic.xml to store the precompiled jsp classes under:
    D:\bea_domains\my_wl_domain\servers\SERVER001\tmp\_WL_user\mywebapp\wxyzzz\war\WEB-INF\classes\jsp_servlet\_jsp directory?
    Is there an "expression" or "variable" that will hold the value of the tmp directory? Thanks.

  • prefer-web-inf-classes in weblogic.xml doesn't work

    When I try to use <prefer-web-inf-classes>true</prefer-web-inf-classes> it works fine with default classloaders structure. But after I changed classloaders hierarhy by means of <classloader-structure> in weblogic-application.xml classes from web app are ignored and classes from outside web app are loaded.
    Here is classloaders structure I use
    <weblogic-application>
    <classloader-structure>
    <module-ref>
    <module-uri>mywar.war</module-uri>
    </module-ref>
    <classloader-structure>
    <module-ref>
    <module-uri>myejb.jar</module-uri>
    </module-ref>
    </classloader-structure>
    </classloader-structure>
    </weblogic-application>
    Has anybody encountered this before?

    Hi, Rob
    Does it work in WL9.2?
    It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
    I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
    <weblogic-web-app>
    <container-descriptor>     
    <prefer-web-inf-classes>true</prefer-web-inf-classes>
    </container-descriptor>
    </weblogic-web-app>
    Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
    <weblogic-application>
    <classloader-structure>
    <module-ref>
    <!-- reminder: this webapp contains
    prefer-web-inf-classes -->
    <module-uri>webapp</module-uri>
    </module-ref>
    <classloader-structure>
    <module-ref>
    <module-uri>mdb.jar</module-uri>
    </module-ref>
    </classloader-structure>
    </classloader-structure>
    </weblogic-application>
    Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all.

Maybe you are looking for