Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 4.3.0-beta-1
-
Fix Version/s: 5.0.0-M1
-
Component/s: Components
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||||
|---|---|---|---|---|---|
|
|||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue depends on |
| Link |
This issue depends on |
| Link |
This issue depends on |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Priority | Minor [ 4 ] | |
| Description |
The SOAP and Mail BCs are able to interpret an undocumented property named com.ebmwebsourcing.wsstar.addressing that contains WS-Addressing properties following the WS-Addressing schema.
This property is actually never used and there is no reason to use it as it is incompatible with the agility assumed by SOA because it bounds an exchange to a given protocol. Furthermore, there is also a second property named "javax.jbi.messaging.protocol.headers" where some similar informations are stored and manipulated by the CDK. This one is used nowhere (not even by the SOAP BC). There is no reason to handle that in such a general way, and if needed, these properties could, in the last resort, be used by concerned BCs. |
The SOAP and Mail BCs are able to interpret an undocumented property named com.ebmwebsourcing.wsstar.addressing that contains WS-Addressing properties following the WS-Addressing schema.
This property is actually never used and there is no reason to use it as it is incompatible with the agility assumed by SOA because it bounds an exchange to a given protocol. Furthermore, there is also a second property named "javax.jbi.messaging.protocol.headers" where some similar informations are stored and manipulated by the CDK. This one is used nowhere (not even by the SOAP BC). There is no reason to handle that in such a general way, and if needed, these properties could, in the last resort, be used by concerned BCs. The JBI spec introduces this property and explicitly says that it should contain BC-specific information, and that this information should be defined in relation to javax.jbi.messaging.protocol.type, which was actually never used in our code. It would maybe make sense to introduce the filling of these properties by the BC in the future... Note: petals-sample-client manipulates "javax.jbi.messaging.protocol.headers" and even though no component interprets it, there is no reason to remove it as it makes sense for the future to be able to set such property. |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.0 [ 10412 ] | |
| Resolution | Fixed [ 1 ] |
| Link | This issue depends on PETALSSAMPCLIENT-6 [ PETALSSAMPCLIENT-6 ] |
| Link | This issue depends on PETALSSAMPCLIENT-6 [ PETALSSAMPCLIENT-6 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
