[jboss-dev] DefaultJndiBinder use of jndi from constructor

[Scott Stark]

Sorry, I meant I'll have the core jndi naming beans in *deployers*, not 
deploy.

Ales Justin wrote:
> I wouldn't put it in deploy/ atm,
> as we don't have JBDEPLOY-135 implemented yet.
>
> Which could potentially mean that some deployments
> installed before your jndi bean is deployed,
> would by-pass the "required" jndi deployer.
>
> Scott Stark wrote:
>   
>> Ok, I'll have the core jndi naming beans in deploy. Deployers that 
>> require a jndi service should have a dependency/demand on a 
>> NamingService alias or maybe even InitialContextProvider since any 
>> deployer making use of the jndi api during its lifecycle should have a 
>> dependency. I should create links from the JBAS-6948 issue to external 
>> deployer projects that will need dependencies declared. What is the weld 
>> jira?
>>