This content has been marked as final. Show 5 replies
It might be some version difference in the used packages.1 person found this helpful
Yes, But the same jar's are working in TomCat... Do i need to do something else for weblogic?
Most of the times I faced such problem with weblogic was due to the fact that weblogic had a version of Jar internally which was being picked by application before any other (classpath or web-inf/lib ) placed jars were picked . Do you have any jar in your application , which contains com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO class?
For e.g. jaxp-ri-1.4.1.jar
or any other . If so then just to verify the problem , I always try putting this jar file at the begining of classpath of weblogic ( in setenv.cmd or startweblogic.cmd ) file and see the results .
There may be a probability that even your weblogic might crash because of wrong version of jar but this gives you an idea about the version mismatch and you can make your code compaitable to the jar provided ny weblogic.
I actually tried before putting the post here.. I did kept excer and xalan jar as a pre classpath.. and it worked... But i dont want to do that cause there are other application deployed under the same wl domain.. Doing this might impact them.
I dont have any jar in my classpath which has this package. This package is under rt.jar.. Sun have moved there old xml parsers files under a new com.sun package , that is why it is not finding the correct implementation of DOM.
If rt.jar has been modified the package structure , then I am not sure of any other way apart from changing your code to suit the new package structure .Is there any reason why can't you change the pacakage structure in your code? Or are you using a thrid party jar which internally calls this modified class?