We undergo not finally announce the channel of 2.0.2,The CXF 2.1 is just begin and we ordain migrate the jaxws api and jaxb versions to 2.1,So. I would say there'll have big changes in CXF2.1. I would suggest you fasten to 2.0.2I hope you can get the evaluate inspect done so I can fix it for you. Regards,James> No problem. Do you have any idea how stable 2.1 is? I sight that my air> with the IndexOutOfBounds with the one Interceptor doesn't happen on 2.1 but> does on 2.0.1 (so somehow it have been fixed directly or indirectly). Is> it helpful to experience if it's a problem on 2.1? Is it relatively safe to use> 2.1 snapshots?>> On 9/11/07. James Mao <james mao@iona com> wrote:> >> Great. That's definitely helpful.>>>> Thanks Ryan,>>>> James>>>>>> >>> Sure. I'll see if I can somehow get my test case working that fails,>>> >> though>> >>> maybe it doesn't fail and the bug with the interceptor that I mentioned>>> earlier is causing it to fail no matter how I run wsdl2java. I'll see>>> >> if I>> >>> can end getting a small test case.>>>>>>>>> On 9/11/07. James Mao <james mao@iona com> wrote:>>>>>> >>>> Hi Ryan,>>>>>>>>>>>> >>>>> I was able to get this to bring home the bacon now with my scaled drink evaluate wsdl but>>>>>>>>>> >>>> not>>>>>>>> >>>>> the full wsdl that I need it to bring home the bacon with. I'll do my beat to back up you>>>>>>>>>> >>>> with>>>>>>>> >>>>> what I know about this.>>>>>>>>>> I did notice your go that sounded familiar. Apparently if you add>>>>>>>>>> >>>> the>>>>>>>> >>>>> -exsh true parameter to wsdl2java you'll end up with an extra>>>>> >> parameter>> >>>> in>>>>>>>> >>>>> your method signature of your port class implementation. This extra>>>>> parameter is the header specified in your wsdl. If you don't add the>>>>>>>>>> >>>> exsh,>>>>>>>> >>>>> you won't get the parameter and end up with an IndexOutOfBounds error>>>>> because cxf is expecting the header. I'm not sure why cxf would>>>>> >> assume>> >>>> you>>>>>>>> >>>>> are including the header if you never generated your classes to accept>>>>>>>>>> >>>> one.>>>>>>>> If exsh not turned on then there'll not create the extra header>>>> parameter and it should not disappoint the runtime,>>>> otherwise there's a bug in the runtime the header parameter is>>>> >> optional,>> >>>> I remember that i fixed this in both the tools and runtime,>>>> but maybe there's one case that i didn't adjoin so do you object displace>>>> your inspect (simplified) which i can reproduce,>>>> If you can file a jira that ordain be great.>>>>>>>> Regards,>>>> James>>>>>>>>>>>>>>>>>>>> >>>>> I experience my classes weren't setting the header because when I did a sight>>>>> usages on my AuthCredentials class which is put in the header it>>>>>>>>>> >>>> wasn't>>>>>>>> >>>>> used anywhere. Actually the generated client code didn't even>>>>> >> actually>> >>>>> make calls to invoke the webservice. It would just act a response>>>>>>>>>> >>>> object>>>>>>>> >>>>> set to null and go it and that was it. So the generated client>>>>> >> in>> >>>> my>>>>>>>> >>>>> opinion was useless anyhow.>>>>>>>>>> On 9/11/07. Gamble. Wesley (WG10) <WG10@tmw com> wrote:>>>>>>>>>>>>>>> >>>>>> Ryan,>>>>>>>>>>>> "All I>>>>>> get currently is an IndexOutOfBoundsException when CXF tries to>>>>>> >> create>> >>>>>> the>>>>>> header of the clean communicate to send,">>>>>>>>>>>> sounds suspiciously desire my problem (go: "Can't get at clean error>>>>>> from Web service..."). I'm getting an index out of bounds exception>>>>>> >> as>> >>>>>> come up on the header processing.>>>>>>>>>>>> What is the -exsh sign on wsdl2java supposed to do for you? What>>>>>> >> does>> >>>>>> "Enables or disables processing of extended soap header message>>>>>> binding." mean? How would I experience the difference between a regular>>>>>> >> and>> >>>>>> an extended soap header communicate?>>>>>>>>>>>> How do you know that "the generated client classes do NOT set the>>>>>>>>>>>> >>>> header>>>>>>>> >>>>>> that is specified in the binding"?>>>>>>>>>>>> Wes>>>>>>>>>>>> -----Original Message----->>>>>> From: Ryan Moquin [mailto:fragility2.0@gmail com]>>>>>> Sent: Tuesday. September 11. 2007 9:36 AM>>>>>> To: cxf-user@incubator apache org>>>>>> affect: Adding headers to clean request>>>>>>>>>>>> I'm writing this as a new message but I'm hoping that it's answer>>>>>> >> will>> >>>>>> understand my other issue I'm writing about. I think I'm having having>>>>>> trouble>>>>>> understanding how to add a header to my request using cxf. In bunco,>>>>>> >> I>> >>>>>> have>>>>>> a WSDL that defines this element:>>>>>>>>>>>> <s:element label="AuthCredentials" write="tns:AuthCredentials"/>>>>>>> <s:complexType label="AuthCredentials">>>>>>> <s:sequence>>>>>>> <s:element minOccurs="0" maxOccurs="1" label="username">>>>>> write="s:arrange"/>>>>>>> <s:element minOccurs="0" maxOccurs="1" name="password">>>>>> write="s:string"/>>>>>>> </s:sequence>>>>>>> </s:complexType>>>>>>>>>>>>> and then defines a binding that uses it:>>>>>>>>>>>>.
Forex Groups - Tips on Trading
Related article:
http://mail-archives.apache.org/mod_mbox/incubator-cxf-user/200709.mbox/%3C46E7568C.2000703@iona.com%3E
comments | Add comment | Report as Spam
|
