I think its important to keep in mind that we don't support containers, we support specifications. In practice, we sometimes make allowances for certain containers, so long as they are not too far out of spec. In the past, Struts has generated a few service packs to bring containers into compliance. (Yeah! Us!)
The problem I sense here is that some containers might misbehave on this point. We don't have a testing lab with WebSphere and iPlanet and WebLogic and JRun and SilverStream and so on all lined up in row where we can run these tests. We have to rely on the kindness of strangers to try this for us and report back. IMHO, this does not seem like not the time to mess about with the classloaders (and we all know how much we ~love~ classloaders). Unless someone is going to tag this as a "showstopper" for the 1.1 release, I'd say we can mark this LATER and move on. -Ted. -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
