The current AMQP 1.0 JMS client's JNDI provider implementation seems a
little odd to me (i.e.
org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory ).
It forces you to specify a provider url[1], but treats that as a file,
making it hard (impossible) to get at a properties file packaged as a
resource.
Is this intentional? Am I missing or misunderstanding something?
--Gordon.
[1] The equivalent implementation from the old JMS client (i.e. 0-10
etc), from which this seems to have been copied, doesn't require a
provider url, so though it has the same treatment of the 'url' as a file
path, it doesn't require you to use that (you can load via
getResourceAsStream() or equivalent).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
