It isn't tied to a particular VM. It's tied to the Sun XML parser
which happens to already be included in the Sun VMs. You can grab
the Sun jaxp jar from:
http://download.java.net/maven/1/com.sun.xml.parsers/jars/
and add that in and it should work.
Dan
On Jul 25, 2008, at 3:51 PM, Fisher, Jonathan wrote:
I may have found the reason here for anyone else with this problem.
http://www.mail-archive.com/[EMAIL PROTECTED]/
msg02950.html
Unfortunately, we're moving backwards to xfire because we can't figure
this issue out... cxf needs an implementation of SAAJ that isn't
tied to
a VM. Websphere is a pretty big player in the Webapp arena and it's
unfortunate ws-security won't run due to an error in a third party
library.
I *did* see that apache-Geronimo has an implementation, and I added
that
to the build before pulling the plug on CXF, unfortunately, that
gave me
this error:Caused by: java.lang.ClassCastException:
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl incompatible with
javax.xml.parsers.DocumentBuilderFactory when trying to parse our
spring
config.
-----Original Message-----
From: Fisher, Jonathan
Sent: Friday, July 25, 2008 9:12 AM
To: '[email protected]'
Subject: RE: SAAJ and WSS4JInInterceptor
Yes, it does work in tomcat, and strangely enough, it runs in the
instance of WebSphere locally, but not on our development servers. The
local instance I believe runs with J9 and not the Sun VM, so this
problem is baffling.
Thank you for your concern on security. I left a good portion of the
config out of my initial email. We our customer and client security
and
privacy very seriously.
Your link did not come through, it looks like everything got
translated
from HTML to plaintext. Can you send the full URL?
-----Original Message-----
From: Glen Mazza [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2008 9:46 PM
To: [email protected]
Subject: Re: SAAJ and WSS4JInInterceptor
If you're using CXF 2.1+, SAAJ is automatically imported when you use
either of the WSS4J interceptors, so you don't need to explicitly
include it in your interceptor chain.
In your shoes, I would first try to make sure your system works with
Tomcat[1], *then* try to get things working with Websphere. This
helps
with troubleshooting, we can first work on any CXF-related problems
with
your code before dealing with the Websphere headaches.
There's some IBM Websphere-specific notes here[2]. You may need to
google a bit over using SAAJ with the IBM JDK--no guarantees here
unfortunately though that you will be able to get that to work. (I
don't know if it works or not.)
As a slight concern, because you're quite possibly working with HIPAA
data, make sure not to divulge too much of your business/security
model
on these mailing lists. Sometimes people forget that when they have
immediate errors and post too quickly to the mailing list. On this
list, all of us work for the American Widget Company, and our
webservices are written for that firm.
HTH,
Glen
[1] http://www.jroller.com/gmazza/entry/using_cxf_and_wss4j_to
[2] http://cwiki.apache.org/CXF20DOC/appserverguide.html
-------------------------------
Glen Mazza, Developer
American Widget Company
[EMAIL PROTECTED]
Fisher, Jonathan wrote:
Hey guys...
I'm getting this error when trying to do WSSE authentication on my
WS.
I'm using Websphere(shudder) and am locked into using their JDK:
<faultcode>soap:Client</faultcode>
<faultstring>Problems creating SAAJ object
model</faultstring>
Is SAAJ required for wss4j? I'm not really sure why I need that in
there, but it doesn't seem to make a difference whether I have the
interceptor in there or not, I get the same error message.
--
View this message in context:
http://www.nabble.com/SAAJ-and-WSS4JInInterceptor-tp18639944p18644236.ht
ml
Sent from the cxf-user mailing list archive at Nabble.com.
PRIVILEGED AND CONFIDENTIAL
This email transmission contains privileged and confidential
information intended only for the use of the individual or entity
named above. If the reader of the email is not the intended
recipient or the employee or agent responsible for delivering it to
the intended recipient, you are hereby notified that any use,
dissemination or copying of this email transmission is strictly
prohibited by the sender. If you have received this transmission in
error, please delete the email and immediately notify the sender via
the email return address or mailto:[EMAIL PROTECTED]
Thank you.
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog