[JBoss JIRA] Created: (RF-1321) Tab Panel encodes wrong tab name
by Denis Morozov (JIRA)
Tab Panel encodes wrong tab name
--------------------------------
Key: RF-1321
URL: http://jira.jboss.com/jira/browse/RF-1321
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Denis Morozov
I have page with tabPanel.
In Html, input is rendered
<input id="mainForm:tabPanel_input" type="hidden" name="mainForm:tabPanel" value="mainForm:tab0"/>
When I scroll scrollableDataTable, an event is fired (org.richfaces.renderkit.TabPanelRendererBase:104)
new SwitchablePanelSwitchEvent(panel, newValue, null).queue();
taking input value as newValue.
Then, in queeuEvent method,
UITab tab = processedTab(switchEvent.getEventSource(),switchEvent.getValue());
returns null because UITab.getName() returns component id (tab0), but not clientId(mainForm:tab0)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (RF-1754) rich:messages class style
by First Last (JIRA)
rich:messages class style
-------------------------
Key: RF-1754
URL: http://jira.jboss.com/jira/browse/RF-1754
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.3
Environment: JBoss 4.2.2
Reporter: First Last
In 3.1.3, the rich-messages class style is render on screen even when there are no messages. In 3.1.2, the rich-messages class styles only get rendered on screen when there are actual messages in the <rich:messages> component.
For example,
<style>
.rich-messages { margin: 10px; 5px; }
</style>
In version 3.1.2., the above styles will not be rendered on screen when <rich:messages> is empty. But in 3.1.3, there will be empty spaces (margin:10px 5px) appear in the location of the <rich:messages> tag even there is no messages being rendered.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Assigned: (RF-1713) RichFaces 'double implementation' MethodNotFoundException bug
by Nick Belaevski (JIRA)
[ http://jira.jboss.com/jira/browse/RF-1713?page=all ]
Nick Belaevski reassigned RF-1713:
----------------------------------
Assignee: Sergey Halipov (was: Nick Belaevski)
Create EAR file (you can use samples/seamEAR) and test if the issue exists
> RichFaces 'double implementation' MethodNotFoundException bug
> -------------------------------------------------------------
>
> Key: RF-1713
> URL: http://jira.jboss.com/jira/browse/RF-1713
> Project: RichFaces
> Issue Type: Bug
> Affects Versions: 3.2.0
> Environment: Linux, Jboss AS 4.2.2, Seam 2.0.0 GA
> Reporter: Bram Biesbrouck
> Assigned To: Sergey Halipov
> Fix For: 3.2.0
>
>
> When I use "adviseNodeOpened" in a rich:tree component, I end up with a javax.faces.el.MethodNotFoundException:
> adviseNodeOpened="#{fileSystemManager.adviseFileSystemTreeNodeOpened}": Method not found: FileSystemManagerImpl:3j011-9i11xv-faathdgv-1-faauxftc-h.adviseFileSystemTreeNodeOpened(org.richfaces.component.UITree)
> The former solution was to set UseJBossWebLoader to true, but this breaks the Seam Mail functionality.
> The new solution came when RichFaces impl and api were splitted, but nothing changed with "adviseNodeOpened"
> In the Wiki-example build.xml, I'm seeing this comment:
> <!-- Still need the * on richfaces due to bug in version mapper -->
> Could this be the reason (the fact that we can't split out the api in the war file just yet) for this exception to be thrown?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (RF-1471) Support non default date types for Calendar component
by Bryan Brouckaert (JIRA)
Support non default date types for Calendar component
-----------------------------------------------------
Key: RF-1471
URL: http://jira.jboss.com/jira/browse/RF-1471
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.1.2
Reporter: Bryan Brouckaert
The current implementation of the Calendar component only supports java.util.Date, java.util.Calendar and java.lang.String as valid types for the component's value. There are many other date types in the Java world. There is the very useful org.joda.time.DateMidnight from joda-time and the javax.xml.datatype.XMLGregorianCalendar that is part of JavaEE.
Supporting all possible date types is impossible, but it is possible to fall back on the string representation of the object via custom converters.
In the case of the XMLGregorianCalendar class, the following section in the faces-config.xml should be taken into account:
<converter>
<converter-for-class>javax.xml.datatype.XMLGregorianCalendar</converter-for-class>
<converter-class>be.cin.mycarenet.portal.converter.XMLGregorianCalendarConverter</converter-class>
</converter>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years