Just have a look at the JettyModuleBuilder, I think that the problem is the mapping validation occurs before merging the default servlet, And, it should have the same behavior for both standalone web application or the one embedded in the ear. The reason why Tomcat 6 work is due to the merging work is delegated to Tomcat. We might also need to double check both Tomcat and Jetty integration in Geronimo 3.0, as now all the merging work is done in Geronimo codes now. I opened a JIRA to track this https://issues.apache.org/jira/browse/GERONIMO-5882
2011/3/30 Thomas Neidhart <[email protected]> > On 03/29/2011 05:25 PM, Kevan Miller wrote: > > > I don't know our builder code well enough to have a simple answer for > you... > > > > You must be using Geronimo 2.2.x, correct? > > Dear Kevan, > > Yes, sorry that I forgot to mention it in my first post, actually i am > using geronimo 2.2.1 with jetty as servlet container. > > > It would be interesting to know what happens on a Geronimo 2.2.x Tomcat > server assembly. Also, have you tried with Geronimo 2.1.x? > > No I have not tried it yet with another configuration, but at least one > guy seemed to have the same problem, and he switched successfully to > tomcat: > > > http://apache-geronimo.328035.n3.nabble.com/Default-servlet-not-found-td337761.html > > I have not yet looked into the TomcatModuleBuilder yet, but I guess the > default servlet may be defined there, while in the JettyModuleBuilder > its an empty set. > > Cheers, > > Thomas > -- Ivan
