On 7/7/06, Philip Dodds <[EMAIL PROTECTED]> wrote:
Davide,
There isn't a fixed answer to that question, you could write your database
persistent steps as a Service Engine, however but nature the service engine
tends to be a service that can be deployed more than once with a different
configuration.
Yes, Philip is correct. Service Engines (SE) are containers that are
deployed for use by many services. The traditional example of a SE is
a BPEL engine. The BPEL engine is not an application but a container
that will execute business logic that is defined using the BPEL
language.
As a point of comparison, consider an EJB container in the J2EE world
where the EJB container accepts deployments of EJBs. The BPEL engine
is very similar to the EJB container. As a developer writing
applications, you wouldn't write your own EJB container, ergo you
wouldn't write your own SE. The only time that you need to consider
creating your own SE is if you have a some type of container that you
want to communicate *locally* with the NMR.
If you want to implement business logic and persistence you might want to
look at the JSR-181 Service Engine, since this allows you to write simple
POJO's to do the work you want without worrying about JBI message
exchanges.
This is a good suggestion as well. Just remember that the JSR181
component's job is to generate WSDL on-the-fly to expose the POJOs as
web services. If you don't need to expose your POJOs as web services,
you might want to consider just writing POJOs using the ServiceMix
client API:
http://servicemix.org/site/client-api.html
The URL above contains some documentation on the use of the ServiceMix
client API from within POJOs. Here is another URL providing
information on this topic:
http://goopen.org/confluence/display/SM/POJO+support#POJOsupport-BeingevenmorePOJO
The thing I like about these example is that it's easier for
traditional Java software developers to understand because it's
actually writing code to develop an application vs. just developing
services and configuring them via a servicemix.xml file or bundling
them up as Service Assemblies.
Please let us know if you have any further questions. Explaining this
stuff helps to produce more content to help others understand it as
well.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://incubator.apache.org/activemq/
Apache ServiceMix - http://incubator.apache.org/servicemix/
Castor - http://castor.org/
