Hide Forgot
Description of problem: When adding new core bridge, user is required to set one of discovery group or static connector. When the user tries to create new bridge in Profile -> Messaging -> Connections _> Bridges in console, but doesn't add any of those two attributes, the error message shown in notification message is: Internal Server Error { "outcome" => "failed", "failure-description" => "JBAS014704: '' is an invalid value for parameter discovery-group-name. Values must have a minimum length of 1 characters", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } However, when trying to create such bridge in CLI, user gets more descriptive error: { "outcome" => "failed", "failure-description" => "JBAS011651: Operation must include parameter static-connectors or parameter discovery-group-name", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } Please show a same error in notification message in console. The one it's showing now might lead the user to think she needs to set discovery-group-name attribute. Version-Release number of selected component (if applicable): EAP 6.2.0.ER5
Can you post the CLI command(s) you used? That may be helpful for the console guys as they can compare the operations they generate to the working CLI equivalents.
In CLI client: cd /subsystem=messaging/hornetq-server=default/bridge ./test-bridge:add(queue-name=test.Queue,forwarding-address=forward.Queue) results in { "outcome" => "failed", "failure-description" => "JBAS011651: Operation must include parameter static-connectors or parameter discovery-group-name", "rolled-back" => true }
I have improved the form validation to respect the constraints.
Should this still remain in POST state?
Form validation is still not present in DR12. Only the error message displayed in notification center now matches the one from CLI. Without the validation, it is kind of a half-baked fix.