I guess, you want your bpel engine to call external services, right ? I do not think it is forbidden, though i do think this is not the best way, because you will loose the possibility to have several interactions (transformation or whatever) before reaching the final service and the external services won't be able to be called by other SEs. This is against the "spirit" of the spec, but not against the programming model.
The "right" way to do that is to have a BC between the SE and the external service. At the end, if your BPEL engine receives http requests and sends http requests, you do really need jbi ;) Cheers, Guillaume Nodet On 3/2/06, Charles Souillard <[EMAIL PROTECTED]> wrote: > > Hi all, > > I have a very important question about the JBI compliance. I hope > someone would know the answer ! > > I read many times the JBI spec and I never found the answer... > In fact, it is written : (4.3 High-Level Achitecture) : > The JBI environment exists within a single JVM. External to the JBI > environment are service consumers and providers. > > My question is : > Is it forbidden to install a SE acting like a proxy to a remote > application ? > It means, the SE will execute the exposed service by calling (via rmi or > http for example) a remote java application. > In this case, the JBI container and the java app (provider) are running > in different JVMs. > > JVM > 1 > JVM 2 > ____________________________________________________ > | > __________ | > __________________________ > | | > | | > | | > | | SE | > ---------------------------------------------------> | Java app > providing the | > | > |__________| | > | business service | > | __________________________________________ > | |___________________________| > | | > | | > | | JBI container | > | > | |_________________________________________| | > | > | > | > | > |____________________________________________________| > > My feeling is that nothing in the spec is telling that this case is wrong. > > Thanks a lot for your advices. > > Charles >
