>If they > are specifying the JNDI names for all their beans in some vendor > deployment descriptors they shouldn't have to do all that work again > in our descriptors, we should just support at least that part of > their vendor's descriptors. If they aren't supplying the names in > descriptors and are relying upon some vendor default, we can > implement the same default. Good idea. Maybe some migration paths from, for example Websphere 5.1 and 6 ? Hope I understood correctly when you said "support a vendors descriptor". -- Karan Singh Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name Ted Kirby
- Re: Default JNDI Name Ted Kirby
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Karan Malhi
- Re: Default JNDI Name David Blevins
- Re: Default JNDI Name Dain Sundstrom
- Re: Default JNDI Name Karan Malhi
