I've commented on the issue itself, but wanted to also comment here so everyone can see...
In your patch, you have a "working" version and a "non-working" version. (btw: that's was a great help. Thanks.) The main difference between the two is that the working version uses the normal JAX-WS API's/generated code and the other uses spring. Under the covers, the "working" version ends up using the WSDL (since the generated code kind of burns that in) whereas your spring configured one does not. It's more of a "java first" case. This kind of exposed two issues: 1) The CXF generated code was wrong. The wsdl is RPC/Lit, but it didn't generate the proper RPC annotation in the code. Thus, in the java first case, it was assuming it was Doc/Lit/Wrapped which is the defaults in the absense of said annotations. 2) I've fixed (1), but it's still not going to work. However, it's a deficiency in the spec. In your wsdl's case, you have <soap:body namespace="....."/> things which define the namespace that needs to be used for the rpc/lit wrapper element. However, nowhere in the spec is there a place to store that namespace in any annotation. Thus, it's lost and CXF/jaxws would end up using the targetnamespace of the service. There really isn't anything we can do about that right now. My suggestion is to change the spring configuration to add the wsdlLocation, serviceName, and endpointName attributes to configure in the proper wsdl information to convert it to a wsdl first scenario like the "working" case. Dan On Saturday 09 August 2008 12:54:56 am Iman Rahmatizadeh wrote: > Done. > https://issues.apache.org/jira/browse/CXF-1740 > > Iman > > On Fri, Aug 8, 2008 at 7:12 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > Damn... Thought I had killed all of those in 2.1.1. Not good at all. > > Obviously missed one. > > > > Is there ANY way you can send a testcase? Even sending it privately to > > me is > > fine. If I can get it reproduced in the debugger, I can take the > > details of your other message as a starting point to really dig into it. > > > > Thanks! > > Dan > > > > On Thursday 07 August 2008 4:21:33 am Iman Rahmatizadeh wrote: > > > I have the following exception when calling a service : > > > > > > java.lang.IndexOutOfBoundsException: Index: 8, Size: 8 > > > > > > at java.util.ArrayList.RangeCheck(ArrayList.java:547) > > > at java.util.ArrayList.get(ArrayList.java:322) > > > at > > > > org.apache.cxf.message.MessageContentsList.get(MessageContentsList.java:7 > >9) > > > > > at > > > > org.apache.cxf.jaxws.interceptors.HolderInInterceptor.handleMessage(Holde > >rI > > > > >nInterceptor.java:64) at > > > > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorCh > >ai > > > > >n.java:221) at > > > org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:449) at > > > > org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRespo > >ns > > > > >e(HTTPConduit.java:2025) at > > > > org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPC > >on > > > > >duit.java:1861) at > > > org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) > > > > at > > > > > org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:593) > > > at > > > > org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingIn > >te > > > > >rceptor.handleMessage(MessageSenderInterceptor.java:62) at > > > > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorCh > >ai > > > > >n.java:221) at > > > org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296) > > > at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:242) > > > at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) > > > at > > > > org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:178) > > > > > at $Proxy36.paymentUtility(Unknown Source) > > > .... > > > > > > I've tried various solutions suggested in previous threads like using > > > 'wsdl2java -all -exsh true' to generate java and also updated to the > > > > latest > > > > > build apache-cxf-2.1.2-20080806, with no success. Any suggestion whats > > > > the > > > > > problem ? > > > > > > Iman > > > > -- > > Daniel Kulp > > [EMAIL PROTECTED] > > http://www.dankulp.com/blog -- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog
