January 2012 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-11897) menuItems do not inherit the mode of the parent contextMenu

by Brian Leathem (JIRA)

Brian Leathem created RF-11897: ---------------------------------- Summary: menuItems do not inherit the mode of the parent contextMenu Key: RF-11897 URL: https://issues.jboss.org/browse/RF-11897 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Setting the mode of the contextMenu to "client" does not propagate to the child menuItems. The mode of the menuItem must be set explicitly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] (RF-11911) contextMenu API for attaching to components should match that of tooltip

by Brian Leathem (JIRA)

Brian Leathem created RF-11911: ---------------------------------- Summary: contextMenu API for attaching to components should match that of tooltip Key: RF-11911 URL: https://issues.jboss.org/browse/RF-11911 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Assignee: Brian Leathem Priority: Minor Fix For: 4.2.0.CR1 in it's initial implementation, contextMenu uses the _attachTo_ (from RichFaces 3) attribute to target another component and tooltip uses the _target_ attribute for the same purpose. The contextMenu _attachTo_ attribute should be renamed to _target_ to have a consistent API with tooltip. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] (RF-11899) the attachId of the contextMenu requires the fully qualified path

by Brian Leathem (JIRA)

Brian Leathem created RF-11899: ---------------------------------- Summary: the attachId of the contextMenu requires the fully qualified path Key: RF-11899 URL: https://issues.jboss.org/browse/RF-11899 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem Providing an attachId of "pic" for instance is insufficient, one must provide "form:pic". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (RF-11900) contextMenu has to be defined after the extendedDatatable, or it cannot attach

by Brian Leathem (JIRA)

Brian Leathem created RF-11900: ---------------------------------- Summary: contextMenu has to be defined after the extendedDatatable, or it cannot attach Key: RF-11900 URL: https://issues.jboss.org/browse/RF-11900 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-menu Reporter: Brian Leathem -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (RF-11898) Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display

by Brian Leathem (JIRA)

Brian Leathem created RF-11898: ---------------------------------- Summary: Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display Key: RF-11898 URL: https://issues.jboss.org/browse/RF-11898 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Leathem Attaching a contextMenu to a h:graphicImage results in a contextMenu that does not display. Wrapping the image with a panelGroup, and attaching the contextMenu to that panelGroup instead does not cause a problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] (RF-11750) onter() with nested tab

by Jean ANDRE (Created) (JIRA)

onter() with nested tab ----------------------- Key: RF-11750 URL: https://issues.jboss.org/browse/RF-11750 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.1.0.CR1 Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT Reporter: Jean ANDRE We put onenter() on tabs, because the actionlistener does not work very well on the first click. Some tabs are static while other are dynamically constructed. Tabs are created after a search and a new tab is created with a list of items. When a user click on item list, the content of the tab is refreshed to display detailed information. These information are displayed also inside 6 static tabs. The problems comes when we click/select these static tabs. Selecting theses tabs, trigger the onter() of the parent tab even if we stay all the time on the parent tab.... We do not known if this behavior is normal or not. The following code is the dynamic tab construction - Note the onenter() {code} <rich:tabPanel id="desktopTabPanel" switchType="ajax" headerPosition="top" activeItem="#{desktopTabController.activeTab}"> <rich:tab id="tab-workitems" name="tab-workitems" header="#{msg['desktop.tab.workitems']}" onenter="enterTab('#{tab.id}')">    </rich:tab> <rich:tab id="tab-search" name="tab-search" header="#{msg['desktop.tab.search']}" onenter="enterTab('#{tab.id}')">    <a4j:outputPanel id="toggleSearchOutput">    <a4j:commandButton id="toggleCommandSearch" value="#{msg[desktopTabController.toggleSearchLabel]}" actionListener="#{desktopTabController.doToggleSearch}" render="toggleSearchOutput" immediate="true"> </a4j:commandButton> <br /> <br />    <ui:include src="client/searchClient.xhtml" />    <ui:include src="workitems/searchWorkItems.xhtml" /> </a4j:outputPanel> </rich:tab> <c:forEach items="#{desktopTabController.desktopTabBean.tabElements}" var="tab"> <rich:tab id="#{tab.id}" name="#{tab.id}" actionListener="#{desktopTabController.doTabListener}" onenter="enterTab('#{tab.id}')">    <f:facet name="header"> <h:panelGrid id="tab-header-#{tab.id}" columns="2" title="#{desktopTabController.getTabHeader(tab.id)}"> <h:outputText value="#{desktopTabController.getAdjustedTabHeader(tab.id)}" /> <h:commandButton image="/images/closeButton.png" styleClass="closeButton" action="#{desktopTabController.doCloseTab(tab.id)}" /> </h:panelGrid> </f:facet> <ui:fragment rendered="#{tab.isTabClient}">    <ui:include src="client/listClient.xhtml" /> </ui:fragment> <ui:fragment rendered="#{tab.isTabWorkItems}">    <ui:include src="workItems/listWorkItems.xhtml" /> </ui:fragment> </rich:tab> </c:forEach> </rich:tabPanel> </h:form> {code} The onenter function definition. This function set only the selectedTab variable in the backing bean {code} <a4j:jsFunction id="enterTab" name="enterTab" action="#{desktopTabController.doEnterTab}" render="menu-opened-tabs"> <a4j:param name="tabId" assignTo="#{desktopTabController.activeTab}" /> </a4j:jsFunction> {code} The onenter function inside the backing-bean {code} public String doEnterTab() { // we just need to set the activeTab because actionListener is not working // for the first click - Bug has been reported by other users. return OUTCOME_DESKTOP; } {code} The following code is the nested tabs - Those tabs appears when the use click on the item from a list. {code} <rich:tabPanel switchType="client" headerPosition="top"> <rich:tab header="#{msg['client.tab.summary']}">    <ui:include src="summaryClient.xhtml" /> </rich:tab> <rich:tab header="#{msg['client.tab.info']}">    <ui:include src="infoClient.xhtml" /> </rich:tab> <rich:tab header="#{msg['client.tab.products']}">    </rich:tab> <rich:tab header="#{msg['client.tab.phone.address']}">    </rich:tab> <rich:tab header="#{msg['client.tab.history']}">    </rich:tab> <rich:tab header="#{msg['client.tab.workitems']}">    </rich:tab> </rich:tabPanel> {code} Then, each time we click on these nested tabs, the parent tab call the onenter(). See the screen capture for better understanding of the scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
8
0 / 0

