Hide Forgot
Date of First Response: 2009-06-16 02:27:59 project_key: SOA Requesting creation of a best practices guide for integration of Seam, jBPM, and ESB in SOA-P. Specifically, this should address using Seam's built-in jBPM annotations to invoke jBPM business processes that use EsbActionHandler to invoke ESB services. There are people that do not believe that we should support "deep" integration between the three components (Seam, jBPM, ESB) - in other words there needs to be a loosely coupled interface between Seam and SOA functionality. Pragmatically, this means that if Seam is going to be tightly integrated with a jBPM process, then that jBPM process should be loosely coupled to ESB services and invoke them through gateways, not through the ESBActionHandler (deep integration). Or if a jBPM process is going to be tightly coupled with ESB Services (ESBActionHandler), then Seam should interact with that jBPM process in a loosely coupled way (ESB service gateway providing access to the jBPM process, not via annotations). This is not necessarily my opinion, but I do think we need to have official documentation of our official best practices - whatever we decide they are.
Link: Added: This issue is related to SOA-1273
How about we use following paragraph to the 'best practices guide': " In the combination of Seam, jBPM and ESB. it is recommended that users are using seam to interact with jBPM in a loosely coupled way, which is through the ESB service gateway, not the jBPM integration annotation directly. In this way, we can see the ESB as the session facade, which provides the entries to all of other service, not only jBPM process, but also other services, like web service, ESB service etc. Now you might feel that seam and jBPM integration is very simple and handy, but it is not a best practice since this is a component-to-component invocation, it is fine that we've just had two components, but if we have more than two components, especially we are having the ESB into play, it is not recommended to do so. In the SOA world, as the ESB term indicates, it is the bus, other components (here like seam, jBPM) should talk to the ESB, not the end-to-end way, which will lead to the spaghetti issue if we have many components, and most of them are talking to component directly. In the future release, we will introduce a set of annotation for seam and ESB integration, it will make users a lot easier to do the seam and ESB integration, just as simple as what we have for the jBPM integration. Before we've had these annotations, it is recommended to do the integration pragmatically that uses the gateway as channel to talk to ESB, and then invoke the target service. (like jBPM process service etc). "
I need two things if this is going to make it into the docs: 1 - Is this content agreed upon as appropriate/correct ? 2 - Where should it be included in the docs?
Hi Darrin, I don't think the content is ready yet.. also not sure if we will include it for SOA 5.
If this content can't be provided by the end of week, 11th December, then we should move it to 5.0.1
moving to 5.0.1
I need some idea of what is happening with this JIRA so I can schedule docs work for 5.0.1 What volume of material? e.g. how many pages, diagrams, etc When will draft material be ready ?
afaik, I don't think we will have this material in 5.0.1 timeframe.
To be verified in the docs for 4.3 CP05