You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Jeff MAURY <jf...@scort.com> on 2001/05/31 14:34:11 UTC
Plugin Transport providers
Hello,
SOAP Apache supports the notion the pluggable transport provider.
However, the choice is given to the client that needs to specify the
transport to use. Is there is a way to have a mecanism that could guess
the right transport according to the form of the URL given, just as the
URL class is doing for the stream handler ?
Thanks
Jeff
--
Jeff MAURY
SCORT CTO
##### ##### ####### ###### #######
# # # # # # # # #
# # # # # # #
##### # # # ###### #
# # # # # # #
# # # # # # # # #
##### ##### ####### # # #
Extending the net to the mainframe
==================================
About the VB-ApacheSOAP sample
Posted by Ricky Cardozo <Ri...@hotmail.com>.
Hi Bojan!!
I have been trying to run the VB-Apache SOAP as well and getting the same
results as well. I guess the strange message is because in somehow the
server is sending you back a message based on any other protocol instead
using SOAP (HTML for example...) . I guess also it is because the
StringBeanInOut section of the sample is based on a complex structure. I
have not figured it out yet but if you got some idea about it I will
appreciate if you can share it with me (and the rest of the soapers here...)
Anyway I would like to get in touch with you regarding MS-SOAP and
ApacheSOAP and how they can interoperate together.
Best Regards
Cyber
-----Original Message-----
From: Furlan Bojan RDSI [mailto:furlan@iskratel.si]
Sent: Friday, May 18, 2001 7:58 AM
To: 'soap-user@xml.apache.org'
Subject: VB to Apache SOAP
Hi all,
I'm trying to run Richard Hansen's VB/Apache demo dated April 25th.
Whenchecking it using Java client, it works fine, but I'm experiencing
strange phenomenon when trying to run VB client. During stringBeanInOut
operation, I get the following message:
Soap Fault:[Client]
Connector - Server returned contenttype other than text/xml
<HRESULT>800a1450</HRESULT>
When trying to check what went wrong using TcpTunnelGui (and TcpTunnelGui2),
things get complicated. If I change last modification date od wsdl file, it
gets transefered to a client, otherwise just part (or none) of it gets
transfered, even though the Content-Length remains the same. In both cases,
no other messages are transfered to, or returned from server. To my
supprise, I get results in VB client window. I have tried to change the
values of strings and results changed accordingly. Can somebody explain what
is going on and help me solve the problem on stringBeanInOut, please.
Thanks
Bojan Furlan
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Plugin Transport providers
Posted by Frederic Jeanne <fj...@symetrx.com>.
The transport provider is defined in the Deployment descriptor of
your SOAP service. At runtime, the provider class is dynamically loaded
thanks to the Provider field of your targeted SOAP service.
To change the targeted provider, create a new service URN.
If you want a more sophisticated scheme, write your own provider, it's quite
intuitive.
Hope this can help you !
FJ.
-----Message d'origine-----
De : Jeff MAURY [mailto:jfmaury@scort.com]
Envoye : jeudi 31 mai 2001 14:34
A : soap-dev@xml.apache.org
Objet : Plugin Transport providers
Hello,
SOAP Apache supports the notion the pluggable transport provider.
However, the choice is given to the client that needs to specify the
transport to use. Is there is a way to have a mecanism that could guess
the right transport according to the form of the URL given, just as the
URL class is doing for the stream handler ?
Thanks
Jeff
--
Jeff MAURY
SCORT CTO
##### ##### ####### ###### #######
# # # # # # # # #
# # # # # # #
##### # # # ###### #
# # # # # # #
# # # # # # # # #
##### ##### ####### # # #
Extending the net to the mainframe
==================================
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: Plugin Transport providers
Posted by Frederic Jeanne <fj...@symetrx.com>.
The transport provider is defined in the Deployment descriptor of
your SOAP service. At runtime, the provider class is dynamically loaded
thanks to the Provider field of your targeted SOAP service.
To change the targeted provider, create a new service URN.
If you want a more sophisticated scheme, write your own provider, it's quite
intuitive.
Hope this can help you !
FJ.
-----Message d'origine-----
De : Jeff MAURY [mailto:jfmaury@scort.com]
Envoye : jeudi 31 mai 2001 14:34
A : soap-dev@xml.apache.org
Objet : Plugin Transport providers
Hello,
SOAP Apache supports the notion the pluggable transport provider.
However, the choice is given to the client that needs to specify the
transport to use. Is there is a way to have a mecanism that could guess
the right transport according to the form of the URL given, just as the
URL class is doing for the stream handler ?
Thanks
Jeff
--
Jeff MAURY
SCORT CTO
##### ##### ####### ###### #######
# # # # # # # # #
# # # # # # #
##### # # # ###### #
# # # # # # #
# # # # # # # # #
##### ##### ####### # # #
Extending the net to the mainframe
==================================
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org