Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by ErikVullings: http://wiki.apache.org/tapestry/PortletSupport ------------------------------------------------------------------------------ I was about to say ... ''ideally, we'll have the technology in place to encode persistent properties as query parameters in 3.1.'' However, that really isn't an issue ... whether it's PortletSession attributes or query parameters inside the render URL, it's still server side state. I wonder how portlet containers deal with browser back button and redirect-after-post issues? - == PLT.11.1.8 == + == PLT.11.1.8 (page 46) == The portlet container is responsible for localization; this bypasses the standard Tapestry issue with a page changing locale, and then rendering in the old locale. + == PLT.12.3.4 (page 53) == + + And here's the namespace needed to keep forms and JavaScript variables/functions from suffering name collisions. + + == PLT.14.3 (page 58) == + + Seems like a natural to "inject" preference attributes as properties, especially if they are read-only. Do we drive this via <meta> tags in the component spec, or do we introduce some + additional spec elements? Can this be generalized, the way <inject> is? + + == PLT.15.3 (page 62) == + + Persistent page properties should be stored as PORTLET_SCOPE. If a portlet has information to share with other portlets, it should inject/obtain the PortletSession and access + its APIs directly. = Status = --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
