[
https://jira.jboss.org/browse/ARQ-168?page=com.atlassian.jira.plugin.syst...
]
Dan Allen commented on ARQ-168:
-------------------------------
I heed your concern, as we don't want to make things more difficult than they already
are. However, I think that this validation can occur on the client side, as Arquillian is
loading. Plus, it's just a syntactical check to make sure that values are reasonable.
The annotations themselves are harmless wherever they travel (though I don't think
container configurations are packaged anyway).
I should also mention that it's important for us to advocate Bean Validation :)
Use Bean Validation on container configuration properties
---------------------------------------------------------
Key: ARQ-168
URL:
https://jira.jboss.org/browse/ARQ-168
Project: Arquillian
Issue Type: Feature Request
Components: Configuration
Affects Versions: 1.0.0.Alpha2
Reporter: Dan Allen
Attachments: ARQ-168-patch.txt
The container needs to ensure that the user has supplied sane configuration values, or
else risk blowing up in weird and unpredictable ways. Rather than doing these laborious
checks manually (and possibly only partially), Bean Validation should be used to enforce
the values fall with a value range or adhere to a required syntax.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira