Mixing java_first_spring_support groovy_spring_support

My goal is to deploy configure a groovy service in tomcat using spring. I started using the java_first_spring_support samples. I deployed it into tomcat and started to modify it a bit. I added the files HelloWorld.groovy HelloWorldImpl.groovy in webapps/spring_http/WEB-INF/classes. I then

RE: Rest Header Info

Are you using CXF HTTP Binding to build your REST service, or CXF JAX-RS (JSR-311) instead? In CXF JAX-RS (JSR-311), the standard way to access HTTP headers is using @HeaderParam, like below: @HttpMethod(GET) @UriTemplate(/books/{bookId}/) public Book getBook(@UriParam(bookId)

RE: using multiple values for @ProduceMime

Hi Akos, you definitely should be able to set multiple values for @ProduceMime. According to spec, if @ProduceMime contains multiple MIME types (or it’s a wild card such as */*), the actual output content type being used is determined by: 1. the output Java type: i.e., if your method is

Re: Mixing java_first_spring_support groovy_spring_support

Hi Guillaume, I tested on my machine, it works. Could you check the required 3rd-party jars was put into WEB-INF/lib, you can find the jars in the README.txt in groovy sample directory. * spring-aop-2.0.x.jar * spring-support-2.0.x.jar * groovy-1.0.jar * antlr-2.7.6.jar * asm-2.2.3.jar

RE: WS-Security error when using BinarySecurityToken

Hi Mayank, Thank you for your answer. I'm surprised as CXF is using WSS4J I thought that what is explained here http://wiki.apache.org/ws/FrontPage/WsFx/wss4jFAQ#many would also work with CXF. Is it just that this fuctionality is not yet implemented in CXF or is it something that I don't

Re: Mixing java_first_spring_support groovy_spring_support

Hi Jeff, I just checked and I have all those files (yes I read the README :-) ) So you mean you get the same WSDL by choosing any of the jaxws:endpoint ? Could you send me your webapp (without the lib dir) ? I am using the 2.0.7 spring version. Cheers Guillaume On Jan 8, 2008 5:12 PM, Jeff

Re: about sample ws_addressing

Glen is correct, the handler_chain.xml is obsolete and should be deleted. The handler_chain.xml is a throw-back to an earlier version of the ws_addressing demo which used an JAX-WS handler (demo.ws_addressing.common.HeaderSnooper) to display the WS-Addressing headers to stdout. However, I

Re: Aegis question

Thanks Eric, but what I want to change is in the schema not in the part i.e. xsd:complexType name=addResponse xsd:sequence xsd:element name=return type=xsd:double/ /xsd:sequence /xsd:complexType Cheers Guillaume On Jan 8, 2008 6:00 PM, Eric Rodriguez [EMAIL

Re: Aegis question

Try @WebParam http://cwiki.apache.org/CXF20DOC/how-do-i-develop-a-service.html Regards, tog wrote: When publishing a service using aegis, the name of the output message is return when my code is doing something like: double sum(double arg0, double arg1) { return (arg0 + arg1)

Re: WS-Security error when using BinarySecurityToken

Wanner Philippe, Bedag wrote: Hi Philippe, Hi Mayank, Thank you for your answer. I'm surprised as CXF is using WSS4J I thought that what is explained here http://wiki.apache.org/ws/FrontPage/WsFx/wss4jFAQ#many You are using CXF or Axis as SOAP engine? I guess the link is for Axis Soap

Re: Mixing java_first_spring_support groovy_spring_support

Hi Guillaume, Since apache maillist can't attach file, I will send to you by your email address. I visit http://localhost:8080/spring_http/HelloWorld?wsdl by the browser, it return the right wsdl file. I use spring 2.0.6. Hope useful. Jeff tog wrote: Hi Jeff, I just checked and I have all

Re: WSDLToJava Error : Thrown by JAXB : undefined element declaration 'ns1:orderBy'

Hi Jim, Changed the logging level to FINE as you indicated and run the wsdl to java on my wsdl, but there is no such a message in there as Classes known to this context:. I've search for classes and context as well and there is nothing on those lines. There are some exceptions that I'm not sure

Re: about sample ws_addressing

I deleted it. Glen Am Dienstag, den 08.01.2008, 10:15 + schrieb Eoghan Glynn: Glen is correct, the handler_chain.xml is obsolete and should be deleted. The handler_chain.xml is a throw-back to an earlier version of the ws_addressing demo which used an JAX-WS handler

Re: Aegis question

Yes, I tried this. Is this working with aegis ? I added geronimo-ws-metadata in my classpath with no success ! I tried also the following file with no success. ?xml version=1.0 encoding=UTF-8? mappings xmlns:sample=http://DefaultNamespace; mapping name=sample:MathService method name=add

new snapshot available

I just completed a new 2.1 snapshot.

How to set Soap version on client side

I use STP plugin in Eclipse. I set STP to use SOAP1.2. Sever side shows that it's using Soap1.2 (Soap12FaultOutInterceptor).But client side still use Soap1.1 (Soap11FaultInInterceptor). How to set Soap version on client side??? *sever side: Dec 26, 2007 1:48:25 PM

Re: How to set Soap version on client side

Thanks! I will definitly give it a try. Now I need to solve some problem to even generate soap1.2 wsdl file first :( Well, I use following configuration (example) beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;

Re: How to set Soap version on client side

Well, I use following configuration (example) beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:jaxws=http://cxf.apache.org/jaxws; xmlns:soap=http://cxf.apache.org/bindings/soap;

Eclipse STP plugin generate not-correct wsdl file for version SOAP1.2

Apache CXF WSDL Generateion Options to SOAP1.2 JAX-WS RI WSDL Generateion Options to SOAP1.2 Below is my interface and the generated wsdl file. The wsdl file shows warning: WS-I:(AP2901) A description uses neither the WSDL MIME Binding as described in WSDL 1.1 Section 5 nor WSDL SOAP binding

Re: How to set Soap version on client side

Look here for setting soap 1.2 on endpoint: http://www.nabble.com/SOAP-1.2-spring-config-to12494148.html#a12497388 DM 2008/1/8, yulinxp [EMAIL PROTECTED]: Thanks! I will definitly give it a try. Now I need to solve some problem to even generate soap1.2 wsdl file first :( Well, I use

Re: GZIP compression done properly

ianroberts wrote: I've been working on a pair of interceptors to properly support GZIP compression of requests and responses in CXF, but I've run into a few problems. Aargh, slip of the fingers - I started writing this mail when I was having problems but I think I've solved them now... Ian

GZIP compression done properly

I've been working on a pair of interceptors to properly support GZIP compression of requests and responses in CXF, but I've run into a few problems. I based my work on the example GZIP interceptor in samples/configuration_interceptor but with modifications to (1) be compatible with MTOM/SwA (2)

Re: Eclipse STP plugin generate not-correct wsdl file for version SOAP1.2

I figure it out. My client was not connecting correctly. But I found another problem with STP pluggin. When first creating a JAX-WS Java First Project, I select Runtime. If the runtime is set to SOAP1.1, the wsdl file will be used SOAP1.1. But if I try to change to SOAP1.2, the wsdl will still

Re: Rest Header Info

Thanks. I'm using jsr311 so that's mixed news. I voted on that issue, however I'll need to formulate a workaround in the meantime. I suppose I'll need to create objects that include the security information along with the required data for the method execution. This is acceptable in posts, and

Re: how to handle exception in CXF

I have figure out the reason. The reason is SOAP version not matched in server/client side. Here is the post for setting client use SOAP1.2 http://www.nabble.com/How-to-set-Soap-version-on-client-side-td14692146.html Interesting, this only happens when Server side throws

Re: How to set Soap version on client side

For my client, I look into the src to find out the setting for SOAP1.2. I don't know whether there's a better way. bean id=client class=demo.spring.HelloWorld factory-bean=clientFactory factory-method=create/ bean id=clientFactory

RE: GZIP compression done properly

Hi Ian, this contribution is very welcome. So your change is based on the existing configuration_interceptor demo, right? Please file a jira with your code as attachment, that should be enough. Thanks. Cheers, Jervis -Original Message- From: ianroberts [mailto:[EMAIL PROTECTED]

RE: Rest Header Info

If you don’t mind going beyond the JSR-311 spec, the best way to handle this kind of security checks is using CXF interceptors [1], i.e., you check the HTTP headers in your own interceptor, if the security criteria is not satisfied, you simply stop the inbound interceptor chain and return.

Re: How to set Soap version on client side

http://markmail.org/message/b7w4vugla43nmj7p? Am Dienstag, den 08.01.2008, 12:43 -0800 schrieb yulinxp: For my client, I look into the src to find out the setting for SOAP1.2. I don't know whether there's a better way. bean id=client class=demo.spring.HelloWorld

Re: WSDLToJava Error : Thrown by JAXB : undefined element declaration 'ns1:orderBy'

Hi Monica, Forget to mention . Search it in java to wsdl 's log . Regards Jim Monica Ferrero wrote: Hi Jim, Changed the logging level to FINE as you indicated and run the wsdl to java on my wsdl, but there is no such a message in there as Classes known to this context:. I've search for

Re: exposed methods with Aegis binding

Hi, Aegis Binding is a data binding , it will not effect which method will be export to the web service. If you are using JaxWs front end , you could use the annotation to define your SEI ( which will be mapped to the WSDL operation) You can find the example here[1].

Re: exposed methods with Aegis binding

Basically, you can use the @WebMethod(exclude=true) to exclude the methods that you don't want it to be exposed. James Hi, Aegis Binding is a data binding , it will not effect which method will be export to the web service. If you are using JaxWs front end , you could use the annotation to