Re: [ebxmlms-develop] JMS URI proposal

[Ronald v. K. <rv...@ab...>]

Mayne, Peter wrote:

> Yes, I'm using a Hashtable as you've described, and reading the 
> properties from a properties file. See how ignorant I am? :-)
>
:-) Happens to me all the time on various subjects

> Aah yes, using javax.naming.Context is using JNDI, but it seems to be 
> a fairly primitive use. After all, I'm explicitly providing a context 
> factory to the Context, so I don't see any difference between the 
> questions in your first paragraph and your second paragraph.
>
It is 'primitive use' but sufficient in many situations. The main 
difference is indeed the fact that you are providing your own context 
factory.

> I can't see the mapping between a jms: URI and the use of the 
> Hashtable, but again, that's just my ignorance. If it works, who am I 
> to complain? :-)
>
All the properties you put in the hashtable could be put in a jms: URI 
and the server will internally parse that and put it in a hashtable etc....

I've seen that apache has a fairly complete implementation of this in 
axis, complete with full url protocol handlers. I'll see if that is in 
some way usable instead of duplicating all the work the've done. 
Especially since in to other projects i'm working on 
(http://chiba.sf.net and http://www.jbpm.org) I run into the same challenge.

http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/components/jms/
http://cvs.apache.org/viewcvs.cgi/ws-axis/java/src/org/apache/axis/transport/jms/

Ronald

> PJDM
> -- 
> Peter Mayne
> Technology Consultant
> Spherion Technology Solutions
> Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
> T: 61 2 62689727  F: 61 2 62689777
>
> > -----Original Message-----
> > From: Ronald van Kuijk [mailto:rv...@ab...]
> > Sent: Thursday, 29 January 2004 8:50 AM
> > To: ebx...@li...
> > Subject: RE: [ebxmlms-develop] JMS URI proposal
> >
> >
> > You mean you use JMS from within a servlet engine without
> > using JNDI? Do
> > you explicitely provide a connectionfactory class, etc?
> >
> > By context and provider url, you mean the java.naming.factory.initial
> > and  java.naming.provider.url property? Or something with a
> > hashtable,
> > properties like
> >
> >     Hashtable properties = new Hashtable();
> >     properties.put(Context.INITIAL_CONTEXT_FACTORY, 
> > "<initial-context-factory-class>");
> >     properties.put(Context.PROVIDER_URL, "<provider-url>");
> >     Context context = new InitialContext(properties);
> >
> > or something like this in a propety file.
> >
> > In these cases, you *are* using JNDI.
>
>The information contained in this email and any attachments to it:
>
>(a) may be confidential and if you are not the intended recipient, any interference with, 
>use, disclosure or copying of this material is unauthorised and prohibited; and
>
>(b) may contain personal information of the recipient and/or the sender as defined 
>under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to 
>collect, hold and use such information and any personal information contained in a 
>response to this email, for any reasonable purpose in the ordinary course of 
>Spherion's 
>business, including forwarding this email internally or disclosing it to a third party. All 
>personal information collected by Spherion will be handled in accordance with 
>Spherion's Privacy Policy. If you have received this email in error, please notify the 
>sender and delete it.
>
>(c) you agree not to employ or arrange employment for any candidate(s) supplied in 
>this email and any attachments without first entering into a contractual agreement with 
>Spherion. You further agree not to divulge any information contained in this document 
>to any person(s) or entities without the express permission of Spherion.
>
>
>  
>