[JBoss JIRA] (RF-11906) Warning when JMS integration is off but JMS is available

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11906: ------------------------------- Summary: Warning when JMS integration is off but JMS is available Key: RF-11906 URL: https://issues.jboss.org/browse/RF-11906 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Reporter: Lukáš Fryč Fix For: 4.2.0.CR1 For JMS detection, following algorithms can be used: * JMS API class detection * JNDI binding {{java://ConnectionFactory}} can be checked {{PushServlet}} can be used as place for triggering detection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (RF-11892) Push: turn on JMS integration by default

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11892: ------------------------------- Summary: Push: turn on JMS integration by default Key: RF-11892 URL: https://issues.jboss.org/browse/RF-11892 Project: RichFaces Issue Type: Task Security Level: Public (Everyone can see) Components: component-push/poll Affects Versions: 4.1.0.Final, 4.0.0.Final Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.2.0.CR1 On team meeting [1], we have discussed necessity to simplify configuration of Push in order to simplify starting with push for new users. I suggest to replace current configuration {{org.richfaces.push.jms.disable}} with {{org.richfaces.push.jms.enable}}, leaving previous one with no effect or providing warning. [1] https://community.jboss.org/wiki/RichFacesTeamMeetingAgenda2012-01-17 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] (RF-11907) Push: added context-param switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup)

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-11907: ------------------------------- Summary: Push: added context-param switch for PushContext initialization on startup (org.richfaces.push.initializeOnStartup) Key: RF-11907 URL: https://issues.jboss.org/browse/RF-11907 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: core Affects Versions: 4.2.0.CR1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.2.0.CR1 For applications like Showcase which are accessing {{TopicsContext}} from non-{{FacesContext}} threads, {{PushContext}} needs to be initialized from the thread which have {{FacesContext}}/{{ExternalContext}} accessible. These applications are typically pushing messages to the topic periodically or they receive messages externally (JMS). New switch {{org.richfaces.push.initializeOnStartup}} should be {{false}} by default, since regular usage of Push does not require so early initialization. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (RF-11483) Elegant way for Push topic creating

by Lukáš Fryč (Created) (JIRA)

Elegant way for Push topic creating ----------------------------------- Key: RF-11483 URL: https://issues.jboss.org/browse/RF-11483 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-push/poll, core Affects Versions: 4.1.0.Milestone1 Reporter: Lukáš Fryč Assignee: Lukáš Fryč Fix For: 4.1.0.CR1 Currently, topics have to be initialized with similar class: https://github.com/richfaces/showcase/blob/4.1.0.20110910-M2/src/main/jav... I suggest to create topic on demand (lazily), when it is accessed first. It needs following changes: * {{PushRendererBase}} - will create Topic for @address attribute * {{JMSTopicsContextImpl}} - will create topic when JMS message received * {{PushObserverMethod}} - will create topic when @Push event for given topic observed * ... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

5
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues January 2012