>
> 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.
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.
Cheers,
Bobby