Stefan
1. In this situation, a normal practice would be to have ALL webservices
coming in or out of the organization go directly through the ESB.
This means that there is a single place to log and monitor all connections.
2. The ESB can automatically take the SOAP/HTTP and drop it in a JMS
Queue for you, simply by deploying a proxy - not code required. It might
make sense for the ESB to do some security validation at this point.
3. You can either publish a Spring service using WSAS and the Spring
support in WSAS or you can use the WSF/Spring library which embeds Axis2
into Spring. Both approaches can support SOAP/JMS and get the message
from the queue.
Paul
stlecho wrote:
Paul, Ruwan,
Thanks for the supplied information and answers to my questions.
I will try to describe a scenario and the way I understand the usage of ESB
and WSAS. Please feel free to correct and/or comment.
-Our application needs to contact webservices that are put at disposal by
our partners. For this, I could use ESB and define a proxy that connects to
the external webservice and handles transparantly the HTTPs connection and
WS-Security related aspects. I've been doing some prototyping and this
works.
-Our partners need to contact webservices that we put at disposal. For this,
I could use WSAS - or ESB that routes to WSAS ? - to host these webservices.
In our current implementation, the Axis2-based webservices server drops the
received SOAP Payload in a Queue with a Message Driven Bean that calls the
appropriate Business Service to process and persist the SOAP Payload.
For this, I could connect WSAS to ESB (or vice versa ?) that will host a
Queue and route the SOAP message to a Service "published" on the ESB. In our
case, the Business Service is based on Spring and that's where it's getting
confusing for me. How do I publish this Spring-based Business Service to the
ESB (with the aid of WSAS?) ?
Regards, Stefan.
Paul Fremantle-2 wrote:
Stefan
Great questions.
I have some difficulties in comparing WSAS & ESB:
-could/should they be used together ?
Yes. We have a lot of customers using both - especially the combination
of Data Services and ESB.
-is the one a kind of "superset" of the other one, i.e. is WSAS using ESB
or
vice-versa ?
Not really. Both are using Axis2, Axiom, Rampart, and other shared
components. There are some ways that we allow you to use them together
in the same JVM (for example it is possible to use Synapse as a module
inside WSAS) and we are looking at expanding those ways... keep your
eyes out later in the year!
-in which cases should I use WSAS and in which cases ESB ?
Use WSAS for hosting services, ESB for mediating, transforming, routing.
That is a simple example, but if you can give a clearer view of your
requirements we can help more. For example, if you gave a scenario, we
could split it into ESB and WSAS.
Regards
Paul
--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse
Office: +44 844 484 8143
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
--
Paul Fremantle
CTO and Co-Founder, WSO2
OASIS WS-RX TC Co-chair
VP, Apache Synapse
Office: +44 844 484 8143
Cell: +44 798 447 4618
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
_______________________________________________
Esb-java-user mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
