Hi there,
JBI was actually my secound though after my JMS plan failed. I must
admit, I just looked at it very briefly and, I don't know why, I
thought JBI was designed to be an integration part for different
applications in different environments (using XML/Web Services), not
as a internal orchestrator...
Right now I am going to look at it once again. If what you said about
JBI, being the kind of thing I need and looking for, I will be really
happy :)
Regards,
Witold Szczerba
2008/2/19, glassfish_at_javadesktop.org <glassfish_at_javadesktop.org>:
> Have you considered looking at the JBI facilities within GF? Because that's essentially what you're talking about, and JBI will do what you want.
>
> Simply, you set up a BPEL script (which is an XML artifact) to lay out your processes, and the JBI engine uses that script to move internal messages around through interested Session Beans. It will do this using a single transaction, and can use the local calling semantics for internal Session Beans.
>
> In the end, you use the BPEL designer tools in NetBeans to maintain the XML file, so that keeps this kind of orchestration away from actual Java code.
>
> It might suit your needs, or at least be a platform to better explore what you may want without having to invent any new wheels on your own.
> [Message sent by forum member 'whartung' (whartung)]
>
> http://forums.java.net/jive/thread.jspa?messageID=259720
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>