Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 4.0.3
-
Fix Version/s: 4.0.3
-
Component/s: None
-
Security Level: Public
-
- Environment:
- os: all
Issue Links
| Duplicate | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Resolve the target operation and MEP in Consumes mode | Resolve the target operation and MEP in consume mode |
| Priority | Blocker [ 1 ] | |
| Description | The component must support operation and MEP resolution in 2 ways in Consumes mode. -If the operation/MEP is set in the Consumes section of the SU JBI descriptor, use it directly. -If not, try to resolve the operation/MEP from the WSDL and EASYWSDL, at the deployment time, and cache the data. At an incoming message process, resolve the operation with the SOAPAction, or with the method signature...and use the operation/MEP cache. | The component must support operation and MEP resolution in 2 ways in consume mode. -If the operation/MEP is set in the Consumes section of the SU JBI descriptor, use it directly. -If not, try to resolve the operation/MEP from the WSDL and EASYWSDL, at the deployment time, and cache the data. At an incoming message process, resolve the operation with the SOAPAction, or with the method signature...and use the operation/MEP cache. |
| Link |
This issue duplicates |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
