Hanging jaxp-1.0.1-parser

We have a bug with a hanging jaxp-parser. Unfortunately the bug is not reproducable, but returns sporadically with serious effects.
We have a permanently running java program, that creates separate worker threads. These threads handle ssl-requests. A request has a xml-format and contains a cdata-section with a base64-coded file in that section. First we read the request in a temporary Unix file. Then we parse the file with a SAX-parser (jaxp.jar, jaxp-1.0.1). The parser parses the file and reads the cdata section. The bug is, that after having read a good part of the cdata section, the parser hangs. At least the parser seems to hang. The java program consumes more and more cpu, so that it seems, that the parser is "actively waiting". The first time, we saw this phenomenon was 6 months ago. At that time we switched from JRE1.2 to JRE1.3. The program had run for 3 years with JRE1.2 without any problems. The bug occurs rarely (only once or twice a day with more than 2000 parsed files a day), but the effect is very serious.
Does any one have an idea?
The idea to replace jaxp-1.0.1 by xerces-j-2.7.1 was discarded because the performance is much worse.
Thanks for your ideas.

JAXP 1.0 does not support schema validation.
JAXP 1.1 & JAXP 1.2 support schema validation.

Similar Messages

JAXP support in XML Parser for Java

Was curious if there were any plans to support JAXP in the XML Parser for Java. Sun's licensing terms was a serious issue of contention when Apache was trying to implement the spec and finally got an exemption from Sun to some of the terms.

The value of JAXP is that it allows one to
freely switch parsers without changing any code. I have an application that uses the JAXP interfaces to create my DOM parser. I am using the Xerces-J parser now. I wanted to try Oracle's parser to see how it compares. To my great surprise, I found the Oracle DOM parser doesn't support JAXP. Because of this I have to CHANGE my code to user the Oracle DOM parser. Thus defeating the purpose of coding my app to the JAXP interface.
I have to add that I am surprised to see that a developer of Oracle's XML parser has to even ask what the value of JAXP is. I would think that being a parser developer, you would know and understand the value of JAXP.
I would like to know why Oracle has chosen not to support JAXP? Or have you just not even thought about whether or not you should support it.
Thanks,
Keith Jensen
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Steven Muench ([email protected]):
What is the perceived value in implementing the JAXP standard? We already implement SAX, have plans for SAX2, and are working with other XSLT vendors on the TRAX api for XSLT processors.
If there is strong customer demand, we'll clearly consider it, but at the moment that has not been the case.<HR></BLOCKQUOTE>
null

URGENT: javax.xml.parsers.DocumentBuilder.parse() method issue

Hi folks,
I have an urgent parsing problem. I developed an app with JDK1.4 and now it needs to run on JDK1.3.1. The problem is this:
If I use the DocumentBuilder.parse() method shipped with JDK1.4 it will parse a document containing namespaces WITHOUT a namespace declaration in the root element. However, since XML support doesn't ship with JDK1.3.1 I need to use JAXP. If I try this with the DocumentBuilder.parse() version shipped with JAXP (latest version) the parse method throws a NullPointerException. If I put the namespace declaration in the document it will parse fine. I tried setting the DocumentBuilderFactory.setNamespaceAware() explicitly to false (should be the default) but no luck. Any ideas other than adding the declaration (long story why I don't want it there...)
thanks

example, with declaration of namespace:
<?xml version="1.0" encoding="UTF-8"?>
<pre:root xmlns:inn="http://blablabla/inn/version/1.0/">
<pre:metadata>
<pre:dublin-core>
<pre:title>mytitle</pre:title>
<pre:description>mydesc</pre:description>
<pre:creator>bjmann</pre:creator>
</inn:dublin-core>
</pre:root>
example, without declaration:
<?xml version="1.0" encoding="UTF-8"?>
<pre:root>
<pre:metadata>
<pre:dublin-core>
<pre:title>mytitle</pre:title>
<pre:description>mydesc</pre:description>
<pre:creator>bjmann</pre:creator>
</inn:dublin-core>
</pre:root>
this may help...

?xml version = '1.0' encoding = 'ASCII'? pl/sql xml parser

