[JBoss JIRA] Reopened: (RF-6746) a4j:include - FacesContext.getCurrentInstance().getViewRoot().getViewId() isn't always correct
by Alexander Smirnov (JIRA)
[ https://jira.jboss.org/jira/browse/RF-6746?page=com.atlassian.jira.plugin... ]
Alexander Smirnov reopened RF-6746:
-----------------------------------
that patch conflicts with StateManager https://jira.jboss.org/jira/browse/RF-7051
> a4j:include - FacesContext.getCurrentInstance().getViewRoot().getViewId() isn't always correct
> ----------------------------------------------------------------------------------------------
>
> Key: RF-6746
> URL: https://jira.jboss.org/jira/browse/RF-6746
> Project: RichFaces
> Issue Type: Bug
> Reporter: David Schlotfeldt
> Assignee: Alexander Smirnov
> Fix For: 3.3.2.GA
>
>
> When a request is made by from inside a a4j:include component UIInclude will set the ViewIdHolder to it self. It does this to ensure FacesContext.getCurrentInstance().getViewRoot().getViewId() returns the viewId of the a4j:include.
> Everything works fine if you only need to access the viewId when its already rendered and its posting back.
> If you, as I am, change the viewId of the UIInclude (the UIInclude is bound to a property of a managed bean), when the page is rendered back it renders the new "view" assigned to the UIInclude. When its rendered any manage-bean used from inside the a4j:include will see the viewId as the "outter view" not the view assigned to the a4j:include.
> I believe the simplest and best solution easiest solution is when rendering the children of uiinclude to:
> ---
> AjaxContext ajaxContext = AjaxContext.getCurrentInstance(context);
> ViewIdHolder viewIdHolder = ajaxContext.getViewIdHolder(); // Store reference to current
> ajaxContext.setViewIdHolder(this); // This is UIInclude
> // render children here...
> ajaxContext.setViewIdHolder(viewIdHolder ); // Put previous back
> ---
--
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
15 years, 9 months
[JBoss JIRA] Created: (RF-4403) Better support for datatable sorting in DB
by Sei Syvalta (JIRA)
Better support for datatable sorting in DB
------------------------------------------
Key: RF-4403
URL: https://jira.jboss.org/jira/browse/RF-4403
Project: RichFaces
Issue Type: Feature Request
Affects Versions: 3.2.2
Reporter: Sei Syvalta
Currently, there are two options for sorting data in dataTable (with or without paging):
1. use sortBy attribute in rich:column. The downside is that the whole data set needs to be loaded from DB for sorting.
2. use commandLinks in rich:cloumn. The downside is that you need to manage the icons, direction etc. by yourself (all this is managed by richfaces in case 1.)
So what I would find very useful would be to get the sort property(ies) to a bean, where it could be used in sql "select ... order by sortProperty limit start maxResults..." clause.
Some discussion about this is also in RF-2916.
To conclude, I'm using a custom datamodel with dataTable pagination which loads data lazily and everything is working fine. However, I would like to add sorting to the headers of table, and I would like to do that at the database level, without doing all the sorting logic manually (ie. option 2).
--
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
15 years, 9 months
[JBoss JIRA] Created: (RF-6641) layoutPanel: componnet incorrect layout inside other layoutPanel.
by Mikhail Vitenkov (JIRA)
layoutPanel: componnet incorrect layout inside other layoutPanel.
-----------------------------------------------------------------
Key: RF-6641
URL: https://jira.jboss.org/jira/browse/RF-6641
Project: RichFaces
Issue Type: Bug
Environment: IE7, IE8, FF 3.0.7, Safari 3.1, Opera 9.62, Chrome 1.0.154.43(3.3.1.BETA2)
Reporter: Mikhail Vitenkov
Assignee: Nick Belaevski
Fix For: 3.3.1
#1. Use code listed below:
<h:form>
<rich:layout>
<rich:layoutPanel position="left">
<rich:layout>
<rich:layoutPanel position="top">
<p>top</p>
</rich:layoutPanel>
<rich:layoutPanel position="center">
<p>center</p>
</rich:layoutPanel>
<rich:layoutPanel position="left">
<p>left</p>
</rich:layoutPanel>
<rich:layoutPanel position="right">
<p>right</p>
</rich:layoutPanel>
<rich:layoutPanel position="bottom">
<p>bottom</p>
</rich:layoutPanel>
</rich:layout>
</rich:layoutPanel>
<rich:layoutPanel position="center">
<p>center-right</p>
</rich:layoutPanel>
</rich:layout>
</h:form>
#2. Navigate to the tested page.
#3. Verify vertical position of "left","center","right" and "top" divs.
Actual behavior:
"left","center","right" and "top" divs placed on the same vertical position. See attached screenshot for more information.
--
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
15 years, 9 months