I ran into a similar issue trying to share JSPs across multiple contexts.
How I solved my problem was to set up a symbolic link under the web content
directory that pointed to a folder in the IFS. All the symbolic links in all
the contexts pointed to the same folder in the IFS.
 Another approach could be to use an "iframe" tag in the html and load the
html file from a different context.
 -Sarah Poger Gladstone

On 11/8/05, Nancy Cochran <ncochran@xxxxxxx> wrote:
> Does anyone have any advice on how to bundle up common headers/footers
> that are just plain html into a jar/war that can be used across multiple
> dynamic web applications without bundling them in all of the applications?
> What I have so far is a jar file with common headers and footers, as well
> as some classes, that will be used across multiple applications. I have set
> up a shared library for the jar in WAS Express 5.0, added this to the
> classloader and have verified that the jsp can import the package.
> The problem is I can't seem to get any .html files from the jar included
> into the jsp. The jsp only seems to be able to include files from it's own
> WebContent directory. I really don't want to have to bundle this common jar
> with every application, but it seems like my whole approach is wrong. Any
> advice is appreciated, I'm a newbie.
> --
> This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
> mailing list
> To post a message email: JAVA400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.