Bobby Bissett - Javasoft wrote:
>>
>> I think what needs to happen is for the client MEX implementation in
>> wsimport to use the same transport pipe implementations to talk to the
>> service.
>
> This is the part (well, one of the parts) that is confusing me. Does
> wsimport use a transport pipe? From what I've seen, it just uses a
> document builder, gives it the address of the wsdl, and off it goes. If
> there were a transport layer in wsimport, that would be great for what
> you'd like to do.
I don't think wsimport uses the transport pipe today, but I think it
needs to, when it uses MEX to retrieve WSDLs. That's the code you wrote,
right?
In fact, aren't you already using JAX-WS to talk to the service to
retrieve WSDL?
> And, yes, the MEX communications are all soap based. Though there's one
> exception -- a mex response can contain a location element like this:
>
> <mex:MetadataSection
> Dialect='http://www.w3.org/2001/XMLSchema'
> Identifier='http://services.example.org/stockquote/schemas'>
> <mex:Location>
> http://services.example.org/stockquote/schemas
> </mex:Location>
> </mex:MetadataSection>
>
> The location element means to just make an http GET call to that
> location for data.
Yes, I think this is consistent with what we discussed so far. I believe
your test scenarios consist of a servlet that sends back an interesting
<mex:MetadataSection>.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com