David, I missed your original question, so am not sure if this solves your problem. Attached is a doc I wrote a while back on how to get a Struts based app to work on iWS 4.1. HTH, Stan David Lineberger wrote: > There is no web.xml file in the iPlanet configuration. I see this often, > but it seems to be a Tomcat or Orien Server requirement. iPlanet requires > the tld file be in a jar. The tld,( actually the jar file with the tld > inside ) is referenced from the jsp, and the jar is put in the jvm classpath > in the WebServer. This is all iPlanet requires, and it worked before I put > the Struts action mapping in place. > Any other ideas? Anyone? > > > -----Original Message----- > > From: Robert Quillen [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 19, 2000 5:21 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: Custom Tags and iPlanet Web Server 4.1 > > > > > > I noticed that you didn't mention the tld configuration bit > > that goes in the > > web application's web.xml file. That might be the problem. > > > > It should look something like this: > > > > <taglib> > > <taglib-uri>/WEB-INF/struts.tld</taglib-uri> > > > > <taglib-location>/WEB-INF/lib/struts.tld</taglib-location> > > </taglib> > > > > I'm not sure what the location should be when the tld is in a > > jar file. I > > imagine that you just give the path for the jar, but you > > should look up the > > specifics. > > > > Robert Quillen > >
Running Struts on iWs 4.1 ------------------------- Here are the issues I ran into while moving my struts based application from Tomcat(supports WebApps and WAR) to iWS 4.1 (does -NOT- support Webapps and WAR). Webapps and WAR will be supported in iWS 5.0,as mentioned in iWS5.0 roadmap. 1. Classpath issues. This is pretty straightforward. Since there is no notion of WEB-INF/lib and WEB-INF/classes the classpath has to be explicitly set in $SERVER_ROOT/config/jvm12.conf 2. Context relative paths All URL's should be visible from the document root. In my case I just created a symbolic link from $DOCROOT/myapp to webapps/myapp. 3. Extension mapping The config file $SERVER_ROOT/config/rules.properties has a similar mechanism as in web.xml. I have this in my rules.properties which forwards all urls ending with "do" to the servlet whose logical name is action. #### @.*[.]do$=action #### 4. ActionServlet configuration The config file $SERVER_ROOT/config/servlets.properties has similar mechanism as in web.xml My entry looks like this: servlet.action.classpath=/u/stansa/jakarta/tomcat/webapps/userx-ui/WEB-INF/lib/struts.jar servlet.action.code=org.apache.struts.action.ActionServlet servlet.action.initArgs=application=UIResources,config=/u/stansa/jakarta/tomcat/webapps/userx-ui/WEB-INF/action.xml, debug=2, detail=2 A detailed document on enabling servlets/jsps on iWS is at this location: http://docs.iplanet.com/docs/manuals/enterprise/41/servlets/contents.htm 5. Custom tag libraries There is no notion of a "uri" as available in web.xml to give logical names to the actual location of the tld files. Instead, the jar file containing the tag implementions follow this structure. struts.jar -META-INF -taglib.tld -org -apache - etc The tld file has to exist under the jar file's META-INF directory. The name has to of the form taglib.jar. The jar file is referenced in the jsp. For example: ##### <%@ taglib uri="/WEB-INF/lib/struts.jar" prefix="struts" %> <struts:iterate id ..... #####
