Page History

...

Going forward we believe JAXB 2.0 is the idea XSD <=> Java mapping layer and JAX-WS the ideal API for working with web services. So going forward all of our WS-* implementations will use JAX-WS for its POJO and service interface creation.

We've left the XMLBeans code around in case folks need to use it but we recommend you migrate to WS Notification instead. Hopefully we can figure out how to patch something like Retroweaver to turn Java 5 specific code into a 1.4 binary so that folks can use JAX-WS and JAXB 2.0 on Java 1.4 JVMs. Incidentally it was the Java 5 dependency of JAXB 2.0 and JAX-WS that led us down the path of XMLBeans.

...

You can then publish WS-Notification messages as follows...

...

...

You can perform a subscription as follows

...

...

Runtime dependencies

Apart from the usual ActiveMQ dependencies (either client side only or full server side dependencies depending on if you're using an embedded broker) the WS-Notification provider has the following dependencies

...