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? :(

Similar Messages

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?

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

How to determine the version of xmlparserv2.jar?

Hi,
Is there any way I can determine the version of an
xmlparserv2.jar file?
I am using XML Parser V2 (xmlparserv2.jar) with the following
file size: 1,086,234 bytes.
This was supplied with JDeveloper 3.1 but I have no idea what
version is it? Any help on this will be appreciated.
TIA,
-Piyush

the class oraxml does not exist in this version of the jar!
however i do see an entry like: xmlparser_2.0.2.6_production
when i open the jar file in winzip!
i have cross verfied with other xmlparserv2 files (diff file
sizes) and this seems to be it.
thanks for the suggestion.
regards,
-Piyush

Jars with JCreator

Hi
I have made a jar with JCreator and it works, but it needs the images and texts (that are in sudirectories; /images and /texts). JCreator shows all the files while making the .jar, and with the jar.exe i can see that the .jar contains the files, but it need them anyway, the jar alone cannot work.
Anybody know? thanks

Are you refering to Java Studio Creator?
You may want to try posting here: http://swforum.sun.com/jive/forum.jspa?forumID=123
What exactly do you mean by "the jar alone cannot work"?
-Alexis

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>>();

Diff between oracle's org.w3c.dom in xmlParserV2.jar and JREs impl?

New to Java/oracle enviornment.
I have an class that retrieves clobs from 10g. I need to include oracles xmlParserV2.jar in the classpath for XMLType support.
I then added this class to my app.
When I do this, areas in my app that previously used the JRE org.w3c.dom bombs with the exception: AbstractMethodError: getTextContent()....
I am assuming that when I set xmlParserv2.jar in my class path, that my app is now using oracle's implementation of the org.w3c.dom....
I say this because I see the org.w3c.dom.. in the xmlParserv2jar. Is my app running into some incompatibility with the way oracle has implemented the org.w3c.dom.
Is there a xmlParserv2.jar without the org.w3c stuff?
I need the XMLType support from xmlParserv2.jar. Is the XMLType support dependent on oracles implementation of the org.w3c.dom....?
Thanks everyone;
Any help appreciated.

I dont find the j2ee_1.3.01.jar file in a simple oc4j installation. Its present in the bpel/lib directory if you install the full soa suite.
I removed the oc4jclient.jar, and I see the same behavior as mentioned above. If I just have two jar files - orabpel.jar and orabpel-common.jar, my application does not start up (no logs are created). When I add the j2ee_1.3.01.jar, then the logs are created but I see the LinkageError in the opmn logs.
Thx,
Prabhat

Can't get matching xdb6.jar, xmlparserv2.jar and ojdbc6.jar

No matter what I try, they are always somewhat different and I'm getting exceptions with JDBC on either setSQLXML or on .getString() once I retrieved the SQLXML object and want to get the content back or I'm downright getting "oracle.xdb.XMLType cannot be cast to java.sql.SQLXML"
How is it possible that Oracle who owns Java and OracleDB can't make a working Java driver? I just want to be able to work with XML, I didn't know this was asking much. I have OracleXE installed.

Welcome to the forum!
Whenever you post you need to provide ALL of the product and version information applicable to the question or issue you are asking about
>
No matter what I try, they are always somewhat different and I'm getting exceptions with JDBC on either setSQLXML or on .getString() once I retrieved the SQLXML object and want to get the content back or I'm downright getting "oracle.xdb.XMLType cannot be cast to java.sql.SQLXML"
>
Before you submit a question or issue use the 'Preview' tab so you can see it as it will display. Then read your entire submission and ask yourself:
>
Could I answer a question like that based ONLY on the information that was provided?
>
For this thread the answer would be NO!
All you have done is complain. That is basically the equivalent of a five year old saying 'Mommy, my tummy hurts'.
>
No matter what I try
>
What did you try? You haven't posted ANY information about what you are even doing, what jars, tools or code you are doing it with or HOW you are doing it.
>
I'm getting exceptions with JDBC on either setSQLXML or on .getString() once I retrieved the SQLXML object
>
What exceptions? You haven't posted ANY exceptions or any of the code that caused those exceptions.
Retrieved WHAT SQLXML object? Retrieved from where? What is the full name and version of the database you are using? For Oracle that would be the 4 digit version as returned by 'SELECT * FROM V$VERSION'. Oracle DB doesn't have any SQLXML objects; it has XMLTYPE columns. Is that what you are trying to access?
>
Can't get matching xdb6.jar, xmlparserv2.jar and ojdbc6.jar
>
Where did you get them from? How did you get them? How do you know that they don't match? What is the full name and version of the jars that you are using?
Have you used this functionality before? Do you know how to use it? If you have never used it and have no expertise with it we need to know that so we can tell you how to get up to speed so you can use it successfully.
Since you haven't provided ANY of the information needed to provide any specific suggestions all we can do is assume that you are using the last, current version of Java and all jars files and have never used the functionality. In that case you need to start at the beginning.
Review the relevant sections of the JDBC Developer's Guide
http://docs.oracle.com/cd/E18283_01/java.112/e16548/jdbcvers.htm#BABGHBCC
>
SQLXML Type
One of the most important updates in JDBC 4.0 standard is the support for the XML data type, defined by the SQL 2003 standard. Now JDBC offers a mapping interface to support the SQL/XML database data type, that is, java.sql.SQLXML. This new JDBC interface defines Java native bindings for XML, thus making handling of any database XML data easier and more efficient.
The oracle.jdbc.getObjectReturnsXMLType Property
In Oracle Database 10g and earlier versions of Oracle Database 11g, Oracle JDBC drivers supported the Oracle SQL XML type (XMLType) through an Oracle proprietary extension. XML values were represented by instances of the oracle.xdb.XMLType class and the SQL XMLType values were read and set through the JDBC standard getObject, setObject, and updateObject methods.
The JDBC standard requires the getObject method to return an instance of java.sql.SQLXML type when called on a SQL XML type column. But, the earlier versions of Oracle JDBC drivers return an instance of oracle.xdb.XMLType. This does not conform to the JDBC standard.
The current release of Oracle JDBC drivers conform to the JDBC standard with the introduction of a new connection property, oracle.jdbc.getObjectReturnsXMLType. If you set this property to false, then the getObject method returns an instance of java.sql.SQLXML type. You can achieve this by using the following command line option while compiling your program with javac:
-Doracle.jdbc.getObjectReturnsXMLType="false"
If you depend on the existing Oracle proprietary support for SQL XMLType using oracle.xdb.XMLType, then you can change the value of this property back to true by using the following command line option:
-Doracle.jdbc.getObjectReturnsXMLType="true"
The value of the oracle.jdbc.getObjectReturnsXMLType property is a String representing a boolean value of either true or false. If the value of this property is true, then the getObject method returns oracle.xdb.XMLType instances, when called for a SQL XMLType column. This is the deafault value of the oracle.jdbc.getObjectReturnsXMLType property. If the value of this property is false, then the getObject method returns java.sql.SQLXML instances. This is the standard JDBC-compliant mode.
Note:
The oracle.jdbc.getObjectReturnsXMLType property affects only the result of the getObject method. All other methods conform to the JDBC 4.0 standard regardless of the value of the property.
>
The exception that you are getting
>
oracle.xdb.XMLType cannot be cast to java.sql.SQLXML
>
is telling that the XMLType is NOT an SQLXML type so you can't use it as one. That doc section above should tell explain that those are two DIFFERENT types. You use one or the other depending on which version of the functionality you want to use. You can use the older 'non-JDBC' standard or the new 'JDBC' standard. But you can't mix the two.
Review that entire chapter of the doc and see if that helps.
If not then you need to provide ALL relevant information if you need more help:
1. Java version
2. DB name and version
3. JAR file names and versions
4. Java code that demonstrates the problem
5. EXACT copies of any and all exceptions and errors that occur
6. A description, in English, of what you are trying to do and how you are trying to do it.
When you post use \ on the line before and on the line after any code to preserve formattting. See the FAQ for other formatting guidelines. Use the 'Preview' tab to see what your post will look like before you submit it.

Xdb.jar and xmlparserv2.jar for JBossWeb/2.0.0.GA

I am using xdb.jar and xmlparserv2.jar files in JBoss 4.0.0 and it is working fine but when i deploy my code on JBossWeb/2.0.0.GA it is giving error.
"java.lang.NullPointerException
org.apache.commons.digester.Digester.getXMLReader(Digester.java:899)
org.apache.commons.digester.Digester.parse(Digester.java:1647)
org.apache.struts.action.ActionServlet.parseModuleConfigFile(ActionServlet.java:1006)
org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:955)
org.apache.struts.action.ActionServlet.init(ActionServlet.java:470)
javax.servlet.GenericServlet.init(GenericServlet.java:212)
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:437)
org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:381)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:595)"
Could anyone pleaese suggest what could be the possibe reason for this error. Do we need some differant version of jar files for the JBossWeb/2.0.0.GA.
Thanks and Regards
Govind Bajoria

