You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by qu...@metronet.com on 2001/05/11 05:42:05 UTC
Using SOAP without HTTP
Howdy!
I'm having difficulty finding information on how to use/modify SOAP
using a transport other than HTTP. The SOAP spec says it is possible
as well as numerous online articles and tutorials, but I have yet to
actually
find examples of how to do it, or what the spec is for using a transport
other
than HTTP. I am writing in Java and would like to implement SOAP over
proprietary protocol(s) for a client where HTTP is not an option.
Can anyone point me in the right direction?
Thanks, Derek
quikdraw@metronet.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP with HTTPS
Posted by William Bathurst <wb...@us.oracle.com>.
I think your SSL installation is flawed since it doesn't understand any of
the SSL directives.
I would look at ww.modssl.org and perform the modssl install from scratch.
----- Original Message -----
From: "gdelgado" <gu...@netquotient.com>
To: <so...@xml.apache.org>
Sent: Monday, May 14, 2001 01:26 PM
Subject: Using SOAP with HTTPS
> > I'm having problems trying to run Apache+SSL+Tomcat for SOAP
>
> here is the configuration I'm using for apache:
> ./configure
> --prefix=/my/path/to/apache
> --enable-module=so
> --enable-shared=ssl
> make
> make install
>
> openssl:
> ./config
> make
>
> modssl:
> ./configure
> --with-apache=/my/path/to/apache1.3.x/
> --with-ssl=/my/path/to/openssl1.3.xxx
> --prefix=/path/to/apache
> --enable-module=so
> --enable-shared=ssl
>
> then I go to apache1.3.x and do:
> make
> make certificate TYPE=dummy
> make install
>
> I changed the httpd.conf to do
> Listen 8443
> Port 8443
> ServerName localhost
> <VirtualHost localhost:8443>
> SSLEnable
> SSLEngine On
> SSLCertificateFile /to/test/cert
> SSLCertificateKeyFile /to/key/file
> </VirtualHost>
> include /my/path/to/tomcat/conf/mod_jk.conf-auto
>
> then I get the mod_jk.so and put it in the libexe directory of apache.
>
> I start tomcat and then I start apache and it tells me that It can't start
apache
> because
> it does not understands SSLEnable or any of the SSL variables inside the
> VirtualHost tag, any ideas of help will be very appreciated, thanks
>
> I've been working on this for too long!:(
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP with HTTPS
Posted by William Bathurst <wb...@us.oracle.com>.
I think your SSL installation is flawed since it doesn't understand any of
the SSL directives.
I would look at ww.modssl.org and perform the modssl install from scratch.
----- Original Message -----
From: "gdelgado" <gu...@netquotient.com>
To: <so...@xml.apache.org>
Sent: Monday, May 14, 2001 01:26 PM
Subject: Using SOAP with HTTPS
> > I'm having problems trying to run Apache+SSL+Tomcat for SOAP
>
> here is the configuration I'm using for apache:
> ./configure
> --prefix=/my/path/to/apache
> --enable-module=so
> --enable-shared=ssl
> make
> make install
>
> openssl:
> ./config
> make
>
> modssl:
> ./configure
> --with-apache=/my/path/to/apache1.3.x/
> --with-ssl=/my/path/to/openssl1.3.xxx
> --prefix=/path/to/apache
> --enable-module=so
> --enable-shared=ssl
>
> then I go to apache1.3.x and do:
> make
> make certificate TYPE=dummy
> make install
>
> I changed the httpd.conf to do
> Listen 8443
> Port 8443
> ServerName localhost
> <VirtualHost localhost:8443>
> SSLEnable
> SSLEngine On
> SSLCertificateFile /to/test/cert
> SSLCertificateKeyFile /to/key/file
> </VirtualHost>
> include /my/path/to/tomcat/conf/mod_jk.conf-auto
>
> then I get the mod_jk.so and put it in the libexe directory of apache.
>
> I start tomcat and then I start apache and it tells me that It can't start
apache
> because
> it does not understands SSLEnable or any of the SSL variables inside the
> VirtualHost tag, any ideas of help will be very appreciated, thanks
>
> I've been working on this for too long!:(
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Using SOAP with HTTPS
Posted by gdelgado <gu...@netquotient.com>.
> I'm having problems trying to run Apache+SSL+Tomcat for SOAP
here is the configuration I'm using for apache:
./configure
--prefix=/my/path/to/apache
--enable-module=so
--enable-shared=ssl
make
make install
openssl:
./config
make
modssl:
./configure
--with-apache=/my/path/to/apache1.3.x/
--with-ssl=/my/path/to/openssl1.3.xxx
--prefix=/path/to/apache
--enable-module=so
--enable-shared=ssl
then I go to apache1.3.x and do:
make
make certificate TYPE=dummy
make install
I changed the httpd.conf to do
Listen 8443
Port 8443
ServerName localhost
<VirtualHost localhost:8443>
SSLEnable
SSLEngine On
SSLCertificateFile /to/test/cert
SSLCertificateKeyFile /to/key/file
</VirtualHost>
include /my/path/to/tomcat/conf/mod_jk.conf-auto
then I get the mod_jk.so and put it in the libexe directory of apache.
I start tomcat and then I start apache and it tells me that It can't start apache
because
it does not understands SSLEnable or any of the SSL variables inside the
VirtualHost tag, any ideas of help will be very appreciated, thanks
I've been working on this for too long!:(
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Using SOAP with HTTPS
Posted by gdelgado <gu...@netquotient.com>.
> I'm having problems trying to run Apache+SSL+Tomcat for SOAP
here is the configuration I'm using for apache:
./configure
--prefix=/my/path/to/apache
--enable-module=so
--enable-shared=ssl
make
make install
openssl:
./config
make
modssl:
./configure
--with-apache=/my/path/to/apache1.3.x/
--with-ssl=/my/path/to/openssl1.3.xxx
--prefix=/path/to/apache
--enable-module=so
--enable-shared=ssl
then I go to apache1.3.x and do:
make
make certificate TYPE=dummy
make install
I changed the httpd.conf to do
Listen 8443
Port 8443
ServerName localhost
<VirtualHost localhost:8443>
SSLEnable
SSLEngine On
SSLCertificateFile /to/test/cert
SSLCertificateKeyFile /to/key/file
</VirtualHost>
include /my/path/to/tomcat/conf/mod_jk.conf-auto
then I get the mod_jk.so and put it in the libexe directory of apache.
I start tomcat and then I start apache and it tells me that It can't start apache
because
it does not understands SSLEnable or any of the SSL variables inside the
VirtualHost tag, any ideas of help will be very appreciated, thanks
I've been working on this for too long!:(
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by "Michael J. Hudson" <mh...@blueprinttech.com>.
Just as a reminder...
though Apache's SMTP is a solution... please keep in mind, that there
is no standard way of using SOAP over SMTP or any other protocol other
than HTTP (and there's still parts in that, that arent clear). Thus,
keep in mind that SMTP solutions are vendor specific and all clients
will have to write to the Apache implementation, not to a SOAP standard.
David Russell wrote:
>
> > On Fri, 11 May 2001 14:06, Michael Hudson wrote:
> > > Yes, technically SOAP could be used with other transport protocols, but
> the
> > > original SOAP spec does it to HTTP pretty closely. And being that the
> only
> > > official SOAP spec out there only mentions HTTP... if you were to
> implement
> > > SOAP over something else... than you would be in your own proprietary
> zone.
> > Wouldn't the best bet be to provide an adapter (proxy really)... taking
> the
> > obvious example of SMTP, Providing a "server" that receives a "request"
> > (email) and then forwards it to the standard HTTP SOAP server. This would
> > then save you most of the work, I think...?
>
> That is exactly how Apache have implemented SOAP over SMTP. Take a
> look at SMTP2HTTPBridge in org.apache.soap.server. On the send side
> take a look at org.apache.soap.server.transport.smtp.SOAPSMTPConnection.
>
> David
>
> > cheers
> > dim
> >
> >
> > >
> > > Of course, you really wouldn't be that alone. Other than the basic XML
> > > framework... there really isn't currently any other definite standards
> or
> > > ways of using SOAP. There are some security enhancements and mime
> > > attachment standards... but that's about it. How you pass session
> state
> > > over is up for grabs. How you link to a stateful session bean is not
> > > settled. Standards for transaction handling and encryption have not
> been
> > > specified either. The main reason is that SOAP was made to be as
> flexible
> > > and simple as possible... so that anyone could do what they wanted with
> it.
> > >
> > > Thus... the only real answer is... its completely up to you. So, uou
> still
> > > have to write your own server-side implementation... and come up with
> your
> > > own standard for incorporating the XML document into the transport
> > > protocol. Any kind of extra information that needs to be passed back
> and
> > > forth like session stuff is all up to it. BUT... if you make it... then
> > > publish it... you might just have the ability to codify a new standard!
> > >
> > > quikdraw@metronet.com wrote:
> > > > Howdy!
> > > >
> > > > I'm having difficulty finding information on how to use/modify SOAP
> > > > using a transport other than HTTP. The SOAP spec says it is possible
> > > > as well as numerous online articles and tutorials, but I have yet to
> > > > actually
> > > > find examples of how to do it, or what the spec is for using a
> transport
> > > > other
> > > > than HTTP. I am writing in Java and would like to implement SOAP over
> > > > proprietary protocol(s) for a client where HTTP is not an option.
> > > >
> > > > Can anyone point me in the right direction?
> > > >
> > > > Thanks, Derek
> > > > quikdraw@metronet.com
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > > For additional commands, email: soap-user-help@xml.apache.org
> > >
> > > --
> > >
> > > ---------------------------------
> > > Michael J. Hudson
> > > Software/Framework Engineer
> > > mhudson@blueprinttech.com
> > >
> > > cell-phone: 703.362.8039
> > > voice mail: 703.827.0638 ext. 4786
> > > fax: 703.734.0987
> > >
> > > Blueprint Technologies
> > > "The E-Solution Architect"
> > > http://www.blueprinttech.com
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
--
-------------------------------------
Michael J. Hudson
Software/Framework Engineer
mhudson@blueprinttech.com
cell-phone: 703.362.8039
voice-mail: 703.827.0638 ext. 4786
fax: 703.734.0987
Blueprint Technologies
"Great software starts with great architecture"
http://www.blueprinttech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by "Michael J. Hudson" <mh...@blueprinttech.com>.
Just as a reminder...
though Apache's SMTP is a solution... please keep in mind, that there
is no standard way of using SOAP over SMTP or any other protocol other
than HTTP (and there's still parts in that, that arent clear). Thus,
keep in mind that SMTP solutions are vendor specific and all clients
will have to write to the Apache implementation, not to a SOAP standard.
David Russell wrote:
>
> > On Fri, 11 May 2001 14:06, Michael Hudson wrote:
> > > Yes, technically SOAP could be used with other transport protocols, but
> the
> > > original SOAP spec does it to HTTP pretty closely. And being that the
> only
> > > official SOAP spec out there only mentions HTTP... if you were to
> implement
> > > SOAP over something else... than you would be in your own proprietary
> zone.
> > Wouldn't the best bet be to provide an adapter (proxy really)... taking
> the
> > obvious example of SMTP, Providing a "server" that receives a "request"
> > (email) and then forwards it to the standard HTTP SOAP server. This would
> > then save you most of the work, I think...?
>
> That is exactly how Apache have implemented SOAP over SMTP. Take a
> look at SMTP2HTTPBridge in org.apache.soap.server. On the send side
> take a look at org.apache.soap.server.transport.smtp.SOAPSMTPConnection.
>
> David
>
> > cheers
> > dim
> >
> >
> > >
> > > Of course, you really wouldn't be that alone. Other than the basic XML
> > > framework... there really isn't currently any other definite standards
> or
> > > ways of using SOAP. There are some security enhancements and mime
> > > attachment standards... but that's about it. How you pass session
> state
> > > over is up for grabs. How you link to a stateful session bean is not
> > > settled. Standards for transaction handling and encryption have not
> been
> > > specified either. The main reason is that SOAP was made to be as
> flexible
> > > and simple as possible... so that anyone could do what they wanted with
> it.
> > >
> > > Thus... the only real answer is... its completely up to you. So, uou
> still
> > > have to write your own server-side implementation... and come up with
> your
> > > own standard for incorporating the XML document into the transport
> > > protocol. Any kind of extra information that needs to be passed back
> and
> > > forth like session stuff is all up to it. BUT... if you make it... then
> > > publish it... you might just have the ability to codify a new standard!
> > >
> > > quikdraw@metronet.com wrote:
> > > > Howdy!
> > > >
> > > > I'm having difficulty finding information on how to use/modify SOAP
> > > > using a transport other than HTTP. The SOAP spec says it is possible
> > > > as well as numerous online articles and tutorials, but I have yet to
> > > > actually
> > > > find examples of how to do it, or what the spec is for using a
> transport
> > > > other
> > > > than HTTP. I am writing in Java and would like to implement SOAP over
> > > > proprietary protocol(s) for a client where HTTP is not an option.
> > > >
> > > > Can anyone point me in the right direction?
> > > >
> > > > Thanks, Derek
> > > > quikdraw@metronet.com
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > > For additional commands, email: soap-user-help@xml.apache.org
> > >
> > > --
> > >
> > > ---------------------------------
> > > Michael J. Hudson
> > > Software/Framework Engineer
> > > mhudson@blueprinttech.com
> > >
> > > cell-phone: 703.362.8039
> > > voice mail: 703.827.0638 ext. 4786
> > > fax: 703.734.0987
> > >
> > > Blueprint Technologies
> > > "The E-Solution Architect"
> > > http://www.blueprinttech.com
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
--
-------------------------------------
Michael J. Hudson
Software/Framework Engineer
mhudson@blueprinttech.com
cell-phone: 703.362.8039
voice-mail: 703.827.0638 ext. 4786
fax: 703.734.0987
Blueprint Technologies
"Great software starts with great architecture"
http://www.blueprinttech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by David Russell <dr...@bindsys.com>.
> On Fri, 11 May 2001 14:06, Michael Hudson wrote:
> > Yes, technically SOAP could be used with other transport protocols, but
the
> > original SOAP spec does it to HTTP pretty closely. And being that the
only
> > official SOAP spec out there only mentions HTTP... if you were to
implement
> > SOAP over something else... than you would be in your own proprietary
zone.
> Wouldn't the best bet be to provide an adapter (proxy really)... taking
the
> obvious example of SMTP, Providing a "server" that receives a "request"
> (email) and then forwards it to the standard HTTP SOAP server. This would
> then save you most of the work, I think...?
That is exactly how Apache have implemented SOAP over SMTP. Take a
look at SMTP2HTTPBridge in org.apache.soap.server. On the send side
take a look at org.apache.soap.server.transport.smtp.SOAPSMTPConnection.
David
> cheers
> dim
>
>
> >
> > Of course, you really wouldn't be that alone. Other than the basic XML
> > framework... there really isn't currently any other definite standards
or
> > ways of using SOAP. There are some security enhancements and mime
> > attachment standards... but that's about it. How you pass session
state
> > over is up for grabs. How you link to a stateful session bean is not
> > settled. Standards for transaction handling and encryption have not
been
> > specified either. The main reason is that SOAP was made to be as
flexible
> > and simple as possible... so that anyone could do what they wanted with
it.
> >
> > Thus... the only real answer is... its completely up to you. So, uou
still
> > have to write your own server-side implementation... and come up with
your
> > own standard for incorporating the XML document into the transport
> > protocol. Any kind of extra information that needs to be passed back
and
> > forth like session stuff is all up to it. BUT... if you make it... then
> > publish it... you might just have the ability to codify a new standard!
> >
> > quikdraw@metronet.com wrote:
> > > Howdy!
> > >
> > > I'm having difficulty finding information on how to use/modify SOAP
> > > using a transport other than HTTP. The SOAP spec says it is possible
> > > as well as numerous online articles and tutorials, but I have yet to
> > > actually
> > > find examples of how to do it, or what the spec is for using a
transport
> > > other
> > > than HTTP. I am writing in Java and would like to implement SOAP over
> > > proprietary protocol(s) for a client where HTTP is not an option.
> > >
> > > Can anyone point me in the right direction?
> > >
> > > Thanks, Derek
> > > quikdraw@metronet.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> >
> > --
> >
> > ---------------------------------
> > Michael J. Hudson
> > Software/Framework Engineer
> > mhudson@blueprinttech.com
> >
> > cell-phone: 703.362.8039
> > voice mail: 703.827.0638 ext. 4786
> > fax: 703.734.0987
> >
> > Blueprint Technologies
> > "The E-Solution Architect"
> > http://www.blueprinttech.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by David Russell <dr...@bindsys.com>.
> On Fri, 11 May 2001 14:06, Michael Hudson wrote:
> > Yes, technically SOAP could be used with other transport protocols, but
the
> > original SOAP spec does it to HTTP pretty closely. And being that the
only
> > official SOAP spec out there only mentions HTTP... if you were to
implement
> > SOAP over something else... than you would be in your own proprietary
zone.
> Wouldn't the best bet be to provide an adapter (proxy really)... taking
the
> obvious example of SMTP, Providing a "server" that receives a "request"
> (email) and then forwards it to the standard HTTP SOAP server. This would
> then save you most of the work, I think...?
That is exactly how Apache have implemented SOAP over SMTP. Take a
look at SMTP2HTTPBridge in org.apache.soap.server. On the send side
take a look at org.apache.soap.server.transport.smtp.SOAPSMTPConnection.
David
> cheers
> dim
>
>
> >
> > Of course, you really wouldn't be that alone. Other than the basic XML
> > framework... there really isn't currently any other definite standards
or
> > ways of using SOAP. There are some security enhancements and mime
> > attachment standards... but that's about it. How you pass session
state
> > over is up for grabs. How you link to a stateful session bean is not
> > settled. Standards for transaction handling and encryption have not
been
> > specified either. The main reason is that SOAP was made to be as
flexible
> > and simple as possible... so that anyone could do what they wanted with
it.
> >
> > Thus... the only real answer is... its completely up to you. So, uou
still
> > have to write your own server-side implementation... and come up with
your
> > own standard for incorporating the XML document into the transport
> > protocol. Any kind of extra information that needs to be passed back
and
> > forth like session stuff is all up to it. BUT... if you make it... then
> > publish it... you might just have the ability to codify a new standard!
> >
> > quikdraw@metronet.com wrote:
> > > Howdy!
> > >
> > > I'm having difficulty finding information on how to use/modify SOAP
> > > using a transport other than HTTP. The SOAP spec says it is possible
> > > as well as numerous online articles and tutorials, but I have yet to
> > > actually
> > > find examples of how to do it, or what the spec is for using a
transport
> > > other
> > > than HTTP. I am writing in Java and would like to implement SOAP over
> > > proprietary protocol(s) for a client where HTTP is not an option.
> > >
> > > Can anyone point me in the right direction?
> > >
> > > Thanks, Derek
> > > quikdraw@metronet.com
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > > For additional commands, email: soap-user-help@xml.apache.org
> >
> > --
> >
> > ---------------------------------
> > Michael J. Hudson
> > Software/Framework Engineer
> > mhudson@blueprinttech.com
> >
> > cell-phone: 703.362.8039
> > voice mail: 703.827.0638 ext. 4786
> > fax: 703.734.0987
> >
> > Blueprint Technologies
> > "The E-Solution Architect"
> > http://www.blueprinttech.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by Dmitri Colebatch <di...@nuix.com.au>.
On Fri, 11 May 2001 14:06, Michael Hudson wrote:
> Yes, technically SOAP could be used with other transport protocols, but the
> original SOAP spec does it to HTTP pretty closely. And being that the only
> official SOAP spec out there only mentions HTTP... if you were to implement
> SOAP over something else... than you would be in your own proprietary zone.
Wouldn't the best bet be to provide an adapter (proxy really)... taking the
obvious example of SMTP, Providing a "server" that receives a "request"
(email) and then forwards it to the standard HTTP SOAP server. This would
then save you most of the work, I think...?
cheers
dim
>
> Of course, you really wouldn't be that alone. Other than the basic XML
> framework... there really isn't currently any other definite standards or
> ways of using SOAP. There are some security enhancements and mime
> attachment standards... but that's about it. How you pass session state
> over is up for grabs. How you link to a stateful session bean is not
> settled. Standards for transaction handling and encryption have not been
> specified either. The main reason is that SOAP was made to be as flexible
> and simple as possible... so that anyone could do what they wanted with it.
>
> Thus... the only real answer is... its completely up to you. So, uou still
> have to write your own server-side implementation... and come up with your
> own standard for incorporating the XML document into the transport
> protocol. Any kind of extra information that needs to be passed back and
> forth like session stuff is all up to it. BUT... if you make it... then
> publish it... you might just have the ability to codify a new standard!
>
> quikdraw@metronet.com wrote:
> > Howdy!
> >
> > I'm having difficulty finding information on how to use/modify SOAP
> > using a transport other than HTTP. The SOAP spec says it is possible
> > as well as numerous online articles and tutorials, but I have yet to
> > actually
> > find examples of how to do it, or what the spec is for using a transport
> > other
> > than HTTP. I am writing in Java and would like to implement SOAP over
> > proprietary protocol(s) for a client where HTTP is not an option.
> >
> > Can anyone point me in the right direction?
> >
> > Thanks, Derek
> > quikdraw@metronet.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
>
> --
>
> ---------------------------------
> Michael J. Hudson
> Software/Framework Engineer
> mhudson@blueprinttech.com
>
> cell-phone: 703.362.8039
> voice mail: 703.827.0638 ext. 4786
> fax: 703.734.0987
>
> Blueprint Technologies
> "The E-Solution Architect"
> http://www.blueprinttech.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by Dmitri Colebatch <di...@nuix.com.au>.
On Fri, 11 May 2001 14:06, Michael Hudson wrote:
> Yes, technically SOAP could be used with other transport protocols, but the
> original SOAP spec does it to HTTP pretty closely. And being that the only
> official SOAP spec out there only mentions HTTP... if you were to implement
> SOAP over something else... than you would be in your own proprietary zone.
Wouldn't the best bet be to provide an adapter (proxy really)... taking the
obvious example of SMTP, Providing a "server" that receives a "request"
(email) and then forwards it to the standard HTTP SOAP server. This would
then save you most of the work, I think...?
cheers
dim
>
> Of course, you really wouldn't be that alone. Other than the basic XML
> framework... there really isn't currently any other definite standards or
> ways of using SOAP. There are some security enhancements and mime
> attachment standards... but that's about it. How you pass session state
> over is up for grabs. How you link to a stateful session bean is not
> settled. Standards for transaction handling and encryption have not been
> specified either. The main reason is that SOAP was made to be as flexible
> and simple as possible... so that anyone could do what they wanted with it.
>
> Thus... the only real answer is... its completely up to you. So, uou still
> have to write your own server-side implementation... and come up with your
> own standard for incorporating the XML document into the transport
> protocol. Any kind of extra information that needs to be passed back and
> forth like session stuff is all up to it. BUT... if you make it... then
> publish it... you might just have the ability to codify a new standard!
>
> quikdraw@metronet.com wrote:
> > Howdy!
> >
> > I'm having difficulty finding information on how to use/modify SOAP
> > using a transport other than HTTP. The SOAP spec says it is possible
> > as well as numerous online articles and tutorials, but I have yet to
> > actually
> > find examples of how to do it, or what the spec is for using a transport
> > other
> > than HTTP. I am writing in Java and would like to implement SOAP over
> > proprietary protocol(s) for a client where HTTP is not an option.
> >
> > Can anyone point me in the right direction?
> >
> > Thanks, Derek
> > quikdraw@metronet.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> > For additional commands, email: soap-user-help@xml.apache.org
>
> --
>
> ---------------------------------
> Michael J. Hudson
> Software/Framework Engineer
> mhudson@blueprinttech.com
>
> cell-phone: 703.362.8039
> voice mail: 703.827.0638 ext. 4786
> fax: 703.734.0987
>
> Blueprint Technologies
> "The E-Solution Architect"
> http://www.blueprinttech.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by Michael Hudson <mh...@blueprinttech.com>.
Yes, technically SOAP could be used with other transport protocols, but the
original SOAP spec does it to HTTP pretty closely. And being that the only
official SOAP spec out there only mentions HTTP... if you were to implement
SOAP over something else... than you would be in your own proprietary zone.
Of course, you really wouldn't be that alone. Other than the basic XML
framework... there really isn't currently any other definite standards or
ways of using SOAP. There are some security enhancements and mime
attachment standards... but that's about it. How you pass session state
over is up for grabs. How you link to a stateful session bean is not
settled. Standards for transaction handling and encryption have not been
specified either. The main reason is that SOAP was made to be as flexible
and simple as possible... so that anyone could do what they wanted with it.
Thus... the only real answer is... its completely up to you. So, uou still
have to write your own server-side implementation... and come up with your
own standard for incorporating the XML document into the transport
protocol. Any kind of extra information that needs to be passed back and
forth like session stuff is all up to it. BUT... if you make it... then
publish it... you might just have the ability to codify a new standard!
quikdraw@metronet.com wrote:
> Howdy!
>
> I'm having difficulty finding information on how to use/modify SOAP
> using a transport other than HTTP. The SOAP spec says it is possible
> as well as numerous online articles and tutorials, but I have yet to
> actually
> find examples of how to do it, or what the spec is for using a transport
> other
> than HTTP. I am writing in Java and would like to implement SOAP over
> proprietary protocol(s) for a client where HTTP is not an option.
>
> Can anyone point me in the right direction?
>
> Thanks, Derek
> quikdraw@metronet.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
--
---------------------------------
Michael J. Hudson
Software/Framework Engineer
mhudson@blueprinttech.com
cell-phone: 703.362.8039
voice mail: 703.827.0638 ext. 4786
fax: 703.734.0987
Blueprint Technologies
"The E-Solution Architect"
http://www.blueprinttech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by Michael Hudson <mh...@blueprinttech.com>.
Yes, technically SOAP could be used with other transport protocols, but the
original SOAP spec does it to HTTP pretty closely. And being that the only
official SOAP spec out there only mentions HTTP... if you were to implement
SOAP over something else... than you would be in your own proprietary zone.
Of course, you really wouldn't be that alone. Other than the basic XML
framework... there really isn't currently any other definite standards or
ways of using SOAP. There are some security enhancements and mime
attachment standards... but that's about it. How you pass session state
over is up for grabs. How you link to a stateful session bean is not
settled. Standards for transaction handling and encryption have not been
specified either. The main reason is that SOAP was made to be as flexible
and simple as possible... so that anyone could do what they wanted with it.
Thus... the only real answer is... its completely up to you. So, uou still
have to write your own server-side implementation... and come up with your
own standard for incorporating the XML document into the transport
protocol. Any kind of extra information that needs to be passed back and
forth like session stuff is all up to it. BUT... if you make it... then
publish it... you might just have the ability to codify a new standard!
quikdraw@metronet.com wrote:
> Howdy!
>
> I'm having difficulty finding information on how to use/modify SOAP
> using a transport other than HTTP. The SOAP spec says it is possible
> as well as numerous online articles and tutorials, but I have yet to
> actually
> find examples of how to do it, or what the spec is for using a transport
> other
> than HTTP. I am writing in Java and would like to implement SOAP over
> proprietary protocol(s) for a client where HTTP is not an option.
>
> Can anyone point me in the right direction?
>
> Thanks, Derek
> quikdraw@metronet.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org
--
---------------------------------
Michael J. Hudson
Software/Framework Engineer
mhudson@blueprinttech.com
cell-phone: 703.362.8039
voice mail: 703.827.0638 ext. 4786
fax: 703.734.0987
Blueprint Technologies
"The E-Solution Architect"
http://www.blueprinttech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by Alex Kordun <ak...@cornell.edu>.
I think there's also an implementation for the SMTP transport as well:
....\xml-soap\java\src\org\apache\soap\transport\smtp\
Alex
At 10:42 PM 5/10/2001 -0500, you wrote:
>Howdy!
>
>I'm having difficulty finding information on how to use/modify SOAP
>using a transport other than HTTP. The SOAP spec says it is possible
>as well as numerous online articles and tutorials, but I have yet to actually
>find examples of how to do it, or what the spec is for using a transport other
>than HTTP. I am writing in Java and would like to implement SOAP over
>proprietary protocol(s) for a client where HTTP is not an option.
>
>Can anyone point me in the right direction?
>
>Thanks, Derek
>quikdraw@metronet.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
>For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: Using SOAP without HTTP
Posted by Alex Kordun <ak...@cornell.edu>.
I think there's also an implementation for the SMTP transport as well:
....\xml-soap\java\src\org\apache\soap\transport\smtp\
Alex
At 10:42 PM 5/10/2001 -0500, you wrote:
>Howdy!
>
>I'm having difficulty finding information on how to use/modify SOAP
>using a transport other than HTTP. The SOAP spec says it is possible
>as well as numerous online articles and tutorials, but I have yet to actually
>find examples of how to do it, or what the spec is for using a transport other
>than HTTP. I am writing in Java and would like to implement SOAP over
>proprietary protocol(s) for a client where HTTP is not an option.
>
>Can anyone point me in the right direction?
>
>Thanks, Derek
>quikdraw@metronet.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
>For additional commands, email: soap-user-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org