Sorry, it is my fault. Rational Application Development. Basicaly it is an
IBM version of Eclipse. Let's say, like there is a Spring version of
eclipse wich comes with Fabric server easily settled, IBM provides RAD wich
has easily setting of Websphere. I guess that I am facing the error because
some jar wich comes with RAD or Websphere is conflicting when I am using
Xarlan but I am not that experienced in Xarlan so I don't know which I
could try remove or update from the previous list.
2014-08-01 12:51 GMT-03:00 André Warnier <a...@ice-sa.com>:
> By the way, pardon my ignorance, but what's a "RAD" ?
> I did look it up in Google, but it comes up with either "Rite Aid
> Corporation" or a unit of nuclear radiation..
>
>
> Deme Carv wrote:
>
>> Fistlly, thank you both of all for answering. I am very glad for very
>> rapid
>> comments. I attached a file in my original question which tells the jar I
>> have in both situation. I guess it might not be delivered to the forum. I
>> know that there is RAD involved but there are as well apache libraries
>> included and I am sure there are a lot of people in this forum with huge
>> experience in such libraries. I don't think my root cause is related to
>> the
>> Websphere server. I guess that there are some conflict between jars. Even
>> though you might think different, could you at least tell me if you see
>> some conflict in this libraries? The problem arises when
>> apache.xalan.serialize.SerializerToXML run with libraries below.
>>
>> C:\IBM\SDP\runtimes\base_v61\lib
>> C:\Rad\workspace\my_app\WebContent\WEB-INF\lib.
>> eclipseproductactivation.jar
>> activation-impl.jarclasses12.jaraspectjrt.jarcommons-
>> collections.jarbase.jar
>> commons-fileupload.jarbootstrap.jarcommons-io-1.4.jarbsf-engines.jar
>> commons-logging.jarcommandlineutils.jaribmjzos.jarEJBCommandTarget.jar
>> javax.jarffdcSupport.jarjstl.jarhtmlshell.jarjta.
>> jarinstallver.jarjzos.jar
>> installxml.jarlog4j-1.2.14.jariscdeploy.jarmail.jarivblogbr.jar
>> quartz-1.6.0.jarIVTClient.jarquartz-all-1.6.0.jarj2ee.
>> jarspring.jarjacl.jar
>> standard.jarlaunchclient.jarxalan-2.4.1.jarlmproxy.jarxerces-1.4.4.jar
>> mail-impl.jarmarshall.jarnif.jarpc-appext.jarphysicalrep.jarpmirm4arm.jar
>> rrd-appext.jarrsadbutils.jarrsahelpers.jarserviceadapter.jar
>> sib.api.jmsra.rarsib.ra.rarsljc.jarspy-sl.jarspy.
>> jarsqlserver.jarstartup.jar
>> tcljava.jarurlprotocols.jarutil.jarwsatlib.jarwsif-compatb.jar
>>
>>
>> 2014-08-01 9:05 GMT-03:00 Daniel Mikusa <dmik...@pivotal.io>:
>>
>> On Thu, Jul 31, 2014 at 8:13 PM, Deme Carv <demec...@gmail.com> wrote:
>>>
>>> I am getting the error from subject when running the below code in
>>>> Websphere in my RAD. It is very interesting that this code doesn't cause
>>>> any error in Server. The server runs up Tomcat 6 but I must set the same
>>>> code to run in Websphere. I have searched for hours in web but I didn't
>>>> find nothing that I could at least give a try. I attached a pdf with the
>>>> libs that I found in each place. I guess that it might exist some
>>>>
>>> conflict
>>>
>>>> but I have no idea why it is working in Tomcat but it is not working in
>>>> Websphere.
>>>>
>>>> Error message in browser:
>>>>
>>>> Error 500:
>>>>
>>>> org/apache/xml/utils/TreeWalker.<init>(Lorg/xml/
>>> sax/ContentHandler;Lorg/apache/xpath/DOMHelperV
>>>
>>>> Error message in RAD console:
>>>> java.lang.NoSuchMethodError:
>>>>
>>>> org/apache/xml/utils/TreeWalker.<init>(Lorg/xml/
>>> sax/ContentHandler;Lorg/apache/xpath/DOMHelperV
>>> NoSuchMethodErrors often occur when you have the wrong version of a
>>> library
>>> on your class path. This happens because your code is looking for one
>>> version, that has method X while the library you've included has a
>>> different version without method X.
>>>
>>> I don't know a lot about WebSphere, but I do recall that it ships with an
>>> older set of libraries and that it prefers those libraries (it calls this
>>> parent first) over ones in the application (it calls this parent last).
>>> I've seen cases where switching to "parent last" mode has resolved
>>> similar
>>> issues.
>>>
>>> If that doesn't help, I second André's suggestion to look for help in a
>>> more appropriate forum.
>>>
>>> Dan
>>>
>>>
>>> at org.apache.xalan.serialize.SerializerToXML.seriali
>>>> ze(SerializerToXML.java:2578)
>>>>
>>>> org.apache.xalan.serialize.SerializerToXML serializertoxml = new
>>>> org.apache.xalan.serialize.SerializerToXML();
>>>>
>>>> My code snippet:
>>>> java.io.FileWriter filewriter = new java.io.FileWriter(file);
>>>>
>>>> serializertoxml.setWriter(filewriter);
>>>>
>>>> serializertoxml.serialize(node); // the error happens here
>>>>
>>>> serializertoxml.flushWriter();
>>>>
>>>> filewriter.write("\n");
>>>>
>>>> filewriter.close();
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>>>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>>>
>>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
