Re: Java client bindings on JBoss ESB

[Jeffrey Bride <jb...@redhat.com>]

Hi,
  I see the change was made to
PropertiesFileInitialContextFactory.java ..... thank you !

I apologize for the confusion .... but as it turns out ..... in some
situations I can't pass the file name with a '/' prefix .... in which
case the existing code in trunk will not find the properties file.  The
following is an unfortunate hack to get the QPid client to work under
all circumstances in the JBoss ESB :

try {
          p.load(this.getClass().getResourceAsStream(file));
} catch(NullPointerException npe) {
         _logger.info("trying again with file = /"+file);
         p.load(this.getClass().getResourceAsStream("/"+file));
}

I can elaborate further on the issue I'm experiencing between JBoss ESB
and QPid if interested.

Arnaud :  I will continue to take your advice into consideration.  I do
currently like the idea of consolidating qpid specific properties in
this file.  I reference this file from several different places in my
application.   

thanks again!  jeff


On Tue, 2009-02-10 at 20:07 +0000, Robert Greig wrote:

> 2009/2/9 Arnaud Simon <as...@redhat.com>:
> 
> > Another solution would be for you to use the property
> > java.naming.provider./url /to specify the path to a qpid property file.
> 
> My advice for this is for people to think about where they want to
> consolidate configuration.
> 
> If you have a configuration file for this purpose, is there any reason
> to introduce yet another file for people to maintain?
> 
> The properties file is useful for scenarios where you don't have
> anywhere else that is useful to store than information or where for
> some reason (e.g. delegation of responsibility) you want to separate
> it from other configuration.
> 
> RG

-- 
Jeffrey Bride
RedHat / JBoss
303-523-7885