Basic Autenticaation without weblogi.xml failed

Hello,
I have a problem with the Basic-Authentication, in a simple Webapp
contains with a Servlet called "servlet1", enable Security in Weblogic
7.0 and add new Role called "testrole" for the Webapp,in the
Defaultrealm. Now configuration the web.xml with Secrity:
<schnipp>
<web-app>
<servlet>
<servlet-name>servlet1</servlet-name>
<servlet-class>testweb3.Servlet1</servlet-class>
<security-role-ref>
<role-name>testrole</role-name>
<role-link>testrole</role-link>
</security-role-ref>
</servlet>
<servlet-mapping>
<servlet-name>servlet1</servlet-name>
<url-pattern>/servlet1</url-pattern>
</servlet-mapping>
<security-constraint>
<display-name>testrole</display-name>
<web-resource-collection>
<web-resource-name>Show</web-resource-name>
<url-pattern>/servlet1</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>testrole</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>myrealm</realm-name>
</login-config>
<security-role>
<role-name>testrole</role-name>
</security-role>
</web-app>
Deploy the application on the Appserver. Called with Webbrowser the URL,
show the Logindialog, enter the Username and Password. wrong!! not login
return Logindialog.
Now Rolemapping in Weblogic.xml
<security-role-assignment>
<role-name>testrole</role-name>
<principal-name>testgroup</principal-name>
</security-role-assignment>
enter Username and Password ,login success.
ist the Way over Weblogic.xml wrong or right? If the user, password,
groups contains in embedded LDAP mapping beetwhen user groups and roles.
and the Basic Realm is "myrealm" without the Weblogic.xml ??
Kind Regards,
Sascha Jostock

Keith, here are a few thoughts:
First, try running your page (spGals/China/galXml.cfm)
outside of spry. If the results show an obvous error, there's your
problem. (The xmlhttprequest expects XML, but CF and web server
come back as HTML.)
And since you have specified a relative path, your test must
use the URL to the page currently loading the XML. It may be that
your request (in the code) should be root-relative (/spGals), for
instance. The browse of the page will tell you.
It may be that the page comes back with CFML debugging turned
on. add <cfsetting showdebugoutput="no">. I discussed this
and related challenges in a blog entry at
http://carehart.org/blog/client/index.cfm/2006/7/13/spry4_unexpected_server_results
And since
http://carehart.org/blog/client/index.cfm/2006/7/13/spry4_unexpected_server_results
You should also try loading your page in the DataSetExplorer
(in the Spry samples).
Indeed, note that (as with your code) you have to load up the
page that's got the spry code from the same server against which
you'll be getting the CFM page serving the XML. You can't do
cross-browser requests.
If you are running Spry 1.2, enable the new debug feature, by
setting Spry.Data.Region.debug = true on your page with the spry
code. See the new 1.2 docs for more.
If you are not running Spry 1.2, look into using an http
proxy (like Fiddler on Windows, or Firebug on Firefox) to watch the
HTTP traffic going on between your client and server. This is
something I will blog about more later.
Let us know if any of those are the trick for you.

