[
https://issues.apache.org/activemq/browse/CAMEL-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1276.
--------------------------------
Fix Version/s: 2.3.0
(was: Future)
Resolution: Duplicate
> Add validation feature to Camel framework in order to validate data
> linked/binded to POJO
> -----------------------------------------------------------------------------------------
>
> Key: CAMEL-1276
> URL: https://issues.apache.org/activemq/browse/CAMEL-1276
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Charles Moulliard
> Assignee: Christian Mueller
> Fix For: 2.3.0
>
>
> With bindy, jaxb and probably other binding frameworks, it would be
> interesting to have a validate option in camel that we can use in combination
> with by example unmarshall
> from(uri)
> .unmarshall(bindy or jaxb or ArtixDS or ...)
> .validate(nonblocking)
> .to())
> The purpose of this feature will be to :
> - verify mandatory fields/properties of POJO,
> - apply business rules on the data received,
> - ...
> Ex, in an csv record, the order n° field is mandatory and the order type must
> be equal to N for new order, C for cancel or U for update.
> Remarks :
> - One parameter that we can provide to the validation method could be "block
> or non block" to generate an array list of errors without creating an error
> in the application. This option is interesting because it allows to keep the
> POJO and save though Hibernate/Ibatis the data in the database and to send a
> report to the issuer to inform it about the errors found in the CSV,
> fixedlength, ... files received
> - Spring 3 who will provide validation support through annotation could be a
> good candidate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
