Hi Brian,
A couple thoughts/questions:
- you shouldn't need to define the phase on the handler.
- What does your callback class look like? It needs a default constructor
- If you turn up debugging on your server what does the full exception
look like?
- Dan
bkbonner wrote:
Stuart, Dan, I'm working on this as well.
I was using XFIRE pre 1.0 with WS-Security from the Sandbox on the server
side and everything was working. I've been trying to get it integrated with
1.1 but running into some roadblocks.
For instance,
I've configured my WSS4JInHandler as follows:
<bean
id="wss4jInHandler"
name="org.codehaus.xfire.security.wss4j.WSS4JInHandler"
class="org.codehaus.xfire.security.wss4j.WSS4JInHandler">
<property name="phase">
<value>parse</value>
</property>
<property name="properties">
<map>
<entry
key="action"
value="UsernameToken">
</entry>
<entry
key="passwordCallbackClass"
value="com.paraware.webservice.gawda.pricecheck.BriansCallback" >
</entry>
</map>
</property>
</bean>
However, when I submit my request into XFire, I get:
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>WSHandler: cannot create instance of password
callback: com.paraware.webservice.gawda.pricecheck.BriansCallback; nested
exception is:
java.lang.ClassCastException:
com.paraware.webservice.gawda.pricecheck.BriansCallback</faultstring>
</soap:Fault>
I don't quite yet understand why the soap:Client fault is being thrown
Where are you at in the process?
--
View this message in context:
http://www.nabble.com/WS-Security-and-UserTokens-t1543793.html#a4212323
Sent from the XFire - User forum at Nabble.com.
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com
http://netzooid.com/blog
