[ openjms-Feature Requests-668839 ] Unify JNDI initial context factories

Feature Requests item #668839, was opened at 2003-01-16 01:29
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474139&aid=668839&group_id=54559

Category: enhancement
Group: None
>Status: Closed
Priority: 5
Submitted By: Tim Anderson (tanderson)
>Assigned to: Tim Anderson (tanderson)
Summary: Unify JNDI initial context factories

Initial Comment:
Currently, there is an InitialContextFactory  
implementation for each of the supported 
connectors:
. RmiJndiInitialContextFactory
. IpcJndiInitialContextFactory
. IntravmJndiInitialContextFactory
. HttpJndiInitialContextFactory
. SslHttpJndiInitialContextFactory

These can be proxied by a single 
InitialContextFactory (tentatively, 
org.exolab.jms.jndi.InitialContextFactory) which 
delegates to the appropriate implementation based 
on the Context.PROVIDER_URL.

Changes required:
. update examples to use the new 
InitialContextFactory implementation
. update documentation





----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2003-04-03 15:58

Message:
Logged In: YES 
user_id=557161

Changes applied in CVS.

Will be available in the 0.7.5 release.

----------------------------------------------------------------------

Comment By: Tim Anderson (tanderson)
Date: 2003-01-16 01:31

Message:
Logged In: YES 
user_id=557161

Also note that the existing InitialContextFactory 
implementations can be deprecated once  
http://sourceforge.net/tracker/index.php?
func=detail&aid=668835&group_id=54559&atid=47413
9 is implemented

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474139&aid=668839&group_id=54559