Anyone have any hints on these questions?
dgoodine wrote:
>
> 1. It seems that alot of people start with the JSR181 service unit and
> HTTP since it's a bit simpler model, but there's very little
> discussion/documentation/demos for implementing your services in a Service
> Engine. I'd prefer the latter, since it allows better abstraction (you
> can build abstract classes for all the Endpoint, Component, etc.,
> requiring minimal coding for new engines and allowing common
> functionality). It also seems a little more natural to the JBI spec to
> expose services directly to the NMR rather than burying them inside
> another component.
>
It this really the best practice?
I believe it is, but I'm dealing with the same question. We have created
SE's that are used by our SAs/SUs. Whenever I try to expose some
functionality through WebServices, the only solution I find is using
JSR181... This only leads to a POJO inside a component, without using JBI.
To achieve that, why not use a standalone WS in a J2EE server? Shouldn't
ServiceMix take advantage of JBI in some way, and already created SEs?
--
View this message in context:
http://www.nabble.com/A-few-questions-about-SEs-and-WSDL-tf3053641s12049.html#a8728254
Sent from the ServiceMix - User mailing list archive at Nabble.com.