When ever I parse a document which has the
<?xml version = '1.0' encoding = 'ASCII'?> tag as the first line hangs the pl/sql xml parser . If I remove the "encoding = 'ASCII'" from the file everything works fine ! What is the problem ?
version 8.1.6 / plsql parser v2 / hpux 11x
Here is the input file
<?xml version = '1.0' encoding = 'ASCII'?>
!--- This is a comment -->
<person>
<employee>
<lastname>GHANTASALA</lastname>
<firstname>SREE</firstname>
<age>32</age>
</employee>
<employee>
<lastname>TAMATAM</lastname>
<firstname>SATISH</firstname>
<age>30</age>
</employee>
</person>
Here is my program
declare
p xmlparser.parser;
doc xmldom.DOMDocument;
dir varchar2(100) := '/apps/oracle/drugstore';
errfile varchar2(30) := 'err.txt' ;
inpfile varchar2(30) := 'person.xml';
nl xmldom.DOMNodeList;
len number;
n xmldom.DOMNode;
new_node xmldom.DOMNode;
node_name varchar2(100);
node_value varchar2(100);
begin
-- new parser
p := xmlparser.newParser;
-- Set some characteristics
xmlparser.setValidationMode(p, FALSE);
xmlparser.setErrorLog(p, dir| |'/'| | errfile );
xmlparser.setBaseDir(p, dir);
-- parse input file
xmlparser.parse(p, dir| |'/'| |inpfile);
-- get document
doc := xmlparser.getDocument(p);
-- get all elements
nl := xmldom.getElementsByTagName(doc, '*');
len := xmldom.getLength(nl);
dbms_output.put_line('Length='| |len);
-- loop through elements
for i in 0..len-1 loop
n := xmldom.item(nl, i);
node_name := xmldom.getNodeName(n);
-- get the text node associated with the element node
n := xmldom.getFirstChild(n);
if xmldom.getNodeType(n) = xmldom.TEXT_NODE then
node_value := xmldom.getNodeValue(n);
if node_name='lastname' then
dbms_output.put_line('The value you are looking for is -->:'| |node_value);
if node_value = 'GHANTASALA' then
xmldom.setNodeValue(n,'TEST2');
end if;
end if;
end if;
end loop;
new_node := xmldom.makeNode(doc);
xmldom.writeToFile(new_node, dir | |'/'| |'mod.xml');
end ;
null

The encoding header is actually generated by
by the following piece of code in my pl/sql program .
new_node := xmldom.makeNode(doc);
xmldom.writeToFile(new_node, dir | |'/'| |'mod.xml');
Since this is a document created by the pl/sql parser, I assume there is some meaning to it !
Also why is it hanging ? PL/sql parser should tell me that it is not a valid string !

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?

Use of Xerces Parser in out application with Oracle App Server 9.0.4

The problem in brief:
Our product is a web-app that runs under various Application servers.
One of our customers who uses Oracle App server, recently upgraded from 9.0.2 (9g) to 9.0.4 (10g), and our product no longer works with the latter version.
Our product uses XML parser Xerces 1.1.
In 9.02 it was possible to replace the App servers parser with Xerces 1.1. In 9.02 it was possible to replace the App servers parser with Xerces 1.1 (We modified the opmn.xml file, setting the Java options for our oc4j instance bootclasspath with xerces parser). Hence, our product works.
In 9.0.4, apparently, Oracle moved to a different parser, and it no longer allows the parser to be replaced. If the bootclasspath is modified with XERCES(tested various versions of xerces) parser, rightfully so ORACLE Application server does not start.
Unlike other prominent Application Servers (such as webshpere etc,) the Oracle application server does not support separate JVMs or namespaces for web-apps either.
We like, oralce application server, OC4J instance for our application to use the xerces parser version qualified with our product. We understand, replacing the XML parser for the entire Oracle Application Server is not supported function.
Since, Oracle Application Server is loading the oracle 'xmlparserv2' at system class path, though the applicaton has xerces.jar in application path (either in AppLib or web-inf/lib directory, Its not a class loading issue) it is not getting used (since javax.xml.parsers.documentbuilderFactory is mapped to oracle parser).
So, it looks like the only option available to us is to modify our product to use Oracle's XML parser. This is a major software change, and we want to keep it as last resort option.
Any suggestion and help will be higly appreciated.
Perraju Nadakuduty (raju)
E-mail:[email protected]

