|
From: Patrick Y. <kc...@ce...> - 2003-07-09 13:01:23
|
Agreed with JNDI contexts. That's why I propose to use a Properties =
object. My proposal is: we provide hook for a client to specify which =
server side delivery hook to be used. To specify, the client specify the =
class name of the hook, together with a Properties object for =
configuration like JNDI contexts. Hermes can then initialize the class =
using the Properties object in server side. When an incoming message =
arrives, the onMessage() method of that class will be called to delivery =
the message.
This proposal is what I called "customized server side delivery".
Regards, -Patrick
----- Original Message -----=20
From: Ronald van Kuijk=20
To: 'ebx...@li...'=20
Sent: Wednesday, July 09, 2003 07:00 PM
Subject: RE: [ebxmlms-develop] Hermes 1.0 (JMS delivery)
don't use url's but an alternative method (jndi contexts?) The can be =
used for filesystem etc. as well.
A client registers which jndi name has to be used by the server to =
lookup the component for delivery.
Ronald
-----Oorspronkelijk bericht-----
Van: Patrick Yee [mailto:kc...@ce...]
Verzonden: woensdag 9 juli 2003 12:30
Aan: ebx...@li...
Onderwerp: Re: [ebxmlms-develop] Hermes 1.0 (JMS delivery)
How to specify the JMS destination in the form of a URL, if the =
single server-side mode only provides an interface for specifying a URL?
Regards, -Patrick
Mayne, Peter wrote:
(Server side delivery mode)
- Shouldn't all (server side ones) implement the same interface =
(onMessage()?) and File and URL just be some default included =
implementations? (Isn't this also a 'hook'?)
I was thinking exactly the same thing. :-) There should be only =
one server-side mode, with a trusted repository and URL redirect =
provided as implementations of that mode. If "customised mode" isn't =
good enough to implement trusted repository or URL redirect, then it =
probably isn't good enough for much else either.
I'd vote for a jms implementation to and volunteer to implement =
one
I've done a JMS implementation, which is what sparked some of the =
discussion about delivery modes. However, including it with Hermes may =
be problematic: since JMS isn't part of the standard JRE, it would not =
be possible to build Hermes unless you had a JMS implementation. Maybe =
we could have a "contributions" library.
------------------------------------------------------- This SF.Net =
email sponsored by: Parasoft Error proof Web apps, automate testing & =
more. Download & eval WebKing and get a free book. =
www.parasoft.com/bulletproofapps =
_______________________________________________ ebxmlms-develop mailing =
list ebx...@li... =
https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop |