signing the Binary Security Token (BST)

Hi, I'm using CXF and WSS4J to develop consumers and providers that exchange signed soap messages. Signing the body and timestamp elements works just fine. However, I also need to sign the x509 certificate that is included in the security header (using the direct reference strategy). Below

Writing blocking input interceptor

Hi How to write a blocking input interceptor which can send a non-fault response back to a client, over HTTP ? Input interceptors can access input Messages in its handleMessage, which, somewhat surprisingly, in case of HTTP, have javax.servlet.HTTPServletRequest/HTTPServletResponse object in

Re: signing the Binary Security Token (BST)

jbendsen wrote: Hi, I'm using CXF and WSS4J to develop consumers and providers that exchange signed soap messages. Signing the body and timestamp elements works just fine. However, I also need to sign the x509 certificate that is included in the security header (using the direct reference

Stacktrace, Why?

Can someone give me a clue as to why I'm getting this stack trace, I don't reference a class by that name ever. class: com.stryker.cmf.cipushep.jaxws.PushReceive could not be found at com.sun.xml.internal.ws.modeler.RuntimeModeler.getClass(RuntimeModeler.j ava:271) at

Microsoft interoperability

I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL from one of my CXF services. The results are not wonderful. I get warnings like the following. Based on my reading of the WSDL, the Microsoft tool is just confused, but I wonder if anyone else has been here? Schema validation

Re: xs:choice

Thanks Jim. I learned something new. :-) To answer the other question: I'm also curious if/how CXF/JAXB can enforce xs:choice? If you turn on schema validation in CXF, the schema validators should be able to enforce the xs:choice schema. If you look in samples/wsdl_first (in 2.0.2

Re: Microsoft interoperability

I've seen that warning from .NET's wsdl tool a number of times. It has never caused any problems though. It sill seems to generate both Vb and C# code that works just fine. Also we have two clients up and running on .NET and all are running fine. On 10/9/07, Benson Margulies [EMAIL PROTECTED]

Re: Microsoft interoperability

One more thing... Can you run our own wsdlvalidator (in the bin directory) against the wsdl just to double check that the wsdl looks OK from it's standpoint? Dan On Tuesday 09 October 2007, Dave Kallstrom wrote: I've seen that warning from .NET's wsdl tool a number of times. It has never

Re: Stacktrace, Why?

That stack trace points to you using the the Sun reference implementation of JAX-WS thats built into JDK 6. You aren't hitting CXF code at all. The classes: com.sun.xml.internal.ws.* are the JAX-WS stuff in JDK 6. Double check that CXF is properly on the classpath. Dan On Tuesday 09

RE: Microsoft interoperability

So far, not too good. 'Unable to generate a temporary class (result = 1). Error CS0030: Cannot convert type BasisTechnology.rnm.ws.Name[] to BasisTechnology.rnm.ws.Name' This is thrown on construction of the proxy class generated by their wsdl tool. I'm also getting all the parameters wrapped

RE: Microsoft interoperability

Also, the Mindreef Soapscope tool has complaints about inaccessible types that I am harassing their tech support for an explanation of. -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 9:55 AM To: cxf-user@incubator.apache.org

RE: Microsoft interoperability

The cs0030 is this charming bug of Microsoft's: http://support.microsoft.com/kb/891386 -Original Message- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 9:57 AM To: cxf-user@incubator.apache.org Subject: RE: Microsoft interoperability Also, the

Re: cxf plain xml http configuration using simple frontend

Willem - Thanks. I configured it using that example. With this simple frontend, how can I set 'wrapped = true? -- View this message in context: http://www.nabble.com/cxf-plain-xml-http-configuration-using-simple-frontend-tf4591639.html#a13117511 Sent from the cxf-user mailing list archive at

Using TCPMon with CXF

Hello, Using the simple server example, I would like to monitor web service request and responses using tcpmon. The tcpmon application needs to know three things in order add a listener: - target hostname: 127.0.0.1 - target Port #: 9000 - Listen Port#: ? How may I determine what

RE: org.apache.cxf.interceptor.Fault: Marshalling Error: class javax.xml.ws.Holder nor any of its super class is known to this context.

Hi Daniel, I am using JaxWsProxyFactoryBean now and it does create the factory and the port class as expected but still getting the exception when invoking any RSI web service, any help in resolving this? JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();

True or false: embedded schemata need to be imported?

-Original Message- From: Mindreef Support [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 09, 2007 5:01 PM To: Benson Margulies Subject: [issue #QSU-61718-589]: Validation errors that don't make sense to me Hi Benson, Thanks for sending the WSDL. Issue #1: When you're on the

RE: deploy webservices

Thanks Willem Now I have two fully webservices Bye -Mensaje original- De: Willem Jiang [mailto:[EMAIL PROTECTED] Enviado el: Lunes, 08 de Octubre de 2007 08:54 p.m. Para: cxf-user@incubator.apache.org Asunto: Re: deploy webservices Hi, You can't reuse the service factory for two

Re: signing the Binary Security Token (BST)

You're trying to sign an element (BST containing the certificate) that hasn't been created yet. This is a bit of an odd use-case -- typically, you'd sign the body of the message with the private key associated with the public key in the certificate you are sending, and then do some kin dof

Re: Using TCPMon with CXF

It's the client port which defined in the wsdl, if you didn't change the way to specify the client port. James Hycel Taylor wrote: Hello, Using the simple server example, I would like to monitor web service request and responses using tcpmon. The tcpmon application needs to know three

Re: help in setting JaxWsProxyFactoryBean endpoint/url in CXF 2.0.2

Jarada, Hussam wrote: Per finding info on setting client url from http://www.nabble.com/Client-question-tf4357978.html#a12419843 I changed my code as follows At which getServiceURL() return http://todev-mda09.tops.aol.com:8080/; MadcapService ss = new MadcapService(); MadcapPort

Re: cxf plain xml http configuration using simple frontend

It is same with the jaxws:endpoint. You need to create a service factory bean and set it to the simple:server. Here is an example bean id=ReflectionServiceFactoryBean class=org.apache.cxf.service.factory.ReflectionServiceFactoryBean property name=wrapped value=true/ /bean simple:server

Re: help in setting JaxWsProxyFactoryBean endpoint/url in CXF 2.0.2

You can specify the wsdl url to your local wsdl url. eg. File://C:\svnwork\reg\trunk\reg\reg-ws\ws-madcap\src\wsdl\madcap.wsdl Willem. Jarada, Hussam wrote: my problem is that the wsdl is not accessible from this web service url. Jarada From: James Mao