RE: JSR 181 Document literal wrapped

bmargulies wrote: Where are you getting the requirement that the response be named 'Response', as opposed to, say, OpNameResponse? Aside from that, I think that what you are asking for is the default behavior of JAX-WS + JAXB. For the name of the response, that's what I said: the

Stopping the jms_queue sample

Hi When following the jms_queue sample what should I do to close the Endpoint? After calling stop() on the endpoint I still have some of JMS threads up and running so I guess I'm missing something. /Mikael Davidsson -- View this message in context:

Re: Stopping the jms_queue sample

Hi, Yes, I just did a quick test for it . I saw some ActiveMQ Scheduler thread there. But after I went through the CXF code , I am sure we close the jms consumer connection. I have no idea why the ActiveMQ Scheduler threads are still there after the consumer is closed. Willem. MickeD wrote:

RE: JSR 181 Document literal wrapped

Unless you ask special for Bare, a method like String[] bloop (String bleep, int floup) And the WSDL will give you one return part and one parameters part. -Original Message- From: cunparis [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 3:40 AM To:

RE: Are namespace prefixes normative in jaxb?

Properties on the JaxbDataBinding, I would propose. -Original Message- From: Jim Ma [mailto:[EMAIL PROTECTED] Sent: Monday, October 15, 2007 10:52 PM To: cxf-user@incubator.apache.org Subject: Re: Are namespace prefixes normative in jaxb? It is ok to set this property to JAXB

Re: MTOM and @XmlMimeType(application/octet-stream) annotation.

I´m trying to implement the @RequestWrapper. My method returns a String and takes a class FicheroXML like a parameter, should I only implement the @RequestWrapper ?, in that case...What methods should have the class ? is there any examples about @RequestWrapper implementions Thanks in

Can someone please post an example of a CXF-generated WSDL file that unpacks properly in Microsoft's wsdl.exe?

I'm negotiating with Microsoft support about a WSDL of mine which, even though the parts are called 'parameters', doesn't get the desired 'wrap/unwrap' behavior. If I could send a working example to them it might advance the cause.

specifying wsdlLocation in jaxws:endpoint

Hello, I am confused a little for this - I want to do wsdl first configuration and I define my jaxws:endpoint with wsdlLocation=WEB-INF/hello.wsdl - but it just seems that the service is build from the java class and not wsdl file. e.g. If I specify a completely wrong wsdl filename in

Simple FrontEnd CXF deployment error

Hi all I was able to get the standalone Simple FrontEnd HelloWorld to work. Now I would like to deploy it as a war . I followed the instructions from the CXF User guide on setting up a CXFServlet I get the below error. Supporting Artifacts are included below (cxf-servlet.xml web.xml) I'm not

Re: Simple FrontEnd CXF deployment error

All! I was able to resolve this with the help of a co-worker's suggestion. I just removed the CXFServlet and it works for me... I'm going to try this out on a more complex real-world example to see if I got this correct. narend wrote: Hi all I was able to get the standalone Simple FrontEnd

Re: Configuring Interceptors

You would probably need to write your own interceptor that would determine the appropriate configuration and then adds that to the chain. Basically, write an interceptor that does: public void handleMessage(Message message) { SOAPMessage msg = message.getContent(SOAPMessage.class);

Re: MTOM and @XmlMimeType(application/octet-stream) annotation.

No, this is different. That thread talks about parameters to the SEI methods that should be attachments.In this case, this is a field inside one of the objects that is a parameter. This SHOULD work. We just pass the object class as-is to JAXB so this seems to be a JAXB issue. Dan

Run service on Java 1.4

Hello ! I'm newby in CXF. Is there any way to run CXF service on Java 1.4 using Servlet transport? Thanks, Egor Samarkhanov ([EMAIL PROTECTED])

Disable access to wsdl in Servlet transport

Hello ! How can I restrict access to WSDL of my service? I don't want someone to access the http//host.com/services/myservice?wsdl content. And I use Servlet transport. Thanks, Egor Samarkhanov ([EMAIL PROTECTED])

RE: Run service on Java 1.4

Since CXF uses annotation, I am not sure if you would be able to run under anything previous to jdk1.5. Regards, Ramanand Singh -Original Message- From: Egor Samarkhanov [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 16, 2007 2:59 PM To: cxf-user@incubator.apache.org Subject: Run

Redundand Request/Response types in WSDL

Hi ! I've created a simple service with one method String echo(String str); and CXF created request/response types in WSLD: xs:element name=echo type=tns:echo / xs:complexType name=echo xs:sequence xs:element minOccurs=0 name=arg0 type=xs:string / /xs:sequence /xs:complexType

Re: MTOM and @XmlMimeType(application/octet-stream) annotation.

OK. Not a JAXB issue. Seems to be an XmlSchema issue. The DOM we feed into XmlSchema contains the contenttype stuff. If I immediately print the schema, it's gone. :-( Dan On Tuesday 16 October 2007, Daniel Kulp wrote: No, this is different. That thread talks about parameters to

Re: simple-frontend.html

At the bottom of simple-frontend.html, there is a tip talked about this, see this JIRA for detail: https://issues.apache.org/jira/browse/CXF-897 I updated it Others title to Well-Known issue for easily to get people's attention. Thanks Jeff Jonathan Slate wrote: Just wanted to ask about an

Re: MTOM and @XmlMimeType(application/octet-stream) annotation.

It's definitely a bug in XmlSchema. Updating to the latest version of XmlSchema helped a little bit, but not enough. It at least attempts to write the extensors. The problem is the parsing only saves the last extensor.I've worked around that bug by writing a Deserializer that

Re: Configuring Interceptors

Hi CXF provides a flexible configuration of interceptor. You can configure the interceptor in Bus level or in Endpoint level. For you case, I think you can define the WSS4J interceptor in your Endpoint B, and add the SAAJ*Interceptor in the bus. In this way, the EndpointA will not check the

Re: Disable access to wsdl in Servlet transport

Jeff, I think he doesn't want people to see the WSDL file. It's not the service he wants to restrict, but viewing its WSDL. I don't know if that can be done. Glen Am Mittwoch, den 17.10.2007, 11:11 +0800 schrieb Jeff Yu: Hi, There is an easy way that I came up is to use a filter in

Re: Disable access to wsdl in Servlet transport

Hi, I think you can take a look at the WSDLQueryHandler in the CXF core. You can extend it and add some security check here, then register the Handler to the QueryHandlerRegistyImpl. Willem. Egor Samarkhanov wrote: Hello ! How can I restrict access to WSDL of my service? I don't want

Re: Redundand Request/Response types in WSDL

Hi, If you are using the simple front end , you need to set the ServerFactoryBean's service wrapped attribute to be false. Willem. James Mao wrote: Hi, Try annotate the SEI with @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) Then the generated elements in the schema will

Re: MTOM and @XmlMimeType(application/octet-stream) annotation.

Hi Dan, Is it fix the java2ws tools as well, or just the runtime? in the runtime the http header now should contain the application/octet-stream, right? But I tested with the java2ws, it's not working. the expectedContentTypes=image/png still missing in the schema James It's definitely a

Re: MTOM and @XmlMimeType(application/octet-stream) annotation.

Sorry, False alarm, I'm testing against with the old distribution which not included Dan's fix The java2ws works perfect, I'll commit a test in java2ws soon Cheers, James Hi Dan, Is it fix the java2ws tools as well, or just the runtime? in the runtime the http header now should contain the