Xmlparserv2 and xalan

Hi
I have deployed an XML based application on Oracle9iAS Release 2 (v9.0.2). Application Server is forcing me to user Oracle's xmlparserv2 (and saxon) whereas my application has been written according to xalan (and xerces).
Can some one help me as how to instruct Oracle9iAS to use xalan insread of xmlparserv2.
I may add here that if I (completely) replace the xmlparserv2.jar with xalan.jar then I am unable to start OC4J.
I would appreciate if could also CC the response to my personal email [email protected]
Atif

I got a very similiar question. In order to use XMLmill I have to start OC4J with following java parameter:
-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl -Dorg.xml.sax.driver=oracle.xml.parser.v2.SAXParser
Could this have any unintentional consequences?
thanks
Klaus

Similar Messages

Xmlparserv2.jar with xerces and xalan

Hello,
I have a Spring/Spring Web Flow application. I also have a separate web application that's using the XML Publisher API to generate reports from RTF files. I am now in the process of merging these two into one application.
The Spring app requires the xerces.jar and xalan.jar JARs in order to parse the various XML files required to configure Spring. The XML Publisher app requires the xmlparserv2.jar JAR in order to parse the XML required for generating reports.
When I have all of these JARs in my one web application, I receive an error when I call the FOProcessor.generate() method. Here it is:
oracle.xml.parser.v2.XMLParseException: Bad character (1).
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:324)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:287)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:292)
     at oracle.xml.parser.v2.XSLProcessor.newXSLStylesheet(XSLProcessor.java:590)
     at oracle.xml.parser.v2.XSLStylesheet.<init>(XSLStylesheet.java:260)
     at oracle.apps.xdo.common.xml.XSLTClassic.transform(XSLTClassic.java:200)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:174)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:1022)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:968)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:209)
     at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1561)
     at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:951)
I was thinking this was because there was a conflict between xalan, xerces and xmlparserv2, so I removed the xalan and xerces JARs from the classpath. Now I get the following whenever I try to hit one of my spring MVC actions:
DEBUG org.springframework.beans.factory.xml.DelegatingEntityResolver(99) - Attempting to resolve XML Schema [http://www.springframework.org/schema/beans/spring-beans-2.0.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver]
<Line 43, Column 57>: XML-24509: (Error) Duplicated definition for: 'identifiedType'
<Line 60, Column 28>: XML-24509: (Error) Duplicated definition for: 'beans'
<Line 145, Column 34>: XML-24509: (Error) Duplicated definition for: 'description'
<Line 158, Column 29>: XML-24509: (Error) Duplicated definition for: 'import'
<Line 180, Column 28>: XML-24509: (Error) Duplicated definition for: 'alias'
<Line 209, Column 33>: XML-24509: (Error) Duplicated definition for: 'beanElements'
<Line 223, Column 44>: XML-24509: (Error) Duplicated definition for: 'beanAttributes'
<Line 486, Column 43>: XML-24509: (Error) Duplicated definition for: 'meta'
<Line 494, Column 35>: XML-24509: (Error) Duplicated definition for: 'metaType'
<Line 511, Column 27>: XML-24509: (Error) Duplicated definition for: 'bean'
<Line 531, Column 38>: XML-24509: (Error) Duplicated definition for: 'constructor-arg'
<Line 600, Column 51>: XML-24509: (Error) Duplicated definition for: 'property'
<Line 611, Column 36>: XML-24509: (Error) Duplicated definition for: 'lookup-method'
<Line 647, Column 38>: XML-24509: (Error) Duplicated definition for: 'replaced-method'
<Line 684, Column 31>: XML-24509: (Error) Duplicated definition for: 'arg-type'
<Line 711, Column 26>: XML-24509: (Error) Duplicated definition for: 'ref'
<Line 749, Column 28>: XML-24509: (Error) Duplicated definition for: 'idref'
<Line 783, Column 28>: XML-24509: (Error) Duplicated definition for: 'value'
<Line 811, Column 27>: XML-24509: (Error) Duplicated definition for: 'null'
<Line 825, Column 39>: XML-24509: (Error) Duplicated definition for: 'collectionElements'
<Line 842, Column 48>: XML-24509: (Error) Duplicated definition for: 'list'
<Line 853, Column 47>: XML-24509: (Error) Duplicated definition for: 'set'
<Line 862, Column 41>: XML-24509: (Error) Duplicated definition for: 'map'
<Line 869, Column 45>: XML-24509: (Error) Duplicated definition for: 'entry'
<Line 877, Column 45>: XML-24509: (Error) Duplicated definition for: 'props'
<Line 886, Column 26>: XML-24509: (Error) Duplicated definition for: 'key'
<Line 897, Column 27>: XML-24509: (Error) Duplicated definition for: 'prop'
<Line 916, Column 39>: XML-24509: (Error) Duplicated definition for: 'propertyType'
<Line 960, Column 45>: XML-24509: (Error) Duplicated definition for: 'baseCollectionType'
<Line 971, Column 46>: XML-24509: (Error) Duplicated definition for: 'typedCollectionType'
<Line 987, Column 34>: XML-24509: (Error) Duplicated definition for: 'mapType'
<Line 1008, Column 36>: XML-24509: (Error) Duplicated definition for: 'entryType'
<Line 1047, Column 40>: XML-24509: (Error) Duplicated definition for: 'listOrSetType'
<Line 1056, Column 36>: XML-24509: (Error) Duplicated definition for: 'propsType'
<Line 1069, Column 45>: XML-24509: (Error) Duplicated definition for: 'defaultable-boolean'
ERROR org.springframework.web.servlet.FrameworkServlet(229) - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Line 10 in XML document from class path resource [spring/servlet/sellitem-webflow-config.xml] is invalid; nested exception is oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
Caused by:
oracle.xml.parser.schema.XSDException: Duplicated definition for: 'identifiedType'
     at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:431)
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:290)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:287)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:181)
     at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:151)
     at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:77)
     at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:405)
     at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:357)
     at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
     at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:126)
     at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:142)
     at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:123)
     at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:91)
     at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:94)
     at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:294)
     at org.springframework.web.context.support.AbstractRefreshableWebApplicationContext.refresh(AbstractRefreshableWebApplicationContext.java:156)
     at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:308)
     at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:252)
     at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:221)
     at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:115)
     at javax.servlet.GenericServlet.init(GenericServlet.java:211)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105)
     at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:757)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:130)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
     at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)
