|
Problem |
Defining your own JSP extensions other than the default
.jsp, .jsv, and .jsw. |
|
Solution |
In WebSphere Application Server V4.0 one can serve JSPs
with arbitrary extensions by defining a "JSP attribute" for their web-app
in AAT (under "Assembly Property Extensions").
The name of the attribute is "jsp.file.extensions" and the value it should
be set to is a colon separated list of extensions, for example...
*.jsp:*.jsv:*.jsw:*.foo:*.bar
The first three are the standard extensions that WebSphere Application
Server normally would process as JSP by default. In the above example, I
have added files with .foo and .bar extensions to be treated as JSP as
well.
This attribute (jsp.file.extensions) overrides the default, so, when you
do define this attribute, you should include the standard extensions
(.jsp, .jsv. .jsw) in the list if you have JSPs with these extensions as
well in your web-application. |
|
|
|
Product
Alias/Synonym |
WAS |
|
|
|
|
|