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 Mahendra Chheda <mc...@Zantaz.com> on 2001/11/27 02:31:11 UTC
Sending File Attachment using SOAP::Lite
Hello,
I am trying to send a file via my soap method call (Perl client using
SOAP::Lite) to the apache based soap server. However, the format of my call
is giving me errors. Can someone pls guide me on how should the call be
structured.
It seems to be a pretty rudimentary question but I could not see any
documentation at http://www.soaplite.com.
Thanx.
Mahendra
METHOD CALL
-----------
sendFile('file:.\1.xml','mmc')
^^^^^^^^^^^^^^
CLIENT CODE
-----------
use SOAP::Lite;
my $s = SOAP::Lite
->uri('urn:zantazapi')
->proxy('http://localhost:8080/soap/servlet/rpcrouter')
->sendFile('file:.\1.xml','mmc');
print $s->result();
RE: Using alternative transport? BEEP
Posted by Colin Renouf <co...@blueyonder.co.uk>.
Wouldn't it be nice to do a JMS version and then use the bridges to
support all messaging systems (i.e. MSMQ, IBM MQ, etc)? We could then use
MSMQ for the MS flavour of web services.
What do you all think?
Cheers,
Colin.
-----Original Message-----
From: Scott Nichol [mailto:snichol@computer.org]
Sent: 27 November 2001 14:59
To: soap-dev@xml.apache.org
Subject: Re: Using alternative transport? BEEP
Yes, if you look at org.apache.soap.transport.SOAPTransport, then the
implementations in the http and smtp packages, you should get a clear
picture of how to write the client transport.
Virtually all the server software is based on providers running in a J2EE
Web container. Support for SMTP on the server is accomplished by the
org.apache.soap.server.SMTP2HTTPBridge class. This is basically a POP3
client that polls for messages, forwards them to an HTTP-based SOAP
server,
then sends the responses back using SMTP. This model would be the easiest
to follow for other non-HTTP protocols.
These comments relate to Apache SOAP, however, not Axis. I am not
familiar
with the Axis source, so it may be that there are provisions for more
direct
support of other transports on the server.
Scott
----- Original Message -----
From: "Sebastian" <th...@informatik.hu-berlin.de>
To: <so...@xml.apache.org>
Sent: Tuesday, November 27, 2001 7:27 AM
Subject: Re: Using alternative transport? BEEP
> Hello there,
>
> For Fitting BEEP in SOAP I would recommend looking at SOAPTransport
first,
> this is the main class for transporting SOAP Messages. I am right now
also
> trying to accomplish SOAP over BEEP and my main concern is the server
> side, which is kind of complicated because there are a lot of classes
> interacting which I don't really see through yet. If anyone has any
> experience in using another protocol than HTTP for SOAP I would be happy
> to hear from them.
>
> So long,
>
> Sebastian
>
> --
>
__________________________________________________________________________
> sebastian thiebes
thiebes@informatik.hu-berlin.de
>
> "Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber
> ich rechne mit Eurer Integenz" - gefunden bei eBay
>
RE: Using alternative transport? BEEP
Posted by Colin Renouf <co...@blueyonder.co.uk>.
Wouldn't it be nice to do a JMS version and then use the bridges to
support all messaging systems (i.e. MSMQ, IBM MQ, etc)? We could then use
MSMQ for the MS flavour of web services.
What do you all think?
Cheers,
Colin.
-----Original Message-----
From: Scott Nichol [mailto:snichol@computer.org]
Sent: 27 November 2001 14:59
To: soap-dev@xml.apache.org
Subject: Re: Using alternative transport? BEEP
Yes, if you look at org.apache.soap.transport.SOAPTransport, then the
implementations in the http and smtp packages, you should get a clear
picture of how to write the client transport.
Virtually all the server software is based on providers running in a J2EE
Web container. Support for SMTP on the server is accomplished by the
org.apache.soap.server.SMTP2HTTPBridge class. This is basically a POP3
client that polls for messages, forwards them to an HTTP-based SOAP
server,
then sends the responses back using SMTP. This model would be the easiest
to follow for other non-HTTP protocols.
These comments relate to Apache SOAP, however, not Axis. I am not
familiar
with the Axis source, so it may be that there are provisions for more
direct
support of other transports on the server.
Scott
----- Original Message -----
From: "Sebastian" <th...@informatik.hu-berlin.de>
To: <so...@xml.apache.org>
Sent: Tuesday, November 27, 2001 7:27 AM
Subject: Re: Using alternative transport? BEEP
> Hello there,
>
> For Fitting BEEP in SOAP I would recommend looking at SOAPTransport
first,
> this is the main class for transporting SOAP Messages. I am right now
also
> trying to accomplish SOAP over BEEP and my main concern is the server
> side, which is kind of complicated because there are a lot of classes
> interacting which I don't really see through yet. If anyone has any
> experience in using another protocol than HTTP for SOAP I would be happy
> to hear from them.
>
> So long,
>
> Sebastian
>
> --
>
__________________________________________________________________________
> sebastian thiebes
thiebes@informatik.hu-berlin.de
>
> "Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber
> ich rechne mit Eurer Integenz" - gefunden bei eBay
>
Re: Using alternative transport? BEEP
Posted by Scott Nichol <sn...@computer.org>.
Yes, if you look at org.apache.soap.transport.SOAPTransport, then the
implementations in the http and smtp packages, you should get a clear
picture of how to write the client transport.
Virtually all the server software is based on providers running in a J2EE
Web container. Support for SMTP on the server is accomplished by the
org.apache.soap.server.SMTP2HTTPBridge class. This is basically a POP3
client that polls for messages, forwards them to an HTTP-based SOAP server,
then sends the responses back using SMTP. This model would be the easiest
to follow for other non-HTTP protocols.
These comments relate to Apache SOAP, however, not Axis. I am not familiar
with the Axis source, so it may be that there are provisions for more direct
support of other transports on the server.
Scott
----- Original Message -----
From: "Sebastian" <th...@informatik.hu-berlin.de>
To: <so...@xml.apache.org>
Sent: Tuesday, November 27, 2001 7:27 AM
Subject: Re: Using alternative transport? BEEP
> Hello there,
>
> For Fitting BEEP in SOAP I would recommend looking at SOAPTransport first,
> this is the main class for transporting SOAP Messages. I am right now also
> trying to accomplish SOAP over BEEP and my main concern is the server
> side, which is kind of complicated because there are a lot of classes
> interacting which I don't really see through yet. If anyone has any
> experience in using another protocol than HTTP for SOAP I would be happy
> to hear from them.
>
> So long,
>
> Sebastian
>
> --
> __________________________________________________________________________
> sebastian thiebes thiebes@informatik.hu-berlin.de
>
> "Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber
> ich rechne mit Eurer Integenz" - gefunden bei eBay
>
Re: Using alternative transport? BEEP
Posted by Scott Nichol <sn...@computer.org>.
Yes, if you look at org.apache.soap.transport.SOAPTransport, then the
implementations in the http and smtp packages, you should get a clear
picture of how to write the client transport.
Virtually all the server software is based on providers running in a J2EE
Web container. Support for SMTP on the server is accomplished by the
org.apache.soap.server.SMTP2HTTPBridge class. This is basically a POP3
client that polls for messages, forwards them to an HTTP-based SOAP server,
then sends the responses back using SMTP. This model would be the easiest
to follow for other non-HTTP protocols.
These comments relate to Apache SOAP, however, not Axis. I am not familiar
with the Axis source, so it may be that there are provisions for more direct
support of other transports on the server.
Scott
----- Original Message -----
From: "Sebastian" <th...@informatik.hu-berlin.de>
To: <so...@xml.apache.org>
Sent: Tuesday, November 27, 2001 7:27 AM
Subject: Re: Using alternative transport? BEEP
> Hello there,
>
> For Fitting BEEP in SOAP I would recommend looking at SOAPTransport first,
> this is the main class for transporting SOAP Messages. I am right now also
> trying to accomplish SOAP over BEEP and my main concern is the server
> side, which is kind of complicated because there are a lot of classes
> interacting which I don't really see through yet. If anyone has any
> experience in using another protocol than HTTP for SOAP I would be happy
> to hear from them.
>
> So long,
>
> Sebastian
>
> --
> __________________________________________________________________________
> sebastian thiebes thiebes@informatik.hu-berlin.de
>
> "Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber
> ich rechne mit Eurer Integenz" - gefunden bei eBay
>
Re: Using alternative transport? BEEP
Posted by Sebastian <th...@informatik.hu-berlin.de>.
Hello there,
For Fitting BEEP in SOAP I would recommend looking at SOAPTransport first,
this is the main class for transporting SOAP Messages. I am right now also
trying to accomplish SOAP over BEEP and my main concern is the server
side, which is kind of complicated because there are a lot of classes
interacting which I don't really see through yet. If anyone has any
experience in using another protocol than HTTP for SOAP I would be happy
to hear from them.
So long,
Sebastian
--
__________________________________________________________________________
sebastian thiebes thiebes@informatik.hu-berlin.de
"Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber
ich rechne mit Eurer Integenz" - gefunden bei eBay
Re: Using alternative transport? BEEP
Posted by Sebastian <th...@informatik.hu-berlin.de>.
Hello there,
For Fitting BEEP in SOAP I would recommend looking at SOAPTransport first,
this is the main class for transporting SOAP Messages. I am right now also
trying to accomplish SOAP over BEEP and my main concern is the server
side, which is kind of complicated because there are a lot of classes
interacting which I don't really see through yet. If anyone has any
experience in using another protocol than HTTP for SOAP I would be happy
to hear from them.
So long,
Sebastian
--
__________________________________________________________________________
sebastian thiebes thiebes@informatik.hu-berlin.de
"Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber
ich rechne mit Eurer Integenz" - gefunden bei eBay
Using alternative transport? BEEP
Posted by Brian Gilman <gi...@harpo.wi.mit.edu>.
Hello,
I would like to try and get started writing a BEEP SOAP transport.
Can someone point to the right set of classes/interfaces that I need to
get going?? I am very interested in using the axis framework in a p2p
application.
Thanks in advance!!
-Brian
-----------------------
Brian Gilman <gi...@genome.wi.mit.edu>
Sr. Software Engineer MIT/Whitehead Inst. Center for Genome Research
One Kendall Square, Bldg. 300 / Cambridge, MA 02139-1561 USA
phone +1 617 252 1069 / fax +1 617 252 1902
Using alternative transport? BEEP
Posted by Brian Gilman <gi...@harpo.wi.mit.edu>.
Hello,
I would like to try and get started writing a BEEP SOAP transport.
Can someone point to the right set of classes/interfaces that I need to
get going?? I am very interested in using the axis framework in a p2p
application.
Thanks in advance!!
-Brian
-----------------------
Brian Gilman <gi...@genome.wi.mit.edu>
Sr. Software Engineer MIT/Whitehead Inst. Center for Genome Research
One Kendall Square, Bldg. 300 / Cambridge, MA 02139-1561 USA
phone +1 617 252 1069 / fax +1 617 252 1902