• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

xerces.jar package difference bw WAS 4 and WAS 5

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello

We have an application running in websphere 4.0.5 Packaging that into an ear file and bringing it into websphere 5.0.2. We are using xerces.jar that comes with WAS 4 "Xerces 1.4.2", now the xerces package on WAS 5 is "XML4J 4.0.12".

Here is the beginning of the error message. DataLoader is the first servlet that gets loaded and the error occurs on the line that tries to create and initiallize RespParser object. It doesn't even get to a constructor. RespParser class has "import org.apache.xerces.parsers.*;" which has org.apache.xerces.framework package that we are using that isn't in XML4J on WAS 5.

Or I think that's what our problem is. I know that that is not what the error message displays, but if someone knows or had similar problem with xerces versions between WAS 4 and WAS 5 please let me know.


SRVE0100E: Did not realize init() exception thrown by servlet DataLoader: javax.servlet.ServletException: (class: com/hsbc/cdm/reftable/RespParser, method: parse signature: (Ljava/util/Hashtable Ljava/util/Hashtable Incompatible object argument for method call
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:99)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)
at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java(Inlined Compiled Code))
at com.ibm.ws.webcontainer.servlet.ServletInstance.init(ServletInstance.java(Compiled Code))
at javax.servlet.GenericServlet.init(GenericServlet.java(Inlined Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.addServlet(WebAppServletManager.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebApp.loadServletManager(WebApp.java(Compiled Code))
at com.ibm.ws.webcontainer.webapp.WebApp.init(WebApp.java(Compiled Code))
at com.ibm.ws.webcontainer.srt.WebGroup.loadWebApp(WebGroup.java(Compiled Code))
at com.ibm.ws.webcontainer.srt.WebGroup.init(WebGroup.java(Compiled Code))
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:985)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:136)
 
today's feeble attempt to support the empire
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic