URGENT: JAXP Provider org.apache.crimson.jaxp.SAXParserFactoryImpl not foun

Hi all
I am having this strage problem. I am using JAXP Apis to do XSLT transformation and everything works fine.
But when I try the samething with
-Djava.security.manager option and
-Djava.security.policy==$WL_HOME/weblogic.policy option set it doesn't work. Stranger still the error it gives:
javax.xml.transform.TransformerException: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.crimson.jaxp.SAXParserFactoryImpl not found
This the command that works:
$JAVA_HOME/java -classpath $WL_CLASSPATH -Dintegration.config=$WL_HOME/integration.cfg com.swl.integration.translation.SendPRThread 24972 451
This one does NOT work:
$JAVA_HOME/java -ms64m -mx64m -verbosegc -classpath $WL_CLASSPATH -Djava.security.manager -Djava.security.policy=$WL_HOME/weblogic.policy -Dintegration.config=$WL_HOME/integration.cfg com.swl.integration.translation.SendPRThread 24972 451
I know it's something to do with Security manager/policy setting, but can't figure it out.
Could anyone please help? It is very urgent.
Thanks a lot
Mak

I have your solution... under Weblogic BEA were giving the same error, I resolved it with this code before the instantiation of SAXParserFactory:
String key = "javax.xml.parsers.SAXParserFactory"
String value = "org.apache.xerces.jaxp.SAXParserFactoryImpl";
Properties props = System.getProperties();
     props.put(key, value);
     System.setProperties(props);

