Details
-
Type:
Task
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 5.5.0
-
Fix Version/s: 5.6.0
-
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 | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Link |
This issue blocks |
| Description |
Instead of managing default value in the code of the CDK, we should exploit the default value from the CDK JBI Schema.
JAXB will do that for us, check for constraints such as > 0 or >=0. This means: - making all needed CDK configuration required in a component jbi.xml - adding positive or zero type for parameters The following changes to the parameters will also be made: - acceptor-stop-max-wait > 0 (instead of just a long) This only concerns parameters for acceptor, processor and monitoring sampling rate. |
Instead of managing default value in the code of the CDK, we should exploit the default value from the CDK JBI Schema.
JAXB will do that for us, check for constraints such as > 0 or >=0. It means deployment will fail in case of errors in the jbi.xml of a component (before the default values were used), see This means: - making all needed CDK configuration required in a component jbi.xml - adding positive or zero type for parameters The following changes to the parameters will also be made: - acceptor-stop-max-wait > 0 (instead of just a long) This only concerns parameters for acceptor, processor and monitoring sampling rate. |
| Description |
Instead of managing default value in the code of the CDK, we should exploit the default value from the CDK JBI Schema.
JAXB will do that for us, check for constraints such as > 0 or >=0. It means deployment will fail in case of errors in the jbi.xml of a component (before the default values were used), see This means: - making all needed CDK configuration required in a component jbi.xml - adding positive or zero type for parameters The following changes to the parameters will also be made: - acceptor-stop-max-wait > 0 (instead of just a long) This only concerns parameters for acceptor, processor and monitoring sampling rate. |
Instead of managing default value in the code of the CDK, we should exploit the default value from the CDK JBI Schema.
JAXB will do that for us, check for constraints such as > 0 or >=0. It means deployment will fail in case of errors in the jbi.xml of a component (before the default values were used), see This means: - making all needed CDK configuration required in a component jbi.xml - adding positive or zero type for parameters The following changes to the parameters will also be made: - acceptor-stop-max-wait > 0 (instead of just a long) This only concerns parameters for acceptor, processor, properties file and monitoring sampling rate. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.6.0 [ 10611 ] | |
| Resolution | Fixed [ 1 ] |
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
