Closed glassfishrobot closed 15 years ago
@glassfishrobot Commented franz1180 said: Created an attachment (id=1551) EAR Application containing an RA and a MDB (with source) - validate() method in activiationspec bean (TestActivationSpec.java) always throws exception but isn't called as described in the issue
@glassfishrobot Commented franz1180 said: Created an attachment (id=1552) Possible patch for ConnectorMessageBeanClient - always call validate method and rethrow exception if validation fails
@glassfishrobot Commented franz1180 said: changed assignment
@glassfishrobot Commented @h2002044 said: In Connectors 1.6 Specification, the recommended mode of requesting for validation is to use bean validation annotations in the activation spec Java Bean.
This is supported in GlassFish v3.
Resolving the request as fixed.
@glassfishrobot Commented File: ConnectorMessageBeanClient.java Attached By: franz1180
@glassfishrobot Commented File: testConnectorEAR.ear Attached By: franz1180
@glassfishrobot Commented Was assigned to h2002044
@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-5140
@glassfishrobot Commented Reported by franz1180
@glassfishrobot Commented Marked as fixed on Monday, November 16th 2009, 6:35:08 pm
When deploying a message driven bean for an inbound resource adapter, the method validate() of the corresponding ActivationSpec Bean isn't called. Although marked as optional by the jca spec, this feature is quite useful because the config properties can be checked during mdb deployment - and in case of error an exception with an useful message can be thrown. And if validation fails, the (invalid) mdb isn't registered as an endpoint in the corresponding resource adapter.
Environment
Operating System: All Platform: All
Affected Versions
[9.1peur1]