WSAD 5.0 and Xerces

Has anybody used Toplink with WSAD 5.0. org.apache.xerces.framework.XMLParser isn't supported in the version of xerces.jar. The xerces.jar that comes with Toplink screws up the app server. The early release of WSAD 5.0 and 4.0 are fine but we need to move to servlet 2.3 and don't want to lose Toplink!
Thanks for any help.

I found the same issue in an earlier topic (Maarten Coene (Feb 24, 2003 7:28 AM)). The work around seems fine but is there news on 9.0.4?
Thanks

Similar Messages

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.

[svn:fx-trunk] 7796: get the correct locales of batik and xerces jars into the build

Revision: 7796
Author:   [email protected]
Date:     2009-06-12 13:01:48 -0700 (Fri, 12 Jun 2009)
Log Message:
get the correct locales of batik and xerces jars into the build
bug: https://bugs.adobe.com/jira/browse/SDK-21565
qa: i18n team (make sure they're all there)
checkintests: pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21565
Modified Paths:
    flex/sdk/trunk/build.xml

Originally posted by: rosec.messagingdirect.com
I'll look into it; I'm a bit under the gun here and can't easily upend
my development environment at this time, but hopefully I can look into
it early next week. Thanks for the pointer.
Daniel Megert wrote:
> Chris Rose wrote:
>> I don't know if this has been asked before (and you'd be amazed at how
>> hard it is to find specific information when your search query is
>> "eclipse 100% cpu usage opening class files in a jar"!) but, well,
>> that's what I'm getting:
>>
>> When I open a class file in the editor that is contained in a jar file
>> anywhere on a Java project's classpath, one of my processor pegs at
>> 100% usage for anywhere from 15-120 seconds and eclipse becomes
>> non-responsive for that period of time, not even redrawing the UI.
>>
>> This occurs for jars as large as the jboss client jar and the weblogic
>> 80Mb uber-jar and for jars as small as a 241kb library jar.
>>
>> Is there anything I can do to track down WHY this is happening? I end
>> up having to trace into third party code a lot while debugging
>> container behaviour and this plays merry havoc with the timeouts for
>> remote calls, so I'm quite motivated to suss out why it's happening.
>>
>> Eclipse details are attached.
> There was a bug regarding big JARs on the build path. Can you try
> whether this still happens using 3.4 M7. If so, please file a bug report
> with steps to reproduce. Also, please create some stack dumps while
> waiting and attach them to the bug report.
>
> Dani
Chris Rose
Developer Planet Consulting Group
(780) 577-8433
[email protected]

Weblogic 8.1 with Xalan 2.6.1 and Xerces 2.6.2 ?!?

Hi,
I'm trying to use Xalan 2.6.1 and Xerces 2.6.2 with Weblogic 8.1SP2, but no result yet...
I found docs on bea website:
http://edocs.bea.com/wls/docs81/pdf/faq.pdf
http://e-docs.bea.com/wls/docs81/xml/xml_admin.html
where I found this:
"Warning: In version 8.1 of WebLogic Server, you can plug in only the following versions of the Apache Xerces parser:
Xerces 2.2.0
Xerces 2.3.0
Xerces 2.4.0
In addition, you can plug in only those versions of the Apache Xalan transformer that are compatible with the preceding versions of the Apache Xerces parser."
I can't find any solution to this?
I tried various option:
- xercesImpl2.6 in the classpath variable
- xalan2.6.2 in the endorsed lib
- registered factory impl names in xml registry
- prefer web-inf set to true
Errors result in following exception:
- NoMethodFound (rhino classes inside weblogic.jar)
- ClassCast (xalan/xerces conflicts)
Any one has suggestions?
Regards
Leonardo

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

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?

DOM and XERCES

Hi Friends,
I am using ECLIPSE IDE and writing a java class using DOM and XERCES
to traverse through an xml file which is already stored in the local drive by hard coding the path in the code.
and this is working fine.
But now i want to traverse an Active Document (an xml file that is already opened when u launch an Eclipse application) so.. is there any method in DOM to access or traverse through the current Active Document ?
if there is please let me know.. it's urgent.. help me on this please.
Thanks in advance,
-Karthik

Can u send me the code. You might have missed out something on reading that XML .

Xalan and Xerces

Where do I get the compatible versions of above jars to do XSL Transformations. Pls help... Tried to do lot of research and not able to do much. Lates Xalan does not have XSLTProcessor, XSLTProcessorFactory and XSLTInputSource. I tried to use older version of Xalan and found that Xerces is not compatible with it.

