Sylvain Wallez wrote:
Such a strong shielding can have some drawbacks, however : if a class is given by the servlet engine (e.g. a JNDI context) and the same class exists in the webapp libs (e.g. in jndi.jar), then you're very likely to get a ClassCastException. This is likely to happen mostly with standard APIs, and the solution is then to remove the offending library from your WEB-INF/lib.
Good explanation. Any chance it will get into Javadoc and wiki? ;-)
Can you give a little more info on when we could expect this to happen? Why would I get a class cast exception?
Geoff
