JSPELL Installation in OAF Pages

Question

Hi All,
Can any body help me to install jspell in oaf pages? i just want to install spell check in self service pages.
is this feasible in SS pages like Forms and javascript?
Any input will be appreciated.
Thanks,
Ramesh Medepalli

Answer 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.