Julian Gosnell wrote: > Your just putting the onus on the Application > programmer to work around shortcomings in the Server - > I think.....
Yes, the app programmer needs to know about classloading. Bug.. feature.. bug... feature.. which'll it be? :-) On the one hand, having straight-forward classloading makes it easy to develop a web-app. On the other hand, having sandboxed classloading makes the web-app more self-contained and portable, since they don't rely on the surrounding server to provide any of its classes. > If you do that with Jetty in stand-alone, compliant > mode - you will simply find you are using the JAXP > that Jetty loaded to parse it's own XML configuration > files. Yes, the straight-forward mode. > If you do it with Jetty in embedded, non-compliant > mode - you will find isAssignableFrom() fails. Yup, the more complex and portable case. /Rickard -- Rickard Öberg _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
