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 th
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
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
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 ex
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
Might be late to the conversation but we've had our share of headaches with
WAS7 (I know you're on 8.5) when deploying any EAR/WAR application that
uses JAX-WS and related dependencies, where one does *NOT* want the WAS7
stack interfering. The wording of this implies it's a server side
applicatio
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 wrote:
Hi Alex,
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
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 Imple
