Endorsed directory

Hello,
I recently downloaded the Java Web Services Developer Pack and I'm trying to use the XML parsers (SAX and DOM) with jdk 1.4.2. I've copied the contents of the "jaxp-1.2.2/jaxp/endorsed" directory from the web services install directory to the "<JAVA_HOME>/jre/lib/endorsed" directory.
I'm trying to compile a simple DOM example and get the error:
package org.w3c does not exist
Do I need to include the jar files in "<JAVA_HOME>/jre/lib/endorsed" in my CLASSPATH?
thanks!

Do I need to include the jar files in "<JAVA_HOME>/jre/lib/endorsed"
in my CLASSPATH?Yes. Since the DOM classes are not in the java.lang package, they need to be in the classpath when you compile and run your app. Of course, for compiling, it doesn't matter whether your classpath points to the jars in jaxp-1.2.2/jaxp/endorsed or <JAVA_HOME>/jre/lib/endorsed.
Cheers,
Mike

Similar Messages

Java "Endorsed" Mechanism not working?

Hello,
I came across a very strange issue earlier this week. I was getting a "NoSuchMethodError" from somewhere in my code. Googling the problem revealed that I was supposed to "endorse" some certain jar files (jaxb-api.jar and jaxws-api.jar). Here is where my problem started.
I added the following option to java when running my code (my jar file(s) ):
-Djava.endorsed.dirs="/path/endorsed"
(For the record: YES, the jar files are in that directory. I've tried all sorts of different configurations in terms of this endorsed dirs option, the classpath, and copying/moving files around. I have thus far been unable to get it to work.)
My code is run from C++ which looks at a conf file to see what options to pass java. This is a potential weakness (an extra "moving part"), but I'm pretty sure these options are concatenated correctly because when I put in the "-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=1044" option, it correctly suspends execution until I attach a debugger. Clearly this is a pretty lazy test, but like I said it's passing the option. Unless java is peculiar about the order of these commandline options, I don't see a problem here.
So, by this point I was pulling my hair out trying to figure this out. I am extremely averse to shoving these jars into the jre/lib/endorsed directory, but I finally tried that (I actually didn't think there was any difference, but it was a last-ditch effort). To my surprise, my code ran fine without the "NoSuchMethodError." So, for now we have this jar file in the "official" jre endorsed directory, but ideally I would be able to figure out this java.endorsed.dirs option so we didn't have to do that (it just seems so dirty - and global, which I especially don't like).
Getting the full java command is a little trick, but I can provide that if necessary. From what I can see in the code it's being constructed as:
java <JAVA_OPTIONS> -jar "<MY_JAR>" "<MY_MAIN_ARGS>"
where:
<JAVA_OPTIONS> comes from this conf file (which I was setting as '-Djava.endorsed.dirs="/path/endorsed" ')
<MY_JAR> is the full path to my "main" jar file which obviously references a bunch of other jars, including these jaxws-api and jaxb-api jars.
<MY_MAIN_ARGS> is the list of arguments passed into the main function which tells "<MY_JAR>" what to do.
P.S.> I also noticed that if I shove these files into the jre/lib/endorsed directory and I still specify the -Djava.endorsed.dirs option, it acts as though the files are not endorsed ("NoSuchMethodError"). As soon as I take the option out, it starts working (no error). I don't know if this is relevant information besides the fact that it seems the -Djava.endorsed.dirs option is actually being passed, even though it's not doing what I expect (as in, it's affecting the execution in some way so it must be making a difference in the call somehow).
So, what gives? Why does -Djava.endorsed.dirs not work?

Hi Gayatri,
There are a lot of reasons as to why the java stack could be down. Try bouncing the J2EE stack again. ( restart), and see if it works
All the best!
cheers,
Prashanth
P.S Please mark helpful answers

Endorsed

-Djava.endorsed.dirs=/export/home/system/endorsed
Why is useful this?
Could anyone explain what it means?

It's a hack - IIRC Sun needed somewhere to let users tuck their XML parser interfaces they wanted to use in lieu of the ones in 1.4, but the classloader wouldn't ever find your stuff since it defers to the system classloader - so Sun dreamed up this endorsed directory to be (sorta) "above" the system loaded class files (I doubt that made any sense). Bottom line, you put stuff in the endorsed directory, and your classloader will find that even if it redefines selected classes from the core API... Ah - I can't explain it well - check it at:
http://java.sun.com/j2se/1.4.2/docs/guide/standards/
Good Luck
Lee

Jwsdp 1.1 and endorsed mechanism

Am using j2sdk 1.4.1_01. As the jwsdp tutorial suggested, in order to use the new jaxp classes, I placed the jars in a new \\jre\lib\endorsed directory in the j2sdk and also set the endorsed directories system variable to point to them. When running the xml example from the jwsdp-1.1\docs\tutorial\doc\JAXPSAX6.html file, I'm still getting the crimson parser and not the xerces parser that the tutorial says should be operating. Can anyone tell me why? Or what I must do to get the right parser? I tried running the command on the command line (Windows 2000) and in an UltraEdit DOS command but I get the same results with both - no Xerces parser.
Thanks.
Madeleine

Just to say this works if you put the jars in the classpath. Is this the only way?
Mad

Alternative to endorsing jar files?

Hi
I want to use the xerces api jar file rather than the sun xml api files. It seems I have to endorse the jar files by putting it in the lib\endorsed directory. But that is going to globally have an affect. I just want only my portal application to get this jar overriden. Anything I can do with the classloading to get this working? Please help. Thanks a lot!

My point wasn't that I wanted to troubleshoot what I had (though I appreciate the offer). I've actually sorted through a few of the issues already. My overall question is if there is a better alternative. The labview implementation doesn't handle errors well at all. For example, it failed to detect that it couldn't find that value in the file (which was written there by the write function, not by hand so I'm reasonably sure it is properly formatted). I'm more interested to see if this is the major option for config values or if people use an alternative (i.e. xml).

J2ee or j2sdk endorsed directories

I have both the J2EE 1.4 and the JSDK 1.4.2_2 installed and I am thoroughly confused over which takes precedence, especially with reference to the endorsed directories. When I run "java" or "javac", which version am I calling? Or is it somewhere else in a jre situated in my Program Files directory (I'm running Windows XP)?! In my System Path, the J2EE comes first but in my Classpath it's the j2sdk. Just to add to the confusion, my personal user Path variable puts the j2sdk before the j2ee.
To achieve this muddle, I simply followed the instructions for each separate installation.
I should add that I also have the JWSDP 1.3 installed! I copied its \endorsed\ directory into my j2sdk, as suggested - but now I see that the jar files in the \endorsed\ directory in the j2ee installation are different - later and much bigger. Should I copy those into the j2sdk as well?
Please can someone clear this up for me and tell me how I can achieve consistency?
Thanks!

Both are separate and distinct product sets (however you need to have the JSDK installed to work with J2EE). The JSDK (aka J2SE - Java 2 Standard Edition) is the core Java product set that includes the development tools (e.g., compiler, runtime, debugger, appletviewer, etc.) and core APIs. J2EE represents the enterpise product set (e.g., EJB, JDBC, JNDI, JSP, etc.).

Error in starting web logic server

Hi
I am new to weblogic and i get the following error when i launched weblogic server for the first time. Please tell me how to remove this error.
####<Aug 29, 2011 2:41:43 PM IST> <Info> <WebLogicServer> <BSLF221A> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1314609103256> <BEA-000000> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
####<Aug 29, 2011 2:41:43 PM IST> <Notice> <Log Management> <BSLF221A> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1314609103334> <BEA-170019> <The server log file D:\middleware\soasuite11g\user_projects\domains\soasuiteps3devdomain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Log Management> <BSLF221A> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1314609103350> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Diagnostics> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103444> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "t3" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "t3s" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "http" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "https" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "iiop" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "iiops" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "ldap" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "cluster" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103631> <BEA-002622> <The protocol "clusters" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103647> <BEA-002622> <The protocol "snmp" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103647> <BEA-002622> <The protocol "admin" is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103647> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Aug 29, 2011 2:41:43 PM IST> <Info> <RJVM> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609103694> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address          :7001
Public Address          N/A
Http Enabled          true
Tunneling Enabled     false
Outbound Enabled     false
Admin Traffic Enabled     true>
####<Aug 29, 2011 2:41:44 PM IST> <Info> <Server> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609104147> <BEA-002609> <Channel Service initialized.>
####<Aug 29, 2011 2:41:44 PM IST> <Info> <Socket> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609104178> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
>
####<Aug 29, 2011 2:41:44 PM IST> <Info> <Socket> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609104209> <BEA-000436> <Allocating 3 reader threads.>
####<Aug 29, 2011 2:41:44 PM IST> <Info> <Socket> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609104209> <BEA-000446> <Native IO Enabled.>
####<Aug 29, 2011 2:41:44 PM IST> <Info> <IIOP> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609104350> <BEA-002014> <IIOP subsystem enabled.>
####<Aug 29, 2011 2:41:46 PM IST> <Error> <Security> <BSLF221A> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1314609106834> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/middleware/soasuite11g/modules/glassfish.jaxb_1.0.0.0_2-1-12.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)>
####<Aug 29, 2011 2:41:46 PM IST> <Critical> <WebLogicServer> <BSLF221A> <AdminServer> <main> <<WLS Kernel>> <> <> <1314609106834> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/middleware/soasuite11g/modules/glassfish.jaxb_1.0.0.0_2-1-12.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/middleware/soasuite11g/modules/glassfish.jaxb_1.0.0.0_2-1-12.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1398)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/middleware/soasuite11g/modules/glassfish.jaxb_1.0.0.0_2-1-12.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
     at com.sun.xml.bind.v2.model.impl.ModelBuilder.<clinit>(ModelBuilder.java:173)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:462)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:308)
     at com.sun.xml.bind.v2.runtime.JAXBContextImpl$JAXBContextBuilder.build(JAXBContextImpl.java:1149)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:136)
     at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:217)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:132)
     at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:372)
     at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:337)
     at oracle.security.jps.internal.keystore.config.FarmKeyStoreConfig.load(FarmKeyStoreConfig.java:48)
     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.openKeyStore(FileKeyStoreManager.java:330)
     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:101)
     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)
     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)
     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)
     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:64)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:850)
     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)
     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)
     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1018)
     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Aug 29, 2011 2:41:46 PM IST> <Notice> <WebLogicServer> <BSLF221A> <AdminServer> <main> <<WLS Kernel>> <> <> <1314609106944> <BEA-000365> <Server state changed to FAILED>