Xalan-Java version 2.6.0 distribution includes xercesImpl.jar from Xerces-Java 2.6.2.
http://xml.apache.org/xalan-j/

SAX parsers hanging (crimson and xerces) on InputStream

Hi,
While searching I've seen a lot of postings about sax parsers hanging on InputStreams. Many have no replies, some do. So far I've tried several fixes mentioned to no avail. I've seen it hang in the startDocument() and hang after reading the entire document. All sorts of hangs . . . Oh and in some situations it works fine, but that's not good enough.
1. I tried wrapping the InputStream as described at the jdom.org FAQ with my own InputStream that hides the close() call. Then I pass my wrapper InputStream to the saxparser.parse() method. This didn't work, because you need to wrap SocketInputStream, not InputStream and SocketInputStream has package permissions which keep me from inheriting from it. If somebody can shed some light on how to do this, I'll try again, but for now that approach is shelved.
2. I tried adding an EOF character, 0x1A, to the end of the xml string being sent over the socket. The parser still hangs.
Any more suggestions?
Thanks,
Steve

Here's a faq question and answer from jdom.org. Can anybody explain how to do this in more detail? He mentions two workarounds. I've done the second and it works fine, but I'd prefer to get the first workaround working instead -- the wrapper InputStream idea.
Why does passing a document through a socket sometimes hang the parser?
The problem is that several XML parsers close the input stream when they read EOF (-1). This is true of Xerces, which is JDOM's default parser. It is also true of Crimson. Unfortunately, closing a SocketInputStream closes the underlying SocketImpl, setting the file descriptor to null. The socket's output stream is useless after this, so your application will be unable to send a response. To workaround, protect your socket's input stream with an InputStream wrapper that doesn't close the underlying stream (override the close() method), or read everything into a buffer before handing off to the JDOM builder:
byte[] buf = new byte[length];
new DataInputStream(inputStream).readFully(buf);
InputStream in = new ByteArrayInputStream(buf);
(Contributed by Joseph Bowbeer)

Importing coherence-tx.rar in WSAD 5.1 and deploying it on WAS 5.1

All,
I have downloaded coherence s/w (3.2.2 build 371) for evaluation purposes, on desktop environment.
I am currently trying to import the cohrence rar file into WSAD 5.1.2 so i can built it into my ear file (which contains an MDB and 1 servlet). I am trying to test the code (published on code section of this web site) demonstrating how to put to a distributed cache within scope of a JTA/MDB/EJB XA transaction.
I tried importing the rar file into WSAD in 2 ways
a) In J2EE hierarchy, under modules ->did right click->import->import rar file. After giving the path of the rar file on my desktop, WSAD gives an error 'Missing required library:Coherence-txConnector/imported_classes' in the 'tasks' panel of WSAD. It also gives errors pertaiing to some weblogic specific ra.xmls. When i removed the weblogic xmls in the rar file and tried again - it still gives the missing requierd library error.
It is however able to create the coherence-txConnector module under 'Connector Modules' tree in J2EE hierarchy tab
b) I then deleted this module from WSAD and tried doing file->import->rar file. again I get the same error pertaining missing classes.
I have added tangosol.lib, coherence.lib to the java build path for my war/MDB projects - dont know if this is related to above issue or not.
2) Assuming I am able to build the ear with this rar included in it, when I am going to install the ear on my WAS instance, are there any specific settings that need to be done to configure the rar adapter (within my ear).
Apologise if these may seem silly questions - but this is the first time i am working with resource adapters in WSAD/WAS environments.
Any help given will be appreciated since this is a stumbling block now.
regards,
Sanjeev.

