I think artems suggestion is perfectly valid. The SubscriptionManager knows about the
schema and could actually validate the event messages. At least this was my original
intention. But as palin already realized, there's two things to be done:
The MetaDataBuilder needs to extract the schema (there might be a better format than
String) and populate the deployment info. This would make the schema available to the
event source instance.
In a second step, the message could be validated in SubscriptionManager.dispatch() before
handiong off to the background task.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980964#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...