Any suggestions?
I'm putting together an extremely basic context sensitive help system for a web app.
The idea is that the help file is going to be a single HTML page, with named anchors delineating sections for each topic. By using the URL "server/.../helpfile.html#topic", the user will be automagically transported tot he section of the document pertaining to the particular topic. Seems really straight-forward. The way I'm trying to make it work is as follows:
* Each page in the app has a javascript navigation header. Part of this header is a "help" link.
* This link, onClick opens a new window.
* The window loads a jsp. (help.jsp)
* The help.jsp gets a session attribute which was set upon loading each page (also jsp) of the app. This attribute defines the topic, and thus context for the help needed.
* The help.jsp then concatenates the name of the single help file with a "#" and the value of the session attribute, which is the same as the name of the corresponding anchor in helpfile.html.
* The help.jsp then contains a jsp:forward directive to reload helpfile.html#topic in the pop-up window.
Pretty brain dead, but it's a creepy feature with no time allocated in the schedule.
The problem is that WebSphere, in it's infinite wisdom, is looking for a file called "helpfile.html#topic", and (obviously) not finding it.
Short of breaking the help system down into separate files, is there any way to get around WebSphere's behavior?
I could make the help function in the javascript header accept the help context as a parameter, I suppose, but that would complicate maintainability of this somewhat. Am I missing something obvious?
The idea is that the help file is going to be a single HTML page, with named anchors delineating sections for each topic. By using the URL "server/.../helpfile.html#topic", the user will be automagically transported tot he section of the document pertaining to the particular topic. Seems really straight-forward. The way I'm trying to make it work is as follows:
* Each page in the app has a javascript navigation header. Part of this header is a "help" link.
* This link, onClick opens a new window.
* The window loads a jsp. (help.jsp)
* The help.jsp gets a session attribute which was set upon loading each page (also jsp) of the app. This attribute defines the topic, and thus context for the help needed.
* The help.jsp then concatenates the name of the single help file with a "#" and the value of the session attribute, which is the same as the name of the corresponding anchor in helpfile.html.
* The help.jsp then contains a jsp:forward directive to reload helpfile.html#topic in the pop-up window.
Pretty brain dead, but it's a creepy feature with no time allocated in the schedule.
The problem is that WebSphere, in it's infinite wisdom, is looking for a file called "helpfile.html#topic", and (obviously) not finding it.
Short of breaking the help system down into separate files, is there any way to get around WebSphere's behavior?
I could make the help function in the javascript header accept the help context as a parameter, I suppose, but that would complicate maintainability of this somewhat. Am I missing something obvious?
