[JBoss JIRA] Created: (RF-4222) Nice to have multiple events in a4j:support tag
by Jan Hoeve (JIRA)
Nice to have multiple events in a4j:support tag
-----------------------------------------------
Key: RF-4222
URL: https://jira.jboss.org/jira/browse/RF-4222
Project: RichFaces
Issue Type: Feature Request
Reporter: Jan Hoeve
Priority: Minor
in the a4j:support tag, it is now possible enter an event for which you want to occur something (e.g. reRender):
<a4j:support event="onblur" reRender="usernameDecorate"/>
Sometimes it would be very userful if reRenders occur for multiple events.
For example there are two events in which you are interesed: onblur and onkeyup.
The onblur should check where a username containts valid characters (by using a regexp)
The onkeyup should display the current length of the username (in an <h:outputText />)
So, based on above example it would me nice if the support tag supported (hehe) more than one event).
For example: <a4j:support event="onblur,onkeyup" reRender="usernameDecorate"/>
I already tried to create a separate a4j:support for each event, but then only the first one is executed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (RF-10228) Component rich:inplaceInput not get facet "controls"
by Antonio Parisi (JIRA)
Component rich:inplaceInput not get facet "controls"
----------------------------------------------------
Key: RF-10228
URL: https://issues.jboss.org/browse/RF-10228
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-input
Affects Versions: 4.0.0.Milestone5
Environment: Mac OSX 10.6.6 - Glassfish v3.0.1 - Richfaces 4.0 M5
Reporter: Antonio Parisi
Fix For: 4.0.0.CR1
The component rich:inplaceInput, don't get facet "controls".
Example:
<rich:inplaceInput defaultLabel="Click here to edit" showControls="true"
controlsHorizontalPosition="left" controlsVerticalPosition="bottom"
id="inplaceInput">
<f:facet name="controls">
<button onmousedown="#{rich:component('inplaceInput')}.save();"
type="button">Save</button>
<button onmousedown="#{rich:component('inplaceInput')}.cancel();"
type="button">Cancel</button>
</f:facet>
</rich:inplaceInput>
Him don't get my Save and Cancel button, but show always default's "V" and "X" icon.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (RF-10756) collapsibleSubtable: id set to tbody differs from component id and break rendering.
by Ilya Shaikovsky (JIRA)
collapsibleSubtable: id set to tbody differs from component id and break rendering.
-----------------------------------------------------------------------------------
Key: RF-10756
URL: https://issues.jboss.org/browse/RF-10756
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
added to richfaces-showcase code:
<rich:column colspan="6">
<rich:collapsibleSubTableToggler for="sbtbl" />
<h:outputText value="#{list.vendor}" />
<a4j:commandButton value="render" render="sbtbl" action="#{carsBean.incDaysLive}">
</a4j:commandButton>
</rich:column>
<rich:collapsibleSubTable value="#{list.vendorItems}" var="item" id="sbtbl"
expandMode="client">
<rich:column>
<h:outputText value="#{item.daysLive}" />
</rich:column>
and
public void incDaysLive(){
for (InventoryVendorList vendor : inventoryVendorLists) {
for (InventoryVendorItem item : vendor.getVendorItems()) {
item.setDaysLive(item.getDaysLive()+1);
}
}
}
do not see values updated before refreshing the browser.
According to log update came fine for the subtable. just wrapper tbody has different id than specified at component. so it can't be updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (RF-970) DDMenu in Toolbar and Opera
by Carsten H?hne (JIRA)
DDMenu in Toolbar and Opera
---------------------------
Key: RF-970
URL: http://jira.jboss.com/jira/browse/RF-970
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Carsten H?hne
Priority: Minor
The dropDown Menu does not work in Opera (9.23) in this constellation:
<ui:component ...>
<rich:toolBar>
<h:form>
<rich:toolBarGroup >
<rich:dropDownMenu value="Collection" >
<rich:menuItem value="List working collection" action="list" />
</rich:dropDownMenu>
</rich:toolBarGroup>
</h:form>
<rich:toolBarGroup location="right">
<h:form>[....]
</h:form>
</rich:toolBarGroup>
</rich:toolBar>
</ui:component>
But it works with IE and Firefox.
If the form is put into the toolbargroup, than the menue is functioning in opera. Or if you put the form around the whole toolbar it works also.
--
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
13 years, 8 months
[JBoss JIRA] Created: (RF-9426) Check iteration state saving for facets of dataTable component
by Nick Belaevski (JIRA)
Check iteration state saving for facets of dataTable component
---------------------------------------------------------------
Key: RF-9426
URL: https://jira.jboss.org/browse/RF-9426
Project: RichFaces
Issue Type: Task
Security Level: Public (Everyone can see)
Components: component-tables, performance
Affects Versions: 4.0.0.Milestone3
Reporter: Nick Belaevski
Assignee: Konstantin Mishin
Fix For: 4.0.0.Milestone4
Here is the excerpt from the letter I've just received:
>>>> There is memory leak in UIDataAdaptorBase/rich:dataTable.
>>>> It affects:
>>>> - external filtering (input in "header" facet)
>>>> - embedded filtering ("filterBy" column attribute) - facet
>>>> "filterValueInput" is added internally
>>>>
>>>> Code in UIDataAdaptorBase#saveChildState:
>>>> itr = c.getFacets().values().iterator();
>>>> while (itr.hasNext()) {
>>>> saveChildState(faces, (UIComponent) itr.next(), childState);
>>>> }
>>>>
>>>> Column facet state is saved in the view for each row.
>>>>
>>>> For the table with 500 rows 5 columns with filtering that resulst in
>>>> 350kB
>>>> of extra view size.
>>>> UIDataAdaptorBase$DataState size - 350 kB
>>>> There are 2500 (500 rows * 5 columns) instances of
>>>> UIDataAdaptorBase$SavedState.
>>>>
>>>> The same table without filtering does not have this issue and
>>>> UIDataAdaptorBase$DataState size is 1 kB.
>>>>
This affects 3.x. Please check if 4.x is affected by the problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] Created: (RF-10825) ClientBehavior: view state is not saved if behavior is marked to hold initial state
by Nick Belaevski (JIRA)
ClientBehavior: view state is not saved if behavior is marked to hold initial state
-----------------------------------------------------------------------------------
Key: RF-10825
URL: https://issues.jboss.org/browse/RF-10825
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: architectural
Affects Versions: 4.0.0.Final
Reporter: Nick Belaevski
ClientBehavior contains the following code:
{noformat} @Override
public Object saveState(FacesContext context) {
Object[] state = null;
Object parentState = super.saveState(context);
if (initialStateMarked()) {
if (parentState != null) {
state = new Object[] { parentState };
}
} else {
Object savedHelper = null;
if(behaviorStateHelper != null) {
savedHelper = behaviorStateHelper.saveState(context);
}
state = new Object[3];
state[0] = parentState;
state[1] = savedHelper;
state[2] = saveBindings(context, bindings);
}
return state;
}{noformat}
however state of state helper should be saved even if initialStateMarked() is returning true.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months