Bug 990110 - Spring and Camel are missing in business central and/or eap6 distribution
Spring and Camel are missing in business central and/or eap6 distribution
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Build and Assembly (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 6.0.0
Assigned To: Julian Coleman
Marek Baluch
: TestBlocker
Depends On:
  Show dependency treegraph
Reported: 2013-07-30 08:09 EDT by Ivo Bek
Modified: 2013-07-31 16:18 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 16:18:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ivo Bek 2013-07-30 08:09:57 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):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 2 Rajesh Rajasekaran 2013-07-31 16:18:14 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.