[jira] [Created] (PLUTO-700) Spec: Clarify Section 20.2.3 titled "Render State Scope"
"Neil Griffin (JIRA)" <[email protected]>
| Newsgroups | gmane.comp.jakarta.pluto.devel |
|---|---|
| Message-ID | <[email protected]> |
Neil Griffin created PLUTO-700:
----------------------------------
Summary: Spec: Clarify Section 20.2.3 titled "Render State Scope"
Key: PLUTO-700
URL: https://issues.apache.org/jira/browse/PLUTO-700
Project: Pluto
Issue Type: Bug
Components: spec
Affects Versions: 3.0.0
Reporter: Neil Griffin
Assignee: Scott Nicklous
Section 20.2.3 of the Portlet 3.0 Specification titled "Render State Scope" states:
{quote}The render state scope is a passivating scope that associates managed beans with the render state.{quote}
While it is true that beans annotated with {{@RenderStateScoped}} need to be "passivating" (meaning they need to be able to save/restore their state), such beans are required to implement javax.portlet.annotations.PortletSerializable rather than java.io.Serializable.
The Portlet 3.0 API {{@RenderStateScoped}} annotation declares the following qualifiers:
{code:java|title=RenderStateScoped.java}
@Retention(RUNTIME)
@Target({TYPE})
@NormalScope()
@Inherited
public @interface RenderStateScoped {
String paramName() default "";
}
{code}
Note that the annotation defines {{@NormalScope()}} and not {{@NormalScope(passivating = true)}}.
Because of this, it is necessary to clarify the sentence in the spec. For example:
{quote}The render state scope is a non-passivating scope that associates managed beans with the render state. Although beans annotated with @RenderStateScoped are non-passivating from a CDI perspective, all such beans must be able to save and restore their state.{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)