rendered attribute is overloaded

[glassfishrobot]

The rendered attribute is used to control whether a widget is rendered on the
page as well as whether it should be included in processing the postback. This
in itself is not a problem (except that the word rendered is misleading to
users), however the value of rendered is revaluated when the form is submitted,
and this value is used to decide whether to process the component.

Unfortunately, there is no easy way around this, especially if we move towards a
more stateless lifecycle. This may be a simple matter of better educating users.

Environment

Operating System: All
Platform: All

Affected Versions

[1.2]

[glassfishrobot]

Reported by pmuir

[glassfishrobot]

pmuir said:
A JBoss top priority issue issue

[glassfishrobot]

@edburns said:
Change target milestone to 2.0

[glassfishrobot]

@edburns said:
This is important for 2.1

[glassfishrobot]

@edburns said:
Prepare to delete api subcomponent

[glassfishrobot]

@edburns said:
Move these to unscheduled because we need to target them correctly. 2.next isn't
specific enough.

[glassfishrobot]

@edburns said:
cat2

[glassfishrobot]

@edburns said:
javadoc

[glassfishrobot]

@edburns said:
rendered

[glassfishrobot]

@edburns said:
These are targeted at 2.1.

[glassfishrobot]

rogerk said:
triage

[glassfishrobot]

@edburns said:
GlassFish 3.1 M6 at the latest.

[glassfishrobot]

@edburns said:
Move these to 2.2

[glassfishrobot]

@edburns said:
Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

[glassfishrobot]

@edburns said:
Worth considering so leave as is.

[glassfishrobot]

This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-478

[glassfishrobot]

Closing this as this issue is migrated to jakartaee/faces#478