[jira] Commented: (CXF-2222) Policy attached to an input operation in a WSDL does not get copied to the Stub operation by WSDL2Java

["Mary Thompson (JIRA)" <ji...@apache.org>]

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

Mary Thompson commented on CXF-2222:
------------------------------------

Hi Dan,
    thanks for the quick response. It looks like the latest snapshot was 
Sunday morning and thus missing your fix. How frequently are the 
snapshots generated? If its going to be more than a few days, I will try 
to do a checkout from the repository to use for my project. Otherwise I 
will wait for the next snapshot.

Mary





> Policy attached to an input operation in a WSDL does not get copied to the Stub operation by WSDL2Java
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2222
>                 URL: https://issues.apache.org/jira/browse/CXF-2222
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.2.1
>         Environment: Maven, cxf 2.2.1, JDK 1.5, MacOS 10.5.6
>            Reporter: Mary Thompson
>            Assignee: Daniel Kulp
>             Fix For: 2.2.2
>
>         Attachments: authn.error.html, authN.tar.gz
>
>
>    I'm new to cxf and trying to get a signed message passed between a
> > client and server. I started from an existing ws-policy which works with
> > axis2/rampart, used the cxf version of wsdl2java to generate all the
> > code. Then merged a few things from
> > apache-cxf-2.2.1/samples/ws_security/interopfest/wssec10.
> > The message appears to be formatted and signed correctly by the client,
> > but the server gets a null pointer exception in
> > org.apache.ws.security.message.token.X509Security.getX509Certificate
> > (X509Security.java:92) when processing the incoming message. I looked at
> > the code and it has found the certificate and is faulting because crypt
> > is null.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.