On Wednesday 26 May 2004 10:13 am, Emile wrote: > Thanks for the info, problem is that something goes seriously wrong with my > root path if I put mmbase into a sub-folder and specify that as it's own > context. I haven't specified the root context (in server.xml), didn't think > I'd have to, but I can't see my index.html - browser comes up blank. If I > do specify empty path "." docbase, I get the following: > java.lang.NoClassDefFoundError: org.mmbase.bridge.jsp.taglib.CloudTag > > Any ideas? maybe first try to run tomcat standalone
we run apache 2.0 as a front proxy so the only rules that we have are proxy/reverse proxy rules in that case you are to configure tomcat to it know it's behind a front-proxy (in order to generate good redirects) still getting blank pages with tomcat sometimes happens if you use servername based virtual hosting and have not well configured the servers The error org.mmbase.bridge.jsp.taglib.CloudTag might point to a missing mmbase-taglib.jar maybe first try a very simple.jsp page <%= new java.util.Date() %> > > Regards > Emile > > > ----- Original Message ----- > From: "Kees Jongenburger" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, May 24, 2004 1:52 AM > Subject: RE: new problems > > > it's not common to put such sites in the ~/public_html directory > since this also is the place apache looks for > > Last time i checked there was one (logic) limitation that is that > your webapp name must be the same as your url path > incomming request to apache > > http://yourserver/mymmbase > | > - | ----------------------------- > | apache > | > - | -tomcat connector------------ > | tomcat > | > \-your webapp named mymmbase > > you can choose to move mmbase-webapp to $TOMCAT_HOME/webapps/mymmbase > or edit $TOMCAT_HOME/conf/server.xml to point a app with name mymmbase > to your prefered directory (In that case the directory may have a > different name. like public_html) > > the public_html of the mymmbase directory > must have this structure > > mymmbase/WEB-INF/web.xml > /myjsp.jsp > > p.s. jsp's are not like cgi's. tomcat is still a server and apache only > forward/proxies the request. still using public_html may be a good > choice if you want the resources to be served by apache and not by > tomcat) > > > > > -- Kees Jongenburger Mediapark C101 Hilversum +31 (0)35 6772910
