|
|
SOAP stacks and XML marshalingWe now use JAX-WS and JAXB 2.0 to create POJOs and interfaces for the common WS-* specifications like WS-Addressing, WS-Notification, WS-ReliableMessaging, WS-Resourceframework etc. The only downside of this approach is its Java 5 specific. We hope with a tool like Retroweaver can one day allow JAX-WS and JAXB 2.0 based code to work perfectly on Java 1.4 JVMs. Using JAXB / JAX-WS we create the POJOs and service interfaces for the common WS-* interfaces (WS-Notification, WS-Addressing, WS-Resource*). Here is the javadoc. WS-NotificationThe WS-Notification support is currently implemented as POJOs which can then either be called directly inside an application or can be wrapped up as a remote web service using a JAX-WS compliant SOAP stack. We are currently using the JAX WS RI which is licensed under CDDL. We have interfaces for the WS-Notification services in the org. servicemix.wspojo.notification package. e.g. here's the NotificationConsumer interface. These interfaces are generated by JAX-WS from the WSDLs and only depend on Java 5 and the JAX-WS and JAXB 2.0 annotations. Then our implementation of these WS-Notification interfaces are here. Using WS-NotificationTo be able to publish or subscribe you need either a NotificationConsumer or NotificationBroker. The current implementation of both is the ActiveMQNotificationBroker - which will create a connection to an ActiveMQ broker (by default making an embedded broker inside the same JVM]. You can then publish WS-Notification messages as follows... Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20
You can perform a subscription as follows Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20
Runtime dependenciesApart from the usual ActiveMQ and ServiceMix dependencies this implementation of WS-Notification depends on
|
