-
2. Re: Spring JNDI lookup using proxyInterface fails
timfox Aug 14, 2007 10:56 AM (in response to nkhadakk)After some thought, I consider this a bug in Spring - Spring is making assumptions about how a particular JMS provider implements its destinations which is incorrect.
I suggest pinging the Spring team and lodging a bug report with them. -
3. Re: Spring JNDI lookup using proxyInterface fails
nkhadakk Aug 14, 2007 11:27 AM (in response to nkhadakk)I can ping the Spring team regarding this.... though this is more of a convienience feature of spring jndi binding that enables 'lazy-binding'. Only requisite for using this feature is that an Interface be available to create a 'proxy' with for lookup.
This feature of spring would appear to work only with providers who provide the (provider specific)Destination interface?
I don't hold much chance for the Spring team to work on this issue...time to look into roll my own 'lazy binding' i guess.
Appreciate your time. -
4. Re: Spring JNDI lookup using proxyInterface fails
timfox Aug 16, 2007 3:11 AM (in response to nkhadakk)Most AOP frameworks have the ability to make class proxies as well as interface proxies.
You could suggest to the Spring team they use such a framework then they wouldn't have this limitation.