-
Sub-task
-
Resolution: Done
-
Optional
-
None
-
None
When creating or updating a ConnectionFactory component, when the jndi-name prop is not specified, I get:
DEPLOYMENTS IN ERROR:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/notx-ds.xml" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null text
when the rar-name prop is not specified, I get:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/xxx-ds.xml" is in error due to the following reason(s): java.lang.IllegalArgumentException: Null name
and when the connection-definition prop is not specified, I get:
Deployment "vfsfile:/C:/opt/jboss-5.1.0.CR1-SNAPSHOT/server/default/deploy/xxx-ds.xml" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: ConnectionDefinition 'null' not found in rar 'null'
which tells me all three of these props are required, so prop.isMandatory() should return true, but it currently returns false. It should return true for both CF templates and existing CF components.
Not directly related to management, but all three of the above error messages could also be significantly improved, e.g.:
The "jndi-name" property was not specified for connection factory "FooBar" - this property is required.
The "rar-name" property was not specified for connection factory "FooBar" - this property is required.
The "connection-definition" property was not specified for connection factory "FooBar" - this property is required.
- relates to
-
JBAS-5261 Check each DS and Destinations properties are accurate/needed
- Closed