Could you explain what does not work ?
Is it at build time or deployment time ?
And please post any exception you have.

On 8/25/06, jeroevi <[EMAIL PROTECTED]> wrote:


Hi,

It has been a while because of vacation and workload.
I finally had a look at your example and it works like a charm in my
setup:
smix 3.0 M2.
My stuff however still doesn't work. I think it has something to do with
the
schema not being in the wsdl.

I put my wsdl and xsd in attachment so you can try it out.

kind regards,
Jeroen

http://www.nabble.com/user-files/235753/validateOrder.wsdl
validateOrder.wsdl
http://www.nabble.com/user-files/235754/Address.xsd Address.xsd
http://www.nabble.com/user-files/235755/Customer.xsd Customer.xsd
http://www.nabble.com/user-files/235756/Order.xsd Order.xsd
http://www.nabble.com/user-files/235757/Product.xsd Product.xsd


gnodet wrote:
>
> I have written a simple example of a wsdl first development using jsr181
> component.
> Take a look at
>
http://svn.apache.org/viewvc/incubator/servicemix/trunk/samples/wsdl-first/
>
> The only limitation is that currently it uses jaxws ri, so you need a
soap
> binding defined in the wsdl.  I hope in the future, we will be able to
use
> xfire jaxws generation and customize it to be able to remove this
> limitation.
>
> Cheers,
> Guillaume Nodet
>
>

--
View this message in context:
http://www.nabble.com/design-first-and-jsr181-tf1755145.html#a5980054
Sent from the ServiceMix - User forum at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to