See comments inline
Charles Souillard wrote:
Guillaume,
in the page you send me, I can read that BPEL pxe is a standard JBI SE.
But the BPEL example is using a servicemix.xml file at SM start.
These are not incompatible : bootstraping ServiceMix is usally done with
a servicemix.xml configuration file. You can also
do that programmatically.
Registering a component into ServiceMix can also be done using different
ways :
* programmatically using the JBIContainer
* using the servicemix.xml configuration file, defining a ActivationSpec
* using standard JBI compliant installer
When you use a standard JBI package, you have more than one option to
actually install the component:
* using jmx
* using an ant task
* using the hot deployment installation directory
All these ways can co-exist on the same ServiceMix container.
So to answer your question, the BPEL sample is bootsrapped using a xml
configuration file but the BPEL engine
is put in the hot deployment installation directory.
I read int the web page :
"Standard JBI components can be deployed at run-time and accept
service units deployments. These components may in addition provide a
way to configure them in a lightweight fashion."
It means that if I want to create a SE for my engine, I will have to
provide "a way" to use my app with the lightweight fashion ?
Notice the "in addition" statement : we provide a way to use these
components using am xml configuration file. If you prefer / need
to use the jbi standard way, you can do so ...
If you want to provide such a configuration for your jbi component, you
are free to do so : this is just spring wiring stuff. We also
use xbean (www.xbean.org) to simplify the spring xml configuration file.
SM does not accept standard JBI SE ?
See previous comments.
Of course it does, but this is not the only way we offer. You may
choose the one that best suits your needs.
Is there a way to use pxe BPEL through the standard JBI API ?
This is the only way to use PXE BPEL engine AFAIK.
Please elaborate ...
The servicemix.xml is subscribing pxe BPEL component "myComponent" to
the jms destination.
I think JBI is giving an API to di that dynamically instead of using
such a xml file mandatory at the servicemix start.
Do you have an example with a dynami subscription ?
You can use the servicemix-lwcontainer or the servicemix-jms components
to deploy a service unit that will create
an endpoint dynamically to be used as a proxy to the bpel process.
You should even bundles the two service units (bpel process and binding
endpoint) withing the same service assembly.
The BPEL example is running with no fault but I am not sure that the
response is the expected one. How can I be sure from that ?
I get on return the same xml message that the one written in message.soap
The BPEL example is not complete and some parts are missing.
Please raise a JIRA :)
Cheers,
Guillaume Nodet
Perhaps I have to perform some configuration about pxe ?
Where can I find guidesline ?
Thanks,
Regards,
Charles
Guillaume Nodet wrote:
See http://servicemix.org/Component+Matrix?refresh=1
This doc is not finished yet, but it may be useful for you.
Charles Souillard wrote:
Hello,
I am trying to understand SM architecture and all of these
components. I have listed those I think are currently integrated in SM.
Can you please for each of them tell me if :
1) it is in the current release (svn)
2) if it ia a BC or a SE
3) if it is a standard JBI component or if it is a light-weight
component or anything else...
Thank you very much for your answers.It will help me a lot going in
depth with SM.
Regards,
Charles
Charles Souillard wrote:
Sorry there were two mistakes :
Rob,
I am trying to write a document to summaryse all components
included in SM.
I made a mix between the architecture document and the list given
on servicemix.org on the left link column named "components".
Can you confirm that all these components exists (available inSM)
and if the type I have affected them is the right one ?
BPEL => SE
Cache => SE
Drools => SE
Email => BC
File => ?
FTP => ?
Groovy => SE
HTTP => BC
Jabber => BC
JAX WS => *JCA* => BC
JMS => BC
Quartz => SE
Reflection => ?
RSS => ?
SAAJ => BC
Scripting => SE
servicemix-lwcontainer => SE
Validation => SE
XFire => BC
XPath Router => SE
XSLT => SE
XSQL => SE
VFS => ?
WSIF => BC
ActiveMQ => BC
*JavaMail* => BC Is it the same component as Email ?
ActiveSOAP => BC
Mule => SE
Agila => SE
WS Notification => SE
WS Reliable Messaging => SE
WS Eventing => SE
WS Ressource Properties => SE
WS Distributed Management => SE
Charles Souillard wrote:
Rob,
I am trying to write a document to summaryse all components
included in SM.
I made a mix between the architecture document and the list given
on servicemix.org on the left link column named "components".
Can you confirm that all these components exists (available inSM)
and if the type I have affected them is the right one ?
BPEL => SE
Cache => SE
Drools => SE
Email => BC
File => ?
FTP => ?
Groovy => SE
HTTP => BC
Jabber => BC
JAX WS => JCA => BC
JMS => BC
Quartz => SE
Reflection => ?
RSS => ?
SAAJ => BC
Scripting => SE
servicemix-lwcontainer => SE
Validation => SE
XFire => BC
XPath Router => SE
XSLT => SE
XSQL => SE
VFS => ?
WSIF => BC
ActiveMQ => BC
Email => BC Is it the same component as Email ?
ActiveSOAP => BC
Mule => SE
Agila => SE
WS Notification => SE
WS Reliable Messaging => SE
WS Eventing => SE
WS Ressource Properties => SE
WS Distributed Management => SE
Do I have forbidden any other component ?
Thanks for your help
Regards,
Charles
Rob Davies wrote:
Hi charles,
just checked the diagram again - it's a bad diagram :) - there
really shouldn't be a separate components box. ActiveMQ and
ActiveSOAP are bindings, the rest are services.
We are going through a process of improving the documentation -
this is a page we'll be visiting soon.
cheers,
Rob
On 4 Jan 2006, at 08:18, Charles Souillard wrote:
Hi Rob,
I know both Binding Components (BC) and Service Engine (SE) are
"components".
BCs provide connectivity to services external to a JBI
environement.
SEs provide business logic and transformation services to other
components.
What I want to know is if
- "bindings" described here :
/http://servicemix.org/Architecture/ are BCs
- "services" and "components" described here : /http://
servicemix.org/Architecture/ are SEs
Are you saying that "services" and "components" are both SE and
BC ?
Regards,
Charles
Rob Davies wrote:
Hi Charles,
A Component is the generic name for bindings and services.
Internally, the container sees little difference between the
two - though the distinction is important for users of JBI
cheers,
Rob
On 4 Jan 2006, at 07:55, Charles Souillard wrote:
Hi all,
I am trying to understand in depth exactly what servicemix
is composed of.
In the architecture (http://servicemix.org/Architecture) I
can see that servicemix is a JBI container (of course) but I
am a bit confused about the difference between "bindings",
"services", "components".
My knowledge of JBI let me think that :
- "bindings" are JBI Binding Components
- "services" and "components" are JBI Service Engines
Is that right ?
Thanks,
Cheers
Charles
