If it described by a java class, you should put some annotations on it
and use JAXB2 to generate a schema.
Then you could validate the xml (on both the client and the server
side) as you will.

On Thu, Sep 4, 2008 at 8:56 PM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> I have a composite Domain object that I expect to send to a PHP consumer
> that describes a COMMAND I want that consumer to act upon.
>
> ---
> Thank You…
>
> Mick Knutson
> BASE Logic, inc.
> (415) 354-4215
>
> Website: http://baselogic.com
> Blog: http://baselogic.com/blog
> BLiNC Magazine: http://blincmagazine.com
> Linked IN: http://linkedin.com/in/mickknutson
> DJ Mick: http://djmick.com
> MySpace: http://myspace.com/mickknutson
> Vacation Rental: http://tahoe.baselogic.com
>
>
>
> On Thu, Sep 4, 2008 at 11:51 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>
>> SOAP is an xml protocol which defines a kind of wrapper around your
>> xml messages.  It does not define the content of the XML data.  Such
>> thing is done using XML schemas (though there are other technologies
>> to describe an xml grammar).  A WSDL is a description of a service.
>> Usually all these things are used together when you deal with "web
>> services" as the WSDL embeds the XML schemas and the SOAP
>> informations.
>> But at the end, if you want to describe your data, you need an XSD
>> (XML schema definition).  When you use a tool such as Java -> WSDL, it
>> will automatically generate an XSD and embed it in the WSDL.  You can
>> also start with an XSD and generate classes using JAXB2 (for example)
>> so that you can do an xml->java or java->xml conversion in servicemix.
>> So in short, if you want to control the XML data, you need a grammar
>> to describe it, not necesseraly a WSDL.   Now, the question is what
>> will be the reference for this data: a set of java classes that you
>> wrote (you can generate a schema from those) or an xml schema or dtd
>> (and you could generate the corresponding java classes) ?
>>
>> On Thu, Sep 4, 2008 at 8:38 PM, Mick Knutson <[EMAIL PROTECTED]>
>> wrote:
>> > will cxf java2wsdl create a schema or just the wsdl for me?
>> >
>> > I guess I am concerned with the content the 2 clients will be send and
>> > consuming.
>> >
>> > I am able right now to allow clients to provide and consume directly to
>> my
>> > jms queue via stomp, but there is no contract on that message. They can
>> send
>> > in junk that I can't use. Also when consuming, they do not know how to
>> > validate what I am sending them.
>> >
>> > What would be the steps I take? Create a wsdl for all my in-out
>> operations
>> > for both providers and consumers? Where does the schema come into play
>> here?
>> >
>> >
>> > ---
>> > Thank You…
>> >
>> > Mick Knutson
>> > BASE Logic, inc.
>> > (415) 354-4215
>> >
>> > Website: http://baselogic.com
>> > Blog: http://baselogic.com/blog
>> > BLiNC Magazine: http://blincmagazine.com
>> > Linked IN: http://linkedin.com/in/mickknutson
>> > DJ Mick: http://djmick.com
>> > MySpace: http://myspace.com/mickknutson
>> > Vacation Rental: http://tahoe.baselogic.com
>> >
>> >
>> >
>> > On Thu, Sep 4, 2008 at 11:28 AM, Guillaume Nodet <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >> Soap has no knowledge of the content of the JMS message, so it should
>> >> be safe to use STOMP to communicate with the JMS broker and put a SOAP
>> >> request into it.  On the servicemix side, you will use a JMS consumer,
>> >> do whatever processing you need and finally send the message to a JMS
>> >> provider.  The PHP client will then be able to receive this JMS
>> >> message using STOMP.
>> >> For the WSDL problem, you can bypass the WSDL if you use the
>> >> <jms:endpoint soap="true" /> which does very basic SOAP processing
>> >> (which may be sufficient in your case), but at some point, you'll need
>> >> to define somehow the XML schema of the request I suppose.  You could
>> >> use the CXF java2wsdl tool if you have a java interface describing
>> >> your service.
>> >>
>> >> On Thu, Sep 4, 2008 at 8:17 PM, Mick Knutson <[EMAIL PROTECTED]>
>> >> wrote:
>> >> > I am using service mix to allow a PHP client send a simple SOAP
>> request
>> >> into
>> >> > a queue, then I want to publish a soap message to an output queue for
>> a
>> >> > Python client.
>> >> >
>> >> > I am having issues getting my head around enforcing a contract for
>> >>  incoming
>> >> > and outgoing messages. I was hoping to leverage cxf and not have a
>> wsdl
>> >> > first apporach so as to not have to maintain wsdl's.
>> >> >
>> >> > Can someone point me in the right direction?
>> >> >
>> >> > ---
>> >> > Thank You…
>> >> >
>> >> > Mick Knutson
>> >> > BASE Logic, inc.
>> >> > (415) 354-4215
>> >> >
>> >> > Website: http://baselogic.com
>> >> > Blog: http://baselogic.com/blog
>> >> > BLiNC Magazine: http://blincmagazine.com
>> >> > Linked IN: http://linkedin.com/in/mickknutson
>> >> > DJ Mick: http://djmick.com
>> >> > MySpace: http://myspace.com/mickknutson
>> >> > Vacation Rental: http://tahoe.baselogic.com
>> >> >
>> >> >
>> >> >
>> >> > On Thu, Sep 4, 2008 at 11:11 AM, Guillaume Nodet <[EMAIL PROTECTED]>
>> >> wrote:
>> >> >
>> >> >> Not sure what you mean exactly.  Could you explain a bit more how
>> >> >> you'd like to use SOAP and STOMP ?
>> >> >>
>> >> >> On Thu, Sep 4, 2008 at 8:03 PM, Mick Knutson <[EMAIL PROTECTED]>
>> >> >> wrote:
>> >> >> > I am wondering how to enforce a soap contract on the sending and
>> >> >> receiving
>> >> >> > of STOMP messages to my queues?
>> >> >> >
>> >> >> > ---
>> >> >> > Thank You…
>> >> >> >
>> >> >> > Mick Knutson
>> >> >> > BASE Logic, inc.
>> >> >> > (415) 354-4215
>> >> >> >
>> >> >> > Website: http://baselogic.com
>> >> >> > Blog: http://baselogic.com/blog
>> >> >> > BLiNC Magazine: http://blincmagazine.com
>> >> >> > Linked IN: http://linkedin.com/in/mickknutson
>> >> >> > DJ Mick: http://djmick.com
>> >> >> > MySpace: http://myspace.com/mickknutson
>> >> >> > Vacation Rental: http://tahoe.baselogic.com
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Cheers,
>> >> >> Guillaume Nodet
>> >> >> ------------------------
>> >> >> Blog: http://gnodet.blogspot.com/
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Cheers,
>> >> Guillaume Nodet
>> >> ------------------------
>> >> Blog: http://gnodet.blogspot.com/
>> >>
>> >
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Reply via email to