So it seems like these JARs are incompatible with each other. Is there any way I can use the Oracle DocumentBuilder for my XML Publisher classes and the xerces for the rest of the app?
Thanks,
Leo Hart

Now one has any advice? :(

What versions of Xerces-J and Xalan-J does JDK 1.5 make use of

Can any one tell me what versions of Xerces-J and Xalan-J does JDK 1.5 make use of.

Hi all,
I have a class which has a Vector<Vector> data
member.
I expect its collection to contain more collections
hence the Vector<Vector> type.Everything is OK with your concept, except that you just declared a variable of type "Vector of Vectors". Instead, you need to declare it as "Vector of Vector of Objects":
private Vector<Vector<Object>> coll;and initialize it with
coll= new Vector<Vector<Object>>();

Xerces and Xalan in OC4j

I am using standalone OC4J 10.1.2.0.2 and would want to use Xerces and Xalan in place or Oracle XML parser. I did initialize the container using -Xbootclasspath flag of JRE. but when the application is brought up the transform activty still shows the oracle.xml.jaxp error messages. Our app is built to work with Xerces and Xalan.
Are there any tricks invovled to make Oc4J recognize these libraries and use them ? Thanks

I think you can work that within the orion-application.xml file:
<imported-shared-libraries>
     <remove-inherited name="oracle.xml"/>
     <import-shared-library name="xalan" />
     <import-shared-library name="xerces" />
</imported-shared-libraries>
Where you've defined shared-lib entries for the above.
Reference:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html
I don't know if this is handled in the same way for the version you are dealing with, however.

Weblogic and xerces and xalan

I understand that xerces and xalan are a part of the weblogic's distribution.
Will BEA also upgrade to newer versions of these softwares as they are available?
If not how do I use newer versions of these softwares with weblogic.
This is becoming a critical issue for us as I already see a remarkable difference
in performance while doing transformations. The newer versions of xalan and xerces
are performing much better with the same xml and xsl documents as compared to
the previous versions.

According to that link your right it is not supported.
Have you tried adding the xerces jars at the beginning of the classpath?

Can jaxp and xalan help

hi
i wants to create a wordprocessor. so can the jaxp and xalan help me in opening and converting files from one type to another. if you ppl know any open source word processor plz send me or if u can give me an example thanx........

No, they can't help you.
And if you want to find an open-source word processor, Google will do that for you.

IAS6.0 SP3 and Xalan

I'm using Xalan to transform some XML messages for user usage and since
installing SP3 (worked great on SP2)
I'm getting an exception on the transformer. This is obviously a major
problem as we are faced with either
scrapping a portion of the application or reverting back to SP2.
Any insight or confirmation of similar problems/successes would be much
appreciated. The exception is as follows:
javax.xml.transform.TransformerConfigurationException: Namespace not
supported by SAXParser at
org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(Transformer
FactoryImpl.java:764)
Again this worked great in service pack 2, and it should be mentioned that I
have tried installing some of Xalan's
sample servlets onto my app server resulting in the same exception.
Thanks in advance,
Rob Woollam

Try moving the jar file for xalan to the front of the classpath
Rob Woollam wrote:
>
I'm using Xalan to transform some XML messages for user usage and since
installing SP3 (worked great on SP2)
I'm getting an exception on the transformer. This is obviously a major
problem as we are faced with either
scrapping a portion of the application or reverting back to SP2.
Any insight or confirmation of similar problems/successes would be much
appreciated. The exception is as follows:
javax.xml.transform.TransformerConfigurationException: Namespace not
supported by SAXParser at
org.apache.xalan.processor.TransformerFactoryImpl.newTransformer(Transformer
FactoryImpl.java:764)
Again this worked great in service pack 2, and it should be mentioned that I
have tried installing some of Xalan's
sample servlets onto my app server resulting in the same exception.
Thanks in advance,
Rob Woollam--
Senior Consultant / Instructor
iPlanet PS - ANZ
iPlanet e-commerce Solutions
- A Sun|Netscape Alliance
Sun Microsystems Australia Pty Ltd

Apparent Weblogic 6.0 and Xalan 2.0.1 Incompatiblity

Xalan 2 XSLT Engine does not appear to work with Weblogic 6.0. The reason
seems to be that Weblogic includes and uses some classes in weblogic.jar
which shadow the Xalan 2 files. This results in an NoSuchMethodError
(segment shown below) during the transformation process.
java.lang.NoSuchMethodError
at
org.apache.xalan.templates.ElemValueOf.execute(ElemValueOf.java:269)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
at
org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:
739)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
If Xalan 2 is placed into JRE/lib/ext, so that it takes precedence over the
weblogic Xalan classes, weblogic does not start at all because of:
javax.xml.parsers.FactoryConfigurationError:
java.lang.ClassNotFoundException: w
eblogic.xml.jaxp.RegistrySAXParserFactory
at
javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
150)
at
weblogic.xml.process.ProcessorDriver.setupSAXParser(ProcessorDriver.j
ava:246)
at
weblogic.xml.process.ProcessorDriver.<init>(ProcessorDriver.java:52)
at
weblogic.ejb20.dd.xml.EjbJarLoader_EJB11.<init>(EjbJarLoader_EJB11.ja
va:491)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at
weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.j
ava:186)
at
weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.j
ava:164)
at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:6
5)
at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4
7)
at
weblogic.ejb20.internal.EJBMBeanFactory.parseEjbJar(EJBMBeanFactory.j
ava:215)
at
weblogic.ejb20.internal.EJBMBeanFactory.getMBeans(EJBMBeanFactory.jav
a:138)
at
weblogic.management.mbeans.custom.Application.initializeMBean(Applica
tion.java:529)
at
weblogic.management.mbeans.custom.Application.initializeMBeans(Applic
ation.java:452)
at
weblogic.management.mbeans.custom.Application.adminLoad(Application.j
ava:252)
at
weblogic.management.mbeans.custom.Application.load(Application.java:2
05)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:559)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:545)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:431)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy12.load(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.loadApplications
(ApplicationManager.java:274)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:236)
at
weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:121)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:559)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:545)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:431)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy40.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:435)
at weblogic.management.Admin.startApplicationManager(Admin.java:959)
at weblogic.management.Admin.finish(Admin.java:459)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Regards
Ben Hutchison
Finetix UK