Raju --
Thanks for the intelligent posting on a difficult issue for you.
I wasn't aware of anything specifically being introduced that prevented the bootclasspath technique from working** in the 904 release.
For 904, the bootclasspath needs to be put in the start parameters tag of the java-options tag.
<process-type id="home" module-id="OC4J" status="enabled">
<module-data>
<category id="start-parameters">
<data id="java-options" ... -Xbootclasspath/a:/java/lib/xerces.jar"/>
</category>
</module-data>
</process-type>
You can also try copying the xerces.jar into the jre/lib/ext directory so it's loaded by the system classloader and see if that works**. This will put xerces at the extension level so
**these workarounds are not supported and will put you in an unsupported situation if a problem occurs.
The good news is that have taken steps to clearly enable the separation of container versus appplication class spaces in thenext production release (10.1.3) of OC4J. We will be providing a new classloading model which cleanly separates the two namespaces and allows applications to provide their own versions or distributions of class libraries with no collisions with the OC4J runtime libraries.
I don't know of any easy ways to do what you need -- other than reworking the app to use JAXP so that the parser implementation used is pluggable as you kind of allude to. If it was possible, I'd do that rather than hard coding in the use of the Oracle XML parser.
But just to reiterate, switching in xerces at the bootclasspath level is not a supported operation since it may have an effect on the OC4J runtime operation.
cheers
-steve-

Parser questions...

Is the parser included with weblogic validating?
Is there SAX2 support?
Thanks,
Serge Monkewitz

Hi Serge,
In WebLogic 5.1.0, the weblogicaux.jar includes the Sun "Project X TR 2"
parser which is validating. In the upcoming (later this month) 5.1.1, we
will be including JAXP along with the Sun XML parser that is included
with Sun's JAXP release. That parser is basically the Project X parser
with some bug fixes and is therefore also validating. Neither support
SAX2. Of course, you can use any XML parser with WebLogic server, if the
Sun one doesn't suit your needs.
Regards,
-Todd
Serge Monkewitz wrote:
>
Is the parser included with weblogic validating?
Is there SAX2 support?
Thanks,
Serge Monkewitz--
Todd Karakashian
BEA Systems, Inc.
[email protected]

JAXP whitespace prob

Hi
This is for my final year project and all was going swell until I hit what should be a straighforward error and can't get around it.
I'm using JAXP to try and parse out the paragraph from an HTML doc and so get the default handler to look for the <p> tag, but iget the following error
org.xml.sax.SAXParseException: Missing whitespace before SYSTEM literal URI.
from the following section of code
     ParagraphParser p = new ParagraphParser();
     try
          // Create a JAXP SAXParserFactory and configure it
          SAXParserFactory spf = SAXParserFactory.newInstance();
          // Create a JAXP SAXParser
          SAXParser sax = spf.newSAXParser();
          File elephant = new File("/home/S99/sterna9/project", "javalinks.html");
If anyone can help or can suggest a better alternative prob all help will be welcomed.
thanks anthony
ps the whole class is below it is not long have a look
package parsers;
* ParagraphParser.java
* Created: Fri Feb 15 13:44:43 2002
* @author Anthony Stern
* @version
import Constants;
import javax.xml.parsers.*;
import org.xml.sax.*;
import org.xml.sax.helpers.*;
import java.io.*;
import java.util.Map;
import java.util.HashMap;
import java.lang.Integer;
public class ParagraphParser extends DefaultHandler {
private boolean inParagraph;
private Map paragraphs;
private int paraCount;
public ParagraphParser ()
     inParagraph = false;
     paragraphs = new HashMap();
     paraCount = 0;
public void startElement(String namespaceURI, String localName,
String elementName, Attributes atts)
     throws SAXException
     if (elementName.equals("P"))
          inParagraph=true;
public void characters(char [] buf, int offset, int len)
     String s = new String(buf, offset, len);
     if (inParagraph)
          Integer paracount = new Integer(paraCount);
          paragraphs.put(paracount, s);
          paraCount++;
          if(Constants.DEBUG)System.out.println("The Paragraph " + s + "is in");
public static void main(String[] args)
     ParagraphParser p = new ParagraphParser();
     try
          // Create a JAXP SAXParserFactory and configure it
          SAXParserFactory spf = SAXParserFactory.newInstance();
          // Create a JAXP SAXParser
          SAXParser sax = spf.newSAXParser();
          File elephant = new File("/home/S99/sterna9/project", "javalinks.html");
          sax.parse(elephant, p);
          catch(ParserConfigurationException pce)
               System.out.println("ParserConfigurationException");
               pce.printStackTrace();
     catch(SAXException se)
          System.out.println("SAXException");
          se.printStackTrace();
     catch (IOException ioe)
System.err.println(ioe);
System.exit(1);
}// ParagraphParser

