Really, it will depend on other non-functional requirements you might have. One argument in favor of an app server exposing the ws is you won't probably need the remote interface for your slsbs. Mule can then proxy your services and add icing on top.
HTH,
Andrew
On Jul 2, 2009 10:27 AM, "Stijn Janssens" <mule.user.relay@...> wrote:
Hi,
Could someone elaborate on how best to use mule with web-services?
Basically, we have implemented several entity-centric service for storing business data. These services are implemented using EJB3 entity beans, persisted using JPA.
We would now like to expose these entity-centric services to be used by front-end applications and by more high-level task services.
What is the best way to do this?
Should we expose the EJB entities (POJOs) via a SLSB facade to Mule and let Mule map them to the canonical data format (XML) before exposing them as web-services or should we add a service layer to our entity services and expose them as web-services directly within the app server? And in that case, should we use Mule to proxy these services?
Thanks,
Stikkos
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
