-- Hello, > I have add the module jserv to Apache, and configure it with gsp. > It works :). > > But I have to configure the ApacheJServ with the jsp 1.0 of sun. > Does anybody have made it ? > Does it work ? I just made a first try to get this working and did have at least partial success. Please note, that I'm not very experienced with this combination (is anyone?) so I probably made some foolish mistakes. > In the zone.properties ,with for example the alias jsp, what 's the=20 > name of the objet I have to set after servlet.jsp.code=3D ?=20 Just as mentioned in the README coming with jswdk1_0ea: servlet.jsp.code=com.sun.jsp.runtime.JspServlet > In the server.jar of the distribution of jsp1.0 , there's the object=20 > com/sun/jsp/compiler/Main.class > is it this objet I have to set in servlet.jsp.code ? No, the above mentioned line works for me quite fine. > How could I configure ( default.cfg ) the jsp with the module Jserv ? > With the "initArgs" property ?=20 I think, you can safely ignore this file. It's only used by the webserver-classes that supplement the jswdk-distribution. It's not needed if you intend to use ApacheJserv. The most relevant parameter I could find is 'scratchDir'. It should point to a directory where the compiled JSP-pages should be stored. It must be writable for the user id ApacheJserv is using. Something like servlet.jsp.initArgs=scratchdir=<path to dir for comiled jsp-pages> in your zone-property file should work. I did however observe some problems, when using this combination: - Some of the examples coming with the jswdk don't work. But this might be because they're using features of the Servlet 2.1 API. I haven't looked at this further. - Strangely I couldn't get this to work when ApacheJserv is started automatically by the webserver, only when I started the java-interpreter manually. So setting "ApJServManual on" in jserv.conf, providing a proper CLASSPATH for java, starting the java-interpreter with "org.apache.jserv.JServ" manually and running the webserver did work for me. I'm not sure why it only worked this way. I got the impression that the "wrapper.classpath" directives in jserv.properties didn't reach the jswdk-classes. - In JSP-pages I often need to fully qualify the class-name. Maybe this is related to the classpath-problems I encountered. But this might be my fault, after fiddling around with it for too long :-). It may work better for you. My configuration: Linux with apache 1.3.4 JDK 1.1.7 ApacheJserv 1.0beta5 (does the final 1.0 make a difference with this combination?) Kind regards, Stephan -- Stephan Krings Tel/Fax: +49 30 61709314 Blue Orange Internetservice Stefan Merath Torstr. 109 10119 Berlin/Germany [EMAIL PROTECTED] -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] READ THE FAQ!!!! <http://java.apache.org/faq/> Archives and Other: <http://java.apache.org/main/mail.html/> Problems?: [EMAIL PROTECTED]