org.xml.sax.SAXParseException has methods to get at where your XML parse is breaking down - see the API for methods:
int getColumnNumber()
int getLineNumber() Then modify your code to print those out, as well as the exception, then take a look at your XML at that line/column.

Problem with Persistence.xml in JDev final after migration

Hi,
I am trying to migrate a current project from JDev 11gTp4 to the JDev production release. When deploying the EJB module I get the following problem though (Stack from DefaultServer.log)
weblogic.application.ModuleException: Exception preparing module: EJBModule(Nexus-NexusModel-ejb)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
     at javax.xml.parsers.DocumentBuilderFactory.setSchema(DocumentBuilderFactory.java:561)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.setupDocumentBuilderFactory(RegistryDocumentBuilder.java:393)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.getDefaultDocumentBuilderFactory(RegistryDocumentBuilder.java:359)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.getDocumentBuilder(RegistryDocumentBuilder.java:298)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:150)
     at org.eclipse.persistence.platform.xml.jaxp.JAXPParser.parse(JAXPParser.java:163)
     at org.eclipse.persistence.platform.xml.jaxp.JAXPParser.parse(JAXPParser.java:197)
     at org.eclipse.persistence.internal.oxm.record.DOMUnmarshaller.unmarshal(DOMUnmarshaller.java:213)
     at org.eclipse.persistence.oxm.XMLUnmarshaller.unmarshal(XMLUnmarshaller.java:309)
     at org.eclipse.persistence.internal.jpa.metadata.xml.XMLEntityMappingsReader.read(XMLEntityMappingsReader.java:72)
     at org.eclipse.persistence.internal.jpa.metadata.xml.XMLEntityMappingsReader.read(XMLEntityMappingsReader.java:112)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.loadStandardMappingFiles(MetadataProcessor.java:343)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.loadMappingFiles(MetadataProcessor.java:271)
     at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:294)
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:830)
     at org.eclipse.persistence.jpa.PersistenceProvider.createContainerEntityManagerFactory(PersistenceProvider.java:189)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:330)
     at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:123)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:331)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptor(AbstractPersistenceUnitRegistry.java:245)
     at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:63)
     at weblogic.ejb.container.deployer.EJBModule.setupPersistenceUnitRegistry(EJBModule.java:209)
     at weblogic.ejb.container.deployer.EJBModule$1.execute(EJBModule.java:310)
     at weblogic.deployment.PersistenceUnitRegistryInitializer.setupPersistenceUnitRegistries(PersistenceUnitRegistryInitializer.java:62)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:376)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
My persistence.xml looks like
<?xml version="1.0" encoding="windows-1252" ?>
<persistence xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
version="1.0" xmlns="http://java.sun.com/xml/ns/persistence">
<persistence-unit name="Nexus-ejbPU">
<provider>
org.eclipse.persistence.jpa.PersistenceProvider
</provider>
<jta-data-source>
jdbc/NexusPoolDS
</jta-data-source>
<mapping-file>
META-INF/orm.xml
</mapping-file>
<properties>
<property name="eclipselink.target-server" value="WebLogic_10"/>
<property name="eclipselink.logging.file" value="Toplink.log"/>
<property name="eclipselink.logging.timestamp" value="true"/>
<property name="eclipselink.logging.exceptions" value="true"/>
<property name="eclipselink.logging.session" value="true"/>
</properties>
</persistence-unit>
</persistence>
orm.xml looks like this
<?xml version="1.0" encoding="windows-1252" ?>
<entity-mappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_1_0.xsd"
version="1.0"
xmlns="http://java.sun.com/xml/ns/persistence/orm">
<persistence-unit-metadata>
<persistence-unit-defaults>
<schema>
XXX
</schema>
</persistence-unit-defaults>
</persistence-unit-metadata>
<package>
za.co.medscheme.model.persistence.xxx
</package>
<schema>
XXX
</schema>
</entity-mappings>
I have noticed that the persistence.xml file have changed quite drastically from the version we had in TP4 release during project upgrade, but can not explain the problem we are getting. I have also tried to just create a dummy project and create a persistence unit, and the file looks exactly the same afterwards. Any thoughts?
Drikus

