Daniel Kulp wrote:
It can be done with 2.1.x, but it requires quite a bit more work on your part to setup the WSS4J interceptors and mapping policies into wss4j properties and a vice-versa.

If you look at the wssec10 stuff in the sandbox/interopfest:
http://svn.apache.org:80/viewvc/cxf/sandbox/interopfest/wssec10/
and go back to the original version I committed in Dec, the server side parts are the original stuff we had when testing with the 2.1 (actually, 2.0 probably) code base.


Dan


have you gotten Reliable messaging ond addressing working yet? I planned to test WCF -> CXF in the following steps:

1) "Bare" Web Service
2) WSRM+Addressing ontop of (1)
3) Security on top of (2)

1) worked with basicHttpBinding

I am failing on (2) using both a custom binding as well as wsHttpBinding. Both give me the following exception:


http://pastebin.com/m4523a449

C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\ConsoleApplication1\ConsoleApplication1
\bin\Debug>ConsoleApplication1.exe

Unhandled Exception: System.ServiceModel.ProtocolException: The remote endpoint responded to the CreateSequence request with a response with action . The response must be a CreateSequenceResponse with action http://schemas.xmlsoap.org/ws/20
05/02/rm/CreateSequenceResponse. The channel could not be opened.

Server stack trace:
at System.ServiceModel.Channels.ClientReliableSession.ProcessCreateSequenceResponse(Message response, DateTime start)

at System.ServiceModel.Channels.ClientReliableSession.Open(TimeSpan timeout) at System.ServiceModel.Channels.ReliableRequestSessionChannel.OnOpen(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Cal
l(ServiceChannel channel, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade) at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, O
bject[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, O
bject[] ins, Object[] outs)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntim
e operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at ConsoleApplication1.ServiceReferenceWCF.WCFBackendBean.runAction(runActionRequest request) at ConsoleApplication1.ServiceReferenceWCF.WCFBackendBeanClient.ConsoleApplication1.ServiceReferenceWCF.WCFBackendBea n.runAction(runActionRequest request) in C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Project s\ConsoleApplication1\ConsoleApplication1\Service References\ServiceReferenceWCF\Reference.cs:line 1132 at ConsoleApplication1.ServiceReferenceWCF.WCFBackendBeanClient.runAction(vdcActionType actionType, vdcActionParamete rs parameters) in C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\ConsoleApplication1\C onsoleApplication1\Service References\ServiceReferenceWCF\Reference.cs:line 1139 at ConsoleApplication1.Program.Main(String[] args) in C:\Documents and Settings\Administrator\My Documents\Visual Stu dio 2008\Projects\ConsoleApplication1\ConsoleApplication1\Program.cs:line 13

C:\Documents and Settings\Administrator\My Documents\Visual Studio 2008\Projects\ConsoleApplication1\ConsoleApplication1
\bin\Debug>ConsoleApplication1.exe
































Reply via email to