Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.2.4
-
Fix Version/s: None
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Minor [ 4 ] | |
| Assignee | Victor NOËL [ vnoel ] |
| Project | Petals SE Camel [ 10230 ] | Petals Distribution [ 10180 ] |
| Key | PETALSSECAMEL-3 | PETALSDISTRIB-119 |
| Issue Type | Improvement Request [ 4 ] | New Feature [ 2 ] |
| Affects Version/s | 4.2.4 [ 10517 ] | |
| Affects Version/s | No version [ 10530 ] |
| Summary | Introduce a Camel BC for external Camel Context | Create a BC Camel |
| Description |
A Camel BC could be responsible of providing interaction between a Camel Context executed externally from Petals (not from within the SE).
Two cases are to be taken into account: - Camel producer (calling Petals from Camel, through a Consumes deployed in the BC). - Camel consumer (calling Camel from Petals, through a Provides deployed in the BC). An alternative case could be imagined: - Providing and Consuming Petals services directly based on the URI used in the Camel consumer and producers (a bit like the RMI SE in a way). |
Petals ESB and Camel are integrated in a way where camel is used as service orchestration through the Petals SE Camel ( Petals ESB and Camel can be integrated also in a way where: # an external JVM running camel invoke Petals services running on the Petals JVM. Here, Camel is a service consumer, # a Camel route running on an external JVM is exposed as Petals service into the Petals JVM. Here, Camel is a service provider. Camel must be extended with an URI implementation associated to Petals services, and Petals ESB must be extended with the Petals BC Camel. The communication between both Camel and Petals BC Camel remains to be defined, perhaps on the model of the Petals SE RMI. |
| Description |
Petals ESB and Camel are integrated in a way where camel is used as service orchestration through the Petals SE Camel ( Petals ESB and Camel can be integrated also in a way where: # an external JVM running camel invoke Petals services running on the Petals JVM. Here, Camel is a service consumer, # a Camel route running on an external JVM is exposed as Petals service into the Petals JVM. Here, Camel is a service provider. Camel must be extended with an URI implementation associated to Petals services, and Petals ESB must be extended with the Petals BC Camel. The communication between both Camel and Petals BC Camel remains to be defined, perhaps on the model of the Petals SE RMI. |
Petals ESB and Camel are integrated in a way where camel is used as service orchestration through the Petals SE Camel ( Petals ESB and Camel can be integrated also in a way where: # an external JVM running camel invoke Petals services running on the Petals JVM. Here, Camel is a service consumer, # a Camel route running on an external JVM is exposed as Petals service into the Petals JVM. Here, Camel is a service provider. Camel must be extended with an URI implementation associated to Petals services, and Petals ESB must be extended with the Petals BC Camel. The communication between both Camel and Petals BC Camel remains to be defined, perhaps on the model of the Petals SE RMI. |
| Link | This issue blocks PETALSSECAMEL-9 [ PETALSSECAMEL-9 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
This one shouldn't be too hard as the current implementation of the SE properly separate the Camel component from the Petals component with clean interfaces.