Similar Messages

  • Exception :Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found

    Hi All,
    I run my application on Redhat Linux 2.4.9-e.27smp using java appname. I'm using JDK1.4.2 and am not using any app server. The app seems to run just fine for a few hours and then I start getting Exception :Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found exception out of blue. I run the app with following parameters -
    java -server -XX:+UseAdaptiveSizePolicy -Xverify:none -Xms512m -Xmx512m -XX:+UseParallelGC -XX:ParallelGCThreads=4
    I suspect this has to do with garbage collection and can't replicate this on will. I wonder if anyone has come across similar issue and is able to point me to the right direction.
    Thanks for any help,
    Vishal Bhasin

    Quick question. I am receiving the following error too:
    Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not found
    I am getting this error intermitently. Do you have any idea why this would happen. I am using an add on to a program.
    Thanks,
    Joe

  • Error: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found

    HI.
    I embed tomcat in my application.when i start embed tomcat ,the following message appears :
    javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found
    at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:99)
    at org.apache.commons.modeler.util.DomUtil.readXml(DomUtil.java:284)
    at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.execute(MbeansDescriptorsDOMSource.java:130)
    at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.loadDescriptors(MbeansDescriptorsDOMSource.java:120)
    i set System.setProperty("javax.xml.parsers.DocumentBuilderFactory", "org.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
    ,but not work.
    by the way :my classpath include xercesImpl.jar & xmlParserAPIs.jar, when i remove them ,my application
    work well.

    by the way my classpath include xercesImpl.jar & xmlParserAPIs.jar, when i remove them ,my application work well.
    Is another jar file which has the org.apache.xerces.jaxp.DocumentBuilderFactoryImpl clas in the Classpath.?

  • WL10.3.3 Console Provider org.apache.xalan.processor.TransformerFactoryImp

    Getting the following error:
    An error occurred during activation of changes, please see the log for details.
    [Management:141191]The prepare phase of the configuration update failed with an exception:
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    Note: we have the FOP added to the domain as a shared library with the following libraries:
    avalon-framework-cvs-20020806.jar
    batik.jar
    fop.jar
    xalan-2.4.1.jar
    xercesImpl-2.2.1.jar
    xml-apis.jar
    Note: Also, the shared libraries are not displaying referencing applications
    Edited by: SK Jennings on Nov 9, 2010 10:25 AM
    Added more info.

    Hi,
    I'm getting the same ClassCastException when I try to activate the changes of my EJB application. Were you able to resolve the error you were getting? Please let me know.
    Thanks

  • WL 10.3.3 Console org.apache.xalan.processor.TransformerFactoryImpl not fou

    Getting the following error:
    An error occurred during activation of changes, please see the log for details.
    [Management:141191]The prepare phase of the configuration update failed with an exception:
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    Note: we have the FOP added to the domain as a shared library with the following libraries:
    avalon-framework-cvs-20020806.jar
    batik.jar
    fop.jar
    xalan-2.4.1.jar
    xercesImpl-2.2.1.jar
    xml-apis.jar
    Note: Also, the shared libraries are not displaying referencing applications

    Getting the following error:
    An error occurred during activation of changes, please see the log for details.
    [Management:141191]The prepare phase of the configuration update failed with an exception:
    Provider org.apache.xalan.processor.TransformerFactoryImpl not found
    Note: we have the FOP added to the domain as a shared library with the following libraries:
    avalon-framework-cvs-20020806.jar
    batik.jar
    fop.jar
    xalan-2.4.1.jar
    xercesImpl-2.2.1.jar
    xml-apis.jar
    Note: Also, the shared libraries are not displaying referencing applications

  • NullPointerException at org.apache.crimson.parser.Parser2.parseInternal

    I've tried to use JavaTM API for XML Processing (JAXP), particulary default SAX parser,
    which is embeded into JAXP.
    I downloaded jaxp-1_1.zip file from http://java.sun.com/xml/download.html, extacted it
    and included crimson.jar, jaxp.jar and xalan.jar to java CLASSPATH.
    After that I'd tried to parse XML document
    with following code
         // prepare SAX parser
    SAXParserFactory factory = SAXParserFactory.newInstance();
    DefaultHandler handler = new XMLHandler();
    try {
    // Create a JAXP SAXParser
    SAXParser saxParser = factory.newSAXParser();
    // url
    File file = new File( fileName );
    String url = file.toURL().toString();
    System.out.println( "URL: " + url );
    // parse
    saxParser.parse( url, handler );
    } catch (Exception ex) {
    ex.printStackTrace();
    throw ex;
    and obtained the message below
    java.lang.NullPointerException
         at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:523)
         at org.apache.crimson.parser.Parser2.parse(Parser2.java:304)
         at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:433)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:346)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:232)
         at com.darout.bot.parser.PObjectsBuilder.parse(PObjectsBuilder.java:54)
         at TestSAXParser.main(TestSAXParser.java:22)
    Could you help me?

    I've found an error. It was in my handler implementation.
    But is it possible to trace a handler exception correctly?

  • Java.lang.ClassCastException: org.apache.crimson.tree.XmlDocument

    Hi all,
    i am new to java. I am trying to parse an xml document. the code is as follows:-
    Document document = null;
    DocumentBuilderFactory factory = ocumentBuilderFactory.newInstance();
    try {
         DocumentBuilder builder = factory.newDocumentBuilder();
         document = builder.parse( new File(xmlFile) );
    after this i am trying to traverse using treewalker :-
    Element docElem = document.getDocumentElement();
                   DocumentTraversal docTrav = (DocumentTraversal) document;
                   TreeWalker treeWalk = docTrav.createTreeWalker(docElem, NodeFilter.SHOW_ELEMENT, new ConfigNodeFilter(), false);
              Node node = treeWalk.nextNode();
    when i compile all is fine but while runnig it. i get the following error:-
    java.lang.ClassCastException: org.apache.crimson.tree.XmlDocument
    at - DocumentTraversal docTrav = (DocumentTraversal) document;.
    my import statements are as follows:-
    import java.io.File;
    import java.io.IOException;
    import java.net.InetAddress;
    import java.net.UnknownHostException;
    import java.util.Vector;
    import java.util.regex.Matcher;
    import java.util.regex.Pattern;
    import javax.servlet.Filter;
    import javax.servlet.FilterChain;
    import javax.servlet.FilterConfig;
    import javax.servlet.RequestDispatcher;
    import javax.servlet.ServletException;
    import javax.servlet.ServletRequest;
    import javax.servlet.ServletResponse;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    import javax.xml.parsers.ParserConfigurationException;
    import org.w3c.dom.Document;
    import org.w3c.dom.Element;
    import org.w3c.dom.Node;
    import org.w3c.dom.traversal.DocumentTraversal;
    import org.w3c.dom.traversal.NodeFilter;
    import org.w3c.dom.traversal.TreeWalker;
    import org.xml.sax.SAXException;
    i am not able to understand why the error is coming.
    any help will be appreciated.

    "In DOMs which support the Traversal feature, DocumentTraversal will be implemented by the same objects that implement the Document interface. "
    My guess is that the DOM parser you are using doesn't support the DocumentTraversal interface which is why you can not cast to that class.

  • Org.apache.crimson and 1.5

    I am trying to test an application in 1.5 and am getting compile errors for crimson references in classes someone else wrote.
    Looking at the JDK src, it looks like the apache packages are not bundeled in to the 1.5 beta.
    Wth the preface that I am mostly a Swing developer my questions are...
    I know it has to do with XML, but what specific functionality did crimson bring to the tale?
    Why did Sun remove the apache libs from the distribution?
    Is there anything in 1.5 to take crimsons place.
    Thanks for your time if you answer,
    Todd

    Looking at the JDK src, it looks like the apache
    packages are not bundeled in to the 1.5 beta.That's correct. The only contract is to supply an XML processor, not a specific one. Crimson is just one; Xerces is the most popular one out there. Looks like 1.5 includes a subset of Xerces (with a different package - com.sun.org.apache.xerces.internal).
    I know it has to do with XML, but what specific
    functionality did crimson bring to the tale?Nothing special. It was just a lightweight XML implementation.
    Why did Sun remove the apache libs from the distribution?
    Is there anything in 1.5 to take crimsons place.It's just replaced them with something they felt they could maintain better.
    You should not ever be referring to Crimson classes directly. You should ONLY use org.w3c.dom or org.w3c.sax classes directly, and use the advertised Factory APIs to create or manipulate Documents, Elements, etc.
    Your best bet is to rip out all references to org.apache.crimson, and use an elementary XML textbook to replace them with references to standard org.w3c.* classes.

  • Org.apache.tomcat.TcpConnection source not found error.

    Hi,
    When I tried to remotely debug a servlet with Sun's J2EEServer, instead of stopping at the breakpoint the Jdev31 stopped at this line:
    //JDeveloper API Decompiler STUB ...
    and when I pressed F8 a messagebox appeared:
    org.apache.tomcat.TcpConnection source not found.
    I think that I have missed someting installing the JDev.
    Your prompt help is higly appreciated,
    Reza

    Hi,
    I just had the same problem and navigated to this page here in hope for a solution...
    However I've solved the problem now. On Eclipse, do the following.
    1) Right-click on the added Jar-file (which is producing the problem)
    2) On the popup-menu choose "Build Path" and "Configure Build Path..."
    3) On the opening preference window, click the checkbox of the Jar
    This is probably necessary because the jar has to be exported such that the simulator is able to execute it.
    Greets,
    Juri
    http://juri-strumpflohner.blogspot.com

  • Org.apache.struts.action.ActionServlet not found in web-application

    Dear All,
    I am new to ADF environment. I tried to create a simple page to show the records from
    a table . I followed the sample application which is available in "Building Oracle ADF Applications: Workshop".
    When i run my action from Struts Page Flow. It is giving error like
    500 Internal Server Error
    Servlet error: Error instantiating servlet 'action'. Servlet class org.apache.struts.action.ActionServlet not found in web-application EmpMaintanance-ViewController-webapp
    anybody can suggest me What i missed?
    Thanks in advance...

    Hi,
    you need to register libraries with th OC4J configuration files. However, you can also deploy the Struts library with you application (see OC4J documentation which is accessible on OTN via Oracle As documentation), in which case they are available from the application classpath
    Frank

  • Org.apache.crimson.tree.DomEx: INVALID_CHARACTER_ERR:

    I am using XML to create an element.
    It fails when I try to create with numbers.
    node = doc.createElement("111");
    why is that?

    So, you think it would be valid to have the following:
    <document>
      <1 1 1>some text</1 1 1>
    </document>That is what you are asking for. The String you specify in the createElement is the tagname. Tagnames cannot have spaces in them. I don't have a reference with me, but I don't think they can start with a numeric.
    How is "node" defined? Did you mean node = doc.createTextNode("1 1 1");
    That should work.
    Dave Patterson

  • Urgent: Why org.apache.tomcat.* package does not exist?

    i am writing some programs about ldap
    my program code has used some packages as the followings
    import org.apache.tomcat.core.*;
    import org.apache.tomcat.util.*;
    import org.apache.tomcat.util.xml.*;
    i am using apache + tomcat4.1 server, jsdk1.4
    i have set the classpath that contains all the jar files in $TOMCAT_HOME\common\lib
    after setting the classpath, i compiled the code
    it said the above packages does not exist
    where should i find those packages?
    Aren't they in the tomcat i installed?
    PLX HELP

    for example, i want to use the class
    org.apache.tomcat.core.Context to create a class
    object.Then you would want to:
    import org.apache.tomcat.core.Context;
    -or-
    import org.apache.tomcat.core.*;
    Note how that is different than your original:
    import org.apache.tomcat.*;i just use as an example import org.apache.tomcat
    but i cannot find org.apache.tomcat.core or even any org.apache.tomcat.*
    so that means i havn't include the correct jar file in the classpath or no corresponding package are stored in the tomcat4.1
    i just want to know what jar file contains such stuff.
    i think it should be a silly problem. So there should be someone know it.

  • Java.lang.NoClassDefFoundError: org/apache/xerces/parsers/SAXParser

    We are trying to evaluate Weblogic 6.1 Beta version.
    We have tried a setup that is working in WebLogic 6.0 sp1 version,
    but the same setup fails in the Beta version.
    We get ...
    java.lang.NoClassDefFoundError:
    org/apache/xerces/parsers/SAXParser
    We had not specified any addl. jars in the classpath
    in 6.0 sp1 version. But this fails in the Beta version.
    Could someone tell if this is a known bug in the Beta release and
    suggest a solution or tell if this will be fixed in the actual version
    when it is
    released in July?
    Thanks.
    -Arvind

    "Jeeva" <[email protected]> wrote in message
    news:3b40ecb5$[email protected]..
    >
    Alternatively u can set the parameters to look at the right parser when uneed
    it. This can be done by:
    System.setProperty("javax.xml.parsers.SAXParserFactory","org.apache.xerces.jaxp.SAXParserFactoryImpl");
    System.setProperty("javax.xml.parsers.DocumentBuilderFactory","org.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
    System.setProperty("javax.xml.parsers.SAXParser","org.apache.xerces.jaxp.SAXParserImpl");
    This is far from being recommended for the following reason:
    The JAXP factories cache the classes used to instantiate the factories,
    therefore you cannot changed dynamically these properties at runtime, you
    will have absolutely NO guarantee that this will work. If a factory is
    instantiated before yours, it will use this one. Additionaly, Weblogic
    already defines these properties at startup so that they refer to their own
    factories that can look into the XML registry.
    Consider these properties as being read-only. Chance are that you will mess
    up everything if you modify them.
    If you need to define a specific parser (such as crimson), then put crimson
    in your system classpath and set the XML registry appropriately.
    If you want to take a look at jaxp strategy. Use the JVM
    property -Djaxp.debug=true.
    As well use -Dweblogic.xml.debug=true for Weblogic XML related info.
    Stéphane Bailliez
    Software Engineer, Paris - France
    iMediation - http://www.imediation.com
    Disclaimer: All the opinions expressed above are mine and not those from my
    company.

  • ClassCastException: org.apache.openjpa.persistence.PersistenceProviderImpl

    I'm running into a ClassCastException (see below) when trying to deploy a EJB application. I'm using WebLogic 10.3.4 and have the following PRE_CLASSPATH variable set in my wlserver_10.3\common\bin\commEnv.cmd script.
    set PRE_CLASSPATH=%BEA_HOME%\modules\javax.persistence_1.0.0.0_2-0-0.jar;%BEA_HOME%\modules\com.oracle.jpa2support_1.0.0.0_2-0.jar
    My EJB application is trying to use the latest/current OpenJPA 2.0.1 and my ejb.jar has a Class-path specified in its META-INF/MANIFEST.MF file, pointing to a provided open-all-2.0.1.jar. This openjpa-all-2.0.1.jar library file is packaged at the ear application level.
    I would really like to use the latest/current OpenJPA 2.0.1 as mentioned above - instead of the Weblogic provided OpenJPA snapshot but for the purpose of testing ... If I don't provide the ebj.jar a Class-path and don't package the open-all-2.0.1.jar lib in my ear, I'll get the ClassNotFoundException error (Error processing persistence unit oraexeu of module ReportBrokerService.jar: Error instantiating the Persistence Provider class org.apache.openjpa.persistence.PersistenceProviderImpl of the PersistenceUnit oraexeu: java.lang.ClassNotFoundException: org.apache.openjpa.persistence.PersistenceProviderImpl). It doesn't matter if I specify <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider> in my persistence.xml or not.
    My weblogic-application.xml file contains the followings. Please ignore the jws and xml stuffs as I'm also using cxf and know it currently works. The only change I recently added to this weblogic-application.xml file is the javax.persistence.* line:
         <prefer-application-packages>
              <package-name>org.apache.*</package-name>
              <package-name>javax.persistence.*</package-name>
              <package-name>javax.jws.*</package-name>
              <package-name>javax.xml.ws.*</package-name>
              <package-name>org.xmlsoap.schemas.wsdl.*</package-name>
         </prefer-application-packages>
    It appears there is some conflict between my provided openjpa-all-2.0.1.jar and the WebLogic provided OpenJPA snapshot (a.k.a. org.apache.openjpa_1.2.0.0_1-1-1-SNAPSHOT.jar) shipped w/ this version of WebLogic 10.3.4.
    I'll appreciate very much any suggestion to fix this issue while still having my application uses the latest openjpa-all-2.0.1.jar. Although the case of ClassNotFoundException is really troublesome ... Should it work w/o my openjpa-all-2.0.1.jar?
    ***** ClassCastException - w/ the open-all-2.0.1.jar packaged in the application ear file and a Class-path specified in the ejb.jar manifest file
    ####<Jan 28, 2011 5:45:14 PM EST> <Error> <Deployer> <CHQDFFD46S0CF1> <examplesServer> <[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296254714529> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1296254714029' for task '5'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(ReportBrokerService.jar)
    weblogic.application.ModuleException: Exception preparing module: EJBModule(ReportBrokerService.jar)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:614)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused By: weblogic.deployment.EnvironmentException: Error processing persistence unit oraexeu of module ReportBrokerService.jar: Error instantiating the Persistence Provider class org.apache.openjpa.persistence.PersistenceProviderImpl of the PersistenceUnit oraexeu: java.lang.ClassCastException: org.apache.openjpa.persistence.PersistenceProviderImpl
         at weblogic.deployment.BasePersistenceUnitInfoImpl.getPersistenceProvider(BasePersistenceUnitInfoImpl.java:375)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:386)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.<init>(BasePersistenceUnitInfoImpl.java:158)
         at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:39)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:349)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:263)
         at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:69)
         at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:223)
         at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:324)
         at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:393)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    >
    ####<Jan 28, 2011 5:45:14 PM EST> <Warning> <Deployer> <CHQDFFD46S0CF1> <examplesServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296254714558> <BEA-149004> <Failures were detected while initiating deploy task for application 'ReportBrokerService'.>
    ####<Jan 28, 2011 5:45:14 PM EST> <Warning> <Deployer> <CHQDFFD46S0CF1> <examplesServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1296254714558> <BEA-149078> <Stack trace for message 149004
    weblogic.application.ModuleException: Exception preparing module: EJBModule(ReportBrokerService.jar)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:614)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused By: weblogic.deployment.EnvironmentException: Error processing persistence unit oraexeu of module ReportBrokerService.jar: Error instantiating the Persistence Provider class org.apache.openjpa.persistence.PersistenceProviderImpl of the PersistenceUnit oraexeu: java.lang.ClassCastException: org.apache.openjpa.persistence.PersistenceProviderImpl
         at weblogic.deployment.BasePersistenceUnitInfoImpl.getPersistenceProvider(BasePersistenceUnitInfoImpl.java:375)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:386)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.<init>(BasePersistenceUnitInfoImpl.java:158)
         at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:39)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:349)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:263)
         at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:69)
         at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:223)
         at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:324)
         at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:393)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    >
    ####<Jan 28, 2011 5:45:14 PM EST> <Error> <Console> <CHQDFFD46S0CF1> <examplesServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <3405a5edc0400a9a:-6936f90f:12dcec06131:-8000-000000000000007b> <1296254714805> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Exception preparing module: EJBModule(ReportBrokerService.jar)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:469)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:518)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:47)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:614)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:208)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    Caused by: weblogic.deployment.EnvironmentException: Error processing persistence unit oraexeu of module ReportBrokerService.jar: Error instantiating the Persistence Provider class org.apache.openjpa.persistence.PersistenceProviderImpl of the PersistenceUnit oraexeu: java.lang.ClassCastException: org.apache.openjpa.persistence.PersistenceProviderImpl
         at weblogic.deployment.BasePersistenceUnitInfoImpl.getPersistenceProvider(BasePersistenceUnitInfoImpl.java:375)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:393)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.initializeEntityManagerFactory(BasePersistenceUnitInfoImpl.java:386)
         at weblogic.deployment.BasePersistenceUnitInfoImpl.<init>(BasePersistenceUnitInfoImpl.java:158)
         at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:39)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:349)
         at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:263)
         at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:69)
         at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:223)
         at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:324)
         at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:393)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
         at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)

    Hi,
    I'm getting the same ClassCastException when I try to activate the changes of my EJB application. Were you able to resolve the error you were getting? Please let me know.
    Thanks

  • Import org.apache.xml.serialize.*;

    .java:66: package org.apache.xml.serialize does not exist
    import org.apache.xml.serialize.*;
    ^
    i am getting this error while running a java program, which i downloaded from a open source.
    i am using J Creator.
    i suppose i need to add a class path or package.
    can anybody tell me how to do this.
    and where can i find that package.
    if i can't find that in my system, where can i get it on net.

    .java:66: package org.apache.xml.serialize does notThe org.apache.xml.serialize.* package is part of Xerces:
    http://xml.apache.org/xerces-j/
    http://xml.apache.org/xerces2-j/index.html

Maybe you are looking for