Sun Portal Server: Unterschied zwischen den Versionen
Keine Bearbeitungszusammenfassung |
(layout) |
||
| Zeile 1: | Zeile 1: | ||
=Layout Customizing= | |||
==Global== | |||
Stylesheets, Images: | |||
/opt/SUNWwbsvr/docs | |||
==AccessManager== | |||
/opt/SUNWwbsvr/https-instance/is-web-apps/services/config/auth/default [/org] | |||
Srcs: | |||
/opt/SUNWam/web-src/services/config/auth/default [/org] | |||
==Portal-Desktop== | |||
/etc/opt/SUNWps/desktop [/org] | |||
==Locales== | |||
/opt/SUNWam/locales | |||
=Tips und Tricks= | =Tips und Tricks= | ||
==Recompiling JSPs== | ==Recompiling JSPs== | ||
| Zeile 5: | Zeile 23: | ||
For example, type | For example, type | ||
touch tab.jsp | touch tab.jsp | ||
===Note=== | ===Note=== | ||
A typical desktop will include content from several JSPs. However, if you make a modification to a non-toplevel JSP that has been included in a top level JSP, the included JSP will not be recomplied. The end result is your desktop changes will never be reflected. | A typical desktop will include content from several JSPs. However, if you make a modification to a non-toplevel JSP that has been included in a top level JSP, the included JSP will not be recomplied. The end result is your desktop changes will never be reflected. | ||
| Zeile 19: | Zeile 36: | ||
See JavaServer Page Caching Information for information on how to find the top-level (parent) JSP. | See JavaServer Page Caching Information for information on how to find the top-level (parent) JSP. | ||
[[ | [[Kategorie:WWW]] | ||
Aktuelle Version vom 17. April 2007, 18:14 Uhr
Layout Customizing
Global
Stylesheets, Images:
/opt/SUNWwbsvr/docs
AccessManager
/opt/SUNWwbsvr/https-instance/is-web-apps/services/config/auth/default [/org]
Srcs:
/opt/SUNWam/web-src/services/config/auth/default [/org]
Portal-Desktop
/etc/opt/SUNWps/desktop [/org]
Locales
/opt/SUNWam/locales
Tips und Tricks
Recompiling JSPs
Every time you make a modification to a JSP file, you need to recompile. You do this by running the touch command on the modified container’s top-level JSP file.
For example, type
touch tab.jsp
Note
A typical desktop will include content from several JSPs. However, if you make a modification to a non-toplevel JSP that has been included in a top level JSP, the included JSP will not be recomplied. The end result is your desktop changes will never be reflected.
If the top-level JSP is touched, the JSP engine recompiles all the relevant JSPs. If you cannot find the top level JSP, run the touch command on all JSPs in the directory, for example,
touch *.jsp
This modifies all JSPs, including the top-level JSP.
See JavaServer Page Caching Information for information on how to find the top-level (parent) JSP.