Hi,
I want to share some of my thoughts, maybe they help us each other to understand more :-)
I see 2 ways of using Apache Hermes. The first one is as a part of the Apache WS-Stack (addressing, apollo,wss4j....). So that other Web Services can be build ontop of it. Thats the way i think the HP guys Ian and Sal are looking at it. They need Hermes for MUWS, which is a spec thats uses WS-RF and WS-N. This way of using Hermes i would call WS-Spec. centric.
The second way one can use Hermes is as a Message Oriented Middleware (MoM). Which is my view of how to use Hermes. That means, that through an API (which is org.apache.ws.pubsub) all the WS stuff is encapsulated and the user which want to send or get notifications is doing it via NotificationConsumer/NotificationProducer Interfaces(the user does not see the communication that is done with the JettyAxisServer).
So applications can be build that use WS-N or WS-E for communication. I call this User-centric
These two ways to use Hermes can exist side by side.
For the first one WSDL2Java is needed, that produces templates, to fill in business logic. Thats the way it is working right now. If you specify the subscribe operation in your wsdl, the Hermes templates are generated.
I think in practise the second approach would be used more often by the users.
any agreement, disagreement, discussion?
thx stefan
-- My place : http://user.cs.tu-berlin.de/~lischke
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
