[JBoss JIRA] (RF-12839) Toggle panels: ajax-related attributes don't work
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12839?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12839:
-------------------------------
Forum Reference: https://community.jboss.org/thread/222390
> Toggle panels: ajax-related attributes don't work
> -------------------------------------------------
>
> Key: RF-12839
> URL: https://issues.jboss.org/browse/RF-12839
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.1
> Environment: RichFaces 4.3.2-SNAPSHOT
> Metamer 4.3.2-SNAPSHOT
> JBoss Application Server: Weld Integration 7.1.3.Final-redhat-4
> JBoss AS 7.1.3.Final-redhat-4
> Java(TM) SE Runtime Environment 1.7.0_04-b20 @ Linux
> Chrome 25.0.1364.160 @ Linux x86_64
> Reporter: Pavol Pitonak
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.3.2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTab/simple.xhtml
> # set oncomplete to "alert('complete')"
> # switch to tab 2 and back to tab 1
> result:
> * alert should be diplayed but isn't
> * tabs are correctly switched
> * worked fine in 4.2.3.Final
> * several attributes don't work - onbegin, onbeforedomupdate, oncomplete, data, execute, immediate, render, limitRender, status
> * affected components: tab, toggle panel item, accordion item
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12846) a4j:commandLink accesskey attribute missing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12846?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12846.
--------------------------------
Fix Version/s: (was: 5-Tracking)
Resolution: Done
Added the Accesskey interface, and changed the commandButton and commandLink to implement that interface
> a4j:commandLink accesskey attribute missing
> -------------------------------------------
>
> Key: RF-12846
> URL: https://issues.jboss.org/browse/RF-12846
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.2.2.Final, 4.2.3.Final, 4.3.1
> Reporter: John Yeary
> Assignee: Brian Leathem
> Priority: Trivial
> Fix For: 4.3.2
>
> Original Estimate: 15 minutes
> Remaining Estimate: 15 minutes
>
> The a4j:commandLink supported accesskey in 3.3.3.final and the org.richfaces.renderkit.html.CommandLinkRenderer supports the accesskey attribute as a pass-through attribute. However it does not appear in the VDL documentation, and produces an error message in the IDE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12897) ExtendedPartialViewContextImpl swallows exceptions
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12897?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12897:
-------------------------------
Fix Version/s: 4.3.2
Assignee: Brian Leathem
Scheduling for 4.3.2 for assessment, and a determination of the impact a fix would have.
> ExtendedPartialViewContextImpl swallows exceptions
> --------------------------------------------------
>
> Key: RF-12897
> URL: https://issues.jboss.org/browse/RF-12897
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 4.2.2.Final
> Environment: Windows 7, JDK 1.6
> Reporter: Cristian Cerb
> Assignee: Brian Leathem
> Priority: Critical
> Labels: richfaces
> Fix For: 4.3.2
>
>
> Method public VisitResult visit(VisitContext context, UIComponent target) of class ExtendedPartialViewContextImpl swallows exceptions. I think exceptions should be wrapped inside a FaceException and propagated. This class http://java.net/projects/mojarra/sources/svn/content/trunk/jsf-ri/src/mai... seems to have served as a model for the RF one, but the RF class inadvertently chose to swallow exceptions instead of propagating them up. This causes unpredictable behaviour, such as system being stuck in the browser.
> I just found an older version of Sun's Mojarra where they had the same issue, but the newer versions seem to have fixed it. See this taken from jsf 2.1.4:
> {code}
> public VisitResult visit(VisitContext context, UIComponent comp) {
> try {
> if (curPhase == PhaseId.APPLY_REQUEST_VALUES) {
> // RELEASE_PENDING handle immediate request(s)
> // If the user requested an immediate request
> // Make sure to set the immediate flag here.
> comp.processDecodes(ctx);
> } else if (curPhase == PhaseId.PROCESS_VALIDATIONS) {
> comp.processValidators(ctx);
> } else if (curPhase == PhaseId.UPDATE_MODEL_VALUES) {
> comp.processUpdates(ctx);
> } else if (curPhase == PhaseId.RENDER_RESPONSE) {
> PartialResponseWriter writer = ctx.getPartialViewContext().getPartialResponseWriter();
> writer.startUpdate(comp.getClientId(ctx));
> try {
> // do the default behavior...
> comp.encodeAll(ctx);
> }
> catch (Exception ce) {
> if (LOGGER.isLoggable(Level.SEVERE)) {
> LOGGER.severe(ce.toString());
> }
> if (LOGGER.isLoggable(Level.FINE)) {
> LOGGER.log(Level.FINE,
> ce.toString(),
> ce);
> }
> }
> writer.endUpdate();
> }
> else {
> throw new IllegalStateException("I18N: Unexpected " +
> "PhaseId passed to " +
> " PhaseAwareContextCallback: " +
> curPhase.toString());
> }
> }
> catch (IOException ex) {
> ex.printStackTrace();
> }
> // Once we visit a component, there is no need to visit
> // its children, since processDecodes/Validators/Updates and
> // encodeAll() already traverse the subtree. We return
> // VisitResult.REJECT to supress the subtree visit.
> return VisitResult.REJECT;
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12927) Review all occurences of org.ajax4jsf string in RichFaces 5 repository
by Pavol Pitonak (JIRA)
Pavol Pitonak created RF-12927:
----------------------------------
Summary: Review all occurences of org.ajax4jsf string in RichFaces 5 repository
Key: RF-12927
URL: https://issues.jboss.org/browse/RF-12927
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: migration
Affects Versions: 5.0.0.Alpha1
Reporter: Pavol Pitonak
There are 57 occurences of string "org.ajax4jsf" in RichFaces 5 repository, e.g. in JavaDocs, package-info files and in web.xml files.
It doesn't make sense to use package org.ajax4jsf anymore.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (RF-12926) rich:notify: ecss contains old (and unused) styleClasses for history
by Jiří Štefek (JIRA)
Jiří Štefek created RF-12926:
--------------------------------
Summary: rich:notify: ecss contains old (and unused) styleClasses for history
Key: RF-12926
URL: https://issues.jboss.org/browse/RF-12926
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: component-validators
Environment: RichFaces 4.3.2-SNAPSHOT
Metamer 5.0.0-SNAPSHOT
Reporter: Jiří Štefek
Remove redundant (from old version of rich:notify*, from RF 4.3.X) all styles and resources for rich:notify* history.
Styles in notify.ecss:
* rf-ntf-hstr
* rf-ntf-hstr-hdr
* rf-ntf-hstr button
* rf-ntf-hstr-hndl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months