Similar Messages

  • Weblogic 10.0 Parsing Failure in config.xml: failed to load java type

    Hello,
    I've just installed a Weblogic 10.0 on a Linux server and when i try to start it, by :
    bash$ : sudo -u weblogic ./startWebLogic.sh
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=128m
    WLS Start Mode=Production
    CLASSPATH=:/opt/weblogic/10.0/patch_wls1002/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/weblogic/10.0/patch_cie640/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/weblogic/10.0/jdk150_15/lib/tools.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic_sp.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic.jar:/opt/weblogic/10.0/modules/features/weblogic.server.modules_10.0.2.0.jar:/opt/weblogic/10.0/modules/features/com.bea.cie.common-plugin.launch_2.1.2.0.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/webservices.jar:/opt/weblogic/10.0/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/opt/weblogic/10.0/modules/net.sf.antcontrib_1.0b2.0/lib/ant-contrib.jar::/opt/weblogic/10.0/weblogic10.0/common/eval/pointbase/lib/pbclient51.jar:/opt/weblogic/10.0/weblogic10.0/server/lib/xqrl.jar::
    PATH=/opt/weblogic/10.0/weblogic10.0/server/bin:/opt/weblogic/10.0/modules/org.apache.ant_1.6.5/bin:/opt/weblogic/10.0/jdk150_15/jre/bin:/opt/weblogic/10.0/jdk150_15/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.5.0_15"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
    Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)
    Starting WLS with line:
    /opt/weblogic/10.0/jdk150_15/bin/java -server -Xms256m -Xmx512m -XX:MaxPermSize=128m -da -Dplatform.home=/opt/weblogic/10.0/weblogic10.0 -Dwls.home=/opt/weblogic/10.0/weblogic10.0/server -Dweblogic.home=/opt/weblogic/10.0/weblogic10.0/server -Dwli.home= -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/opt/weblogic/10.0/patch_wls1002/profiles/default/sysext_manifest_classpath:/opt/weblogic/10.0/patch_cie640/profiles/default/sysext_manifest_classpath -Dweblogic.security.providers.authentication.LDAPDelegatePoolSize=50 -Dweblogic.management.username=system -Dweblogic.management.password=admin9424 -Dweblogic.Name=AdminServer -Djava.security.policy=/opt/weblogic/10.0/weblogic10.0/server/lib/weblogic.policy weblogic.Server
    <Jun 7, 2010 9:49:12 AM CEST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    /opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n-schemas.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n_common.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/p13n_system.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/p13n/wlp_services.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_common.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_schemas.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/netuix_system.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/wsrp-client.jar:/opt/weblogic/10.0/weblogic10.0/platform/lib/wlp/wsrp-common.jar>
    <Jun 7, 2010 9:49:13 AM CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_15-b04 from Sun Microsystems Inc.>
    <Jun 7, 2010 9:49:13 AM CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.0 MP2 Sat Apr 25 01:45:38 EDT 2009 1213942 >
    i got the following error messages :
    *<Jun 7, 2010 9:49:14 AM CEST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: failed to load java type corresponding to e=domain@http://www.bea.com/ns/weblogic/920/domain>*
    <Jun 7, 2010 9:49:14 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jun 7, 2010 9:49:14 AM CEST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jun 7, 2010 9:49:14 AM CEST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    If i start the server as root, it boots but i cant deploy anything.
    Any idea about this behavior ?

    Hi,
    It is the problem in prasing the DTD of config.xml file
    It look like this
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
    instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml http://www.bea.com/
    ns/weblogic/90/security/xacml.xsd http://www.bea.com/ns/weblogic/90/security http://www.bea.com/ns/weblogic/90/security.xsd http://www.bea.com/ns/weblogic/92
    0/domain http://www.bea.com/ns/weblogic/920/domain.xsd http://www.bea.com/ns/weblogic/90/security/wls http://www.bea.com/ns/weblogic/90/security/wls.xsd">
    Please change your DTD to this lines and start the server.
    Regards
    Ravi D

  • Weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal UsernameToke

    Hello,
    I'm developing an web service client and I have an error when I call the web service :
    *<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<faultcode>wsse:InvalidSecurity</faultcode>*
    *<faultstring>weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken</faultstring>*
    *</env:Fault>*
    The wsdl has the following policy set:
    *<WL5G3N1:Policy WL5G3N2:Id="ws-policy">*
    *<sp:SupportingTokens>*
    *<wsp:Policy>*
    *<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">*
    *<wsp:Policy>*
    *<sp:HashPassword/>*
    *<sp:WssUsernameToken10/>*
    *</wsp:Policy>*
    *</sp:UsernameToken>*
    *</wsp:Policy>*
    *</sp:SupportingTokens>*
    *</WL5G3N1:Policy>*
    *<wsp:UsingPolicy WL5G3N0:Required="true"/>*
    And the SOAP header of my request is as follows :
    *<S:Header>*
    *<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">*
    *<wsse:Username>user</wsse:Username>*
    *<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">pVK3p4MC0YJ/qGeb/lMGrrNQBwQ=</wsse:Password>*
    *<wsse:Nonce>NjkwMjk2Mzgw</wsse:Nonce>*
    *<wsse:Created>2012-02-22T14:59:10Z</wsse:Created>*
    *</wsse:UsernameToken></wsse:Security>*
    *</S:Header>*
    Do you know what might be the cause of the error?
    Thank you.
    Edited by: 916856 on Feb 24, 2012 8:39 AM
    Edited by: 916856 on Feb 24, 2012 8:40 AM

    Hello,
    I'm developing an web service client and I have an error when I call the web service :
    *<env:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<faultcode>wsse:InvalidSecurity</faultcode>*
    *<faultstring>weblogic.xml.dom.marshal.MarshalException: Failed to unmarshal {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken</faultstring>*
    *</env:Fault>*
    The wsdl has the following policy set:
    *<WL5G3N1:Policy WL5G3N2:Id="ws-policy">*
    *<sp:SupportingTokens>*
    *<wsp:Policy>*
    *<sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">*
    *<wsp:Policy>*
    *<sp:HashPassword/>*
    *<sp:WssUsernameToken10/>*
    *</wsp:Policy>*
    *</sp:UsernameToken>*
    *</wsp:Policy>*
    *</sp:SupportingTokens>*
    *</WL5G3N1:Policy>*
    *<wsp:UsingPolicy WL5G3N0:Required="true"/>*
    And the SOAP header of my request is as follows :
    *<S:Header>*
    *<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">*
    *<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">*
    *<wsse:Username>user</wsse:Username>*
    *<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">pVK3p4MC0YJ/qGeb/lMGrrNQBwQ=</wsse:Password>*
    *<wsse:Nonce>NjkwMjk2Mzgw</wsse:Nonce>*
    *<wsse:Created>2012-02-22T14:59:10Z</wsse:Created>*
    *</wsse:UsernameToken></wsse:Security>*
    *</S:Header>*
    Do you know what might be the cause of the error?
    Thank you.
    Edited by: 916856 on Feb 24, 2012 8:39 AM
    Edited by: 916856 on Feb 24, 2012 8:40 AM

  • Creation of Virtual Directory in weblogic.xml (OBIEE11 Weblogic)

    We are using OBIEE 11.1.1.6.4, we want to create a Virtual directory mapping in weblogic server so that we can place our static image files to access from the application URL.
    To do this activity, we have performed following steps -
    1) Navigated to C:\OBIEE11G\Oracle_BI1\bifoundation\jee
    2) Open analytics.ear file
    3) Existing code in weblogic.xml is: (if weblogic.xml is not present we need to create the file with below code)
    <?xml version = '1.0' encoding = 'US-ASCII'?>
    <weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
    <session-descriptor>
    <cookie-path>/analytics</cookie-path>
    </session-descriptor>
    </weblogic-web-app>
    4) We have added virtual-directory-mapping tag; After adding virtual directory mapping tag, the code in weblogic.xml is
    <?xml version = '1.0' encoding = 'US-ASCII'?>
    <weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
    <session-descriptor>
    <cookie-path>/analytics</cookie-path>
    </session-descriptor>
    <virtual-directory-mapping>
    <local-path>D:/virtualdirectory</local-path>
    <url-pattern>/images/*</url-pattern>
    <url-pattern>*.jpeg</url-pattern>
    </virtual-directory-mapping>
    </weblogic-web-app>
    5) We have created a folder virtualdirectory under D: drive. And then created a folder images within folder virtualdirectory.
    6) Then we have placed an image (lets say) test.jpeg within image folder.
    7) Restarted all BI services,
    8) Now when we try to access URL http://localhost:9704/analytics/images/test.gif. Now we are able to see the image, it’s working perfectly fine.
    If we paste the above URL in browser it will automatically displays the image without any authentication. So our requirement is, on pasting the URL in browser first it should redirect to OBIEE homepage and when authentication is done then it should display the image.
    Request you to please advise with your inputs.

    Why did you modify analytics.ear ?
    Should'nt you make changes here : Middleware_Home>\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1
    \analyticsRes\WEB_INF\web.xml
    Follow this note : OBIEE 11g: How To Access Custom Files Through URL By Creating Virtual Directory In Weblogic Server? [ID 1408240.1]
    And you should be able to deploy that virtual directory and access it after authentication.
    HTH,
    SVS

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

  • XML failing with Rosettanet DTD

    Hi,
    We are using a PIP5D5 xml message for an interface. This message is structurally defined as per the DTD provided in the Rosettanet standards. But for some segments where multiples are allowed, we are trying to use an attribute to distinguish each segment from other. (For Ex. <PartnerBusinessIdentification Type = "One">. )This new xml with attributes when verified against the dtd is failing with error, The element has no declaration for an attibute named 'Type'.
    Is the usage of attributes invalid if you want to create a message as per Rosettanet standards? If so, how can we distinguish a segment when multiple occurences can be there?
    Prabhakar

    Peter Roemer (guest) wrote:
    : Hello!
    : How can the Oracle XML-Parser parse a XML-Document without the
    : XML-Declaration. There is no information about the Version and
    : the DTD in the XML-Document. Can I use an extern DTD?
    : Thanks,
    : Peter
    Have you tried oracle.xml.parser.v2.XMLParser.setDoctype(DTD)?
    Oracle XML Team
    http://technet.oracle.com
    Oracle Technology Network
    null

  • 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

  • Upgrading weblogic.xml from 6.1 to 8.1

    I'am upgrading form weblogic 6. to weblogic 8.1.
    I have a problem upgrading my weblogic.xml, i get this message when i validate
    the xml file:
    The content of element type "weblogic-web-app" must match "(description?,weblogic-version?,security-role-assignment*,run-as-role-assignment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filter?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-match-map?,preprocessor*,preprocessor-mapping*,security-permission?,context-root?,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
    I have changed the header form:
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 6.1//EN"
    "http://www.bea.com/servers/wls610/dtd/weblogic-web-jar.dtd">
    to:
    <!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">
    Is there any oder changes i must do to the weblogic.xml and what is the reason
    for the error message ?
    -Bjørnar-

    "Bjørnar" <[email protected]> wrote in message
    news:[email protected]..
    >
    I'am upgrading form weblogic 6. to weblogic 8.1.
    I have a problem upgrading my weblogic.xml, i get this message when ivalidate
    the xml file:
    The content of element type "weblogic-web-app" must match"(description?,weblogic-version?,security-role-assignment*,run-as-role-assig
    nment*,reference-descriptor?,session-descriptor?,jsp-descriptor?,auth-filter
    ?,container-descriptor?,charset-params?,virtual-directory-mapping*,url-match
    -map?,preprocessor*,preprocessor-mapping*,security-permission?,context-root?
    ,wl-dispatch-policy?,servlet-descriptor*,init-as*,destroy-as*)".
    >
    I have changed the header form:
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD WebApplication 6.1//EN"
    "http://www.bea.com/servers/wls610/dtd/weblogic-web-jar.dtd">
    to:
    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD WebApplication
    8.1//EN""http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
    >
    Is there any oder changes i must do to the weblogic.xml and what is thereason
    for the error message ?
    The upgrade has this note.
    XML Parsing
    Issue: The new XML parser rejects some XML documents that were accepted
    by the previous parser.
    The built-in XML parser for WebLogic Server 8.1 is based on the Apache
    Xerces 1.4.4 parser, which is stricter than its predecessors.
    Symptom: An EAR file's deployment descriptors are all correct, but the
    EAR still cannot be loaded.
    Solution: Verify that the other XML documents in your deployment comply
    with Version 2 SAX and DOM interfaces. Track down and repair the XML. For
    6.x see Apache Xerces XML Parser; for 7.1 see Apache Xerces XML Parser. For
    an example, see Fix Encoding Error, where a minor encoding error is fixed.
    I would compare the XML file to the new DTD and see if you can determine why
    the parse is failing. You may also want to ask this in the
    weblogic.developer.interest.servlet newsgroup.

  • Weblogic.xml.schema.binding.DeserializationException

    Hi all.
    I am using WLS 8 and in my web application I have implemented a web service client. The client uses an API that I created with the clientgen executable providing a valid WSDL. That WSDL defines custom data types that are used during the communication to the web service server. Whenever I use one of those custom data types in my web service request everything works fine. But when I call a web service that responds with one of those custom data types I am getting the following exception:
    Error occured while calling webservice! Error : web service invoke failed; nested exception is:
         javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException: mapping lookup failure.
    The weird thing is that weblogic somehow tries to refer to that custom data type with an IP address (e.g. 123.123.123.123) but in the WSDL all the URLs are defined with names (e.g. my.web-service.de) .
    Has anyone experienced a similar problem and/or can help me with this issue?

    Hi all.
    I am using WLS 8 and in my web application I have implemented a web service client. The client uses an API that I created with the clientgen executable providing a valid WSDL. That WSDL defines custom data types that are used during the communication to the web service server. Whenever I use one of those custom data types in my web service request everything works fine. But when I call a web service that responds with one of those custom data types I am getting the following exception:
    Error occured while calling webservice! Error : web service invoke failed; nested exception is:
         javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.binding.DeserializationException: mapping lookup failure.
    The weird thing is that weblogic somehow tries to refer to that custom data type with an IP address (e.g. 123.123.123.123) but in the WSDL all the URLs are defined with names (e.g. my.web-service.de) .
    Has anyone experienced a similar problem and/or can help me with this issue?

  • Editing web.xml OR weblogic.xml programmatically

    Hi there,
    I am trying to edit the web.xml and weblogic.xml programmatically. I am trying to load the above deployment descriptors in DOM object. But as DTD is mentioned externally, connection to URL is failing.
    But weblogic.jar contains all DTD in local machine. Is there any way to make parser to refer DTD in weblogic.jar. Or any weblogic API available to edit the deployment descriptors programatically.
    Thanks in advance.
    I am getting following error.
    java.net.ConnectException: Connection timed out: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:306)
    at sun.net.www.http.HttpClient.<init>(HttpClient.java:267)
    at sun.net.www.http.HttpClient.New(HttpClient.java:339)
    at sun.net.www.http.HttpClient.New(HttpClient.java:320)
    at sun.net.www.http.HttpClient.New(HttpClient.java:315)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
    ction.java:512)
    at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection
    .java:489)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
    nection.java:617)
    at java.net.URL.openStream(URL.java:913)
    at weblogic.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityMan
    ager.java:836)
    at weblogic.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEntity
    Manager.java:796)
    at weblogic.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTDSc
    annerImpl.java:275)
    at weblogic.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.disp
    atch(XMLDocumentScannerImpl.java:841)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocume
    nt(XMLDocumentFragmentScannerImpl.java:329)
    at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguratio
    n.java:525)
    at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguratio
    n.java:581)
    at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
    at weblogic.apache.xerces.parsers.DOMParser.parse(DOMParser.java:257)
    at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilder
    Impl.java:201)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:151)
    at JAXPandDOM.main(JAXPandDOM.java:39)

    I believe you could get around this with a custom EntityResolver. It's possible that Tomcat does something like this.
    However, I would question why you are trying to do this. If your container is set to Development mode, you might get away with the container automatically reloading your changes, but it certainly won't happen in Production mode, and even in Development mode, I don't know that I could predict how that would work.
    You'd be better off, with respect to portability and flexibility, if you store dynamic resources in an external file, not in the web.xml or weblogic.xml file. You could have a timed "watcher" for the file, to see when it's modified.

  • Weblogic.xml.jaxp.RegistrySAXParserFactor

    we are getting following error with weblogic 10.3.2 in one of our pages. Is this a known issue?
    tlogin.jsp:1:1: The validator class: "org.apache.taglibs.standard.tlv.JstlCoreTLV" has failed with the following exception: "java.lang.ClassCastException: weblogic.xml.jaxp.RegistrySAXParserFactory cannot be cast to javax.xml.parsers.SAXParserFactory".
    <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    ^-------------------------------------------------------------------
    %>
    -^

    I was encountering similiar issue deploying war file in weblogic 10.3.
    there were a couple of xml parsers jars which were critical and i couldnt have afforded to remove.
    java.lang.ClassCastException: weblogic.xml.jaxp.RegistrySAXParserFactory cannot be cast to javax.xml.parsers.SAXParserFactory
    Finally putting
    <prefer-application-packages>
    <package-name>org.apache.xerces.*</package-name>
    </prefer-application-packages>
    in weblogic-application.xml worked.
    initially i was putting weblogic-application.xml in web project's src/META-INF/ but it didnt worked. I wasted almost a day trying to run my jsp's but no success.
    finally I created a ear for my web project and tried putting weblogic-application.xml at application level and it worked.
    -Tariq

  • 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

  • Error starting WL - weblogic.xml.dom.ChildCountException: missing child home in ejb-ref

    hi,
    i get this following error when i start the WL 7.0. The web application fails
    to start but the ejbs are started properly. This is an example from the Monson
    Haefel book, on the CMP: Entity bean relationships.
    Can anybody tell me what is happening ??
    -thanks
    -vasanth
    Error log:
    =============
    <Error> <HTTP> <101179> <[HTTP] Error parsing des criptor in Web appplication
    "C:\bea\user_projects\mydomain\.\myserver\.wlnotdele
    te\titan\titan.war" [Path="C:\eclipse\workspace\titan4\dist\titan.ear", URI="tit
    an.war"
    weblogic.xml.dom.ChildCountException: missing child home in ejb-ref
            at weblogic.xml.dom.DOMUtils.getElementByTagName(DOMUtils.java:147)
            at weblogic.xml.dom.DOMUtils.getValueByTagName(DOMUtils.java:128)
            at weblogic.servlet.internal.dd.EJBReference.<init>(EJBReference.java:61
            at weblogic.servlet.internal.dd.WebAppDescriptor.<init>(WebAppDescriptor
    .java:247)
            at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(Descri
    ptorLoader.java:540)
            at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader
    .java:253)
            at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader
    .java:215)
            at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.ja
    va:282)
            at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:714)
            at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:555)
            at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:458)
            at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplic
    ations(SlaveDeployer.java:490)
            at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeploy
    er.java:253)
            at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initi
    alize(DeploymentManagerServerLifeCycleImpl.java:150)
            at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.j
    ava:54)
            at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
            at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
            at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
            at weblogic.Server.main(Server.java:32)
    >
    <Jun 23, 2003 10:10:51 AM CDT> <Error> <Deployer> <149205> <The Slave Deployer
    f
    ailed to initialize the application titan due to error weblogic.management.Appli
    cationException: Prepare failed. Task Id = null
    Module Name: titan.war, Error: Could not load web application from 'C:\bea\user_
    projects\mydomain\.\myserver\.wlnotdelete\titan\titan.war'
    weblogic.management.ApplicationException: Prepare failed. Task Id = null
    Module Name: titan.war, Error: Could not load web application from 'C:\bea\user_
    projects\mydomain\.\myserver\.wlnotdelete\titan\titan.war'
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:720)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:555)
    at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:458)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplic
    ations(SlaveDeployer.java:490)
    at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeploy
    er.java:253)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initi
    alize(DeploymentManagerServerLifeCycleImpl.java:150)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.j
    ava:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >

    It is working now.
    For a local entity bean, i was using <ejb-ref> instead of <local-ejb-ref>
    Once i changed that, it worlked.
    thanks
    -vasanth
    "Sanjeev Chopra" <[email protected]> wrote:
    correct url for doc...
    http://e-docs.bea.com/wls/docs81/webapp/web_xml.html#1020090
    "Sanjeev Chopra" <[email protected]> wrote in message
    news:[email protected]...
    Seems like titan.war's WEB-INF/web.xml has an ejb-ref element witha
    missing
    <home> element .
    see http://e-docs/wls/docs81/webapp/web_xml.html#1020090
    "Vasanth" <[email protected]> wrote in message
    news:[email protected]...
    hi,
    i get this following error when i start the WL 7.0. The web applicationfails
    to start but the ejbs are started properly. This is an example from
    the
    Monson
    Haefel book, on the CMP: Entity bean relationships.
    Can anybody tell me what is happening ??
    -thanks
    -vasanth
    Error log:
    =============
    <Error> <HTTP> <101179> <[HTTP] Error parsing des criptor in Webappplication
    "C:\bea\user_projects\mydomain\.\myserver\.wlnotdele
    te\titan\titan.war" [Path="C:\eclipse\workspace\titan4\dist\titan.ear",URI="tit
    an.war"
    weblogic.xml.dom.ChildCountException: missing child home in ejb-ref
    atweblogic.xml.dom.DOMUtils.getElementByTagName(DOMUtils.java:147)
    at
    weblogic.xml.dom.DOMUtils.getValueByTagName(DOMUtils.java:128)
    atweblogic.servlet.internal.dd.EJBReference.<init>(EJBReference.java:61
    atweblogic.servlet.internal.dd.WebAppDescriptor.<init>(WebAppDescriptor
    java:247)
    atweblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(Descri
    ptorLoader.java:540)
    atweblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader
    java:253)
    atweblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader
    java:215)
    atweblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.ja
    va:282)
    atweblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:714)
    atweblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:555)
    atweblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:458)
    atweblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplic
    ations(SlaveDeployer.java:490)
    atweblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeploy
    er.java:253)
    atweblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initi
    alize(DeploymentManagerServerLifeCycleImpl.java:150)
    atweblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.j
    ava:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    <Jun 23, 2003 10:10:51 AM CDT> <Error> <Deployer> <149205> <The SlaveDeployer
    f
    ailed to initialize the application titan due to errorweblogic.management.Appli
    cationException: Prepare failed. Task Id = null
    Module Name: titan.war, Error: Could not load web application from'C:\bea\user_
    projects\mydomain\.\myserver\.wlnotdelete\titan\titan.war'
    weblogic.management.ApplicationException: Prepare failed. Task Id
    = null
    Module Name: titan.war, Error: Could not load web application from'C:\bea\user_
    projects\mydomain\.\myserver\.wlnotdelete\titan\titan.war'
    atweblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:720)
    atweblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:555)
    atweblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContain
    er.java:458)
    atweblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplic
    ations(SlaveDeployer.java:490)
    atweblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeploy
    er.java:253)
    atweblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initi
    alize(DeploymentManagerServerLifeCycleImpl.java:150)
    atweblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.j
    ava:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >

  • Weblogic 10 jaas and login.jsp and web.xml/weblogic.xml security constaints

    Hello,
    I struggled through and got the examples.security.jaas.SampleCallbackHandler.java and examples.common.utils.ExampleUtils.java/ExampleConstants.java into eclipse where they compile. A bean I made can call SambleCallbackHandler like such:
    mybean.logmein(username,password,url). I can then do a mybean.getStatus() or even a mybean.returnCode(). It does seem to correctly identlify that it is authenticating me (I see in stdout logs that it shows success or failures. The problem I have is I do not know how to apply this weblogic and web.xml/weblogic.xml so that if authentication works it redirects me to the page requiring the authentication. In web.xml I have the following set up:
    <security-role>
         <role-name>Admins</role-name>
    </security-role>
    <login-config>
         <auth-method>FORM</auth-method>
         <realm-name>default</realm-name>
         <form-login-config>
              <form-login-page>/login.jsp</form-login-page>
              <form-error-page>/badlogin.html</form-error-page>
         </form-login-config>
    </login-config>
    <security-constraint>
         <web-resource-collection>
              <web-resource-name>empower</web-resource-name>
              <description>These pages are only accessible by authorized users.</description>
              <url-pattern>/admin/*</url-pattern>
              <http-method>GET</http-method>
              <http-method>POST</http-method>
         </web-resource-collection>
    <auth-constraint>
    <description>These are the roles who have access</description>
    <role-name>Administrators</role-name>
    </auth-constraint>
         <user-data-constraint>
         <description>This is how the user data must be transmitted</description>
         <transport-guarantee>NONE</transport-guarantee>
         </user-data-constraint>
    </security-constraint>
    My weblogic.xml has:
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
    <wls:security-role-assignment>
    <wls:role-name>Admins</wls:role-name>
    <wls:principal-name>Administrators</wls:principal-name>
    <wls:principal-name>dashap</wls:principal-name>
    </wls:security-role-assignment>
    </wls:weblogic-web-app>
    With this set up, if I try to go to a page in /admin folder in my application, it correctly pops up the login page. The jaas in the bean is doing a loginContext.login(), which I thought does authentication too, but it never goes back to the /admin page I was going to that needed the authentication. With jaas, can I not use the web.xml FORM security option? Do I Need to use j_security in the login.jsp's form's action= option and j_username and j_password for the input type names? How do I use j_username/j_password things if I am using jaas? I could just ignore using the web.xml security stuff and put something in the pages that need authentication, but it would be easier if I could use jaas with the security featurs without doing all that. Note that my code above is using a realm called default just because that was what was in the example I got from the web. Does that need to be something else?

    Hi John,
    I would like magic of course. However, in this case I want something special: my authentication provider uses special means and contents of headers, cookies and service from external identity management systems to determine the user's identity.
    I do not want the application to present the login dialog! I want to derive the identity and the fact that the user is logged in from whatever the authentication provider returns in terms of Subject.
    Ideally, the flow is something like:
    - user accesses an unprotected resource - resource is shown, no interaction with authentication provider
    - user presses a link or button that takes him/her to a protected resource
    - the authentication provider is contacted to work with the identity asserter to establish the identity of the current user and create a subject object for this user
    - the application can access the subject and principals
    - ADF Security recognizes the identity and the roles (based on the principals) and coordinates access based on this.
    the authentication method is client certificate. presumably this prompts WebLogic/OPS to use an identity asserter to work with custom headers and cookies ("... when you configure a web application to use CLIENT-CERT authentication. In this case, WebLogic can perform identity assertion based on values from request headers and cookies. If the header name or cookie name matches the active token type for the provider, the value is passed to the provider."). No login form should be presented to the user, as all information required to perform the authentication is already available.
    I am trying to understand what I must do to have the ADF application adopt the subject set by the authentication provider - if anything?!
    If you more ideas to share - I would love to hear them.
    best regards,
    Lucas

  • ClassNotFoundException at weblogic.xml.schema.binding.util.ClassUtil!!

    Hi,
    We are getting below exception everytime we are starting the weblogic 10 server. This is coming in clustered as well as non-clustered environment. Full stack trace is as below:-
    <03-Oct-2009 12:24:19 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: FileOutputServletIgnoring: unable to load class:java.lang.ClassNotFoundException: FileOutputServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
    Any pointers will be helpful.....
    Thanks & Regards,
    Sanjeev

    How are you starting your weblogic server? From the console or command prompt? Try both ways and see still the error occurs. Both uses different script to start the server. See that makes any difference.

Maybe you are looking for