Just thought I would add a temporary solution to the problem for those of you sitting with the same issue.
In the root folder of your application you will find a src folder with a meta-inf folder and weblogic-application.xml inside.
Add the following before the closing weblogic-application tag...
<xml>
<parser-factory>
<saxparser-factory>
weblogic.xml.jaxp.WebLogicSAXParserFactory
</saxparser-factory>
<document-builder-factory>
weblogic.xml.jaxp.WebLogicDocumentBuilderFactory
</document-builder-factory>
<transformer-factory>
weblogic.xml.jaxp.WebLogicSAXTransformerFactory
</transformer-factory>
</parser-factory>
</xml>
If there wasnt an xml tag in the file, it seems that JDeveloper somehow adds one on the fly for you pointing to an oracle xml parser that does not contain the setSchema method required by weblogic on deployment.
Hope this helps anybody else that has this problem.
Regards
Drikus Britz

Problem while Consuming Java Webservice from WCF client

Hi,
I am trying to Consume Java Webservice from WCF client.The webservice main functionality is digital data management.The client can Query Digital data and upload digital data by calling webservice methods.Problem is when i am trying to call webmethod from WCF client its giving "Unrecognised message versions".I have no idea about how the message objects are processed at serverside.but at server side they have used JAXP for XML document parsing.
The response content type is Multipart/related and applicatio/XOP+XML.
Can u plz help me how to handle this situation.I have minimum knowledge in Java WS architecture.Basically i am .Net programmer.
Can U please guide me in a proper way to resolve the problem.

Hi Abinash,
I have the same problem. Have you solve that problem?
I am using a java program to call a webservice too. And I have generated the client proxy definition for Stand alone proxy using NWDS. When I call the method of the webservice I am getting the correct result but along with the result I am getting one error and one warning message in the output.
The java code to call the webservice is as follows.
MIDadosPessoaisSyncService service = new MIDadosPessoaisSyncServiceImpl();
MIDadosPessoaisSync port = service.getLogicalPort("MIDadosPessoaisSyncPort");
port._setProperty("javax.xml.rpc.security.auth.username","xpto");
port._setProperty("javax.xml.rpc.security.auth.password","xpto");
String out = port.MIDadosPessoaisSync("xpto", "xpto");
System.out.println(out);
The result I am getting is :
Warning ! Protocol Implementation [com.sap.engine.services.webservices.jaxrpc.wsdl2java.features.builtin.MessageIdProtocol] could not be loaded (NoClassDefFoundError) !
Error Message is :com/sap/guid/GUIDGeneratorFactory
<b>The result of the WS is correct!!!</b>
The Java project does not have any warning. But the stand alone proxy project has following warnings associated with it.
This method has a constructor name     MIDadosPessoaisSync.java
The import javax.xml.rpc.holders is never used     MIDadosPessoaisSyncBindingStub.java
The import javax.xml.rpc.encoding is never used     MIDadosPessoaisSyncBindingStub.java
The constructor BaseRuntimeException(ResourceAccessor, String, Throwable) is deprecated     MIDadosPessoaisSyncBindingStub.java
It is very similar with your problem, could you help me?
Thanks
Gustavo Freitas

Reading a data file from an Applet

...new to Applet Programming. I have a stand-alone application that converts
an XML file to a DOM, then to a JTree. I have converted the application to an Applet
But I can't find the trick to having the applet connect to the XML file.
This is the line of code which works fine in the stand-alone, but hangs the Applet:
document = builder.parse( new File( "P6B.Xml" ) );
How can the applet read data located on the host in the same directory as the class?
Sounds simple, but somehow can't find a way of doing this.
One suggested solution (when the file is always needed) I have found browsing
through this site is to wrap both the File and the Class in a JAR.
In this instance, how can I parse the file?
Appreciate any help.

Give the complete URL of your xml file.

IceFaces 1.8 dataTable-sort example gives error

