Jspell Installation in Sun Web Server
Hi,
We haven抰 been able to get JSpell work on our server. So far the instructions were to drop the JSpell war file (jspellhtml2k4.war) in the webapps directory and restart the webserver. After done this, we were only able to see in the directory just the war file. Following the instructions we wanted to test the software using the test.html file, since we were not able to see it, we used the unzip command to extract the files from the .war file. Using the ls command we got:
JSpell.jsp jspell.css jspellhtml2k4.war
JSpellHTML2k4.pdfjspell.jsjspellmodal.html
META-INFjspell_alt.css jspellpopup.html
WEB-INFjspell_proxy.aspproxy.js
blank.html jspell_proxy.phptest.html
Once done this, using the test.html we clicked on the Spell Check button and it didn抰 work (file not found error).
I went and looked and the paths in jspell.js and noticed that everything was pointing to jspellhtml2k4 directory which was never created (not in the instructions). I try changing the path to where our jspell files actually are but that didn抰 work either.
Are we missing any steps? Where is the jspellhtml2k4 directory created? Did we need to unzip the war files or not?
Has anyone installed JSPell on a sun server that could help us get this up and running. Apparently the instruction from Solutions Cafe are not complete.
Thanks!
[1395 byte] By [
alex_08] at [2007-11-26 10:43:19]
# 1
Have you looked at the webapps documentation?
http://docs.sun.com/app/docs/doc/819-6518
especially the section on deploying webapps?
http://docs.sun.com/app/docs/doc/819-6518/6n8hd7tej?a=view
I have found that often the web.xml file for an app that runs OK in other environments needs to be edited to appease SWS -- root elements and DTD/doctype declarations are usually all that requires special attention. Sun has docs on a sample config here:
http://docs.sun.com/app/docs/doc/819-6518/6n8hd7tev?a=view
Our typical web.xml start with
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
As for unpakcing the war files, you can deploy a webapp with 'wdeploy' (http://docs.sun.com/app/docs/doc/819-6518/6n8hd7ten?a=view) without unpacking it, but we've moved away from that. I find it easier to manually add a line like this to server.xml inside the <VS> element:
<WEBAPP uri="/Appname" path="/path/to/Appname" enabled="true"/>
where I've unpacked the warfile into /path/to/Appname such that web.xml is /path/to/Appname/WEB-INF/web.xml, etc.
With a default SWS config (i.e., one with the default J2EE functions/entries intact in the various config files), you can probably unpack the webapp to /path/to/Appname, edit server.xml, and stop+start SWS to get the app running.
To update/redeploy the app, we have a custom script that replaces /path/to/Appname and conditionally runs the 'reconfig' script for the SWS instance if there's a major change (vs. static content, JSPs, etc.).
More caveats: 'reconfig' is nice (usually quicker & less intrusive than a full stop + start cycle), but we've found you can't run it too many times before the JVM starts running out of resources (memory) and requires you to stop & start up again the SWS instance to clear things up.
