Note | ||||
---|---|---|---|---|
| ||||
|
Why not a section called "JSR-168 development"? Because that would be out of scope of a manual about uPortal – part of the point of JSR-168 as a standard is that how to develop JSR-168s is documented and discussed elsewhere.
However, there are nuances of uPortal's JSR-168 support that are useful to understand in successfully developing JSR-168s for use in uPortal.
Tip | ||
---|---|---|
| ||
See also ~choldophCris Holdorph's article on using opensource JSR-168 portlets in uPortal and on using the "exclusive" window state in uPortal. |