Congrats on the 1.0 release and 1.1 looks good.

I've modified an application to make use of XFire 1.1-beta-1.  It looks like
the WS-Security  
stuff was substantially reworked.

However, I've made several modifications to the configuration, but it
appears I've left something out.

I'm receiving:

<soap:Fault>
            <faultcode>soap:Client</faultcode>
            <faultstring>WSHandler: cannot create instance of password
callback: org.apache.ws.security.WSPasswordCallback; nested exception is: 
        java.lang.InstantiationException:
org.apache.ws.security.WSPasswordCallback</faultstring>
        </soap:Fault>

I'm setting up the WSS4JInHandler as follows via Spring:

    <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="org.apache.ws.security.WSPasswordCallback" >
                </entry>
            </map>
        </property>
    </bean>

Any thoughts on this one?

Thanks,

Brian
--
View this message in context: 
http://www.nabble.com/WS-Security-1.1-beta-1-configuration-t1476075.html#a3993520
Sent from the XFire - User forum at Nabble.com.

Reply via email to