I had a similar problem using xmlparserv2.jar and commons-digester in the same application. It appears that xmlparserv2 sets itself as the default SaxParser but commons-digester doesn't like this (I read it looks for a Version class for the SaxParser and can't find it).
I solved this problem by explictly setting the SaxParserFactory by adding this System parameter
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
This works for JDK 6 but I assume if you are using an early JDK version and have xerces jar on the class path then setting the following will also work
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl

Xmlparserv2.jar conflicts with xmlparserv2-904.jar

Hi everyone,
I'm trying to use the BI Publisher APIs within a Java Embedding activity. These APIs uses the xmlparserv2-904.jar version of the library. But the oracle.xml shared library that the OC4J instance contains, uses the xmlparserv2.jar which is not compatible with the BI Publisher APIs. Is there a way i can tell a BPEL process to use the version of the library that I deploy with my projet instead of using those from the OC4J instance shared libraries??
Any help is welcome!!
P.S: See post:
XML publisher with jdeveloper
Message was edited by:
GMB

Now one has any advice? :(

How to compile and creat JAR with native function

Hi there,
I wrote some native function for J2ME. But it seems like using J2ME wireless Toolkits, we can not compile native function. Is it right?
Is anyone knowing how to compile and make JAR with J2MEWTK or command line?
Thanks,
Merry Christmas!!

[zack327],
JNI like or native interfaces APIs is not supported in the CLDC/MID Profile 1.0 specification. If you have J2ME code that includes JNI code, the J2MEWTK tool will not compile successfully for you.
To package the compiled code to a MIDlet suite .jar file, use the 'Package' command in the J2MEWTK toolkit. It is found on the top menu bar 'Project' option as item on the dropdown list.
To package the MIDlets into a MIDlet suite .jar file from the command line, you can execute the usual jar file command:
jar cf MyMIDletSuite.jar Midlet.class
You will also need to create a MIDlet .jad Application Descriptor file as well.
HTH.
Allen Lai
Developer Technical Support
SUN Microsystems
http://www.sun.com/developers/support/

Object tag not downloading jars with JRE 1.4.2 and above

Hi All,
I have a HTML page and following object tag in it:
<OBJECT id = obj classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93" WIDTH="0" HEIGHT="0">
<PARAM NAME ="code" VALUE="VIP6.class">
<PARAM NAME ="archive" VALUE="vipjar.jar,vipserver.jar,powerj.zip">
<PARAM NAME="type" VALUE="application/x-java-applet;jpi-version=1.4">
<PARAM NAME="scriptable" VALUE = "true">
<br>
<P>
<H2>The Java 2 plugin is required for this application. Please call Application Support or the Inventory Hotline<br>
</H2>
</P>
</OBJECT>Above OBJECT tage downloads files vipjar.jar,vipserver.jar and powerj.zip on user's machine when page is browsed using JRE version 1.3.1. But when JRE version 1.4.2 and above is used then the jar's doesn't get downloaded and the application does not find the neccessary class files for execution.
Please advice what needs to be done so that the object tag runs correctly with JRE version's 1.4.2 and above.
Thanks in advance for any help.
Vineet

Hello,
Indeed those JAR files are compiled with JDK 1.3. However, the AS Java systems are running 1.4.x, hence, there is no problem to use those JARs with the JRE 1.4. That's why I do not believe your issue is related to the JRE version. In addition, those JAR files do not have 1.4 compiled version.
Kind regards,
Tsvetomir
Edited by: Tsvetomir Tsvetanov on Jun 9, 2009 5:47 PM

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

OC4J 10.1.2 to Weblogic 11g (10.3.5) xmlparserv2.jar dependency

I am trying to upgrade from OC4J 10.1.2 to Weblogic 11g (10.3.5).
I used the smartupgrade tool and it has highlighted some required modifications before upgrading.
For example:
<snip>
Rule: Oracle Private Dependencies
Category: api
Priority: required
Complexity: high
Reason: xxx.admin.ejb.AdminCtrl.jar contains the following unsupported Oracle dependencies:
AdminCtrlBean.class on [oracle.xml.parser.v2.DOMParser (orasaaj.jar), oracle.xml.parser.v2.XMLParseException (orasaaj.jar), oracle.xml.parser.v2.XMLDocument (orasaaj.jar)]
Advice: To ensure the proper functioning of deployed applications, features that depend upon the identified API need to discontinue using the identified unpublished Oracle API.
Implication: Features associated with the identified API may be broken, or the application itself may not function properly if at all because they depend upon unpublished Oracle dependencies.
</snip>
I want to follow the 'Advice', but I'm not sure what the best method is for correcting this issue.
Should I move away from the xmlparserv2.jar for xml processing?
If yes, what is the recommended replacement for xmlparserv2.jar in Weblogic 11g?
Any help, guidance or pointers are greatly appreciated.
Thank you.
Edited by: loopy1 on May 29, 2012 11:42 AM

When migrating to weblogic from oc4j, you should discontinue use of the Oracle xml parser. Use the standard java sdk parser.
This code snip:
StringReader sr = new StringReader(xmlString.toString());
DOMParser parser = new DOMParser();
parser.parse(sr);
Document doc = parser.getDocument();
Is converted to this code snip:
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
StringReader sr = new StringReader(Sparameters);
InputSource is = new InputSource(sr);
Document doc = db.parse(is);
I found this information in this documentation:
http://docs.oracle.com/cd/E13222_01/wls/docs103/xml/programming.html#wp1069856
I hope this is helpful to someone.
S

Xmlparserv2.jar with xerces and xalan

Similar Messages

Maybe you are looking for