Details
Bug
Resolved
Blocker
-
- Environment:
- Windows XP
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Project | Petals-ESB-Container [ 10029 ] | Petals-CDK [ 10032 ] |
| Key | PETALSESBCONT-171 |
|
| Affects Version/s | 5.1.2 [ 10180 ] | |
| Affects Version/s | 3.1.3 [ 10252 ] |
| Summary | processInterceptors methode no longer exists in the ServiceUnitManager class | Unable to compute dynamically the provider service name |
| Description | The new method getServiceName was added to AbstractServiceUnitManager class to allaw the change of the service name. |
We have a specific binding component previously developped with CDK 4. Our BC needs to define dynamically the provider service name according to its associated resource. Several instances of the BC, connected to different instances of the same applicative resource, are running on Petals network. The service name is defined from the service name provided by the SU and a property value defined at the BC instance.
So, with the CDK 4, we used the method ServcieUnitManager.processProvidesNode(...) and ServcieUnitManager.processProvidesNodes(...) to compute the right service name. These methods are no more visible inthe CDK 5. They are defined as 'private' methods of AbstractServiceUnitManager. Please, add an extension point in CDK-5 to be able to redefine the provider service name. |
| Priority | Blocker [ 1 ] |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Component/s | runtime [ 10075 ] |
| Description |
We have a specific binding component previously developped with CDK 4. Our BC needs to define dynamically the provider service name according to its associated resource. Several instances of the BC, connected to different instances of the same applicative resource, are running on Petals network. The service name is defined from the service name provided by the SU and a property value defined at the BC instance.
So, with the CDK 4, we used the method ServcieUnitManager.processProvidesNode(...) and ServcieUnitManager.processProvidesNodes(...) to compute the right service name. These methods are no more visible inthe CDK 5. They are defined as 'private' methods of AbstractServiceUnitManager. Please, add an extension point in CDK-5 to be able to redefine the provider service name. |
We have a specific binding component previously developped with CDK 4. Our BC needs to define dynamically the provider service name according to its associated resource. Several instances of the BC, connected to different instances of the same applicative resource, are running on Petals network. The service name is defined from the service name provided by the SU and a property value defined at the BC instance.
So, with the CDK 4, we used the method {{ServcieUnitManager.processProvidesNode(...)}} and {{ServcieUnitManager.processProvidesNodes(...)}} to compute the right service name. These methods are no more visible inthe CDK 5. They are defined as 'private' methods of {{AbstractServiceUnitManager}}. Please, add an extension point in CDK-5 to be able to redefine the provider service name. |
| Attachment | patch.txt [ 10709 ] |
| Attachment | patch.txt [ 10709 ] |
| Attachment | patch.patch [ 10710 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.1.3 [ 10284 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 5.3.0 [ 10338 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |