Red Hat Bugzilla – Bug 990110
Spring and Camel are missing in business central and/or eap6 distribution
Last modified: 2013-07-31 16:18:14 EDT
Description of problem:
Business central nor the EAP6 distribution don't contain any libraries for Spring, Camel, and the dependencies. There is also a question whether business central should have set the Spring, Camel integration in default.
I would consider to add the integration libraries as a modules, so when a user needs them, he or she will put them to jboss-deployment-structure.xml and will do the necessary changes such as set the spring-beans.xml, and web.xml, etc.
In this time the integration libraries are available only in the deployable distribution (jboss-bpms-engine).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Kris - I don't think that including them in business central is necessary (at least, that's not how I envisioned it). When you are writing an application using spring or camel respectively, you can use these jars to get (better) integration, meaning make it easy to get access to a (local) session and nicer integration. If they want to access business-central, they can already I believe, by calling the remote (REST / JMS) api.
It would make sense to distribute these as part of the bin zip (so people can pick them up), and probably also include them in a module (so people writing an app on top of eap6 can reuse the module).
Mark - Right now the "business central" server has no need for spring/camel/blueprints. It can author a kjar that can be provisioned into fabric, that has hose dependencies though - as this is the recommended way to do stateless rule services.
So they'll need to be part of the platform, just not on the actual BRMS/BPMS server installation.