Re: design first and jsr181

[bob23 <bo...@yahoo.com>]

Is the issue solved now?
Even I am facing the same issue with the design first approach.

I am using Servicemix 3.1 and I use XFire 1.2.2 for generating server side
classes.

I also tried setting the wsdl resource in the jsr181 component. But this
gives me another error. It returns a SOAPFault with jaxb unmarshall
exception saying "unexpected element .... expected elements are (none)]




Philip Dodds-2 wrote:
> 
> Can you try changing the binding to rpc in your WSDL and re-generating the
> classes?
> 
> P
> 
> On 8/28/06, jeroevi <fo...@jeroevi.be> wrote:
>>
>>
>> I tried again using snapshot
>> servicemix-3.0-incubating-20060827.104511-36.
>> I still have the same problem: operation not supported. The log files are
>> in
>> attachment.
>>
>> regards,
>> Jeroen
>>
>> http://www.nabble.com/user-files/235781/clientSideLog.txt
>> clientSideLog.txt
>> http://www.nabble.com/user-files/235782/serverSideLog.txt
>> serverSideLog.txt
>>
>>
>> gnodet wrote:
>> >
>> > Mmh, strange.  The operation has not been correctly recognized.
>> > Have you tried that with 3.0M2 or a recent snapshot ?
>> > There has been some changes in servicemix-http post M2 to
>> > better recognize the wsdl operation to use.
>> > Could you try with a recent snapshot or build from sources ?
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/design-first-and-jsr181-tf1755145.html#a6017061
>> Sent from the ServiceMix - User forum at Nabble.com.
>>
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/design-first-and-jsr181-tf1755145s12049.html#a9684360
Sent from the ServiceMix - User mailing list archive at Nabble.com.