####<Aug 29, 2011 2:41:46 PM IST> <Error> <WebLogicServer> <BSLF221A> <AdminServer> <main> <<WLS Kernel>> <> <> <1314609106944> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Aug 29, 2011 2:41:46 PM IST> <Notice> <WebLogicServer> <BSLF221A> <AdminServer> <main> <<WLS Kernel>> <> <> <1314609106944> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Aug 29, 2011 2:41:46 PM IST> <Info> <WebLogicServer> <BSLF221A> <AdminServer> <main> <<WLS Kernel>> <> <> <1314609106975> <BEA-000236> <Stopping execute threads.>

"Caused By: java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/D:/middleware/soasuite11g/modules/glassfish.jaxb_1.0.0.0_2-1-12.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)"
You have to upgrade your JAXB library in the rt.jar (located in the <JDK-HOME>/jre/lib directory).
Steps are presented here: http://jaxb.java.net/guide/Migrating_JAXB_2_0_applications_to_JavaSE_6.html section 7.1.2
Also note the line "newer releases (since update 4) of JavaSE 6 contain JAXB 2.1" in section 7.1.2. If this is an option for
you I would upgrade your JDK.

Problem with Xalan and JDK and Tomcat

hi all,
i have a webapplication under Apache Tomcat 4.1.30/Linux which use an XML/XSL transformation.
I got the following error:
org.apache.xml.utils.WrappedRuntimeException: The output format must have a '{http://xml.apache.org/xalan}content-handler' property!
     at org.apache.xalan.serialize.SerializerFactory.getSerializer(SerializerFactory.java:142)
     at org.apache.xalan.transformer.TransformerImpl.createResultContentHandler(TransformerImpl.java:1048)
     at
Any suggestion ?
Cheers.
Stefano

Here is an anwser for you
http://testdrive.mapinfo.com/TECHSUPP/MIPROD.NSF/0/4a9bc2a8f684237f85256e63006f9ad4?OpenDocument
JDK 1.4 and above, I believe, is packaged with an old version of Xalan jar. So sometimes, like when trying to run XSLTC, you have to override the JDK 1.4 Xalan version with the newer Xalan.jar. Or else your newer Xalan.jar classes are not looked at. You do this by putting your Xalan.jar in the /lib/endorsed directory. or /common/endorsed in this case.
http://xml.apache.org/xalan-j/faq.html#faq-N100CC
Hope this helps

Question on Insallation Approach for SOA 11.1.1.3

I would appreciate if any Fusion experts can answer this :
*Environment :OEL 5.3 64 bit, Oracle DB 11.1.0.7 , WLS 10.3.3, SOA Suite 11.1.13 and JRockit
I am setting up DEV environment
I installed Oracle DB 11.1.0.7 and RCU 11.1.1.3
I installed JRockit R27.5.0 for Java SE 6 for Linux x86-64” . While installing Web Logic Server 10.3.3 (generic) on 64 bit, I could see the Available JRockit 27.5 , I went ahead with that and I could install WLS. But while Installing SOA Suite I got this Error
java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/tmp/OraInstall2010-07-17_10-13-18PM/ext/jlib/glassfish.jaxb_1.2.0.0_2-1-7.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/)
I think this JRockit does not support SOA Suite 11.1.1.3 Right now WLS 10.3.3 is pointing to the JRockit 27.5 (not supported for SOA Suite)
Later I installed JRockit Mission Control 4.0.1 for Linux X86- 64. [jrmc-4.0.1-1.6.0-linux-x64.bin] in /u01/app/oracle/product
Now I went ahead with SOA Suite 11.1.1.2 runInstaller and then SOA 11.1.1.3 patch runInstaller , which worked .
But while creating SOA Domain I could only see JRockit 27.5 in Available JRockit list , so I browsed and selected jrmc-4.0.1-1.6.0 from product directory I installed and I could successfully create SOA Domain.
I can start Admin Server & Managed Server . Admin Server & SOA Server is shown up in Enterprise Manager. So far , I am assuming what I did is correct ??
QUESTIONS: -
1. But WLS is still pointing to JRockit 27.5 . Will there be any issues/ errors later during Deployment ?
2. Should I change or point the WLS to JRockit Mission Control. Can I do this without UN-INSTALLING . Like changing PATH or CLASS PATH , Can anyone suggest how to do?
3. Are they any post installation steps I need to follow?
Thanks
Arvind
Edited by: Arvind on Jul 19, 2010 10:13 AM
Edited by: Arvind on Jul 19, 2010 11:34 AM