Dimitri,
Further updates to this issue (as on 27th Feb) - I tried the following strategy (since there were no responses to my forum posting)
1) I cleaned up my ear project in WSAD (removed the connector and all references to it in the ear) and simply imported the connector rar as a standalone connector in WSAD (not part of the ear) using File->import->import rar file (note - i have removed the weblogic specific xml from the rar files shipped with Coherence).
2) Was able to build my ear without any issues (I have kept references to tangosol.jar and coherence.jar in the root of the ear). The web project within the ear refers to these 2 jars via entries in its manifest file.
3) I additionally deployed the rar file on a WAS instance through the admin console using Resources->Resource Adapters->install RAR.Once it installed, I gave the JNDI name (in J2C connection Factories) as tangosol.coherenceTx for this resource adapter. I used defaults for everything else.
4) After that - I deployed the ear without any issues.
5) However - when I execute my servlet (which basically puts a cache entry via the CacheAdapter, within a JTA transaction) - I get the following exception.
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R (Wrapped) com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.NoClassDefFoundError: com/tangosol/util/WrapperException
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at java.lang.Class.getDeclaredConstructors0(Native Method)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at java.lang.Class.privateGetDeclaredConstructors(Class.java(Compiled Code))
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at java.lang.Class.getConstructor1(Class.java(Compiled Code))
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at java.lang.Class.newInstance3(Class.java(Compiled Code))
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at java.lang.Class.newInstance(Class.java(Compiled Code))
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ejs.j2c.J2CXAResourceFactory.createMCFEntry(J2CXAResourceFactory.java:344)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1414)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1201)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:873)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:680)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1712)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1567)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1480)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1187)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1067)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at javax.naming.InitialContext.lookup(InitialContext.java:360)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.tangosol.run.jca.CacheAdapter.<init>(CacheAdapter.java:94)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at CacheMessagePublisher.doGet(CacheMessagePublisher.java:46)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:974)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:555)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:200)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:439)
[2/26/07 15:30:43:248 IST] 2de2d2e4 SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R (Wrapped) com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.NoClassDefFoundError: com/tangosol/util/WrapperException
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at java.lang.Class.getDeclaredConstructors0(Native Method)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at java.lang.Class.privateGetDeclaredConstructors(Class.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at java.lang.Class.getConstructor1(Class.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at java.lang.Class.newInstance3(Class.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at java.lang.Class.newInstance(Class.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ejs.j2c.J2CXAResourceFactory.createMCFEntry(J2CXAResourceFactory.java:344)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1414)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1201)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:873)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:680)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1712)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1567)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1480)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1187)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1067)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at javax.naming.InitialContext.lookup(InitialContext.java:360)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.tangosol.run.jca.CacheAdapter.<init>(CacheAdapter.java:94)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at CacheMessagePublisher.doGet(CacheMessagePublisher.java:46)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java(Inlined Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java(Inlined Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:119)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:276)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
[2/27/07 11:02:59:106 IST] 6d9ed2e5 SystemErr R      at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
The WrapperException class is within tangosol.jar which is present in manifest reference of war file, so I am not able to understand why this exception should come.
Any help on this matter is highly appreciated - since without resolving this issue I cannot evaluate the transactional abilities of Coherence.
Pls let me know if you want me to send u additional details/the ear itself?
regards,
Sanjeev.

SunOne and Xerces-c

We developed a C++ native driver which linked with Xerces-c lib. When our jsp under SunOne to load our native driver and parse xml file cause sunOne crashed at /opt/SunWappserver7/lib/libxerces-c.so commonInit(...). It looks like sunOne's Xerces-c conflict with our Xerces-c. We used Xerces-c2.2. Did anyone knows what version of Xerces sunOne used?
Thank you.

Your question seems to be about the Sun ONE application server, and not about C++. You could try the Java Technology forum, but you probably need to go the tech support route for the app server. It's not likely that anyone in the C++ forum would be able to help.

MTOM, Plugin and Xerces

Hi folks,
I really need some help (again) with example of how to handle binary files in a response.
When I use soapUI the response look's like this,
<filData>
                  <dokumenttyp>RSV99001601</dokumenttyp>
                  <fil>
                     <Include href="cid:[email protected]" xmlns="http://www.w3.org/2004/08/xop/include"/>
                  </fil>
                  <filFormat>xml</filFormat>
                  <formatVersion/>
                  <originalNamn>vdata065.xml</originalNamn>
                  <signaturMetod/>
                  <sprak>sv</sprak>
               </filData>
We started with an function for the subject, and I have no problem to handle all the text tag. But for binary I do need some help.
tx_ws_write_fml_value_from_base64_xml( DOMElement * startNode, char * nspace, char * name, FBFR32 ** buf, FLDID32 fieldid )
Do anyone have any code example how to parse a xml (WS) with a binary file attached into a FML32 buffer in SALT Plugin?
I simply don't get it. It could be age or just stupidity.
Should I use XMLChar, XMLByte?
I guess that I should decode it before I update the FML buffer.
And ofcorse are we in a timelimit, it must work before 1/12. Feel no preasure.
Best Regards and thank's in advance.
Mats

        Hi Todd,
