Xslproceesor problem and new xml parser.

I'm curious how I can use javascript in xsl. I can use user defined script with xsl which provided by Microsoft. but I'm not sure with oracle. I heard that it's possible to use that. so I wanna know that.
I need exact example to use this.
This is an example for msxsl. if anybody know this to use with oracle. please let me know.
and I need new xmlparserv2_2029, where can I get it? thanks. please let me know.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
          xmlns:msxsl="http://www-microsoft-com/XSL/Transform/"
          xmlns:user="urn:my-scripts"
version="1.0">
<msxsl:script language="JAVAScript" implements-prefix="user">
</msxsl:script>

Thanks for the pointers! I hadn't encountered lazy-DOM before. It sounds like an interesting idea, although I think its goal is quite different from PAX. I found the following quote in a description of it on the Xerces website: "This shortens the time it takes to parse an XML file and create a DOM tree at the expense of requiring more memory during parsing and traversing the document." So it takes even more memory than a standard DOM parser.
I'll definitely check out the xml.org discussion list. I've been looking for a good place to get feedback, and this board seemed like a likely candidate.
Peter

Similar Messages

  • Oracle9i: Difference between oraxml and oracle.xml.parser.v2.DOMParser?

    I have parsed the following xml document with the oraxml batch
    and with the sample '..\xdk\demo\java\parser\dom\DOMSample' and
    observed a diffent behavior in Oracle9i:
    <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
    <Document xmlns:n1='urn:example:some-names'
    xmlns:n2='urn:example:some-names'>
    <BadAttrs_XML_1.0 att='1' att='2' />
    <BadAttrs_Namespaces n1:att='1' n2:att='2' />
    <OKAttrs_XML_1.0 att='1' n2:att='2' />
    </Document>
    ----------------------------1.) oraxml
    C:\oracle\ora9011\xdk\demo\java\parser\dom>oraxml -version
    -warning Namespaces2.xml
    Parser version: Oracle XDK Java 9.0.1.0.0 Production
    The input XML file is parsed without errors using partial
    validation mode
    Oraxml does not recognize the two attributes with the same name
    in element 'BadAttrs_XML_1.0' as an error.
    2.) oracle.xml.parser.v2.DOMParser
    C:\oracle\ora9011\xdk\demo\java\parser\dom>java DOMSample
    Namespaces2.xml
    file:Namespaces2.xml<Line 8, Column 38>: XML-0124: (Fata
    l Error) An attribute cannot appear more than once in the same
    start tag.
    oracle.xml.parser.v2.XMLParseException: An attribute cannot
    appear more than once in the same start tag.
    I have modified the DomSample.java. The DomParser just checks for
    well-formed documents and doesn't validate the document anymore.
    (only a comment before
    parser.setValidationMode(DOMParser.DTD_VALIDATION);)
    My question is:
    Is there really a difference between oracle.xml.parser.v2.oraxml
    and oracle.xml.parser.v2.DOMParser or which parameters do I have
    to use to get the same results?
    With Oracle8i, both report an xml error!!
    (Oracle9i, Win2000, JDK1.3)
    Thanx in advance!
    Markus

    It would appear that there is a difference when a loadjava is given a jar vs. the individual class files. When I load the jar, I get the previously described error, but when I load the individual class files (the same class files that the jar contains) the error goes away.
    Why?

  • Problem to swap XML parser

    Hi all,
    I am trying to replace the official oracle XML library by apache xerces on a soa suite 10.1.3.1 developper hosted on a linux red hat platform.
    I have found a how to on oracle web site (http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html). I hadn't found any archive containing the source so I have buid a simple test using EJB 3 (In fact, I have created a "hello word" session bean that return a String containing the Dom builder factory class name).
    I have create the shared library using Entreprise manager as described in the how to.
    My test works fine if I deploy it with the default XML factory but if I add the following lines to the orion-application.xml, the deployment process ends with a null pointer exception :
    <imported-shared-libraries>
    <import-shared-library name="apache.xml" />
    <remove-inherited name="oracle.xml" />
    </imported-shared-libraries>
    I have tried to deploy the test using the entreprise manager web UI (as explain in how to) but the result was the same.
    I have tried to remove the "<remove-inherited name="oracle.xml" />" line but in this case, the XML parser still the oracle one.
    Do you know if the library specification is available in the last soa suite ?
    Thank in advance for your responses.
    Alexandre CUCUMEL
    PS: I can send the test code source if needed
    PS2: here is the complete opmn stack trace when I try to deploy the test application
    08/08/08 15:46:36 java.lang.RuntimeException: javax.xml.parsers.FactoryConfigurationError: Provider oracle.xml.jaxp.JXDocumentBuilderFactory could not
    be instantiated: java.lang.NullPointerException
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:105)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator$DeploymentCompileTool.run(DeploymentGenerator.java:205)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator.generateDeploymentArtifacts(DeploymentGenerator.java:131)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.EJBWebServiceAnnotationParser.parseAnnotatedBean(EJBWebServiceAnnotationParser.ja
    va:165)
    08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    08/08/08 15:46:36 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    08/08/08 15:46:36 at java.lang.reflect.Method.invoke(Method.java:585)
    08/08/08 15:46:36 at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:85
    08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.notifyAnnotationListeners(AnnotationParser.java:201)
    08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.parseAnnotations(AnnotationParser.java:73)
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:939)
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:832)
    08/08/08 15:46:36 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
    08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:413)
    08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:314)
    08/08/08 15:46:36 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
    08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
    08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
    08/08/08 15:46:36 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
    08/08/08 15:46:36 at java.lang.Thread.run(Thread.java:595)
    08/08/08 15:46:36 Caused by: javax.xml.parsers.FactoryConfigurationError: Provider oracle.xml.jaxp.JXDocumentBuilderFactory could not be instantiated:
    java.lang.NullPointerException
    08/08/08 15:46:36 at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
    08/08/08 15:46:36 at oracle.j2ee.ws.wsdl.extensions.oracle.schema.SchemaSchemaElement.<init>(SchemaSchemaElement.java:37)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.generateSchema(WSDLTypeGenerator.java:435)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.processElement(WSDLTypeGenerator.java:735)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.processElementsInMessage(WSDLTypeGenerator.java:352)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLTypeGenerator.run(WSDLTypeGenerator.java:207)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.generateTypes(WSDLGenerator.java:291)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.generateDocument(WSDLGenerator.java:242)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.doGeneration(WSDLGenerator.java:176)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.doGeneration(WSDLGenerator.java:141)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.generator.wsdl.WSDLGenerator.perform(WSDLGenerator.java:126)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.processor.Processor.runActions(Processor.java:97)
    08/08/08 15:46:36 ... 23 more
    08/08/08 15:46:36 WARNING: Application.setConfig Application: testDeployement is in failed state as initialization failed.
    java.lang.InstantiationException: Error initializing ejb-modules: nested exception is: java.lang.NullPointerException
    08/08/08 15:46:36 oracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Application: testDeployement is in failed state as i
    nitialization failed
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:515)
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
    08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
    08/08/08 15:46:36 at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
    08/08/08 15:46:36 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
    08/08/08 15:46:36 at java.lang.Thread.run(Thread.java:595)
    08/08/08 15:46:36 Caused by: java.lang.InstantiationException: Application: testDeployement is in failed state as initialization failed
    08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:471)
    08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:314)
    08/08/08 15:46:36 at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
    08/08/08 15:46:36 at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
    08/08/08 15:46:36 ... 6 more
    08/08/08 15:46:36 Caused by: java.lang.InstantiationException: Error initializing ejb-modules: nested exception is: java.lang.NullPointerException
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1064)
    08/08/08 15:46:36 at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
    08/08/08 15:46:36 at com.evermind.server.Application.setConfig(Application.java:413)
    08/08/08 15:46:36 ... 9 more
    08/08/08 15:46:36 Caused by: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:356)
    08/08/08 15:46:36 at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:92
    08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.notifyAnnotationListeners(AnnotationParser.java:201)
    08/08/08 15:46:36 at com.evermind.server.ejb.AnnotationParser.parseAnnotations(AnnotationParser.java:73)
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:939)
    08/08/08 15:46:36 at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:832)
    08/08/08 15:46:36 ... 11 more
    08/08/08 15:46:36 Caused by: java.lang.NullPointerException
    08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator.generateDeploymentArtifacts(DeploymentGenerator.java:138)
    08/08/08 15:46:36 at oracle.j2ee.ws.common.metadata.annotation.EJBWebServiceAnnotationParser.parseAnnotatedBean(EJBWebServiceAnnotationParser.ja
    va:165)
    08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    08/08/08 15:46:36 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    08/08/08 15:46:36 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    08/08/08 15:46:36 at java.lang.reflect.Method.invoke(Method.java:585)
    08/08/08 15:46:36 at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:85
    08/08/08 15:46:36 ... 15 more
    08/08/08 15:46:36 WARNING: DeployerRunnable.run java.lang.InstantiationException: Application: testDeployement is in failed state as initialization fa
    iledoracle.oc4j.admin.internal.DeployerException: java.lang.InstantiationException: Application: testDeployement is in failed state as initialization
    failed
    at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:126)
    at oracle.oc4j.admin.jmx.server.mbeans.deploy.OC4JDeployerRunnable.doRun(OC4JDeployerRunnable.java:52)
    at oracle.oc4j.admin.jmx.server.mbeans.deploy.DeployerRunnable.run(DeployerRunnable.java:81)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: java.lang.InstantiationException: Application: testDeployement is in failed state as initialization failed
    at com.evermind.server.Application.setConfig(Application.java:471)
    at com.evermind.server.Application.setConfig(Application.java:314)
    at com.evermind.server.ApplicationServer.addApplication(ApplicationServer.java:1853)
    at oracle.oc4j.admin.internal.ApplicationDeployer.addApplication(ApplicationDeployer.java:512)
    at oracle.oc4j.admin.internal.ApplicationDeployer.doDeploy(ApplicationDeployer.java:196)
    at oracle.oc4j.admin.internal.DeployerBase.execute(DeployerBase.java:93)
    ... 4 more
    Caused by: java.lang.InstantiationException: Error initializing ejb-modules: nested exception is: java.lang.NullPointerException
    at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:1064)
    at com.evermind.server.ApplicationStateRunning.initializeApplication(ApplicationStateRunning.java:217)
    at com.evermind.server.Application.setConfig(Application.java:413)
    ... 9 more
    Caused by: javax.ejb.EJBException: nested exception is: java.lang.NullPointerException
    at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
    at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:356)
    at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:92)
    at com.evermind.server.ejb.AnnotationParser.notifyAnnotationListeners(AnnotationParser.java:201)
    at com.evermind.server.ejb.AnnotationParser.parseAnnotations(AnnotationParser.java:73)
    at com.evermind.server.ejb.EJBPackageDeployment.parseMetaData(EJBPackageDeployment.java:939)
    at com.evermind.server.ejb.EJBContainer.postInit(EJBContainer.java:832)
    ... 11 more
    Caused by: java.lang.NullPointerException
    at oracle.j2ee.ws.common.metadata.annotation.DeploymentGenerator.generateDeploymentArtifacts(DeploymentGenerator.java:138)
    at oracle.j2ee.ws.common.metadata.annotation.EJBWebServiceAnnotationParser.parseAnnotatedBean(EJBWebServiceAnnotationParser.java:165)
    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:585)
    at oracle.j2ee.ws.server.deployment.oc4j.WebServiceAnnotationListener.parseAnnotatedClass(WebServiceAnnotationListener.java:85)
    ... 15 more

    Andre,
    Thanks for your interest on my problem.
    In fact, I have created a test with just an interface and a class. No additional jars are added at compilation or ejb creation time.
    My java code is very simple (I have just copied the example main method and convert it to a SOAP method :
    package be.test;
    import javax.ejb.Stateless;
    import javax.jws.WebService;
    import javax.xml.parsers.DocumentBuilder;
    import javax.xml.parsers.DocumentBuilderFactory;
    @Stateless
    @WebService(endpointInterface = "be.test.Test")
    public class TestImpl implements Test {
         public String test() {
              DocumentBuilder builder=null;
              DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
              try
              builder = factory.newDocumentBuilder();
              return "<BR><B>DocumentBuilderFactory Instance:</B> " + factory.getClass().getName() +
              "<BR><B>DocumentBuilder Instance:</B> " + builder.getClass().getName() +"<BR>"; }
              catch (Exception e)
              return "Error processing DOM -- " + e.getMessage();
    Unfortunately, I think that the problem may come from EJB 3 stack that does not support an other XML library.
    Thanks again for your help.
    Best regards,
    Alexandre
    PS: appologies for the message formatting... I don't understand why the new line caracters are not corrects.

  • XML parsing problems with Oracle XML parser for PL/SQL

    I am using the Oracle XML parser for PL/SQL to transform XML into HTML usign XSL. The parser gives me sporadic errors trying to parse various XML documents. For the same XML source, the XMLPARSER will parse without errors one day and the next day will give me errors such as "invalid char in text", "Expected ';'.", or even Java null pointer exceptions.
    I have verified that the XML sources are well formed, so I am pretty certain that the problems I am having are bugs in the XMLPARSER.
    Is there going to be a XML parser for PL/SQL version 2 that will fix these bugs? If so, when??? If not, is there anything else I could do to fix these problems?
    Thanks!

    You can use the latest version.

  • RSS - Rolling News - XML Parsing - Accessing KM...

    Hello everyone! I am trying to make an iview wich shows rolling news through RSS Feeds, and filtering its content with XLS.
    I´ve downloaded an example "Simple XML Parsing iview" and uploaded it into the portal. The thing is that the iview is quite limited because the XSL file has to be in the internet; but i need to have de XLS in the KM, i mean, i need the iview to accept paths like :
    http://suarbulpd1d01:50100/irj/go/km/docs/documents/DocumentosPortal/RecursosPortal/Varios/rss-html.xsl
    Don´t know how could i modify the code to so i can achieve this.. here it goes:
    package com.portalsamples.simplexml;
    import java.io.*;
    import javax.xml.transform.TransformerFactory;
    import javax.xml.transform.Transformer;
    import javax.xml.transform.Source;
    import javax.xml.transform.stream.StreamSource;
    import javax.xml.transform.stream.StreamResult;
    import com.sapportals.portal.prt.component.*;
    public class simplexsl extends AbstractPortalComponent
         public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
              IPortalComponentProfile profile = request.getComponentContext().getProfile();
              Writer out = response.getWriter();
               try
                 //Creates an instance of the transformer
                 TransformerFactory tFactory = TransformerFactory.newInstance();
                 //Pulls XMLSource and XSLSource from the iView Profile
                 Source xmlSource = new StreamSource(profile.getProperty("xmlsource"));
                 Source xslSource = new StreamSource(profile.getProperty("xslsource"));
                 response.write(xslSource.toString());
                 Transformer transformer = tFactory.newTransformer(xslSource);
                 //Places resulting HTML into the response
                   transformer.transform(xmlSource, new StreamResult(out));
               catch (Exception e)
                 response.write(e.getMessage());
    Any help will be rewarded...
    Regards, Marco.

    Hello, this is my new code; although it is limited to only accessing xsl files inside the par, it works perfectly. If you want the complete par for rolling news, my mail is [email protected] .
         public void doContent(IPortalComponentRequest request, IPortalComponentResponse response)
              IPortalComponentProfile profile = request.getComponentContext().getProfile();
              Writer out = response.getWriter();
                   try
                    TransformerFactory tFactory = TransformerFactory.newInstance();
                    //Pulls XMLSource and XSLSource from the iView Profile
                    Source xmlSource = new StreamSource(profile.getProperty("xmlsource"));
                   String location= request.getPublicResourcePath()+"/xsl/"+profile.getProperty("xslsource");
                         File f = new File(location);
                    Source XSLSou = new StreamSource(f);
                    Transformer transformer = tFactory.newTransformer(XSLSou);
                   transformer.transform(xmlSource, new StreamResult(out));
                    catch (Exception e)
                     response.write(e.getMessage());
    Greetings,
    Marco.

  • I recently updated and after the update i tried import my passwords and recieved XML parsing error. Passwords could not be imported.

    ''Duplicate post, continue here - [https://support.mozilla.com/en-US/questions/788710]''
    after a recent update to fire fox 3.6.13 i believe that was the version. I tried import my passwords all 30 of them or more I received this message XML parsing error. Passwords could not be imported. please help me to regain my passwords and to fix this problem so it wont happen again thank you

    Are you using the Password Exporter extension?

  • New XML parser

    I'm working on developing a new style of XML parser. I've created an initial proof of concept implementation, and I'd be grateful for feedback on it.
    The idea is to create a high level, DOM-like API which is suitable for both streaming and in-memory parsers. This provides several advantages over existing parsers:
    -It's much easier to use than other streaming parsers like SAX or StAX.
    -Switching from an in-memory parser to a streaming parser (or vice versa) is much easier than with any other parsers, because they use exactly the same API. You can even support both, then decide which parser to use at runtime (based on the file size, for example, or how many passes you need to make through it).
    -Many useful utilities can be written once, then used with either parser.
    The current implementation is available at
    http://drizzle.stanford.edu/~peastman/pax.zip
    All source code is in the public domain. Feedback would be gratefully appreciated!
    Peter

    Thanks for the pointers! I hadn't encountered lazy-DOM before. It sounds like an interesting idea, although I think its goal is quite different from PAX. I found the following quote in a description of it on the Xerces website: "This shortens the time it takes to parse an XML file and create a DOM tree at the expense of requiring more memory during parsing and traversing the document." So it takes even more memory than a standard DOM parser.
    I'll definitely check out the xml.org discussion list. I've been looking for a good place to get feedback, and this board seemed like a likely candidate.
    Peter

  • Problems with namespace XML Parsing of ABAP PI 7.0 Integration Engine

    Hi,
    I discovered the following problem.
    The customer sends a SOAP message with is forwarded through a SOAP Adapter in the integration engine.
    The structure of the message is very simple:
    <Envelope>
    <Body>
    <ORDERS05>...</ORDERS05>
    </Body>
    </Envelope>
    The customer adds the namespace information a special way:
    <Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope">
    <Body>
    <orders05 xmlns="">...</orders05>
    </Body>
    <Envelope>
    Here the namespaces is declared in the first element. It should be inherited into all child elements. The 'orders05' should not have the namespace ' xmlns="http://schemas.xmlsoap.org/soap/envelope" ', therefore the namespace is overwritten with ' xmlns="" '. However I don't know if this is a correct xml statement, the SAP system did not understand this.
    The integration throws an error which is stated in the message in the adapter engine:
    2008-11-06 17:31:44 Fehler SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIProtocol/ITEM_MISSING; Params: /@mustUnderstand, ST: ST_XMS_MSGHDR30_RM; AdditionalText: Attribut 'mustUnderstand' erwartet; ApplicationFaultMessage: ; ErrorStack: Das XML-Element /@mustUnderstand fehlt im SOAP-Message Header (SAP XI Extension) Attribut 'mustUnderstand' erwartet
    2008-11-06 17:31:44 Fehler Fehler beim Übertragen der Message zum Endpunkt http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry über die Verbindung SOAP_http://sap.com/xi/XI/System. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header
    If I changed the SOAP message to the common format, it is accepted by the integration engine.
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope">
    <SOAP:Body>
    <orders05>...</orders05>
    </SOAP:Body>
    </SOAP:Envelope>
    Here the namespace ' xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope" ' is defined with a prefix and assigned to the elements 'envelope' and 'body'. The 'orders05' element has no namespace.
    However due to the xml syntax both messages are the same, so why the integration engine handle the messages different?
    Best regards,
    Nils Kloth

    The valid SOAP format supported by XI is as follows
    <SOAP:Envelope
      xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Body>
        <m:MessageTypeName xmlns:m="Some-URI">
          <Price>34.5</Price>
        </m:MessageTypeName>
      </SOAP:Body>
    </SOAP:Envelope>
    Ur sender system is not sending the data in correct Soap format and thats the cause of message rejection. The option you have to use the Soap adapter in "no soap" mode.
    Regards,
    Prateek

  • Weblogic 6.0sp2, problems useing new XML Registry

    I'm trying to configure a parser other than the Built-In Parser, but WLS seems
    to still us its default.
    I follow the documentation at http://edocs.bea.com/wls/docs60/xml/xml_admin.html#1055027,
    and use xerces 1.4.3, also creating a new server that is targeted.
    I have attached a java file that I set as a startup class, targeted to myserver.
    It shows the classname of saxparsers.
    I allways get the following printout:
    parserFactory: weblogic.xml.jaxp.RegistrySAXParserFactory
    saxParser: weblogic.xml.jaxp.RegistrySAXParser
    parser: weblogic.xml.jaxp.RegistryParser
    But if I run the program from the command prompt, with xerces in the classpath
    I get the following:
    parserFactory: org.apache.xerces.jaxp.SAXParserFactoryImpl
    saxParser: org.apache.xerces.jaxp.SAXParserImpl
    parser: org.xml.sax.helpers.XMLReaderAdapter
    Anyone now anything about this, seems like a bug?
    -perotto
    The parser
    [PrintParserInfo.java]

    hi,
    try keeping the xerces.jar file before the weblogic.jar in the classpath of the
    server script...
    cuz' weblogic.jar file includes weblogic xerces parser..
    but weblogic does not support all the features that xerces 1.4.3 version support.and
    they(BEA) does not recommend to use other versions...
    hope it will help you..
    Vijay
    "Per Otto Christensen" <[email protected]> wrote:
    >
    >
    >
    I'm trying to configure a parser other than the Built-In Parser, but
    WLS seems
    to still us its default.
    I follow the documentation at http://edocs.bea.com/wls/docs60/xml/xml_admin.html#1055027,
    and use xerces 1.4.3, also creating a new server that is targeted.
    I have attached a java file that I set as a startup class, targeted to
    myserver.
    It shows the classname of saxparsers.
    I allways get the following printout:
    parserFactory: weblogic.xml.jaxp.RegistrySAXParserFactory
    saxParser: weblogic.xml.jaxp.RegistrySAXParser
    parser: weblogic.xml.jaxp.RegistryParser
    But if I run the program from the command prompt, with xerces in the
    classpath
    I get the following:
    parserFactory: org.apache.xerces.jaxp.SAXParserFactoryImpl
    saxParser: org.apache.xerces.jaxp.SAXParserImpl
    parser: org.xml.sax.helpers.XMLReaderAdapter
    Anyone now anything about this, seems like a bug?
    -perotto
    The parser

  • XML Parser and Content-type/encoding problem

    I've write a little and simple XML parser and a simple "trasformer" that recive an XML file and an XSL one and return HTML, here is the code:
    public static String toHTML(Document doc, String xslSource){
            ByteArrayOutputStream testo = new ByteArrayOutputStream();
            try{
                DOMSource source = new DOMSource(doc);
                TransformerFactory tFactory = TransformerFactory.newInstance();
                System.out.println("----> " + xslSource);
                Transformer transformer = tFactory.newTransformer(new StreamSource(xslSource));
                transformer.setOutputProperty(OutputKeys.INDENT, "yes");
                transformer.setOutputProperty("{http://xml.apache.org/xslt}indent-amount", "2");
                transformer.setOutputProperty(OutputKeys.METHOD, "html");
             transformer.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, "yes");
             transformer.setOutputProperty(OutputKeys.ENCODING, "UTF-8");
                transformer.transform(source, new StreamResult(testo));
            }catch(Exception ioe){
                System.out.println("2 XMLTool.toHTML " + new java.util.Date());
                System.out.println(ioe);        
            return testo.toString();
        }the problem is that I would like to put the HTML code its return into a JEditorPane; now I'm trying with this code:
    JEditorPane jep1 = new JEditorPane();
    jep1.setContentType("text/html");
    jep1.setText(v);
    // 'v' is the string returned by the code posted up (the XML/XSL transformer)but I can't see anything in my JEditorPane.
    I think that the problem is this line of code that the transformer add automaticaly ad HTML code:
    <META http-equiv="Content-Type" content="text/html; charset=UTF-8">Infact if I try to delete this line from the code I can see what I want but is'n good delete a line of code without understend where is the problem.
    So, can anyone help me?

    good.
    when u set ur output properties to html , transformer
    searches for all entity references and converts accordingly.
    if u r using xalan these files will be used for conversion of
    Character entity references for markup-significant
    output_html.properties
    (this should be in templates package)
    and HTMLEntities.res(should be in serialize package)
    vasanth-ct

  • Oracle XML parser and IBM jdk bug

    Hello,
    From a few messages found in the XML forum it seems that IBM jvm could cause problems with oracle XML parser. ( see http://technet.oracle.com:89/ubb/Forum11/HTML/003823.html )
    I am using IBM jvm (jdk 1.3) on a linux box, and problems are starting to arise:
    I have
    - 1 BC4J based jsp app which works fine.
    - 2 XML parsing BC4J apps which cause strange errors (like parsing 40 documents fine and failing on the 41st for no apparent reason)
    Hopefully, Steven Muench provided precious advice on this (basically, disabling the JIT), however some issues are still open:
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>You should file a bug with IBM to get this fixed, using your stylesheet as a testcase. Lots of people have hit this problem.<HR></BLOCKQUOTE>
    Has anyone (from oracle or else) done this yet? I have gone (quickly) through IBM website but I didn't find any bug report utility or the like...
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Disable your JIT compiler (or switch JVM's) and you won't have the error.<HR></BLOCKQUOTE>
    Turning off the JIT indeed made the errors vanish, thanks a lot for the tip!
    I have a few more questions though :
    * As the BC4J framework uses the xml parser, It is fairly possible that the ibm jvm bug will affect it...
    I haven't had any problems (yet?) with the BC4J part of my applications, but I'm a bit concerned about having random bugs lurking around (I have more than enough of my own :) )
    Has anyone stumbled upon IBM JVM vs oracle parser issues in BC4J? (oracle.xml.parser.v2.XXXXXX exceptions...)
    * If BC4J is indeed affected, what's the solution?
    - Disable the JIT? (And forget about performance?... hmmm... no)
    - Switch parsers? (oracle parser is too tightly integrated in the BC4J Framework isn't it?.. hmm... not possible either)
    - Wait for a patch from IBM (and use another one in the meantime) / switch JVM :
    In either case, I'd really like to know what is the JVM that oracle people use / would advise.
    Thanks for your help
    null

    For those interested,
    last week i reported this bug in the ibm jvm news forum.
    They said that the problem had been investigated and would be fixed in their next service release.
    FYI: the current release (SR7, labeled "build cx130-20010329) still has various problems wih oracle XML parser.
    Remi
    null

  • Xsl processor and xml parser?

    Hello,
    Can someone tell me wich is the xsl processor and the xml parser used by Livecycle ES? And their versions?
    Thank you

    XML Parser parses the text representation of an XML 1.0-compliant document to make the document's information set -- elements, attributes, text, comments, processing instructions, namespace declarations -- available for access to a comptuter program.
    Without a parser, a program cannot make heads or tails of the tree of information contained in your tags.
    An XSL Processor is a program that takes an XML Document as input, along with an XSLT transformation definition (also known as a stylesheet), and effects the transformation of the source document as instructed by the stylesheet. This might mean transforming:
    <ROWSET>
    <ROW>
    <ENAME>Steve</ENAME>
    </ROW>
    </ROWSET>
    into
    <human-resources>
    <employee name="Steve"/>
    </human-resources>
    or alternatively into:
    <html>
    <body>
    <b>Steve</b>
    </body>
    </html>
    In both cases, the source XML document
    is the same, but when transformed by
    one stylesheet, it might become
    the <human-resources> XML document.
    When transformed by another stylesheet,
    it can become pretty HTML.
    To put the two terms in context, an XSL processor uses an XML parser to read the source XML document and to read the XSL transformation definition (aka stylesheet) -- since it, too, is an XML document -- and then it proceeds to transform the source into the target.

  • Moving from com.sun.xml classes to the new xml support integrated in java

    So far, for our XML implementation, we have used the DocumentEx, ElementEx, etc. from com.sun.xml.
    We understand that xml is now supported by the java itself (javax.xml.parsers?) and we wish to update our code to use the newer API.
    Is there a simple mapping between the old DocumentEx and ElementEx and new classes in javax.xml? Can it really be simple to "get rid" of com.sun.xml?

    The combination of the:
    Oracle XML SQL Utility
    and
    Oracle XML Parser for PLSQL V2
    give you what you need.
    null

  • Perl-xml-parser Conflict

    I'm needing to install intltool and perl-xml-parser is a dependency of it but the files for perl-xml-parser are conflicting with perlxml. I read this thread and ran
    pacman -Qo /usr/lib/perl5/vendor_perl/XML/Parser.pm
    to find out that it was conflicting with perlxml.
    Is it safe to run
    pacman -Sf perl-xml-parser
    or is there a way to work around the conflicts?
    This is the error that I'm getting:
    perl-xml-parser: /usr/lib/perl5/vendor_perl/XML/Parser.pm exists in filesystem
    and there are around 35-50 other files that have the same error and they all belong to perlxml.
    Last edited by ShadowsDemise (2011-02-26 23:40:50)

    I had the same problem when installing xmltv.
    First I checked what package owned the file: pacman -Qo /usr/lib/perl5/site_perl/current/XML/SAX/ParserDetails.ini
    Then I removed the package, and I still got a similar error, so I just removed the file, because no package owned it any longer.

  • XML Parser Limitations?

    I'm having problems using the XML Parser from
    Oracle. I've encountered this both in the
    transviewer beans as well as my own implemenatation of the parser.
    The problem occurs when I use an XSL document with a for-each declarative in it. Internet Explorer successfully parses an XML document using this XLS file, but when I use the Oracle Transviewer, the data from the XML document is not parsed into the output.
    Is this an error of mine or a limitation of XML Parser?
    Here are my XML and XLS docs:
    <?xml version = '1.0'?><?xml-stylesheet type="text/xsl" href="cd.xsl"?>
    <PatientSummary>
    <PATIENT>
    <PatName>JONES
    </PatName>
    <PatFirstName>FRED Z
    </PatFirstName>
    <PatGenderCode>M
    </PatGenderCode>
    <PatBirthDtm>06Jul1976
    </PatBirthDtm>
    <PatPrimAddressStreet>123 Main Street
    </PatPrimAddressStreet>
    <PatPrimAddressPost>498555
    </PatPrimAddressPost>
    <PatPrimAddressCity>Edmonton
    </PatPrimAddressCity>
    <PatPrimPhoneNum>6045374321
    </PatPrimPhoneNum>
    </PATIENT>
    <PATIENT>
    <PatName>JONES
    </PatName>
    <PatFirstName>FRED Z
    </PatFirstName>
    <PatGenderCode>M
    </PatGenderCode>
    <PatBirthDtm>06Jul1976
    </PatBirthDtm>
    <PatPrimAddressStreet>123 Main Street
    </PatPrimAddressStreet>
    <PatPrimAddressPost>498555
    </PatPrimAddressPost>
    <PatPrimAddressCity>Edmonton
    </PatPrimAddressCity>
    <PatPrimPhoneNum>6045374321
    </PatPrimPhoneNum>
    </PATIENT>
    </PatientSummary>
    <?xml version = '1.0'?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
    <xsl:template match="/">
    <html>
    <body>
    <xsl:for-each select="PatientSummary/PATIENT">
    <table border="2" bgcolor="yellow">
    <tr>
    <td>
    <xsl:value-of select="PatName"/>
    </td>
    </tr>
    <tr>
    <td>
    <xsl:value-of select="PatFirstName"/>
    </td>
    </tr>
    <tr>
    <td>
    <xsl:value-of select="PatGenderCode"/>
    </td>
    </tr>
    <tr>
    <td>
    <xsl:value-of select="PatBirthDtm"/>
    </td>
    </tr>
    <tr>
    <td>
    <xsl:value-of select="PatPrimAddressStreet"/>
    </td>
    </tr>
    <tr>
    <td>
    <xsl:value-of select="PatPrimAddressPost"/>
    </td>
    </tr>
    </table>
    </xsl:for-each>
    </body>
    </html>
    </xsl:template>
    </xsl:stylesheet>
    null

    Hi,
    For the XSL file, you need to use
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0" version="1.0">
    instead of
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
    We were able to parse the file with this modification. If this does not solve your problem, please provide us with some description of the error that you are getting.
    Thank you,
    Oracle XML Team

Maybe you are looking for

  • Searching for missing column names in a single database.

    I have a database with about 100 tables, database gets generated using entity framework. The application has been enhanced  so users deployed with older version of the application need to upgrade to newer version. The database generated is both versi

  • HT4009 In-ap purchase error

    Can anyone tell me what could be wrong if I click "buy" in a confirm purchase dialog box but then get an error message stating my purchase could not be completed?

  • LR4.4: Nex5 vs Nex5T no longer reads arw file

    My Sony Nex5 broke and is no longer available, so I bought the Sony Nex5T. I use Win7 on desktop and Lightroom 4.4. When I take picture with my Nex5, I import the photos off the card into a 'dump' folder based on date and Copy as DNG. I can preview t

  • HT4623 how can i get ios 7.1 beta 2?

    how can i get ios7.1 Beta 2 on my 5s?

  • Formula variable on Time Characterstics in reporting

    Hai, I have two Characterstics called ZStart_Time & ZEnd_Time, My scnario is to calculate the Duration between these tho fileds in Reporting. Can any one explain me how to calculate these value using Formula/Rkf/CKF. Thanks Harsha