Hi,
I solved the problem under WL 5.1.0 & WL 6.0 putting xalan.jar &
xerces.jar before weblogicaux.jar (weblogic.jar in WL 6.0).
WL include a DOM level 1 API while Xalan requires a DOM level 2.
But putting xerces.jar before it in the path should fix it.
set CLASSPATH=.\config\efgweb\wl_cp_lib\xalan.jar
set CLASSPATH=%CLASSPATH%;.\config\efgweb\wl_cp_lib\xerces.jar
set CLASSPATH=%CLASSPATH%;.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
Regards
Simone
Ben Hutchison wrote:
>
Xalan 2 XSLT Engine does not appear to work with Weblogic 6.0. The reason
seems to be that Weblogic includes and uses some classes in weblogic.jar
which shadow the Xalan 2 files. This results in an NoSuchMethodError
(segment shown below) during the transformation process.
java.lang.NoSuchMethodError
at
org.apache.xalan.templates.ElemValueOf.execute(ElemValueOf.java:269)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
at
org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:
739)
at
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
If Xalan 2 is placed into JRE/lib/ext, so that it takes precedence over the
weblogic Xalan classes, weblogic does not start at all because of:
javax.xml.parsers.FactoryConfigurationError:
java.lang.ClassNotFoundException: w
eblogic.xml.jaxp.RegistrySAXParserFactory
at
javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:
150)
at
weblogic.xml.process.ProcessorDriver.setupSAXParser(ProcessorDriver.j
ava:246)
at
weblogic.xml.process.ProcessorDriver.<init>(ProcessorDriver.java:52)
at
weblogic.ejb20.dd.xml.EjbJarLoader_EJB11.<init>(EjbJarLoader_EJB11.ja
va:491)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at
weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.j
ava:186)
at
weblogic.xml.process.ProcessorFactory.getProcessor(ProcessorFactory.j
ava:164)
at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:6
5)
at
weblogic.ejb20.dd.xml.DDUtils.loadDeploymentDescriptor(DDUtils.java:4
7)
at
weblogic.ejb20.internal.EJBMBeanFactory.parseEjbJar(EJBMBeanFactory.j
ava:215)
at
weblogic.ejb20.internal.EJBMBeanFactory.getMBeans(EJBMBeanFactory.jav
a:138)
at
weblogic.management.mbeans.custom.Application.initializeMBean(Applica
tion.java:529)
at
weblogic.management.mbeans.custom.Application.initializeMBeans(Applic
ation.java:452)
at
weblogic.management.mbeans.custom.Application.adminLoad(Application.j
ava:252)
at
weblogic.management.mbeans.custom.Application.load(Application.java:2
05)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:559)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:545)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:431)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy12.load(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.loadApplications
(ApplicationManager.java:274)
at
weblogic.management.mbeans.custom.ApplicationManager.startConfigManag
er(ApplicationManager.java:236)
at
weblogic.management.mbeans.custom.ApplicationManager.start(Applicatio
nManager.java:121)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:559)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:545)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:285)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
55)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
23)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:431)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:172)
at $Proxy40.start(Unknown Source)
at
weblogic.management.configuration.ApplicationManagerMBean_CachingStub
.start(ApplicationManagerMBean_CachingStub.java:435)
at weblogic.management.Admin.startApplicationManager(Admin.java:959)
at weblogic.management.Admin.finish(Admin.java:459)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:429)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:170)
at weblogic.Server.main(Server.java:35)
Regards
Ben Hutchison
Finetix UK

JDK1.4.2 and xalan conflict?

In my java code, I apply an xsl to an xml file. It works fine in JDK 1.4.1 but when I change JDK to 1.4.2
I got the following error
javax.xml.transform.TransformerException: java.lang.ArrayIndexOutOfBoundsException: 0.
The error occurs in org.apache.xalan.transformer.TransformerImpl class. I know JDK1.4.2 bundled with xalan classes. Is there any conflict? Why it works in JDK1.4.1 but not JDK1.4.2? How can I bypass xalan classes in JDK1.4.2 and use seperate xalan.jar from apache?

I have a similar problem where using XPathAPI.selectSingleNode(aNode, "/Parent/Child/") works
fine with jdk1.4.1 but not with jdk1.4.2;
the error i get is a javax.xml.transform.TransformerException where is complains about
"A location step was expected following the '/' or '//' token."
What i tried doing was removing the trailing slash at the end of the xpath expression and it seemed
to resolve it fine.
Is this a change in the way xalan's XPathAPI behaves to remove ambiguity in the xpath expression?
As a side not, I am using weblogic 8.1 SP1 and trying to put another version of xalan in the startup
PRE_CLASSPATH doesnt seem to get around this.
would appreciate any insight.

JRE 1.5.0 and XALAN issue

<xsl:sort> does not give output on jre version 1.5.0 and above,while for jre versions 1.4.2 it gives proper output.
Can anybody provide any solution.
Thanks in advance

Yes try Mozilla-1.7.3. Remove the dirs of the old java installations. rm -rf /usr/javaxxx . Look where java is installed. Go to this link and download and do this rpm -i j2re-1.4.2-8.0.rh9.dag.i586.rpm
mozilla-j2re-1.4.2-9.0.rh9.dag.i586.rpm
The link where the packages are:
http://dag.wieers.com/packages/j2re/
I think you can update mozilla by using yum in rh9.
yum update mozilla
and there you go :D

XALAN and XERCES on WL6

Hi!
I just can't get WLS6.0 to use new versions of XALAN and XERCES. I keep
getting errors that are obviously because Weblogic is loading an older
version of XALAN before my app ever gets loaded, and as a result I'm having
trouble with <xsl:param> and <xsl:variable> tags not being able to recognise
other params and variables in the top level scope. This is crucial to my
application but after a day of messing around with everything from
classpaths to startweblogic.cmd, I'm pretty much stuck.
Does ANYONE know how to fix this?
TIA,
Navneet

Hmm.. what's this I'm hearing about an XML registry for weblogic?
"Jeffrey Winter" <[email protected]> wrote in message
news:3ae702c5$[email protected]..
>
If you put the latest xerces.jar and xalan.jar file before anything elsein the
CLASSPATH in your startup command file it will work. I'm doing in rightnow with
Xerces 1.3.1 and Xalan 2.0.1.
If you're trying to use JAXP however, you'll have problems because WLalways returns
their own internal version of the DocumentBuilderFactory even if you putthe JAXP
1.1 jar file in the class path and specify theorg.apache.xerces.jaxp.DocumentBuilderFactory
in your registry.
We got around this by defining a stub subclass of DocumentBuilderFactoryand instantiating
is directly instead of through DocumentBuilderFactory.newInstance(). It'sa pain,
but after that you can get around using the older versions that they'vebaked
in.

Oracle xmlparserv2

Hi
I have deployed an XML based application on Oracle9iAS Release 2 (v9.0.2). Application Server is forcing me to user Oracle's xmlparserv2 (and saxon) whereas my application has been written according to xalan (and xerces).
Can some one help me as how to instruct Oracle9iAS to use xalan insread of xmlparserv2.
I may add here that if I (completely) replace the xmlparserv2.jar with xalan.jar then I am unable to start OC4J.
I would appreciate if could also CC the response to my personal email [email protected]
Atif

Atif,
Please post queries related to Oracle9iAS in the Application Server forum at : Oracle Application Server - General for quick response.
Thanks
Pushkala

JTextPane and XMLParser and jdk .-) problems

