Hide Forgot
Affects: Release Notes project_key: JBEPP
Affects: Removed: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Added: [Release Notes]
Link: Added: This issue depends GTNWSRP-232
Release Notes Docs Status: Added: Needs More Info Release Notes Text: Added: Release Notes need more information about the issue and how it was fixed.
Release Notes Docs Status: Removed: Needs More Info Added: Documented as Resolved Issue Release Notes Text: Removed: Release Notes need more information about the issue and how it was fixed. Added: A NullPointerException was raised when the producer didn't require consumers to register with it due to improper checks in the JCR persistence of the producer configuration. This has been addressed by properly checking that a RegistrationPolicy is provided before attempting to work with it.
Release Notes Text: Removed: A NullPointerException was raised when the producer didn't require consumers to register with it due to improper checks in the JCR persistence of the producer configuration. This has been addressed by properly checking that a RegistrationPolicy is provided before attempting to work with it. Added: Due to improper checks in the JCR persistence of the WSRP producer configuration, the producer didn't require consumers to register with it. This produced a NullPointerException. The issue has been addressed in this release by properly checking that a RegistrationPolicy is provided before attempting to work with it.
Release Notes Text: Removed: Due to improper checks in the JCR persistence of the WSRP producer configuration, the producer didn't require consumers to register with it. This produced a NullPointerException. The issue has been addressed in this release by properly checking that a RegistrationPolicy is provided before attempting to work with it. Added: Due to improper checks in the JCR persistence of the WSRP producer configuration, a NullPointerException was thrown when the producer didn't require consumers to register with it. The issue has been addressed in this release by properly checking that a RegistrationPolicy is provided before attempting to work with it.