cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pam Holzner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-3818) Provide Better Error Messages?
Date Thu, 22 Sep 2011 13:28:27 GMT

    [ https://issues.apache.org/jira/browse/CXF-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112551#comment-13112551
] 

Pam Holzner commented on CXF-3818:
----------------------------------

I've made progress on this.  I think the root cause was not having the right versions of all
of the jars.  In particular, I upgraded the version of wss4j to 1.6.2 (from looking at the
pom) and added xercesImpl 2.9.1  
and now I'm happily getting a different (and less cryptic) error.

As for building the source, Netbeans is still complaining about various files in ...ws.security.policy,
sts, and trust but fortunately, not anything I am using so I can breakpoint in the source
 although I must manually pull up the java file.  This is probably an issue with NetBeans
not being able to handle your very fancy hierarchical tree of pom projects.

> Provide Better Error Messages?
> ------------------------------
>
>                 Key: CXF-3818
>                 URL: https://issues.apache.org/jira/browse/CXF-3818
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.4.2
>         Environment: Windows Vista; jdk 1.6.0_23; netbeans 6.9.1;soap-ui plugin
>            Reporter: Pam Holzner
>            Priority: Minor
>              Labels: wss4j
>
> This is probably not really an issue for cxf but I'm a bit stumped.
> Any advice on how to debug my attempt to configure cxf to pass the username and token
in the soap header?  I am getting the cryptic NoSuchMethod error which isn't helping me much.
> <bean id="serverPasswordCallback" class="com.mycompany.myproj.security.ServerPasswordCallback"
/>
> <bean id="wss4jInInterceptor" class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor">
> <constructor-arg>
> <map>
> <entry key="action" value="UsernameToken" />
> <entry key="passwordType" value="PasswordText" />
> <entry key="signaturePropFile" value="c:/java/myproj/signature.properties" />
> <entry key="passwordCallbackRef">
> <ref bean="serverPasswordCallback" />
> </entry>
> </map>
> </bean>
> <jaxws:endpoint id="MyServImpl"
> implementor="com.mycompany.myproj.myserv.MyServImpl"
> endpointName="e:myserv"
> serviceName="e:myserv"
> address="myserv"
> xmlns:e:urn:myserv.services.mycompany.com"
> />
> The endpoint was working fine before I added in the WSS4J configuration. 
> com.mycompany.myproj.security.ServerPasswordCallback.java
> has 
> public class ServerPasswordCallback implements CallbackHandler {
> public ServerPasswordCallback()
> {
> System.out.println("inside constructor");
> }
> public void handle(Callback[] callbacks) throws IOException, UnsupportedCallbackException
{
> System.out.println("inside handle method");
> }
> When I run, I see that the constructor is called, but when I try to exercise the service
using soap-ui (with the login/password) I get 
> SEVERE: Servlet.service() for servlet WebServicePort threw exception
> java.lang.NoSuchMethodError: org.apache.ws.security.WSSecurityEngine.getWssConfig()Lorg/apache/ws/security/WSSConfig:
> at org.apache.cxf.ws.security.wss4j.WSS4JIjInterceptor.handleMessage(WSS4JInInterceptor.java:193)
>  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message