Hi there.
I have a nice problem, which really gives me headaches.
I have an XML editor (working as an applet or as an aplication, using a JTextPane). All worked ok untill jdk1.3 and parts even until jdk1.4. Now 2 big problems appeared.
1.Under jdk1.4.1:
Spaces between lines are awful big. The actual characters are ok, but the cursor is almost twice as the characters. The distance from the bottom of a character and the bottom of the line is pretty big. Now that looked to me as a SpaceBelow or LineSpacing problem. I've tried to set up the SpaceBelow or/and LineSpacing... everything that I've thought it should work. No result. Seems like they have no effect when XMLParser comes in place and sets up the document content (at least i think this is the reason, also i'm not sure). An element tree implemented shows me that this attributes are set to the values I've intended, but no 'visual' effect. Does anyone know ANYTHING about this? Please!
2.Starting from jdk1.3. Doubling of tags.
If the XML editor reads something like <FT>something</FT> from a xml file, it sets in the JTextPane <FT><FT>something</FT></FT>. It's working under jdk1.2 but if I switch to 1.3 or 1.4does something like this. Any idea what's going on? Could it be an unfortunate mix between jdk and xalan libraries?
I REALLY hope that ANYONE of you knows ANYTHING about these!!!
THNX!

Hi DrClap.
Well, this would be the best thing to do. The only problem is that those are long time gone. Not really 'gone', but they are not to be found.
There's something about first problem: At the end of starting process, after the parser finished his work, if I come and set the attributes (in the document of the JTextPane, using StyleConstants) with replace set to true, the display is ok but, of course, I loose any style defined in the xml file. That means is not a problem of the JTextPane in jdk 1.4 (at one time I thought it might be a 'mapping' problem of the JTP in 1.4) or?
Because I'm really stuck, I have all kind of strange ideas!!!
Could be "old libraries(for the parser) - new jdk" mixture problem, perhaps? (I've told you!)
THX for your previous response.

Xalan XPathAPI selectNodeIterator help

so i got xml something like this
<abc>
<bcd>
   <cde/>
   <cde/>
</bcd>
<bcd>
   <cde/>
   <cde/>
</bcd>
</abc>
so i parse the doc tree using xerces which seems fine, and i pass the
root element to XPathAPI with xpath /abc/bcd and it gives me back a list
of the 2 <bcd> nodes which is great. then i try to process each their
childs so i pass each of the <bcd> node to XPathAPI with xpath of
/bcd/cde and i get nothing. so fine, i give it //cde with each one of
the <bcd> node as the other argument but now i get all 4 of the <cde>
nodes back instead of the 2 child <cde>. what am i doing wrong?
i am using jdk 1.3.1_01, and xalan 2.5.0. thanks.

...then i try to
process each their
childs so i pass each of the <bcd> node to XPathAPI
with xpath of
/bcd/cde and i get nothing.That's right, none of the bcd elements have children that are bcd elements with cde children. If you want the cde children of a bcd node then "/cde" would work better. (Or "cde", perhaps.)
so fine, i give it //cde
with each one of
the <bcd> node as the other argument but now i get all
4 of the <cde>
nodes back instead of the 2 child <cde>.That's right, //cde means "start at the root and find all cde elements at any depth".

Xalan.jar can't ever be deployed in a .war?

          I'm using WLS 6.1 SP3.
          Even when xalan.jar is bundled in a .war at /WEB-INF/lib, trying to use the Xalan
          classes results in the following exception:
          javax.xml.transform.TransformerFactoryConfigurationError: java.lang.ClassNotFoundException:
          org.apache.xalan.processor.TransformerFactoryImpl
          at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:121)
          The most commonly recommended solution is to add xalan.jar to the system classpath
          prior to starting WLS. And xalan.jar should come before weblogic.jar in the classpath.
          I see this workaround commonly recommended, but I've yet to see an explanation
          as to why it's neccesary. Given that I'd rather not have libs in the system classpath
          unless it's absolutely necessary (since they can't be dynamically redeployed),
          I want to make sure I understand the reasons behind adding xalan.jar to the system
          classpath. Here's my understanding. Let me know how mistaken I am. :-)
          Even though xalan.jar isn't needed at startup, xalan.jar needs to be in the system
          classpath instead of just contained within the .war. This is because weblogic.jar
          contains the javax.xml.transform.TransformerFactory class. And even though the
          system property "javax.xml.transform.TransformerFactory" is set to "org.apache.xalan.processor.TransformerFactoryImpl"
          by default, the parent classloader (i.e. the system classloader which has loaded
          TransformerFactory from weblogic.jar) can't see the Xalan classes it needs from
          the child classloader (i.e. a .war classloader that would contain xalan.jar.)
          Is this assertion correct? Classloader hierarchy issues?
          Thanks,
          Matt


Assuming you can't use the weblogic-application semantics in a WAR, you might consider using a servlet context listener. I don't know exactly what context you need to have available for this task, but when the context is about to be destroyed, the "contextDestroyed()" method of the context listener will be called, which might be sufficient for your needs.

Xmlparserv2 and xalan

Similar Messages

Maybe you are looking for