-
1. Re: Event source deployment
thomas.diesler Dec 19, 2005 6:40 PM (in response to hbraun)Yes, the unified meta data model (UMDM) should have this property at the endpoint level, which the deployers should act upon
-
2. Re: Event source deployment
hbraun Dec 20, 2005 4:26 AM (in response to hbraun)I've created a Jira:
http://jira.jboss.org/jira/browse/JBWS-585 -
3. Re: Event source deployment
hbraun Jan 24, 2006 9:36 AM (in response to hbraun)The scenario described above makes it really painful and error-prone to deploy event sources:
A developer would have to create a custom WSDL that includes the standard eventing wsdl and schema. Add a standard jaxrpc-mapping, chose the default jboss SEI implementation wrap it up and deploy everything.
This would mean 99% redundancy between all event sources deployed on a server. The only difference would be the event source names and the notification schemas.
Opposed to that i decided to implement it the other way around:
A developer configures an event source name and notification schema. The actual endpoints are setup by the eventing implementation and the corresponding WSDL is generated dynamically.
Take a look at the example configuration:<!-- A subscription manager for WS-Eventing --> <mbean code="org.jboss.ws.eventing.mgmt.SubscriptionManager" name="jboss.ws.eventing:service=SubscriptionManager"> <attribute name="EventSourceConfig" serialDataType="jbxb"> <jbwse:config xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xmlns:jbwse="urn:jboss:eventsource-config:1.0" xs:schemaLocation="urn:jboss:eventsource-config:1.0 resource:eventsource-config_1_0.xsd"> <jbwse:eventsource name="WindReport"> <jbwse:schema> [CDATA[ <xs:schema targetNamespace="http://www.example.org/oceanwatch" elementFormDefault="qualified" blockDefault="#all" xmlns:xs='http://www.w3.org/2001/XMLSchema' > <xs:element name="WindReport"> <xs:complexType> <xs:sequence> <xs:element name="Date" type="xs:string"/> <xs:element name="Time" type="xs:string"/> <xs:element name="Speed" type="xs:string"/> <xs:element name="Location" type="xs:string"/> <xs:element name="County" type="xs:string"/> <xs:element name="State" type="xs:string"/> <xs:element name="Lat" type="xs:string"/> <xs:element name="Long" type="xs:string"/> <xs:element name="Comments" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> ]] </jbwse:schema> </jbwse:eventsource> </jbwse:config> </attribute> </mbean>
That's all that needs to done.
When the subscription manager starts up it registers an event source called 'WindReport' and does setup the endpoints.
Further explanations can be found here:
http://wiki.jboss.org/wiki/Wiki.jsp?page=WSEventing