[jboss-user] [JBoss Web Services] - Re: Attaching a WS-Security policy forces use of "Standard WSSecurity Endpoint" configuration

Riccardo Serafin do-not-reply at jboss.com
Mon Jan 17 05:04:21 EST 2011

Riccardo Serafin [http://community.jboss.org/people/barakka] created the discussion

"Re: Attaching a WS-Security policy forces use of "Standard WSSecurity Endpoint" configuration"

To view the discussion, visit: http://community.jboss.org/message/581140#581140

Grazie Alession,

I was in fact thinking to switch to CXF, but the native stack seemed more simple for what I needed. I'm trying to integrate with the PIcketLink-STS, where the integration, as far as I know, is based on the native stack.

In any case the change needed to avoid the problem should be fairly easy, just checking if the correct handler is already in the chain and if not loading the standard configuration. Or I'm missing something? I'll try to create a patch for that in the next week and submit it.

Btw, what's the focus of the native stack at the moment? I've seen the roadmap, but as you have said it seems that much of the WS-* support has been left aside in favor of CFX (Metro support has been discontinued, right?). Are you planning on filling the gap, or will the native stack be left just for experimental stuff?


Reply to this message by going to Community

Start a new discussion in JBoss Web Services at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20110117/ca5e8096/attachment.html 

More information about the jboss-user mailing list