Hi All:
I need help, please!! Any help or hint is greatly appreciated it!!
In the tutorial from IceFaces 1.8
Data Table Component Tutorials
I am using weblogic 10.3.2, IceFaces 1.8 and Jsf 1.2.
I am using the jars that comes with the IceFaces 1.8 download.
index.jsp:
<html>
<head>
<title>ICEfaces Component Showcase</title>
</head>
<body>
<jsp:forward page="sortableTable.iface" />
</body>
</html>
sortableTable.jspx:
<f:view xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ice="http://www.icesoft.com/icefaces/component">
<ice:outputDeclaration doctypeRoot="HTML"
doctypePublic="-//W3C//DTD HTML 4.01 Transitional//EN"
doctypeSystem="http://www.w3.org/TR/html4/loose.dtd"/>
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1"></meta>
<title>DataTable Component Tutorial</title>
<link href="./xmlhttp/css/xp/xp.css" rel="stylesheet" type="text/css"/>
</head>
<body>
<h2>Sortable dataTable Component</h2>
<p>In this example commandSortHeader components have been added to the
table headers. Clicking on the headers will sort the table data.</p>
<ice:form>

<ice:dataTable
id="dataSortData"
sortColumn="#{inventoryList.sortColumnName}"
sortAscending="#{inventoryList.ascending}"
value="#{inventoryList.carInventory}"
var="item">

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.stockColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.stockColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.stock}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.modelColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.modelColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.model}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.descriptionColumnName} "
arrow="true" >
<ice:outputText value="#{inventoryList.descriptionColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.description}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.odometerColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.odometerColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.odometer}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.priceColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.priceColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.price}"/>
</ice:column>
</ice:dataTable>
</ice:form>
</body>
</html>
</f:view>
Error 500--Internal Server Error
java.lang.Exception: javax.faces.FacesException: Can't parse stream for /index.jsp The prefix "jsp" for element "jsp:forward" is not bound.
at com.icesoft.faces.context.View.servePage(View.java :152)
at com.icesoft.faces.webapp.http.core.MultiViewServer .service(MultiViewServer.java:67)
at com.icesoft.faces.webapp.http.common.ServerProxy.s ervice(ServerProxy.java:11)
at com.icesoft.faces.webapp.http.servlet.MainSessionB oundServlet$4.service(MainSessionBoundServlet.java :149)
at com.icesoft.faces.webapp.http.common.standard.Path DispatcherServer.service(PathDispatcherServer.java :24)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptin gServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.PathDispatch er.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.SessionDispa tcher.service(SessionDispatcher.java:53)
at com.icesoft.faces.webapp.http.servlet.PathDispatch er.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.MainServlet. service(MainServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at weblogic.servlet.internal.StubSecurityHelper$Servl etServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invok eServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute( ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(Tail Filter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFi lter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$Ser vletInvocationAction.run(WebAppServletContext.java :3592)
at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Se curityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.sec uredExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.exe cute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(S ervletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread. java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java :173)
Caused by: javax.faces.FacesException: Can't parse stream for /index.jsp The prefix "jsp" for element "jsp:forward" is not bound.
at com.icesoft.faces.application.D2DViewHandler.rende rResponse(D2DViewHandler.java:445)
at com.icesoft.faces.application.D2DViewHandler.rende rView(D2DViewHandler.java:159)
at com.sun.faces.lifecycle.RenderResponsePhase.execut e(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:1 00)
at com.sun.faces.lifecycle.LifecycleImpl.render(Lifec ycleImpl.java:139)
at com.icesoft.faces.webapp.http.core.JsfLifecycleExe cutor.apply(JsfLifecycleExecutor.java:19)
at com.icesoft.faces.context.View$2$1.respond(View.ja va:48)
at com.icesoft.faces.webapp.http.servlet.ServletReque stResponse.respondWith(ServletRequestResponse.java :201)
at com.icesoft.faces.context.View$2.serve(View.java:7 7)
at com.icesoft.faces.context.View.servePage(View.java :149)
... 25 more
Caused by: org.xml.sax.SAXParseException: The prefix "jsp" for element "jsp:forward" is not bound.
at com.sun.org.apache.xerces.internal.parsers.Abstrac tSAXParser.parse(AbstractSAXParser.java:1231)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserI mpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogic XMLReader.java:133)
at weblogic.xml.jaxp.RegistryXMLReader.parse(Registry XMLReader.java:173)
at org.apache.commons.digester.Digester.parse(Digeste r.java:1785)
at com.icesoft.faces.webapp.parser.Parser.parse(Parse r.java:130)
at com.icesoft.faces.application.D2DViewHandler.rende rResponse(D2DViewHandler.java:439)
... 34 more

Hi All:
I need help, please!! Any help or hint is greatly appreciated it!!
In the tutorial from IceFaces 1.8
Data Table Component Tutorials
I am using weblogic 10.3.2, IceFaces 1.8 and Jsf 1.2.
I am using the jars that comes with the IceFaces 1.8 download.
index.jsp:
<html>
<head>
<title>ICEfaces Component Showcase</title>
</head>
<body>
<jsp:forward page="sortableTable.iface" />
</body>
</html>
sortableTable.jspx:
<f:view xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:ice="http://www.icesoft.com/icefaces/component">
<ice:outputDeclaration doctypeRoot="HTML"
doctypePublic="-//W3C//DTD HTML 4.01 Transitional//EN"
doctypeSystem="http://www.w3.org/TR/html4/loose.dtd"/>
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1"></meta>
<title>DataTable Component Tutorial</title>
<link href="./xmlhttp/css/xp/xp.css" rel="stylesheet" type="text/css"/>
</head>
<body>
<h2>Sortable dataTable Component</h2>
<p>In this example commandSortHeader components have been added to the
table headers. Clicking on the headers will sort the table data.</p>
<ice:form>

<ice:dataTable
id="dataSortData"
sortColumn="#{inventoryList.sortColumnName}"
sortAscending="#{inventoryList.ascending}"
value="#{inventoryList.carInventory}"
var="item">

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.stockColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.stockColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.stock}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.modelColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.modelColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.model}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.descriptionColumnName} "
arrow="true" >
<ice:outputText value="#{inventoryList.descriptionColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.description}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.odometerColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.odometerColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.odometer}"/>
</ice:column>

<ice:column>
<f:facet name="header">
<ice:commandSortHeader
columnName="#{inventoryList.priceColumnName}"
arrow="true" >
<ice:outputText value="#{inventoryList.priceColumnName}"/>
</ice:commandSortHeader>
</f:facet>
<ice:outputText value="#{item.price}"/>
</ice:column>
</ice:dataTable>
</ice:form>
</body>
</html>
</f:view>
Error 500--Internal Server Error
java.lang.Exception: javax.faces.FacesException: Can't parse stream for /index.jsp The prefix "jsp" for element "jsp:forward" is not bound.
at com.icesoft.faces.context.View.servePage(View.java :152)
at com.icesoft.faces.webapp.http.core.MultiViewServer .service(MultiViewServer.java:67)
at com.icesoft.faces.webapp.http.common.ServerProxy.s ervice(ServerProxy.java:11)
at com.icesoft.faces.webapp.http.servlet.MainSessionB oundServlet$4.service(MainSessionBoundServlet.java :149)
at com.icesoft.faces.webapp.http.common.standard.Path DispatcherServer.service(PathDispatcherServer.java :24)
at com.icesoft.faces.webapp.http.servlet.BasicAdaptin gServlet.service(BasicAdaptingServlet.java:16)
at com.icesoft.faces.webapp.http.servlet.PathDispatch er.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.SessionDispa tcher.service(SessionDispatcher.java:53)
at com.icesoft.faces.webapp.http.servlet.PathDispatch er.service(PathDispatcher.java:23)
at com.icesoft.faces.webapp.http.servlet.MainServlet. service(MainServlet.java:131)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at weblogic.servlet.internal.StubSecurityHelper$Servl etServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invok eServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute( ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(Tail Filter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFi lter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$Ser vletInvocationAction.run(WebAppServletContext.java :3592)
at weblogic.security.acl.internal.AuthenticatedSubjec t.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Se curityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.sec uredExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.exe cute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(S ervletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread. java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java :173)
Caused by: javax.faces.FacesException: Can't parse stream for /index.jsp The prefix "jsp" for element "jsp:forward" is not bound.
at com.icesoft.faces.application.D2DViewHandler.rende rResponse(D2DViewHandler.java:445)
at com.icesoft.faces.application.D2DViewHandler.rende rView(D2DViewHandler.java:159)
at com.sun.faces.lifecycle.RenderResponsePhase.execut e(RenderResponsePhase.java:110)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:1 00)
at com.sun.faces.lifecycle.LifecycleImpl.render(Lifec ycleImpl.java:139)
at com.icesoft.faces.webapp.http.core.JsfLifecycleExe cutor.apply(JsfLifecycleExecutor.java:19)
at com.icesoft.faces.context.View$2$1.respond(View.ja va:48)
at com.icesoft.faces.webapp.http.servlet.ServletReque stResponse.respondWith(ServletRequestResponse.java :201)
at com.icesoft.faces.context.View$2.serve(View.java:7 7)
at com.icesoft.faces.context.View.servePage(View.java :149)
... 25 more
Caused by: org.xml.sax.SAXParseException: The prefix "jsp" for element "jsp:forward" is not bound.
at com.sun.org.apache.xerces.internal.parsers.Abstrac tSAXParser.parse(AbstractSAXParser.java:1231)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserI mpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogic XMLReader.java:133)
at weblogic.xml.jaxp.RegistryXMLReader.parse(Registry XMLReader.java:173)
at org.apache.commons.digester.Digester.parse(Digeste r.java:1785)
at com.icesoft.faces.webapp.parser.Parser.parse(Parse r.java:130)
at com.icesoft.faces.application.D2DViewHandler.rende rResponse(D2DViewHandler.java:439)
... 34 more

Load jar from jar in applet

hi i made an applet that read xml files.
i using in jaxp.jar and in parser.jar currently i put them in ext folder in plug in. is there any other way to put them in my jar applet file and to load them from there.

The xml stuff is one of the optional packages you can install and belongs in the /ext (extension) folder just like you have it. Possibly, this will be integrated in the v1.4 release, but I'm not sure about that. Anyway, my best advice for you is to follow the instructions Sun gives on exactly this situation:
http://java.sun.com/j2se/1.3/docs/guide/extensions/extensions.html
Also on this page is a link to Optional Package Versioning that I highly recommend you read, as it details how the v1.3 plug-in will automatically install the xml jars on the client machine for you. It doesn't get any easier than this! :-)
-Ron

Need info about GV$HANG_STATISTICS

Can any one help me understand the hang management framework in detail? Wanted to know details about metrics available in GV$HANG_STATISTICS, how they are computed and frequency of this view getting updated etc.

Hi,
it's information displayed about hangs found on the cluster.
A hang can be an open wait chain or closed wait chain (cycle or deadlock). A wait chain is a series of sessions that are blocking one another. Each row represents a hang and describes how severe the hang is. This view also includes the victim or final blocker of the hang.
You found two Views v$hang_info, v$hang_statistics.
Here the output from a running production database.
SQL> select * from v$hang_statistics
STATISTIC# NAME                                               VALUE
         0 number of deadlocks detected and ignored               0
         1 number of hangs detected                               8
         2 number of local hangs                                  7
         3 number of global hangs                                 1
         4 number of transient hangs                              0
         5 hangs ignored due to high CPU on root's node           0
         6 hangs ignored due to high IO on root's node            0
         7 hangs ignored due to application contention            0
         8 hangs ignored due to long running operations           0
         9 hangs monitored due to archiving issues                0
        10 hangs ignored due to archiving issues                  0
        11 hangs ignored, blocked by remote database              0
        12 hangs ignored due to SQL parsing                       0
        13 hangs ignored due to dumping system state              0
        14 hangs ignored, instance termination required           0
        15 hangs ignored, only one active instance                0
        16 number of explicitly resolved hangs                    0
        17 number of self-resolved hangs                          8
        18 total self-resolved hang time in seconds             209
        19 minimum self-resolved hang time in seconds             1
        20 maximum self-resolved hang time in seconds            30
        21 number of HSC matched hangs                            8
        22 hangs resolved due to instance termination             0
23 rows selected.
regards

XML Processing Implementaion

Hi,
While studying, I found the following sentence :
The Java API for XML Processing (JAXP) enables applications to parse and transform XML documents independent of a particular XML processing implementation.
In the above sentence, what is a "XML processing implementation"?
Regards

I think an SAP man should answer here, but my common sense and SAP knowledge suggests me:
A1: yes, evidently
A2: the fact that DOM4J is quoted in a weblog doesn't mean it's officialy supported by SAP, it's just an option, just like Apache Xerces and others. You can use them in interface dev, it's up to you, but an Adapter is a completly different story: SAP wants to make sure it has full control over a Certified Adapter, and the only way to do that is to have full control on the additional libraries that this Adapter uses. SAP can have this control on SAP XML Toolkit, but not on DOM4J or Xerces, obviously.
A3: no difference, except that logically and pragmatically is much more convenient to package and deploy everyhting your stuff needs in order to work properly.
Regards,
Alex

Hanging jaxp-1.0.1-parser

Similar Messages

Maybe you are looking for