This content has been marked as final.
Show 2 replies
-
1. Re: InitialContext binding unexpected behavior after hot deploy ...
hoang_to May 20, 2013 12:02 PM (in response to tonyweb)It seems to me that once you redeploy the portlet, the class loader of portlet application is reassigned (to a new instance of WebAppClassLoader) AND your JNDI factory class is available in a .jar under WEB-INF/lib, so the JNDI naming is recreated.
If i were you, i would put a breakpoint at line 240 of InitialContext (in JDK code) to see what is JNDI factory class in use. Then, check if .jar containing that class exists in both tomcat/lib and WEB-INF/lib. If it is the case, let's remove the one under WEB-INF/lib
-
2. Re: InitialContext binding unexpected behavior after hot deploy ...
tonyweb Jun 4, 2013 3:54 AM (in response to hoang_to)Thank you for looking into it.
I'll try to do what you suggested (I never "debugged" JDK code) and see if I can understand what's happening.
Regards,
Antonio