Hi artem,
I can't understand what you mean? Specification of ws-eventing doesn't constrain notifications because (specification said) any message MAY be a notification.
But in real world producer and receiver have to constrain the message accepted. And it is an application level know how.
Of course should be convenient if the application engine does it for you, but I can't understand where is the value of that: immagine you (event producer) define a schema for notification and a subscriber implement a different schema. When you will send notifications you will construct the xml according to your schema (the only one you are supposed to know). You are asking the engine to validate notifications according to the receiver schema, but in that case (schema defined by the ws-eventing source != schema implemented by the event sink) it wold (always) fail and throws an exption. You can check the exception, but anyway you can't recover it. Isn't it?
Instead the validation of the producer defined schema could be conveniently made by the engine, but it can be done also at application level as Alessio already said.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980948#3980948
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980948