Details
-
Type:
Improvement Request
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 5.0.1
-
Component/s: Configuration, Consumer mode, Monitoring (Business), Provider mode
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Description |
The Petals BC SOAP must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming SOAP request contains the header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing'. * its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined at service consumer level or component configuration level. |
The Petals BC SOAP must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming SOAP request contains the SOAP header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing'. * its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined at service consumer level or component configuration level. The new SOAP header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing' should appear in the service contract |
| Description |
The Petals BC SOAP must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming SOAP request contains the SOAP header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing'. * its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined at service consumer level or component configuration level. The new SOAP header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing' should appear in the service contract |
The Petals BC SOAP must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming SOAP request contains the HTTP header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing'. * its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined at service consumer level or component configuration level. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.1.0 [ 10867 ] | |
| Resolution | Fixed [ 1 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Description |
The Petals BC SOAP must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if an incoming SOAP request contains the HTTP header '{http://petals.ow2.org/components/soap/version-4}activate-flow-tracing'. * its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level. * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined at service consumer level or component configuration level. |
The Petals BC SOAP must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover: * if an incoming SOAP request contains the HTTP header 'org.ow2.petals.monitoring.activate-flow-tracing', its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level, * if an incoming SOAP request contains the JMS property 'org.ow2.petals.monitoring.activate-flow-tracing', its boolean value is used to overload the flow tracing activation state defined at service consumer level or component configuration level, * the flow tracing activation is propagated to the service provider invoked according to the flow tracing activation propagation defined at service consumer level or component configuration level. |
| Link | This issue depends on PETALSBCSOAP-220 [ PETALSBCSOAP-220 ] |
| Fix Version/s | 5.2.0 [ 11109 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
Support of MONIT trace filtering on provider and HTTP consumer sides added in trunk with unit tests. As the unit tests cover all combinations of flow tracing configuration, a dedicated integration test is not needed.