[JBoss JIRA] (RFPL-3037) InplaceSelect metamer tests always fail
by Matej Novotny (JIRA)
Matej Novotny created RFPL-3037:
-----------------------------------
Summary: InplaceSelect metamer tests always fail
Key: RFPL-3037
URL: https://issues.jboss.org/browse/RFPL-3037
Project: RichFaces Planning
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.3.4
Reporter: Matej Novotny
In class TestInplaceSelectFAjax in method testClick() there is always an assert failure. This also happens in tests for version 5.0 (according to Jenkins job).
The problem appears in this assert: assertTrue(select.advanced().isInState(InplaceComponentState.CHANGED))
While debugging this test you can see that the class attribute is not set properly when element.click() is called. Although the value is in fact set properly and is visible as output.
When performed manually everything works as expected.
--
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, 7 months
[JBoss JIRA] (RFPL-2984) Update Photoalbum deployment on OpenShift
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2984?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2984:
--------------------------------
Original Estimate: 30 minutes
Remaining Estimate: 30 minutes
> Update Photoalbum deployment on OpenShift
> -----------------------------------------
>
> Key: RFPL-2984
> URL: https://issues.jboss.org/browse/RFPL-2984
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: administration
> Reporter: Lukáš Fryč
> Assignee: Michal Petrov
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Photoalbum was improved in RF-12793, it got new features and the demo should be updated to update those changes.
> Prepare the photoalbum for deployment:
> * do any changes which are necessary before publishing it online publicly (maybe no changes are required?)
> * change the development to use latest RF release
> * update web.xml to use Production mode
--
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, 7 months
[JBoss JIRA] (RFPL-2978) Push VDL details out of Component Reference
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RFPL-2978?page=com.atlassian.jira.plugin.... ]
Brian Leathem updated RFPL-2978:
--------------------------------
Original Estimate: 2 hours
Remaining Estimate: 2 hours
> Push VDL details out of Component Reference
> --------------------------------------------
>
> Key: RFPL-2978
> URL: https://issues.jboss.org/browse/RFPL-2978
> Project: RichFaces Planning
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 5.0.0.Alpha1
> Reporter: Lukáš Fryč
> Fix For: 5.0.0.Alpha2
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> See [Forum Reference].
> ----
> I have noticed each of the components in Component Reference contains referecen data:
>
>
> {code}
> 3.5.2. Reference data
>
> component-type: org.richfaces.CommandLink
> component-class: org.richfaces.component.UICommandLink
> component-family: javax.faces.Command
> renderer-type: org.richfaces.CommandLinkRenderer
> {code}
>
> Similarly, VDL doc contains same information:
>
> {code}
> Tag Information
> Component type org.richfaces.CommandLink
> Tag Name a4j:commandLink
> Renderer Type org.richfaces.CommandLinkRenderer
> Handler Class None
> {code}
>
>
> The advantage of VDL doc is that it is automatically generated and so it doesn't need to be updated manually everytime something is changed.
>
> On the other hand, those are also not information which are used regularly - they are intented for advanced users and use cases.
>
> Thus I suggest to remove the Reference Data from Components Reference.
--
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, 7 months