As you might remember I am working in close collaboration with Mats regarding all our TUXEDO- and SALT-related activities. Unfortunately we have a hard time finding any appropriate documentation regarding the support for MTOM in conjunction with SALT. Can you point us in the right direction? Can you provide us with examples of code when using GWWS plugins?
Thanks a lot in advance!
        Kind regards,
                Birger

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

Xalan-j_2_0_1 xerces-1_3_1 and jdom-b6

I know that people have already posted message regarding xalan, xerces compatability
with weblogic 6.0sp1 but all the fixes suggested don't work when I use jdom!
When using JDOM, if i put xerces before the weblogic_sp.jar then Hotspot will
die with the following error when i start using jdom.
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Error ID: 4F533F57494E13120E43505002D4
if I put xerces after weblogic_sp.jar and before weblogic.jar then xalan gets
a method not found error when I try a to execute transform() on a document. Also,
I tried my transformation outside of weblogic and it worked just fine.
here is the exception when i try to do the transform in weblogic
java.lang.NoSuchMethodError
at org.apache.xpath.patterns.NodeTest.execute(NodeTest.java:403)
at org.apache.xpath.axes.PredicatedNodeTest.acceptNode(PredicatedNodeTest.java:388)
at org.apache.xpath.axes.ChildTestIterator.nextNode(ChildTestIterator.java:193)
at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:428)
at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:193)
at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2202)
at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:739)
at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:498)
at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:193)
at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2202)
at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2085)
at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1219)
at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2942)
at java.lang.Thread.run(Thread.java:484)

I could see how that would fail if Weblogic was using the default registry
values of:
DocumentBuilderFactory="weblogic.apache.xerces.jaxp.DocumentBuilderFactoryIm
pl"
SAXParserFactory="weblogic.apache.xerces.jaxp.SAXParserFactoryImpl"
it would find weblogic's internal classes.
But if Weblogic is using an xml registry such as:
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
and was starting with the system property of:
..-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.Transf
ormerFactoryImpl ...
Wouldn't JDOM correctly find the org.apache factories instead?
I seem to be having a very similar problem to yours with 6.0 sp2; I'm not
invoking JDOM directly, but I'm using Syslog from protomatter to handle
logging; and Syslog DOES invoke the new SAXBuilder() that you cite. I'm
using xalan 2.1.0 and xerces 1.3.1 placed after the weblogic jars. I also
get a NoSuchMethodError during the transformer.transform, but the same
document is successfully transformed at the command line
TransformerFactory tFactory = TransformerFactory.newInstance();
String xString = xmlDoc.toString() ;
StringReader xmlReader = new StringReader( xString );
StreamSource streamSource = new StreamSource( xmlReader ) ;
Source stylesheet = tFactory.getAssociatedStylesheet( streamSource,
media, title, charset);
Transformer transformer = tFactory.newTransformer(stylesheet);
StreamResult streamResult = new StreamResult( outWriter ) ;
transformer.transform( new StreamSource( new StringReader( xString ) ),
streamResult ) ;
"Eric Van" <[email protected]> wrote in message
news:[email protected]...
>
FIGURED IT OUT!
The problem is that JDOM's SAXBuilder, when used with weblogic, loadsweblogic's
jaxp sax parser, which for some reason doesn't work if the newest xercesis placed
in the classpath before weblogic_sp.jar.
So, to get around this all you have to do is tell JDOM's SAXBuilder to useanother
parser when you create it, preferable one that WORKS!!
I used the one that comes with xerces
new SAXBuilder("org.apache.xerces.parsers.SAXParser")
and it worked fine.
Hope this helps everyone else out.
"Steve Liles" <[email protected]> wrote:
Eric's solution works great if you can get away with always using a
DOMBuilder.
>>
However, I can't always use a DOMBuilder - I need to use the SAXBuilder
in one particular
case where I need to specify the SystemId dynamically as in:
.. SAXBuilder builder = new SAXBuilder(reader, _systemId); ..
There is no DOMBuilder equivalent. Anyone have any suggestions?
cheers,
Steve Liles
"Eric Van" <[email protected]> wrote:
Looks like if you avoid using the org.jdom.input.SAXBuilder and usethe
org.jdom.input.DOMBuilder
instead that the Hotspot error can be avoided. I have a feeling thatthere
is
something else going on here, but OH WELL, NOW IT WORKS.
"Eric Van" <[email protected]> wrote:
I know that people have already posted message regarding xalan, xerces
compatability
with weblogic 6.0sp1 but all the fixes suggested don't work when I
use
jdom!
When using JDOM, if i put xerces before the weblogic_sp.jar then
Hotspot
will
die with the following error when i start using jdom.
# HotSpot Virtual Machine Error, EXCEPTION_ACCESS_VIOLATION
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Error ID: 4F533F57494E13120E43505002D4
if I put xerces after weblogic_sp.jar and before weblogic.jar thenxalan
gets
a method not found error when I try a to execute transform() on a
document.
Also,
I tried my transformation outside of weblogic and it worked just fine.
here is the exception when i try to do the transform in weblogic
java.lang.NoSuchMethodError
atorg.apache.xpath.patterns.NodeTest.execute(NodeTest.java:403)
atorg.apache.xpath.axes.PredicatedNodeTest.acceptNode(PredicatedNodeTest.java:
388)
atorg.apache.xpath.axes.ChildTestIterator.nextNode(ChildTestIterator.java:193)
atorg.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.ja
va:428)
atorg.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav
a:193)
atorg.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
atorg.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:
739)
atorg.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.ja
va:498)
atorg.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav
a:193)
atorg.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform
erImpl.java:2202)
atorg.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer
Impl.java:2085)
atorg.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j
ava:1219)
atorg.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:2942)
at java.lang.Thread.run(Thread.java:484)