Hi,
As you already have the cascade setup between Country and State set the default value for the state with SQL. The way to do it is use a presentation variable for country and use that variable in the state default sql as a filter. Sort the values and pick the 1st value in the sql. This would return the 1st value in the State prompt.
Let me know if this worked.
Regards,
Jay

How to use embeddable EJB container (Java EE 6 / EJB 3.1) on Mac OS?

To my understanding, the intent of the embeddable EJB 3.1 container is - among others - to support out-of-container testing. I've created a JUnit test case that uses glassfish embeddable for integration testing of ejb 3.1 Light ejbs. I run the tests using Maven.
I have one general problem and one problem specific to Mac OS (I'm not able to use the embeddable container at all on Mac OS).
1. First the general problem: the ejb container does not inject or publish classes that are on the test class-path only:
src>main>java>MyEjb.class
src>test>java>MyTestEjb.class
The test case looks like this:
public class TestCase1b {
     static EJBContainer container;
     @BeforeClass
     public static void initEjbContainer() {
          container = EJBContainer.createEJBContainer();
          for ( Object property : System.getProperties().keySet() ) {
          System.out.print(property + " : ");
          System.out.println(System.getProperty((String)property));
     @Test
     public void canTestWithTransaction() throws NamingException, NotSupportedException, SystemException {
          Context ctx = container.getContext();
          OrderServiceTesterEjb orderServiceTester = (OrderServiceTesterEjb) ctx
                    .lookup("java:global/classes/OrderServiceTesterEjb");
          Assert.assertNotNull(orderServiceTester.testCreateOrderWithTransaction());
     @AfterClass
     public static void closeEjbContainer() {
          container.close();
The idea with a test-ejb is to mimic the way I typically perform junit integration testing with Spring: the test database i preloaded with test data. Each test-method of the junit test case starts a transaction, invokes the service, evaluates the state of the database and finally performs a rollback. My idea was to mimic that by creating a test ejb (Stateless, REQUIRES_NEW), that injects the EJB to test, calls the method to test, evaluates the result or db state and finally sets rollbackonly before returning. The problem is that the test case can lookup ejbs in src/main/java, but not the "test" ejbs in src/test/java. My workaround is to include the test-EJBs in src/main/java which I think is not acceptable.
2. Next the Mac-problem:
The Mac OS JDK 1.6 contains version 1.0 of javax.annotation (jsr 250). EJBs developed with Java EE 6 depends on version 1.1 of javax.annotation. Specifically, one typically need @Resource(lookup=... and @DataSourceDefinition of javax.annotation.sql which are both missing in the JDK. I can compile my EJBs by adding the javaee-api-6.0.jar library to my classpath. But when running unit tests with maven (as described above), a runtime error is reported, stating that the lookup-property of the @Resource annotation is undefined. This is logical, since the boot classpath should have precedence. So I added javaee-api-6.0.jar to the lib/endorsed directory of the jre. Unfortunetely, this triggers a segmentation fault of the Mac OS JVM when running the test. I have no other workaround than switching to windows. Any help / hints are much appreciated.
/Johan

Just as an update, we're soon to release the WLS 11g R1 PS2 update, which will contain WLS 10.3.3 just to confuse things.
As part of that, we're distributing for the first time, an additional .zip version of WLS to make it easier for developers.
The zip file distribution has no GUI installer -- it's a simple case of unzip, run a script it provides, then start the server.
The zip file distribution has been specifically tested on Mac OS X and the WLS config/domain scripts automatically adjust as necessary for the Mac OS X java environment.
Once the zip file distribution is available, we hope that developing against WLS on Mac OS X (and Windows/Linux) will be an easier task.
-steve-

Error Occured While Creating message class 8II In SapNote 1486147

Dear All
I applied SapNote 1486147 but at the time of creating message class 8II
It shows error like this
Object MSAG 8II is in reserved name range for sap partner
Any body help on this.
Edited by: chandrap on Feb 24, 2011 2:08 PM

Hi Yasir,
remove the jaxb.jar from the WEB_INF/lib and move
them to your SUNWappserv/lib/endorsed - dir, together
with the following jars:
dom.jar jaxb-api.jar jaxb-impl.jar jaxb-libs.jar
jaxb-xjc.jar namespace.jar relaxngDatatype.jar
r xalan.jar
xercesImpl.jar xsdlib.jar
(restart the deploytool if used)
This should work,
Bas van OudenaardeHi Bas
Thank you for the very useful tip but I don't seem to have a SUNWappserv/lib/endorsed - directory inside my .war archive , could you please advise on this issue

Error in loading package in the application

Hi all,
We are getting an error in loading packages in our application.We are using oc4j.
The following is the error message we got.
Not Found
The requested URL /credit/pls/cnhcalms/add_new_customer.handleAction was not found on this server.
Thanks in advance.

Hi Rajat:
Thank you for the reply.
I had the xercers jars in jdk/jre/lib/endorsed directory.
If I remove these, the ejbql works. I do need these in there for a different reason. Is there any way I can have the xercers jars in jdk/jre/lib/endorsed directory and still the ejbql work on oc4j.
Thanks,
Sabu

Swapping XML Parser and XSLT to Xalan 2.7.0 - Not Working (OC4J 10.1.3)

Hi-
I'm trying to use the latest Xercies/Xalan classes in OC4J 10.1.3 as described in the How-To swap XML Parsers document:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html
What I can see happening is that the oracle.xml shared library is successfully 'turned off', but the xalan libraries are not added. Instead, the default xml classes that are distributed with the JDK become visible. For instance, using a slightly modified version of the index.jsp page from the how-to, I get this result:
------ Output from JSP page ----------------
TransformerFactory Instance: org.apache.xalan.processor.TransformerFactoryImpl
Transformer Instance: org.apache.xalan.transformer.TransformerIdentityImpl
Transformer Version: Xalan Java 2.4.1 (!!)
What I expect is for that last line to say version 2.7.0, which is the version of the xalan.jar included in my shared library (code to add that line to the how-to shown below).
I suspect what is happening is that the class loader is simply not letting a shared library override a system library - to do that you probably need to place the jar files in system endorsed directory.
Has anyone gotten this how-to to work - actually replacing the XML parser/transform classes with the latest Xalan classes? Are you sure it is seeing the current version you placed in the shared library?
Thanks,
Eric Everman
---- My modified getXSLTDetails() method in the index.jsp page of the how-to -------

<%@ page import="org.apache.xalan.Version" %>
public static String getXSLTDetails()
Transformer transformer=null;
TransformerFactory transformerfactory = TransformerFactory.newInstance();
     Version ver = null;
     String br = "<" + "br" + ">"; //otherwise the otn forum chocks on the break.
try
transformer = transformerfactory.newTransformer();
          ver = (Version) transformer.getClass().forName("org.apache.xalan.Version").newInstance();
          String ret_val =
               "TransformerFactory Instance: "+transformerfactory.getClass().getName() + br +
               "Transformer Instance: "+transformer.getClass().getName() + br;
          if (ver != null) {
               ret_val = ret_val + "Transformer Version: " + ver.getVersion() + br;
          } else {
               ret_val = ret_val + "Transformer Version not Available" + br;
          return ret_val;
catch (Exception e)
e.printStackTrace();
return e.getMessage();
}--------------------------------------------------------------------

Steve - Thanks for responding on this.
The Xalan SQL extension is built into Xalan. The most painless way to try it out is to run it via JEdit: www.jedit.org
JEdit a OS Java application with a fairly painless install process (I'm assuming you already have a current JRE installed). Once its installed, you'll need to install the XSLT plugin - in JEdit goto Plugins | Plugin Manager | Install and pick the XSLT plugin. You'll need the Oracle JDBC classes on your classpath - this can be done by copying the oracle_jdbc4.jar into the [JEdit install directory]/jars directory.
Restart to load that jar and you should be all set.
I included a sample XSLT page at the bottom of this post that is somewhat of a template transform for the SQL extension - its more complicated then it needs to be, but it does some nice things with the results of the query. Save it as a file and make the appropriate changes to the 'datasource' parameter near the top of the file.
Then in JEdit, open the file and make sure the XSLT plugin is visible (Plugins | XSLT | XSLT Processor Toggle - or alternately dock it in the window via global prefs). In the XSLT plugin: Allow the current buffer to be used as the source, Add that same file as a stylesheet via the '+' button, and pick a result file at the bottom. Then click the 'Transform XML' button.
Troubleshooting: I seem to remember having some classpath errors when I tried this on windows, but others have had it work w/o issues. I do remeber that the XSLT plugin had a popup window that gave a pretty good explaintion of the problem, if it occurs. Also, for some reason the XSLT plugin will not create a new file for the output, so its often best to create a file first, then choose it as the output. Of course, you can always run a transformation from the command line or w/in an applicatoin. Full docs on the Xalan SQL extension can be found at: http://xml.apache.org/xalan-j/extensionslib.html#sql
Here is my sample XSLT transform using the SQL extension:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
          xmlns:sql="http://xml.apache.org/xalan/sql"
          xmlns:str="http://exslt.org/strings"
          xmlns:xalan="http://xml.apache.org/xalan"
          extension-element-prefixes="sql str xalan">
     <xsl:output indent="yes"/>
     <xsl:param name="driver">oracle.jdbc.OracleDriver</xsl:param>
     <xsl:param name="datasource">jdbc:oracle:thin:jqpublic/jqpublic@server_name:1521:dbname</xsl:param>
     <xsl:param name="jndiDatasource"></xsl:param>
     <xsl:param name="debug">true</xsl:param>
     <xsl:variable name="connection" select="sql:new()"/>
     <xsl:variable name="uppercase" select="'ABCDEFGHIJKLMNOPQRSTUVWXYZ'"/>
     <xsl:variable name="lowercase" select="'abcdefghijklmnopqrstuvwxyz'"/>
     
     <xsl:param name="query">
     select * from (
SELECT
          'One' FIELD_1,
          'Two' FIELD_2
     FROM DUAL
     ) where rownum < 100
     </xsl:param>
     
     <xsl:variable name="connection" select="sql:new()"/>
     <xsl:template match="/">
    <xsl:choose>
      <xsl:when test="$jndiDatasource != ''">
        <xsl:if test="not(sql:connect($connection, $jndiDatasource))">
          <xsl:message>Failed to connect to db via jndi connection</xsl:message>
          <xsl:comment>Failed to connect to db via jndi connection</xsl:comment>
          <xsl:if test="$debug = 'true'">
            <xsl:copy-of select="sql:getError($connection)/ext-error"/>
          </xsl:if>
        </xsl:if>
      </xsl:when>
      <xsl:otherwise>
        <xsl:if test="not(sql:connect($connection, $driver, $datasource))">
          <xsl:message>Failed to connect to db via driver/url connection</xsl:message>
          <xsl:comment>Failed to connect to db via driver/url connection</xsl:comment>
          <xsl:if test="$debug = 'true'">
            <xsl:copy-of select="sql:getError($connection)/ext-error"/>
          </xsl:if>
        </xsl:if>
      </xsl:otherwise>
    </xsl:choose>
          
          <xsl:variable name="table" select="sql:query($connection, $query)"/>
          <xsl:if test="not($table)">
               <xsl:message>Error in Query</xsl:message>
               <xsl:copy-of select="sql:getError($connection)/ext-error"/>
          </xsl:if>
          <page>
               
               <xsl:copy-of select="xalan:checkEnvironment()"/>
               
               <meta>
                    <cols>
                         <xsl:apply-templates select="$table/sql/metadata/column-header"/>
                    </cols>
               </meta>
               <rowset>
                    
                    <xsl:apply-templates select="$table/sql/row-set"/>
               </rowset>
          </page>
          <xsl:value-of select="sql:close($connection)"/>
     </xsl:template>
     <xsl:template match="row">
          <row>
               <xsl:apply-templates select="col"/>
          </row>
     </xsl:template>
     <xsl:template match="column-header">
          <col>
               <xsl:attribute name="type">
                    <xsl:value-of select="@column-typename"/>
               </xsl:attribute>
               <xsl:attribute name="display-name">
                    <xsl:call-template name="create-display-name"/>
               </xsl:attribute>
               <xsl:value-of select="@column-name"/>
          </col>
     </xsl:template>
     
     <xsl:template name="create-display-name">
          <xsl:variable name="col-name">
               <xsl:for-each select="str:tokenize(@column-name, '_')">
                    <xsl:value-of
                         select="concat(translate(substring(., 1, 1), $lowercase, $uppercase), translate(substring(.,2), $uppercase, $lowercase), ' ')"/>
               </xsl:for-each>
          </xsl:variable>
          <xsl:value-of select="substring($col-name, 1, string-length($col-name) - 1)"/>
     </xsl:template>
     
     <xsl:template match="col">
          <col>
               <xsl:attribute name="column-name"><xsl:value-of select="@column-name"/></xsl:attribute>
               <xsl:value-of select="."/>
          </col>
     </xsl:template>
</xsl:stylesheet>

JAXB Problem: xjc gives an error

Hello everyone,
I would like to use JAXB to extract various information from a class of XML documents that conform to a schema. After tweaking the schema so that I avoid namespace conflicts with xjc, I settled the namespace conflicts, but I got the following error. Even if you don't have an answer, could you give me some pointers so that I can at least begin tackling the problem?
Thank you very much!
Here is the output of the command I ran:
C:\Documents and Settings\Berk Kapicioglu\Desktop>xjc -p test.jaxb ownership4ADocument.xsd.xml -d work
parsing a schema...
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused by: java.util.MissingResourceException: Can't find resource for bundle ja
va.util.PropertyResourceBundle, key parser.cc.8
at java.util.ResourceBundle.getObject(ResourceBundle.java:314)
at java.util.ResourceBundle.getString(ResourceBundle.java:274)
at com.sun.msv.datatype.xsd.regex.RegexParser.ex(RegexParser.java:138)
at com.sun.msv.datatype.xsd.regex.ParserForXMLSchema.parseCharacterClass
(ParserForXMLSchema.java:291)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseAtom(RegexParser.java
:736)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseFactor(RegexParser.ja
va:638)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseTerm(RegexParser.java
:342)
at com.sun.msv.datatype.xsd.regex.RegexParser.parseRegex(RegexParser.jav
a:320)
at com.sun.msv.datatype.xsd.regex.RegexParser.parse(RegexParser.java:158
at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
pression.java:3040)
at com.sun.msv.datatype.xsd.regex.RegularExpression.setPattern(RegularEx
pression.java:3051)
at com.sun.msv.datatype.xsd.regex.RegularExpression.<init>(RegularExpres
sion.java:3017)
at com.sun.msv.datatype.xsd.PatternFacet.compileRegExps(PatternFacet.jav
a:79)
at com.sun.msv.datatype.xsd.PatternFacet.<init>(PatternFacet.java:67)
at com.sun.msv.datatype.xsd.TypeIncubator.derive(TypeIncubator.java:261)
at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.restrictionSimpleT
ype(DatatypeBuilder.java:82)
at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
leTypeImpl.java:66)
at com.sun.tools.xjc.reader.xmlschema.DatatypeBuilder.build(DatatypeBuil
der.java:65)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.buildPrimitiveTy
pe(SimpleTypeBuilder.java:161)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.access$100(Simpl
eTypeBuilder.java:50)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.checkCon
version(SimpleTypeBuilder.java:201)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder$Functor.restrict
ionSimpleType(SimpleTypeBuilder.java:276)
at com.sun.xml.xsom.impl.RestrictionSimpleTypeImpl.apply(RestrictionSimp
leTypeImpl.java:66)
at com.sun.tools.xjc.reader.xmlschema.SimpleTypeBuilder.build(SimpleType
Builder.java:93)
at com.sun.tools.xjc.reader.xmlschema.cs.DefaultClassBinder.simpleType(D
efaultClassBinder.java:130)
at com.sun.xml.xsom.impl.SimpleTypeImpl.apply(SimpleTypeImpl.java:89)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector._bindToClass(Clas
sSelector.java:212)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.bindToType(ClassS
elector.java:177)
at com.sun.tools.xjc.reader.xmlschema.TypeBuilder.elementDeclFlat(TypeBu
ilder.java:213)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.elementDecl(FieldBuil
der.java:384)
at com.sun.xml.xsom.impl.ElementDecl.apply(ElementDecl.java:174)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.build(FieldBuilder.ja
va:76)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.part
icle(DefaultParticleBinder.java:399)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.applyRecursively(BGMBui
lder.java:490)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.mode
lGroup(DefaultParticleBinder.java:462)
at com.sun.xml.xsom.impl.ModelGroupImpl.apply(ModelGroupImpl.java:80)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.buil
d(DefaultParticleBinder.java:368)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.part
icle(DefaultParticleBinder.java:433)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder$Builder.buil
d(DefaultParticleBinder.java:371)
at com.sun.tools.xjc.reader.xmlschema.DefaultParticleBinder.build(Defaul
tParticleBinder.java:70)
at com.sun.tools.xjc.reader.xmlschema.ct.FreshComplexTypeBuilder$1.parti
cle(FreshComplexTypeBuilder.java:48)
at com.sun.xml.xsom.impl.ParticleImpl.apply(ParticleImpl.java:68)
at com.sun.tools.xjc.reader.xmlschema.ct.FreshComplexTypeBuilder.build(F
reshComplexTypeBuilder.java:35)
at com.sun.tools.xjc.reader.xmlschema.ct.ComplexTypeFieldBuilder.build(C
omplexTypeFieldBuilder.java:56)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.complexType(FieldBuil
der.java:228)
at com.sun.xml.xsom.impl.ComplexTypeImpl.apply(ComplexTypeImpl.java:194)
at com.sun.tools.xjc.reader.xmlschema.FieldBuilder.build(FieldBuilder.ja
va:76)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.build(ClassSelect
or.java:340)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.access$000(ClassS
elector.java:54)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector$Binding.build(Cla
ssSelector.java:107)
at com.sun.tools.xjc.reader.xmlschema.cs.ClassSelector.executeTasks(Clas
sSelector.java:240)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder._build(BGMBuilder.java:
118)
at com.sun.tools.xjc.reader.xmlschema.BGMBuilder.build(BGMBuilder.java:8
0)
at com.sun.tools.xjc.GrammarLoader.annotateXMLSchema(GrammarLoader.java:
424)
at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:130)
at com.sun.tools.xjc.GrammarLoader.load(GrammarLoader.java:79)
at com.sun.tools.xjc.Driver.run(Driver.java:177)
at com.sun.tools.xjc.Driver._main(Driver.java:80)
at com.sun.tools.xjc.Driver.access$000(Driver.java:46)
at com.sun.tools.xjc.Driver$1.run(Driver.java:60)

Hi,
A similar error occur to me twice.
One because pattern specification error (The pattern was incorrectly written)
The other one was because I had in the directory JAVA_HOME\jre\lib\endorsed the files that come from JWSDP_HOME\jaxb\lib.
This files (jaxb-api.jar, jaxb-impl.jar, jaxb-libs.jar, jaxb-xjc.jar) should only be in the directory where they come from JWSDP_HOME\jaxb\lib
If you have them in the JAVA_HOME\jre\lib\endorsed directory try removing them from there.
Hope I help you.

Error occured while creating WAR using DeployTool

Hi,
I am creating a webservice application. I used JAXB to create JAVA implementation of my XML schema. My webservice core is based on JAVA servlets. I have included all required JAXB API / implementation JARs into the lib directory. When I try to proceed from "Choose Component Type" screen in DeployTool I get the following error:
Unable to load servlet class specified in module.
Please consult online help for assistance.
java.lang.ClassNotFoundException: jp/co/swiftinc/relax/verifier/RELAXErrorHandler
I tried to search this file locally and on internet but couldn't find. Please help me how to avoid this problem during creation of war file. Thanx
Regards,
Yasir Khan

Hi Yasir,
remove the jaxb.jar from the WEB_INF/lib and move
them to your SUNWappserv/lib/endorsed - dir, together
with the following jars:
dom.jar jaxb-api.jar jaxb-impl.jar jaxb-libs.jar
jaxb-xjc.jar namespace.jar relaxngDatatype.jar
r xalan.jar
xercesImpl.jar xsdlib.jar
(restart the deploytool if used)
This should work,
Bas van OudenaardeHi Bas
Thank you for the very useful tip but I don't seem to have a SUNWappserv/lib/endorsed - directory inside my .war archive , could you please advise on this issue

Endorsed directory

Similar Messages

Maybe you are looking for