Hi Alex, I guess you need two packages. Unfortunately, whenever it gets a bit more complex, all application servers need some special treatment.
- Florian > The AtomPub issue shows up only in Tomcat. > > I would like to use the same packaged web application for WebSphere and > Tomcat. When the 1.4x jaxp-api.jar and jaxp-ri.jar are included in > WEB-INF/lib, the workbench throws that exception. When the 2 jars aren't > included in the Tomcat deployment, the workbench client works fine. > > Thanks > > > On Friday, July 4, 2014 8:32 PM, Florian Müller <f...@apache.org> wrote: > > > > Hi Alex, > > Are you running the Workbench also with the IBM JDK? > If not, then that it is not a Workbench issue. The jaxp library has nothing to > do with the AtomPub parsing on the client side. > > Does your server return extensions? If so, do they all have a namespace? > > > - Florian > > > > > Hi Florian, > > > > I think you are right. I do need jaxp 1.4.2. The AtomPub issue seems to be > > specific to the workbench client only. I tested with a few other clients and > > they seem to work ok. Adding jaxp on the server's classpath maybe altering > > the > > xml response which causes workbench to throw this exception? > > Do we need a JIRA for this? > > > > Thanks > > Alex > > > > > > On Friday, July 4, 2014 7:23 PM, Florian Müller <f...@apache.org> wrote: > > > > > > > > Hi Alex, > > > > I think you need the jaxp-ri version 1.4.2 on the server. > > The AtomPub issue is probably something different. It might be an issue with > > the > > StAX implementation. > > Please follow Marks recommendation and make sure that your classloader > > configuration is set to PARENT_LAST. > > > > - Florian > > > > > > > > > Thanks Florian. I am using WebSphere version 8.5. The attached doc has > > > stack > > > traces. There are 3 scenarios -- > > > 1. without xerces & jaxp > > > 2. with xerces > > > 3. with jaxp > > > > > > The 3rd option looks the most promising. > > > > > > Thanks again > > > Alex > > > > > > > > > On Thursday, July 3, 2014 9:01 PM, Florian Müller <f...@apache.org> wrote: > > > > > > > > > > > > Hi Alex, > > > > > > Which WebSphere version you are using? Which Xerces/JAXP versions are you > > > adding? > > > Can you provide stack traces of the exceptions that OpenCMIS throws? > > > > > > - Florian > > > > > > > > > > > > > Hello, > > > > > > > > When deploying an open CMIS server framework based application on > > > > Websphere, > > > > I > > > > need to include either xerces or jaxp to get around a similar problem as > > > > the > > > > one discussed here -- The Standard Implementation for JAX-WS: > > > > us...@jax-ws.java.net: Archive — Project Kenai > > > > > > > > The Standard Implementation for JAX-WS: users@jax-ws.... > > > > Use Advanced Search to search the entire archive. Re: Please help > > > > java.lang.NoClassDefFoundError: > > > > com.sun.org.apache.xerces.internal.dom.DocumentIm... > > > > View on java.net Preview by Yahoo > > > > > > > > > > > > I guess SAAJ api's internally depend on Sun's xerces implementation. > > > > > > > > However, including xerces causes a conflict with open CMIS ( Error: > > > > javax.xml.parsers.DocumentBuilderFactory.setFeature) > > > > whereas including JAXP based on the link above seems to cause problems > > > > with > > > > getRepositories specifically when using the atompub protocol. > > > > > > > > Based on my understanding then SAAJ needs to have a xerces impl from Sun > > > > on > > > > Websphere. However both xerces or JAXP seem to conflict with open CMIS. > > > > > > > > Any recommendations on how this could be resolved? > > > > > > > > Thanks > > > > Alex
