You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Aleksandar Milanovic <am...@galdosinc.com> on 2001/03/28 02:44:52 UTC
SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: SOAP vs. J2EE
Posted by George I Matkovits <ma...@qwest.net>.
JMS has a 'free' implementation over HTTP. Also a JMS wrapper for MQSeries is
also available from IBM (MQSeries can be bridged to MSMQ, only within a LAN).
SOAP is great for Java/MS inter operation. For 'reliable' and 'scalable'
Enterprise messaging I would use JMS over HTTP and I am a true 'SOAP' bigot! :-)
I also use J2EE. I am an engineer and IMHO NOBODY invented the universal
programming unswer to all and everything, yet! (42?)
Regards - George
Peter Glynn wrote:
> I definintly agree with Anne
> - if your looking for an enterprise scalable performance minded system go
> for ejb's (Enterprise Java Beans) because of the lovely features that Anne
> has described. If your looking for a book I recommend "Java Server
> Programming" which covers all of J2EE or even Java Enterprise in a Nutshell.
>
> - it is a matter of SOAP and J2EE not SOAP Vs J2EE.
> Although a ejb server can be use as a distribution technology locally - ie
> on the same LAN which is far more efficient to use then SOAP. So if you what
> to implement a distributed system maybe use the approach of anything local
> (on same LAN) use ejb server / RMI (J2EE) and anything global (on the
> Internet) use SOAP. Would people agree.
>
> ----- Original Message -----
> From: "Anne Thomas Manes" <at...@sun.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, March 28, 2001 3:10 AM
> Subject: RE: SOAP vs. J2EE
>
> > It's not a question of one versus the other. Since you need a cross
> platform
> > solution, I'd recommend that you use Java. So the answer is: use both SOAP
> > and J2EE.
> >
> > SOAP is simply an XML messaging protocol. The code that implements the
> SOAP
> > service has to run somewhere -- for example, in a J2EE application server.
> > Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
> > Clear, etc.)
> >
> > The question you want to ask yourself is what type of an application
> server
> > do you need. Will a JSP/servlet engine suffice? Or do you need a
> full-blown
> > EJB-based application server.
> >
> > Both servlet and EJB application servers manage resources for you, such as
> > database connection pooling, session management, and some degree of load
> > balancing. JSP/servlet engines are great for moderate-sized applications,
> > but they often don't provide super-high-scale features such as
> > multithreading, sophisticated load balancing, and bullet-proof fault
> > tolerance. An EJB application server provides these services as well as
> > automatic transaction management, state management, security, and
> > (optionally) persistence management.
> >
> > Anne
> >
> > -----Original Message-----
> > From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> > Sent: Tuesday, March 27, 2001 4:45 PM
> > To: Soap-User
> > Subject: SOAP vs. J2EE
> >
> >
> > Hi SOAPers,
> >
> > I have to make a decision whether to use J2EE or SOAP for a distributed
> > software system. I have more knowledge about SOAP than J2EE, but the
> > principles of the latter are known to me. Still, I am having hard time
> > picking the favourite technology.
> >
> > For example, J2EE facilitates transaction control, which may be useful,
> but
> > it's not obvious to me whether this is so useful as to make it mandatory.
> >
> > The software system in question is XML-centric, but may also deal with
> > non-XML data (e.g. images, voice), which will be somehow encoded in XML
> > (probably Base64). It will accept updates from distributed clients and
> will
> > communicate with other systems via an unspecified protocol (CORBA, RMI or
> > something else, maybe even SOAP). SOAP, if used, would serve for traffic
> > between the server and the clients.
> >
> > It is expected that most of the time this system will have low traffic
> > volume, but occasionally it will increase sharply, and then, more than one
> > client will want to read and update data belonging to the same "object".
> > Scalability is potentially a factor. The system will most likely have
> dozens
> > or hundreds of clients, but the choice of technology should not restrict
> > this number from growing to thousands (more than that is very unlikely).
> > Data integrity is perhaps a less important factor because most data
> updates
> > will consist of inserting new data (appending) rather than modifying the
> > existing.
> >
> > The system should be cross-platform, easy to develop and extensible.
> > Performance is of secondary priority.
> >
> > Any opinions are welcome.
> >
> > thx
> > Alex
> >
> >
> > ---------------------------------------------------------------------
> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: SOAP vs. J2EE
Posted by George I Matkovits <ma...@qwest.net>.
JMS has a 'free' implementation over HTTP. Also a JMS wrapper for MQSeries is
also available from IBM (MQSeries can be bridged to MSMQ, only within a LAN).
SOAP is great for Java/MS inter operation. For 'reliable' and 'scalable'
Enterprise messaging I would use JMS over HTTP and I am a true 'SOAP' bigot! :-)
I also use J2EE. I am an engineer and IMHO NOBODY invented the universal
programming unswer to all and everything, yet! (42?)
Regards - George
Peter Glynn wrote:
> I definintly agree with Anne
> - if your looking for an enterprise scalable performance minded system go
> for ejb's (Enterprise Java Beans) because of the lovely features that Anne
> has described. If your looking for a book I recommend "Java Server
> Programming" which covers all of J2EE or even Java Enterprise in a Nutshell.
>
> - it is a matter of SOAP and J2EE not SOAP Vs J2EE.
> Although a ejb server can be use as a distribution technology locally - ie
> on the same LAN which is far more efficient to use then SOAP. So if you what
> to implement a distributed system maybe use the approach of anything local
> (on same LAN) use ejb server / RMI (J2EE) and anything global (on the
> Internet) use SOAP. Would people agree.
>
> ----- Original Message -----
> From: "Anne Thomas Manes" <at...@sun.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, March 28, 2001 3:10 AM
> Subject: RE: SOAP vs. J2EE
>
> > It's not a question of one versus the other. Since you need a cross
> platform
> > solution, I'd recommend that you use Java. So the answer is: use both SOAP
> > and J2EE.
> >
> > SOAP is simply an XML messaging protocol. The code that implements the
> SOAP
> > service has to run somewhere -- for example, in a J2EE application server.
> > Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
> > Clear, etc.)
> >
> > The question you want to ask yourself is what type of an application
> server
> > do you need. Will a JSP/servlet engine suffice? Or do you need a
> full-blown
> > EJB-based application server.
> >
> > Both servlet and EJB application servers manage resources for you, such as
> > database connection pooling, session management, and some degree of load
> > balancing. JSP/servlet engines are great for moderate-sized applications,
> > but they often don't provide super-high-scale features such as
> > multithreading, sophisticated load balancing, and bullet-proof fault
> > tolerance. An EJB application server provides these services as well as
> > automatic transaction management, state management, security, and
> > (optionally) persistence management.
> >
> > Anne
> >
> > -----Original Message-----
> > From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> > Sent: Tuesday, March 27, 2001 4:45 PM
> > To: Soap-User
> > Subject: SOAP vs. J2EE
> >
> >
> > Hi SOAPers,
> >
> > I have to make a decision whether to use J2EE or SOAP for a distributed
> > software system. I have more knowledge about SOAP than J2EE, but the
> > principles of the latter are known to me. Still, I am having hard time
> > picking the favourite technology.
> >
> > For example, J2EE facilitates transaction control, which may be useful,
> but
> > it's not obvious to me whether this is so useful as to make it mandatory.
> >
> > The software system in question is XML-centric, but may also deal with
> > non-XML data (e.g. images, voice), which will be somehow encoded in XML
> > (probably Base64). It will accept updates from distributed clients and
> will
> > communicate with other systems via an unspecified protocol (CORBA, RMI or
> > something else, maybe even SOAP). SOAP, if used, would serve for traffic
> > between the server and the clients.
> >
> > It is expected that most of the time this system will have low traffic
> > volume, but occasionally it will increase sharply, and then, more than one
> > client will want to read and update data belonging to the same "object".
> > Scalability is potentially a factor. The system will most likely have
> dozens
> > or hundreds of clients, but the choice of technology should not restrict
> > this number from growing to thousands (more than that is very unlikely).
> > Data integrity is perhaps a less important factor because most data
> updates
> > will consist of inserting new data (appending) rather than modifying the
> > existing.
> >
> > The system should be cross-platform, easy to develop and extensible.
> > Performance is of secondary priority.
> >
> > Any opinions are welcome.
> >
> > thx
> > Alex
> >
> >
> > ---------------------------------------------------------------------
> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by graham glass <gr...@mindspring.com>.
i don't agree that RMI/CORBA is far more efficient than SOAP.
with the right technology in place, SOAP is about the same speed.
cheers,
graham
-----Original Message-----
From: Peter Glynn [mailto:glynnp@tcd.ie]
Sent: Wednesday, March 28, 2001 2:15 AM
To: soap-user@xml.apache.org
Subject: Re: SOAP vs. J2EE
I definintly agree with Anne
- if your looking for an enterprise scalable performance minded system go
for ejb's (Enterprise Java Beans) because of the lovely features that Anne
has described. If your looking for a book I recommend "Java Server
Programming" which covers all of J2EE or even Java Enterprise in a Nutshell.
- it is a matter of SOAP and J2EE not SOAP Vs J2EE.
Although a ejb server can be use as a distribution technology locally - ie
on the same LAN which is far more efficient to use then SOAP. So if you what
to implement a distributed system maybe use the approach of anything local
(on same LAN) use ejb server / RMI (J2EE) and anything global (on the
Internet) use SOAP. Would people agree.
----- Original Message -----
From: "Anne Thomas Manes" <at...@sun.com>
To: <so...@xml.apache.org>
Sent: Wednesday, March 28, 2001 3:10 AM
Subject: RE: SOAP vs. J2EE
> It's not a question of one versus the other. Since you need a cross
platform
> solution, I'd recommend that you use Java. So the answer is: use both SOAP
> and J2EE.
>
> SOAP is simply an XML messaging protocol. The code that implements the
SOAP
> service has to run somewhere -- for example, in a J2EE application server.
> Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
> Clear, etc.)
>
> The question you want to ask yourself is what type of an application
server
> do you need. Will a JSP/servlet engine suffice? Or do you need a
full-blown
> EJB-based application server.
>
> Both servlet and EJB application servers manage resources for you, such as
> database connection pooling, session management, and some degree of load
> balancing. JSP/servlet engines are great for moderate-sized applications,
> but they often don't provide super-high-scale features such as
> multithreading, sophisticated load balancing, and bullet-proof fault
> tolerance. An EJB application server provides these services as well as
> automatic transaction management, state management, security, and
> (optionally) persistence management.
>
> Anne
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: Tuesday, March 27, 2001 4:45 PM
> To: Soap-User
> Subject: SOAP vs. J2EE
>
>
> Hi SOAPers,
>
> I have to make a decision whether to use J2EE or SOAP for a distributed
> software system. I have more knowledge about SOAP than J2EE, but the
> principles of the latter are known to me. Still, I am having hard time
> picking the favourite technology.
>
> For example, J2EE facilitates transaction control, which may be useful,
but
> it's not obvious to me whether this is so useful as to make it mandatory.
>
> The software system in question is XML-centric, but may also deal with
> non-XML data (e.g. images, voice), which will be somehow encoded in XML
> (probably Base64). It will accept updates from distributed clients and
will
> communicate with other systems via an unspecified protocol (CORBA, RMI or
> something else, maybe even SOAP). SOAP, if used, would serve for traffic
> between the server and the clients.
>
> It is expected that most of the time this system will have low traffic
> volume, but occasionally it will increase sharply, and then, more than one
> client will want to read and update data belonging to the same "object".
> Scalability is potentially a factor. The system will most likely have
dozens
> or hundreds of clients, but the choice of technology should not restrict
> this number from growing to thousands (more than that is very unlikely).
> Data integrity is perhaps a less important factor because most data
updates
> will consist of inserting new data (appending) rather than modifying the
> existing.
>
> The system should be cross-platform, easy to develop and extensible.
> Performance is of secondary priority.
>
> Any opinions are welcome.
>
> thx
> Alex
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by graham glass <gr...@mindspring.com>.
i don't agree that RMI/CORBA is far more efficient than SOAP.
with the right technology in place, SOAP is about the same speed.
cheers,
graham
-----Original Message-----
From: Peter Glynn [mailto:glynnp@tcd.ie]
Sent: Wednesday, March 28, 2001 2:15 AM
To: soap-user@xml.apache.org
Subject: Re: SOAP vs. J2EE
I definintly agree with Anne
- if your looking for an enterprise scalable performance minded system go
for ejb's (Enterprise Java Beans) because of the lovely features that Anne
has described. If your looking for a book I recommend "Java Server
Programming" which covers all of J2EE or even Java Enterprise in a Nutshell.
- it is a matter of SOAP and J2EE not SOAP Vs J2EE.
Although a ejb server can be use as a distribution technology locally - ie
on the same LAN which is far more efficient to use then SOAP. So if you what
to implement a distributed system maybe use the approach of anything local
(on same LAN) use ejb server / RMI (J2EE) and anything global (on the
Internet) use SOAP. Would people agree.
----- Original Message -----
From: "Anne Thomas Manes" <at...@sun.com>
To: <so...@xml.apache.org>
Sent: Wednesday, March 28, 2001 3:10 AM
Subject: RE: SOAP vs. J2EE
> It's not a question of one versus the other. Since you need a cross
platform
> solution, I'd recommend that you use Java. So the answer is: use both SOAP
> and J2EE.
>
> SOAP is simply an XML messaging protocol. The code that implements the
SOAP
> service has to run somewhere -- for example, in a J2EE application server.
> Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
> Clear, etc.)
>
> The question you want to ask yourself is what type of an application
server
> do you need. Will a JSP/servlet engine suffice? Or do you need a
full-blown
> EJB-based application server.
>
> Both servlet and EJB application servers manage resources for you, such as
> database connection pooling, session management, and some degree of load
> balancing. JSP/servlet engines are great for moderate-sized applications,
> but they often don't provide super-high-scale features such as
> multithreading, sophisticated load balancing, and bullet-proof fault
> tolerance. An EJB application server provides these services as well as
> automatic transaction management, state management, security, and
> (optionally) persistence management.
>
> Anne
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: Tuesday, March 27, 2001 4:45 PM
> To: Soap-User
> Subject: SOAP vs. J2EE
>
>
> Hi SOAPers,
>
> I have to make a decision whether to use J2EE or SOAP for a distributed
> software system. I have more knowledge about SOAP than J2EE, but the
> principles of the latter are known to me. Still, I am having hard time
> picking the favourite technology.
>
> For example, J2EE facilitates transaction control, which may be useful,
but
> it's not obvious to me whether this is so useful as to make it mandatory.
>
> The software system in question is XML-centric, but may also deal with
> non-XML data (e.g. images, voice), which will be somehow encoded in XML
> (probably Base64). It will accept updates from distributed clients and
will
> communicate with other systems via an unspecified protocol (CORBA, RMI or
> something else, maybe even SOAP). SOAP, if used, would serve for traffic
> between the server and the clients.
>
> It is expected that most of the time this system will have low traffic
> volume, but occasionally it will increase sharply, and then, more than one
> client will want to read and update data belonging to the same "object".
> Scalability is potentially a factor. The system will most likely have
dozens
> or hundreds of clients, but the choice of technology should not restrict
> this number from growing to thousands (more than that is very unlikely).
> Data integrity is perhaps a less important factor because most data
updates
> will consist of inserting new data (appending) rather than modifying the
> existing.
>
> The system should be cross-platform, easy to develop and extensible.
> Performance is of secondary priority.
>
> Any opinions are welcome.
>
> thx
> Alex
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: SOAP vs. J2EE
Posted by Peter Glynn <gl...@tcd.ie>.
I definintly agree with Anne
- if your looking for an enterprise scalable performance minded system go
for ejb's (Enterprise Java Beans) because of the lovely features that Anne
has described. If your looking for a book I recommend "Java Server
Programming" which covers all of J2EE or even Java Enterprise in a Nutshell.
- it is a matter of SOAP and J2EE not SOAP Vs J2EE.
Although a ejb server can be use as a distribution technology locally - ie
on the same LAN which is far more efficient to use then SOAP. So if you what
to implement a distributed system maybe use the approach of anything local
(on same LAN) use ejb server / RMI (J2EE) and anything global (on the
Internet) use SOAP. Would people agree.
----- Original Message -----
From: "Anne Thomas Manes" <at...@sun.com>
To: <so...@xml.apache.org>
Sent: Wednesday, March 28, 2001 3:10 AM
Subject: RE: SOAP vs. J2EE
> It's not a question of one versus the other. Since you need a cross
platform
> solution, I'd recommend that you use Java. So the answer is: use both SOAP
> and J2EE.
>
> SOAP is simply an XML messaging protocol. The code that implements the
SOAP
> service has to run somewhere -- for example, in a J2EE application server.
> Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
> Clear, etc.)
>
> The question you want to ask yourself is what type of an application
server
> do you need. Will a JSP/servlet engine suffice? Or do you need a
full-blown
> EJB-based application server.
>
> Both servlet and EJB application servers manage resources for you, such as
> database connection pooling, session management, and some degree of load
> balancing. JSP/servlet engines are great for moderate-sized applications,
> but they often don't provide super-high-scale features such as
> multithreading, sophisticated load balancing, and bullet-proof fault
> tolerance. An EJB application server provides these services as well as
> automatic transaction management, state management, security, and
> (optionally) persistence management.
>
> Anne
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: Tuesday, March 27, 2001 4:45 PM
> To: Soap-User
> Subject: SOAP vs. J2EE
>
>
> Hi SOAPers,
>
> I have to make a decision whether to use J2EE or SOAP for a distributed
> software system. I have more knowledge about SOAP than J2EE, but the
> principles of the latter are known to me. Still, I am having hard time
> picking the favourite technology.
>
> For example, J2EE facilitates transaction control, which may be useful,
but
> it's not obvious to me whether this is so useful as to make it mandatory.
>
> The software system in question is XML-centric, but may also deal with
> non-XML data (e.g. images, voice), which will be somehow encoded in XML
> (probably Base64). It will accept updates from distributed clients and
will
> communicate with other systems via an unspecified protocol (CORBA, RMI or
> something else, maybe even SOAP). SOAP, if used, would serve for traffic
> between the server and the clients.
>
> It is expected that most of the time this system will have low traffic
> volume, but occasionally it will increase sharply, and then, more than one
> client will want to read and update data belonging to the same "object".
> Scalability is potentially a factor. The system will most likely have
dozens
> or hundreds of clients, but the choice of technology should not restrict
> this number from growing to thousands (more than that is very unlikely).
> Data integrity is perhaps a less important factor because most data
updates
> will consist of inserting new data (appending) rather than modifying the
> existing.
>
> The system should be cross-platform, easy to develop and extensible.
> Performance is of secondary priority.
>
> Any opinions are welcome.
>
> thx
> Alex
>
>
> ---------------------------------------------------------------------
> 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: SOAP vs. J2EE
Posted by Peter Glynn <gl...@tcd.ie>.
I definintly agree with Anne
- if your looking for an enterprise scalable performance minded system go
for ejb's (Enterprise Java Beans) because of the lovely features that Anne
has described. If your looking for a book I recommend "Java Server
Programming" which covers all of J2EE or even Java Enterprise in a Nutshell.
- it is a matter of SOAP and J2EE not SOAP Vs J2EE.
Although a ejb server can be use as a distribution technology locally - ie
on the same LAN which is far more efficient to use then SOAP. So if you what
to implement a distributed system maybe use the approach of anything local
(on same LAN) use ejb server / RMI (J2EE) and anything global (on the
Internet) use SOAP. Would people agree.
----- Original Message -----
From: "Anne Thomas Manes" <at...@sun.com>
To: <so...@xml.apache.org>
Sent: Wednesday, March 28, 2001 3:10 AM
Subject: RE: SOAP vs. J2EE
> It's not a question of one versus the other. Since you need a cross
platform
> solution, I'd recommend that you use Java. So the answer is: use both SOAP
> and J2EE.
>
> SOAP is simply an XML messaging protocol. The code that implements the
SOAP
> service has to run somewhere -- for example, in a J2EE application server.
> Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
> Clear, etc.)
>
> The question you want to ask yourself is what type of an application
server
> do you need. Will a JSP/servlet engine suffice? Or do you need a
full-blown
> EJB-based application server.
>
> Both servlet and EJB application servers manage resources for you, such as
> database connection pooling, session management, and some degree of load
> balancing. JSP/servlet engines are great for moderate-sized applications,
> but they often don't provide super-high-scale features such as
> multithreading, sophisticated load balancing, and bullet-proof fault
> tolerance. An EJB application server provides these services as well as
> automatic transaction management, state management, security, and
> (optionally) persistence management.
>
> Anne
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: Tuesday, March 27, 2001 4:45 PM
> To: Soap-User
> Subject: SOAP vs. J2EE
>
>
> Hi SOAPers,
>
> I have to make a decision whether to use J2EE or SOAP for a distributed
> software system. I have more knowledge about SOAP than J2EE, but the
> principles of the latter are known to me. Still, I am having hard time
> picking the favourite technology.
>
> For example, J2EE facilitates transaction control, which may be useful,
but
> it's not obvious to me whether this is so useful as to make it mandatory.
>
> The software system in question is XML-centric, but may also deal with
> non-XML data (e.g. images, voice), which will be somehow encoded in XML
> (probably Base64). It will accept updates from distributed clients and
will
> communicate with other systems via an unspecified protocol (CORBA, RMI or
> something else, maybe even SOAP). SOAP, if used, would serve for traffic
> between the server and the clients.
>
> It is expected that most of the time this system will have low traffic
> volume, but occasionally it will increase sharply, and then, more than one
> client will want to read and update data belonging to the same "object".
> Scalability is potentially a factor. The system will most likely have
dozens
> or hundreds of clients, but the choice of technology should not restrict
> this number from growing to thousands (more than that is very unlikely).
> Data integrity is perhaps a less important factor because most data
updates
> will consist of inserting new data (appending) rather than modifying the
> existing.
>
> The system should be cross-platform, easy to develop and extensible.
> Performance is of secondary priority.
>
> Any opinions are welcome.
>
> thx
> Alex
>
>
> ---------------------------------------------------------------------
> 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: SOAP vs. J2EE
Posted by Court Demas <co...@idoox.com>.
We have just released a preview of our WASP 2.0 toolkit which contains both
fine-grained security and transactions. Our security is based on the GSS-API and
SPKM certificates and allows each Web Service to have its own identity (as opposed
to SSL which has a single identity per Web server/domain). We also support
transactional context propogation from EJB components. Our ejbtool generates
transactional SOAP wrappers from EJB beans; the transactions may be controlled from
client code via UserTransaction.
http://www.idoox.com/products/wasp20/index.html
As Graham said, it would be really nice if these features were defined in the
protocol somewhere! Having security/transaction interoperability between
SOAP implementations would be incredibly powerful. Unfortunately, interop is the
primary weakness of SOAP right now.
As far as scalability, most Java-based SOAP implementations (including Idoox's) are
based upon the Servlet API (for SOAP over HTTP). We're fortunate to have dozens of
high-quality servlet-capable application servers available, many of which are
free. These provide developers with many options for scalability and robustness
(failover, clustering, etc).
court
http://www.idoox.com
Dennis Sosnoski wrote:
> The discussion of SOAP and J2EE as some form of competitors seems to miss the
> point. SOAP is designed for request-response operations with no state,
> essentially RPC to anonymous services (*not* to objects, despite the name, since
> objects generally imply state). These services are basically the equivalent of
> calls to stateless session beans, in J2EE/EJB terms.
>
> J2EE/EJB is an architecture for building scalable distributed applications. It
> generally uses a web front-end for the user interface, with servlets and JSPs.
> SOAP is more of an alternative to this web front-end than a competing
> implementation technology. As opposed to the web front-end for users working
> through browsers, SOAP gives an more general purpose interface for other types
> of programs to use.
>
> SOAP cannot replace RMI for use with EJBs for several reasons, including the
> lack of state in SOAP. It may still make sense to supply a SOAP interface to
> selected parts of your J2EE/EJB system, though. An example might be an ecommerce
> system which provides a SOAP interface for checking item pricing and
> availability, order status, and shipment information.
>
> - Dennis
>
> Dennis M. Sosnoski
> Sosnoski Software Solutions, Inc.
> http://www.sosnoski.com
>
> Aleksandar Milanovic wrote:
>
> > Hm, that's basically my dilemma. I am interested in:
> >
> > * scalability (more in data volume per user than the number of users, which
> > might rise to thousands)
> > * security (authentication, authorization)
> > * extensibility
> > * portability
> > * ease of use/development
> > * data integrity (there may be many clients writing to the same data object
> > at the same time, but most updates will be actually inserting new data)
> >
> > The combination of SOAP and SSL addresses security. It is not clear to me
> > how scaleable SOAP solutions are. Obviously, they are extensible and
> > portable, and easy to develop.
> > Data integrity may not be an important factor since most access will consist
> > of reads and inserts.
> >
> > I need to make a decision very soon. Any advice would be appreciated.
> >
> > thx
> > Alex
> >
> > -----Original Message-----
> > From: Mathew Clark [mailto:matt@genicomsystems.com]
> > Sent: Wednesday, March 28, 2001 4:40 PM
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > We have identified the J2EE features that we believe add to the scalability
> > and robustness of our architecture without disproportional increases in
> > performance, maintenance and complexity.
> >
> > regards,
> >
> > Matthew.
> >
> > -----Original Message-----
> > From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> > Sent: 29 March 2001 01:05
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > Do you mean that you will use partial, less sophisticated, J2EE
> > implementations or that you will use only some J2EE features such as RMI and
> > JMSG?
> >
> > Alex
> >
> > -----Original Message-----
> > From: Mathew Clark [mailto:matt@genicomsystems.com]
> > Sent: Wednesday, March 28, 2001 4:10 PM
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > Hey guys - we have been discussing the very same thing here... So far, we
> > have been very impressed with SOAP... once we got past some install issues
> > with Apache SOAP, we were able to do some fairly hefty load testing on our
> > development platform - I should point out that this is over Gigabit
> > Ethernet...
> >
> > The bottleneck is the EJBs not the weight of the SOAP messages. We are very
> > unlikely to go fully J2EE - it seems to make far more sense to use the bits
> > that you need rather than restrict yourself. Somewhere between "super
> > servlets" and J2EE.
> >
> > Regards,
> >
> > Matthew.
> >
> > ' Never use technology for the sake of technology. '
> >
> > -----Original Message-----
> > From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> > Sent: 28 March 2001 19:33
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
> > with SOAP. However, it's not clear to me if J2EE's super-high-scale features
> > depend somehow on the use of RMI. This is important, because the main
> > components of this distributed system should communicate among themselves
> > using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
> > used for interoperability.
> > So the question is, can SOAP replace RMI for intercomponent communication on
> > J2EE?
> >
> > thx
> > Alex
>
> ---------------------------------------------------------------------
> 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: SOAP vs. J2EE
Posted by Court Demas <co...@idoox.com>.
We have just released a preview of our WASP 2.0 toolkit which contains both
fine-grained security and transactions. Our security is based on the GSS-API and
SPKM certificates and allows each Web Service to have its own identity (as opposed
to SSL which has a single identity per Web server/domain). We also support
transactional context propogation from EJB components. Our ejbtool generates
transactional SOAP wrappers from EJB beans; the transactions may be controlled from
client code via UserTransaction.
http://www.idoox.com/products/wasp20/index.html
As Graham said, it would be really nice if these features were defined in the
protocol somewhere! Having security/transaction interoperability between
SOAP implementations would be incredibly powerful. Unfortunately, interop is the
primary weakness of SOAP right now.
As far as scalability, most Java-based SOAP implementations (including Idoox's) are
based upon the Servlet API (for SOAP over HTTP). We're fortunate to have dozens of
high-quality servlet-capable application servers available, many of which are
free. These provide developers with many options for scalability and robustness
(failover, clustering, etc).
court
http://www.idoox.com
Dennis Sosnoski wrote:
> The discussion of SOAP and J2EE as some form of competitors seems to miss the
> point. SOAP is designed for request-response operations with no state,
> essentially RPC to anonymous services (*not* to objects, despite the name, since
> objects generally imply state). These services are basically the equivalent of
> calls to stateless session beans, in J2EE/EJB terms.
>
> J2EE/EJB is an architecture for building scalable distributed applications. It
> generally uses a web front-end for the user interface, with servlets and JSPs.
> SOAP is more of an alternative to this web front-end than a competing
> implementation technology. As opposed to the web front-end for users working
> through browsers, SOAP gives an more general purpose interface for other types
> of programs to use.
>
> SOAP cannot replace RMI for use with EJBs for several reasons, including the
> lack of state in SOAP. It may still make sense to supply a SOAP interface to
> selected parts of your J2EE/EJB system, though. An example might be an ecommerce
> system which provides a SOAP interface for checking item pricing and
> availability, order status, and shipment information.
>
> - Dennis
>
> Dennis M. Sosnoski
> Sosnoski Software Solutions, Inc.
> http://www.sosnoski.com
>
> Aleksandar Milanovic wrote:
>
> > Hm, that's basically my dilemma. I am interested in:
> >
> > * scalability (more in data volume per user than the number of users, which
> > might rise to thousands)
> > * security (authentication, authorization)
> > * extensibility
> > * portability
> > * ease of use/development
> > * data integrity (there may be many clients writing to the same data object
> > at the same time, but most updates will be actually inserting new data)
> >
> > The combination of SOAP and SSL addresses security. It is not clear to me
> > how scaleable SOAP solutions are. Obviously, they are extensible and
> > portable, and easy to develop.
> > Data integrity may not be an important factor since most access will consist
> > of reads and inserts.
> >
> > I need to make a decision very soon. Any advice would be appreciated.
> >
> > thx
> > Alex
> >
> > -----Original Message-----
> > From: Mathew Clark [mailto:matt@genicomsystems.com]
> > Sent: Wednesday, March 28, 2001 4:40 PM
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > We have identified the J2EE features that we believe add to the scalability
> > and robustness of our architecture without disproportional increases in
> > performance, maintenance and complexity.
> >
> > regards,
> >
> > Matthew.
> >
> > -----Original Message-----
> > From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> > Sent: 29 March 2001 01:05
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > Do you mean that you will use partial, less sophisticated, J2EE
> > implementations or that you will use only some J2EE features such as RMI and
> > JMSG?
> >
> > Alex
> >
> > -----Original Message-----
> > From: Mathew Clark [mailto:matt@genicomsystems.com]
> > Sent: Wednesday, March 28, 2001 4:10 PM
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > Hey guys - we have been discussing the very same thing here... So far, we
> > have been very impressed with SOAP... once we got past some install issues
> > with Apache SOAP, we were able to do some fairly hefty load testing on our
> > development platform - I should point out that this is over Gigabit
> > Ethernet...
> >
> > The bottleneck is the EJBs not the weight of the SOAP messages. We are very
> > unlikely to go fully J2EE - it seems to make far more sense to use the bits
> > that you need rather than restrict yourself. Somewhere between "super
> > servlets" and J2EE.
> >
> > Regards,
> >
> > Matthew.
> >
> > ' Never use technology for the sake of technology. '
> >
> > -----Original Message-----
> > From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> > Sent: 28 March 2001 19:33
> > To: soap-user@xml.apache.org
> > Subject: RE: SOAP vs. J2EE
> >
> > Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
> > with SOAP. However, it's not clear to me if J2EE's super-high-scale features
> > depend somehow on the use of RMI. This is important, because the main
> > components of this distributed system should communicate among themselves
> > using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
> > used for interoperability.
> > So the question is, can SOAP replace RMI for intercomponent communication on
> > J2EE?
> >
> > thx
> > Alex
>
> ---------------------------------------------------------------------
> 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: SOAP vs. J2EE
Posted by graham glass <gr...@mindspring.com>.
i don't understand this whole think about
SOAP having "no state". with SOAP, you send
a message to an endpoint. this endpoint can
process messages on a per-request, per-session,
per-application basis or whatever else it
wants to do.
our own platform GLUE, like apache SOAP,
supports all of these modes and it's a piece
of cake to expose a stateful object as
a web service. in fact, we designed GLUE
specifically so it could be used as a replacement
to RMI (in addition to other purposes of course).
cheers,
graham
-----Original Message-----
From: Dennis Sosnoski [mailto:dms@sosnoski.com]
Sent: Wednesday, March 28, 2001 9:05 PM
To: soap-user@xml.apache.org
Cc: matt@genicomsystems.com
Subject: Re: SOAP vs. J2EE
The discussion of SOAP and J2EE as some form of competitors seems to miss
the
point. SOAP is designed for request-response operations with no state,
essentially RPC to anonymous services (*not* to objects, despite the name,
since
objects generally imply state). These services are basically the equivalent
of
calls to stateless session beans, in J2EE/EJB terms.
J2EE/EJB is an architecture for building scalable distributed applications.
It
generally uses a web front-end for the user interface, with servlets and
JSPs.
SOAP is more of an alternative to this web front-end than a competing
implementation technology. As opposed to the web front-end for users working
through browsers, SOAP gives an more general purpose interface for other
types
of programs to use.
SOAP cannot replace RMI for use with EJBs for several reasons, including the
lack of state in SOAP. It may still make sense to supply a SOAP interface to
selected parts of your J2EE/EJB system, though. An example might be an
ecommerce
system which provides a SOAP interface for checking item pricing and
availability, order status, and shipment information.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
Aleksandar Milanovic wrote:
> Hm, that's basically my dilemma. I am interested in:
>
> * scalability (more in data volume per user than the number of users,
which
> might rise to thousands)
> * security (authentication, authorization)
> * extensibility
> * portability
> * ease of use/development
> * data integrity (there may be many clients writing to the same data
object
> at the same time, but most updates will be actually inserting new data)
>
> The combination of SOAP and SSL addresses security. It is not clear to me
> how scaleable SOAP solutions are. Obviously, they are extensible and
> portable, and easy to develop.
> Data integrity may not be an important factor since most access will
consist
> of reads and inserts.
>
> I need to make a decision very soon. Any advice would be appreciated.
>
> thx
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:40 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> We have identified the J2EE features that we believe add to the
scalability
> and robustness of our architecture without disproportional increases in
> performance, maintenance and complexity.
>
> regards,
>
> Matthew.
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 29 March 2001 01:05
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Do you mean that you will use partial, less sophisticated, J2EE
> implementations or that you will use only some J2EE features such as RMI
and
> JMSG?
>
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:10 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Hey guys - we have been discussing the very same thing here... So far, we
> have been very impressed with SOAP... once we got past some install issues
> with Apache SOAP, we were able to do some fairly hefty load testing on our
> development platform - I should point out that this is over Gigabit
> Ethernet...
>
> The bottleneck is the EJBs not the weight of the SOAP messages. We are
very
> unlikely to go fully J2EE - it seems to make far more sense to use the
bits
> that you need rather than restrict yourself. Somewhere between "super
> servlets" and J2EE.
>
> Regards,
>
> Matthew.
>
> ' Never use technology for the sake of technology. '
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 28 March 2001 19:33
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Thx for the reply. I was indeed contemplating the use of J2EE in
conjunction
> with SOAP. However, it's not clear to me if J2EE's super-high-scale
features
> depend somehow on the use of RMI. This is important, because the main
> components of this distributed system should communicate among themselves
> using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably
be
> used for interoperability.
> So the question is, can SOAP replace RMI for intercomponent communication
on
> J2EE?
>
> thx
> Alex
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Mathew Clark <ma...@genicomsystems.com>.
Hi, I just noticed this was CCed to me..
I was not viewing them as competitors - We use some of the services provided
by the J2EE architecture and we also use SOAP. We also found that there are
a lot of unnecessary complexities, overheads etc with much of the J2EE
architecture.
regards,
Matthew.
-----Original Message-----
From: Dennis Sosnoski [mailto:dms@sosnoski.com]
Sent: 29 March 2001 04:05
To: soap-user@xml.apache.org
Cc: matt@genicomsystems.com
Subject: Re: SOAP vs. J2EE
The discussion of SOAP and J2EE as some form of competitors seems to miss
the
point. SOAP is designed for request-response operations with no state,
essentially RPC to anonymous services (*not* to objects, despite the name,
since
objects generally imply state). These services are basically the equivalent
of
calls to stateless session beans, in J2EE/EJB terms.
J2EE/EJB is an architecture for building scalable distributed applications.
It
generally uses a web front-end for the user interface, with servlets and
JSPs.
SOAP is more of an alternative to this web front-end than a competing
implementation technology. As opposed to the web front-end for users working
through browsers, SOAP gives an more general purpose interface for other
types
of programs to use.
SOAP cannot replace RMI for use with EJBs for several reasons, including the
lack of state in SOAP. It may still make sense to supply a SOAP interface to
selected parts of your J2EE/EJB system, though. An example might be an
ecommerce
system which provides a SOAP interface for checking item pricing and
availability, order status, and shipment information.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
Aleksandar Milanovic wrote:
> Hm, that's basically my dilemma. I am interested in:
>
> * scalability (more in data volume per user than the number of users,
which
> might rise to thousands)
> * security (authentication, authorization)
> * extensibility
> * portability
> * ease of use/development
> * data integrity (there may be many clients writing to the same data
object
> at the same time, but most updates will be actually inserting new data)
>
> The combination of SOAP and SSL addresses security. It is not clear to me
> how scaleable SOAP solutions are. Obviously, they are extensible and
> portable, and easy to develop.
> Data integrity may not be an important factor since most access will
consist
> of reads and inserts.
>
> I need to make a decision very soon. Any advice would be appreciated.
>
> thx
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:40 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> We have identified the J2EE features that we believe add to the
scalability
> and robustness of our architecture without disproportional increases in
> performance, maintenance and complexity.
>
> regards,
>
> Matthew.
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 29 March 2001 01:05
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Do you mean that you will use partial, less sophisticated, J2EE
> implementations or that you will use only some J2EE features such as RMI
and
> JMSG?
>
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:10 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Hey guys - we have been discussing the very same thing here... So far, we
> have been very impressed with SOAP... once we got past some install issues
> with Apache SOAP, we were able to do some fairly hefty load testing on our
> development platform - I should point out that this is over Gigabit
> Ethernet...
>
> The bottleneck is the EJBs not the weight of the SOAP messages. We are
very
> unlikely to go fully J2EE - it seems to make far more sense to use the
bits
> that you need rather than restrict yourself. Somewhere between "super
> servlets" and J2EE.
>
> Regards,
>
> Matthew.
>
> ' Never use technology for the sake of technology. '
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 28 March 2001 19:33
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Thx for the reply. I was indeed contemplating the use of J2EE in
conjunction
> with SOAP. However, it's not clear to me if J2EE's super-high-scale
features
> depend somehow on the use of RMI. This is important, because the main
> components of this distributed system should communicate among themselves
> using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably
be
> used for interoperability.
> So the question is, can SOAP replace RMI for intercomponent communication
on
> J2EE?
>
> thx
> Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by graham glass <gr...@mindspring.com>.
i don't understand this whole think about
SOAP having "no state". with SOAP, you send
a message to an endpoint. this endpoint can
process messages on a per-request, per-session,
per-application basis or whatever else it
wants to do.
our own platform GLUE, like apache SOAP,
supports all of these modes and it's a piece
of cake to expose a stateful object as
a web service. in fact, we designed GLUE
specifically so it could be used as a replacement
to RMI (in addition to other purposes of course).
cheers,
graham
-----Original Message-----
From: Dennis Sosnoski [mailto:dms@sosnoski.com]
Sent: Wednesday, March 28, 2001 9:05 PM
To: soap-user@xml.apache.org
Cc: matt@genicomsystems.com
Subject: Re: SOAP vs. J2EE
The discussion of SOAP and J2EE as some form of competitors seems to miss
the
point. SOAP is designed for request-response operations with no state,
essentially RPC to anonymous services (*not* to objects, despite the name,
since
objects generally imply state). These services are basically the equivalent
of
calls to stateless session beans, in J2EE/EJB terms.
J2EE/EJB is an architecture for building scalable distributed applications.
It
generally uses a web front-end for the user interface, with servlets and
JSPs.
SOAP is more of an alternative to this web front-end than a competing
implementation technology. As opposed to the web front-end for users working
through browsers, SOAP gives an more general purpose interface for other
types
of programs to use.
SOAP cannot replace RMI for use with EJBs for several reasons, including the
lack of state in SOAP. It may still make sense to supply a SOAP interface to
selected parts of your J2EE/EJB system, though. An example might be an
ecommerce
system which provides a SOAP interface for checking item pricing and
availability, order status, and shipment information.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
Aleksandar Milanovic wrote:
> Hm, that's basically my dilemma. I am interested in:
>
> * scalability (more in data volume per user than the number of users,
which
> might rise to thousands)
> * security (authentication, authorization)
> * extensibility
> * portability
> * ease of use/development
> * data integrity (there may be many clients writing to the same data
object
> at the same time, but most updates will be actually inserting new data)
>
> The combination of SOAP and SSL addresses security. It is not clear to me
> how scaleable SOAP solutions are. Obviously, they are extensible and
> portable, and easy to develop.
> Data integrity may not be an important factor since most access will
consist
> of reads and inserts.
>
> I need to make a decision very soon. Any advice would be appreciated.
>
> thx
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:40 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> We have identified the J2EE features that we believe add to the
scalability
> and robustness of our architecture without disproportional increases in
> performance, maintenance and complexity.
>
> regards,
>
> Matthew.
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 29 March 2001 01:05
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Do you mean that you will use partial, less sophisticated, J2EE
> implementations or that you will use only some J2EE features such as RMI
and
> JMSG?
>
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:10 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Hey guys - we have been discussing the very same thing here... So far, we
> have been very impressed with SOAP... once we got past some install issues
> with Apache SOAP, we were able to do some fairly hefty load testing on our
> development platform - I should point out that this is over Gigabit
> Ethernet...
>
> The bottleneck is the EJBs not the weight of the SOAP messages. We are
very
> unlikely to go fully J2EE - it seems to make far more sense to use the
bits
> that you need rather than restrict yourself. Somewhere between "super
> servlets" and J2EE.
>
> Regards,
>
> Matthew.
>
> ' Never use technology for the sake of technology. '
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 28 March 2001 19:33
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Thx for the reply. I was indeed contemplating the use of J2EE in
conjunction
> with SOAP. However, it's not clear to me if J2EE's super-high-scale
features
> depend somehow on the use of RMI. This is important, because the main
> components of this distributed system should communicate among themselves
> using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably
be
> used for interoperability.
> So the question is, can SOAP replace RMI for intercomponent communication
on
> J2EE?
>
> thx
> Alex
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Mathew Clark <ma...@genicomsystems.com>.
Hi, I just noticed this was CCed to me..
I was not viewing them as competitors - We use some of the services provided
by the J2EE architecture and we also use SOAP. We also found that there are
a lot of unnecessary complexities, overheads etc with much of the J2EE
architecture.
regards,
Matthew.
-----Original Message-----
From: Dennis Sosnoski [mailto:dms@sosnoski.com]
Sent: 29 March 2001 04:05
To: soap-user@xml.apache.org
Cc: matt@genicomsystems.com
Subject: Re: SOAP vs. J2EE
The discussion of SOAP and J2EE as some form of competitors seems to miss
the
point. SOAP is designed for request-response operations with no state,
essentially RPC to anonymous services (*not* to objects, despite the name,
since
objects generally imply state). These services are basically the equivalent
of
calls to stateless session beans, in J2EE/EJB terms.
J2EE/EJB is an architecture for building scalable distributed applications.
It
generally uses a web front-end for the user interface, with servlets and
JSPs.
SOAP is more of an alternative to this web front-end than a competing
implementation technology. As opposed to the web front-end for users working
through browsers, SOAP gives an more general purpose interface for other
types
of programs to use.
SOAP cannot replace RMI for use with EJBs for several reasons, including the
lack of state in SOAP. It may still make sense to supply a SOAP interface to
selected parts of your J2EE/EJB system, though. An example might be an
ecommerce
system which provides a SOAP interface for checking item pricing and
availability, order status, and shipment information.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
Aleksandar Milanovic wrote:
> Hm, that's basically my dilemma. I am interested in:
>
> * scalability (more in data volume per user than the number of users,
which
> might rise to thousands)
> * security (authentication, authorization)
> * extensibility
> * portability
> * ease of use/development
> * data integrity (there may be many clients writing to the same data
object
> at the same time, but most updates will be actually inserting new data)
>
> The combination of SOAP and SSL addresses security. It is not clear to me
> how scaleable SOAP solutions are. Obviously, they are extensible and
> portable, and easy to develop.
> Data integrity may not be an important factor since most access will
consist
> of reads and inserts.
>
> I need to make a decision very soon. Any advice would be appreciated.
>
> thx
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:40 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> We have identified the J2EE features that we believe add to the
scalability
> and robustness of our architecture without disproportional increases in
> performance, maintenance and complexity.
>
> regards,
>
> Matthew.
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 29 March 2001 01:05
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Do you mean that you will use partial, less sophisticated, J2EE
> implementations or that you will use only some J2EE features such as RMI
and
> JMSG?
>
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:10 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Hey guys - we have been discussing the very same thing here... So far, we
> have been very impressed with SOAP... once we got past some install issues
> with Apache SOAP, we were able to do some fairly hefty load testing on our
> development platform - I should point out that this is over Gigabit
> Ethernet...
>
> The bottleneck is the EJBs not the weight of the SOAP messages. We are
very
> unlikely to go fully J2EE - it seems to make far more sense to use the
bits
> that you need rather than restrict yourself. Somewhere between "super
> servlets" and J2EE.
>
> Regards,
>
> Matthew.
>
> ' Never use technology for the sake of technology. '
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 28 March 2001 19:33
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Thx for the reply. I was indeed contemplating the use of J2EE in
conjunction
> with SOAP. However, it's not clear to me if J2EE's super-high-scale
features
> depend somehow on the use of RMI. This is important, because the main
> components of this distributed system should communicate among themselves
> using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably
be
> used for interoperability.
> So the question is, can SOAP replace RMI for intercomponent communication
on
> J2EE?
>
> thx
> Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: SOAP vs. J2EE
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
The discussion of SOAP and J2EE as some form of competitors seems to miss the
point. SOAP is designed for request-response operations with no state,
essentially RPC to anonymous services (*not* to objects, despite the name, since
objects generally imply state). These services are basically the equivalent of
calls to stateless session beans, in J2EE/EJB terms.
J2EE/EJB is an architecture for building scalable distributed applications. It
generally uses a web front-end for the user interface, with servlets and JSPs.
SOAP is more of an alternative to this web front-end than a competing
implementation technology. As opposed to the web front-end for users working
through browsers, SOAP gives an more general purpose interface for other types
of programs to use.
SOAP cannot replace RMI for use with EJBs for several reasons, including the
lack of state in SOAP. It may still make sense to supply a SOAP interface to
selected parts of your J2EE/EJB system, though. An example might be an ecommerce
system which provides a SOAP interface for checking item pricing and
availability, order status, and shipment information.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
Aleksandar Milanovic wrote:
> Hm, that's basically my dilemma. I am interested in:
>
> * scalability (more in data volume per user than the number of users, which
> might rise to thousands)
> * security (authentication, authorization)
> * extensibility
> * portability
> * ease of use/development
> * data integrity (there may be many clients writing to the same data object
> at the same time, but most updates will be actually inserting new data)
>
> The combination of SOAP and SSL addresses security. It is not clear to me
> how scaleable SOAP solutions are. Obviously, they are extensible and
> portable, and easy to develop.
> Data integrity may not be an important factor since most access will consist
> of reads and inserts.
>
> I need to make a decision very soon. Any advice would be appreciated.
>
> thx
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:40 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> We have identified the J2EE features that we believe add to the scalability
> and robustness of our architecture without disproportional increases in
> performance, maintenance and complexity.
>
> regards,
>
> Matthew.
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 29 March 2001 01:05
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Do you mean that you will use partial, less sophisticated, J2EE
> implementations or that you will use only some J2EE features such as RMI and
> JMSG?
>
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:10 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Hey guys - we have been discussing the very same thing here... So far, we
> have been very impressed with SOAP... once we got past some install issues
> with Apache SOAP, we were able to do some fairly hefty load testing on our
> development platform - I should point out that this is over Gigabit
> Ethernet...
>
> The bottleneck is the EJBs not the weight of the SOAP messages. We are very
> unlikely to go fully J2EE - it seems to make far more sense to use the bits
> that you need rather than restrict yourself. Somewhere between "super
> servlets" and J2EE.
>
> Regards,
>
> Matthew.
>
> ' Never use technology for the sake of technology. '
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 28 March 2001 19:33
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
> with SOAP. However, it's not clear to me if J2EE's super-high-scale features
> depend somehow on the use of RMI. This is important, because the main
> components of this distributed system should communicate among themselves
> using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
> used for interoperability.
> So the question is, can SOAP replace RMI for intercomponent communication on
> J2EE?
>
> thx
> Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
Re: SOAP vs. J2EE
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
The discussion of SOAP and J2EE as some form of competitors seems to miss the
point. SOAP is designed for request-response operations with no state,
essentially RPC to anonymous services (*not* to objects, despite the name, since
objects generally imply state). These services are basically the equivalent of
calls to stateless session beans, in J2EE/EJB terms.
J2EE/EJB is an architecture for building scalable distributed applications. It
generally uses a web front-end for the user interface, with servlets and JSPs.
SOAP is more of an alternative to this web front-end than a competing
implementation technology. As opposed to the web front-end for users working
through browsers, SOAP gives an more general purpose interface for other types
of programs to use.
SOAP cannot replace RMI for use with EJBs for several reasons, including the
lack of state in SOAP. It may still make sense to supply a SOAP interface to
selected parts of your J2EE/EJB system, though. An example might be an ecommerce
system which provides a SOAP interface for checking item pricing and
availability, order status, and shipment information.
- Dennis
Dennis M. Sosnoski
Sosnoski Software Solutions, Inc.
http://www.sosnoski.com
Aleksandar Milanovic wrote:
> Hm, that's basically my dilemma. I am interested in:
>
> * scalability (more in data volume per user than the number of users, which
> might rise to thousands)
> * security (authentication, authorization)
> * extensibility
> * portability
> * ease of use/development
> * data integrity (there may be many clients writing to the same data object
> at the same time, but most updates will be actually inserting new data)
>
> The combination of SOAP and SSL addresses security. It is not clear to me
> how scaleable SOAP solutions are. Obviously, they are extensible and
> portable, and easy to develop.
> Data integrity may not be an important factor since most access will consist
> of reads and inserts.
>
> I need to make a decision very soon. Any advice would be appreciated.
>
> thx
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:40 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> We have identified the J2EE features that we believe add to the scalability
> and robustness of our architecture without disproportional increases in
> performance, maintenance and complexity.
>
> regards,
>
> Matthew.
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 29 March 2001 01:05
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Do you mean that you will use partial, less sophisticated, J2EE
> implementations or that you will use only some J2EE features such as RMI and
> JMSG?
>
> Alex
>
> -----Original Message-----
> From: Mathew Clark [mailto:matt@genicomsystems.com]
> Sent: Wednesday, March 28, 2001 4:10 PM
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Hey guys - we have been discussing the very same thing here... So far, we
> have been very impressed with SOAP... once we got past some install issues
> with Apache SOAP, we were able to do some fairly hefty load testing on our
> development platform - I should point out that this is over Gigabit
> Ethernet...
>
> The bottleneck is the EJBs not the weight of the SOAP messages. We are very
> unlikely to go fully J2EE - it seems to make far more sense to use the bits
> that you need rather than restrict yourself. Somewhere between "super
> servlets" and J2EE.
>
> Regards,
>
> Matthew.
>
> ' Never use technology for the sake of technology. '
>
> -----Original Message-----
> From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
> Sent: 28 March 2001 19:33
> To: soap-user@xml.apache.org
> Subject: RE: SOAP vs. J2EE
>
> Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
> with SOAP. However, it's not clear to me if J2EE's super-high-scale features
> depend somehow on the use of RMI. This is important, because the main
> components of this distributed system should communicate among themselves
> using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
> used for interoperability.
> So the question is, can SOAP replace RMI for intercomponent communication on
> J2EE?
>
> thx
> Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Hm, that's basically my dilemma. I am interested in:
* scalability (more in data volume per user than the number of users, which
might rise to thousands)
* security (authentication, authorization)
* extensibility
* portability
* ease of use/development
* data integrity (there may be many clients writing to the same data object
at the same time, but most updates will be actually inserting new data)
The combination of SOAP and SSL addresses security. It is not clear to me
how scaleable SOAP solutions are. Obviously, they are extensible and
portable, and easy to develop.
Data integrity may not be an important factor since most access will consist
of reads and inserts.
I need to make a decision very soon. Any advice would be appreciated.
thx
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:40 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
We have identified the J2EE features that we believe add to the scalability
and robustness of our architecture without disproportional increases in
performance, maintenance and complexity.
regards,
Matthew.
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 29 March 2001 01:05
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Do you mean that you will use partial, less sophisticated, J2EE
implementations or that you will use only some J2EE features such as RMI and
JMSG?
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Hm, that's basically my dilemma. I am interested in:
* scalability (more in data volume per user than the number of users, which
might rise to thousands)
* security (authentication, authorization)
* extensibility
* portability
* ease of use/development
* data integrity (there may be many clients writing to the same data object
at the same time, but most updates will be actually inserting new data)
The combination of SOAP and SSL addresses security. It is not clear to me
how scaleable SOAP solutions are. Obviously, they are extensible and
portable, and easy to develop.
Data integrity may not be an important factor since most access will consist
of reads and inserts.
I need to make a decision very soon. Any advice would be appreciated.
thx
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:40 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
We have identified the J2EE features that we believe add to the scalability
and robustness of our architecture without disproportional increases in
performance, maintenance and complexity.
regards,
Matthew.
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 29 March 2001 01:05
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Do you mean that you will use partial, less sophisticated, J2EE
implementations or that you will use only some J2EE features such as RMI and
JMSG?
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by Mathew Clark <ma...@genicomsystems.com>.
We have identified the J2EE features that we believe add to the scalability
and robustness of our architecture without disproportional increases in
performance, maintenance and complexity.
regards,
Matthew.
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 29 March 2001 01:05
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Do you mean that you will use partial, less sophisticated, J2EE
implementations or that you will use only some J2EE features such as RMI and
JMSG?
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Mathew Clark <ma...@genicomsystems.com>.
We have identified the J2EE features that we believe add to the scalability
and robustness of our architecture without disproportional increases in
performance, maintenance and complexity.
regards,
Matthew.
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 29 March 2001 01:05
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Do you mean that you will use partial, less sophisticated, J2EE
implementations or that you will use only some J2EE features such as RMI and
JMSG?
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Do you mean that you will use partial, less sophisticated, J2EE
implementations or that you will use only some J2EE features such as RMI and
JMSG?
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Do you mean that you will use partial, less sophisticated, J2EE
implementations or that you will use only some J2EE features such as RMI and
JMSG?
Alex
-----Original Message-----
From: Mathew Clark [mailto:matt@genicomsystems.com]
Sent: Wednesday, March 28, 2001 4:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Mathew Clark <ma...@genicomsystems.com>.
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by Mathew Clark <ma...@genicomsystems.com>.
Hey guys - we have been discussing the very same thing here... So far, we
have been very impressed with SOAP... once we got past some install issues
with Apache SOAP, we were able to do some fairly hefty load testing on our
development platform - I should point out that this is over Gigabit
Ethernet...
The bottleneck is the EJBs not the weight of the SOAP messages. We are very
unlikely to go fully J2EE - it seems to make far more sense to use the bits
that you need rather than restrict yourself. Somewhere between "super
servlets" and J2EE.
Regards,
Matthew.
' Never use technology for the sake of technology. '
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: 28 March 2001 19:33
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org
RE: SOAP vs. J2EE
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Thx for the reply. I was indeed contemplating the use of J2EE in conjunction
with SOAP. However, it's not clear to me if J2EE's super-high-scale features
depend somehow on the use of RMI. This is important, because the main
components of this distributed system should communicate among themselves
using SOAP (rather than RMI). RMI and maybe CORBA and DCOM would probably be
used for interoperability.
So the question is, can SOAP replace RMI for intercomponent communication on
J2EE?
thx
Alex
-----Original Message-----
From: Anne Thomas Manes [mailto:atm@sun.com]
Sent: Tuesday, March 27, 2001 6:10 PM
To: soap-user@xml.apache.org
Subject: RE: SOAP vs. J2EE
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Anne Thomas Manes <at...@sun.com>.
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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: SOAP vs. J2EE
Posted by Anne Thomas Manes <at...@sun.com>.
It's not a question of one versus the other. Since you need a cross platform
solution, I'd recommend that you use Java. So the answer is: use both SOAP
and J2EE.
SOAP is simply an XML messaging protocol. The code that implements the SOAP
service has to run somewhere -- for example, in a J2EE application server.
Most Java-based SOAP implementations are based on J2EE (Apache, IBM, Cape
Clear, etc.)
The question you want to ask yourself is what type of an application server
do you need. Will a JSP/servlet engine suffice? Or do you need a full-blown
EJB-based application server.
Both servlet and EJB application servers manage resources for you, such as
database connection pooling, session management, and some degree of load
balancing. JSP/servlet engines are great for moderate-sized applications,
but they often don't provide super-high-scale features such as
multithreading, sophisticated load balancing, and bullet-proof fault
tolerance. An EJB application server provides these services as well as
automatic transaction management, state management, security, and
(optionally) persistence management.
Anne
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Tuesday, March 27, 2001 4:45 PM
To: Soap-User
Subject: SOAP vs. J2EE
Hi SOAPers,
I have to make a decision whether to use J2EE or SOAP for a distributed
software system. I have more knowledge about SOAP than J2EE, but the
principles of the latter are known to me. Still, I am having hard time
picking the favourite technology.
For example, J2EE facilitates transaction control, which may be useful, but
it's not obvious to me whether this is so useful as to make it mandatory.
The software system in question is XML-centric, but may also deal with
non-XML data (e.g. images, voice), which will be somehow encoded in XML
(probably Base64). It will accept updates from distributed clients and will
communicate with other systems via an unspecified protocol (CORBA, RMI or
something else, maybe even SOAP). SOAP, if used, would serve for traffic
between the server and the clients.
It is expected that most of the time this system will have low traffic
volume, but occasionally it will increase sharply, and then, more than one
client will want to read and update data belonging to the same "object".
Scalability is potentially a factor. The system will most likely have dozens
or hundreds of clients, but the choice of technology should not restrict
this number from growing to thousands (more than that is very unlikely).
Data integrity is perhaps a less important factor because most data updates
will consist of inserting new data (appending) rather than modifying the
existing.
The system should be cross-platform, easy to develop and extensible.
Performance is of secondary priority.
Any opinions are welcome.
thx
Alex
---------------------------------------------------------------------
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