Wls 6.0sp1, xerces 1.1

I'm in the process of upgrading to weblogic 6.0sp1 from 5.1. My app uses
xerces 1.1 for all xml parsing. My original configuration was jbuilder 4.0,
weblogic 5.1, jdk1.2.2 and xerces 1.1. This configuration worked and all
xml parsed fine. After upgrading to wls 6.0 my new configuration is jb4,
wls 6.0, xerces 1.1 and jdk130. In this configuration i always get
exceptions when i call the parse method on DOMParser. I've tried swapping
out jdk's, and using the xerces that is bundled with wls 6.0 but have had no
success. Any help would be much appreciated.
Below are some code snippets to indicate my usage of DOMParser:
import org.apache.xerces.parsers.DOMParser;
import org.apache.xerces.dom.DocumentImpl;
import org.apache.xml.serialize.OutputFormat;
import org.apache.xml.serialize.XMLSerializer;
import org.xml.sax.InputSource;
import org.xml.sax.SAXParseException;
import org.w3c.dom.Document;
public class XMLModel {
try {
String loadXmlFileName = new String("whatever.xml");
if(useDOM) {
// If possible, parse the file
DOMParser parser = new DOMParser();
if (loadXmlFileName != null) {
parser.parse(loadXmlFileName);
Document loadDoc = parser.getDocument();
Document loadDoc = XMLParser.parse(loadXmlFileName);
catch (Exception e) {
Log.writeError(e);
return;
Again...This worked with jdk1.2.2, wls 5.1, xerces 1.1....but does not
with jdk130, wls 6.0, xerces 1.1 (or xerces 1.2 bundled with wls 6).
Thanks for any help.
By the way...the exception i get indicates the file can not be found. But i
create an instance of File and ensure that i can read it before calling
parse on the DOMParser.

Is there any plan to support backward compatibility in future ?
Due to above restriction we have to use lowest common BEA version.
I guess BEA must learn how real world application work. I guess compatability
should be like ORACLE RDBMS.
Thanks
Kumar Allamraju <[email protected]> wrote:
No.
As of 6.0 release, the client & server should be on the same version.
Kumar
Rakesh wrote:
Hello,
Can my client running on WLS 5.1.0.9 can connect/work with applicationdeployed
on WLS 6.0.0.1 ?
Thanks

What is the story with Java and UTF-8

Im getting bits of info about java and utf-8, things like
"unless you wrap the FileInputStream, you'll get exceptions with UTF-8 encoding"
So can someone tell where there is a good resource for detailing problems / advice when dealing with utf-8 encoded data???
or
Give me the low down and what the dodge actually is?
Sorry for my poor English - im a scally
Many thanks

1) you've chosen SAX probably because it sticks well to your business requirements (i hope ;-), so keep it!
2) i am using both James Clark's XP and Xerces as my SAX parsers (XP for big volumes because it offers better performances): i am processing only UTF-8 encoded files with no problems,
3) sure, if you hit some troubles post again and a lot of pair of eyes will look into it!

WSAD 5.0 and Xerces

Similar Messages

Maybe you are looking for