[JBoss JIRA] (RF-13547) @ResourceDependency with missing resource doesn't throw an exception
by Lukáš Macko (JIRA)
Lukáš Macko created RF-13547:
--------------------------------
Summary: @ResourceDependency with missing resource doesn't throw an exception
Key: RF-13547
URL: https://issues.jboss.org/browse/RF-13547
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: cdk
Reporter: Lukáš Macko
If there is an annotation {{@ResourceDependency}} with not existing resource
such as {{@ResourceDependency(library = "org.richfaces", name = "base-component.reslib")}}
It doesn't throw an exception. However, exception CacheLoader returned null for key org.richfaces:base-component.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13546) Forge plugin: support for Servlet or JavaEE containers
by Juraj Húska (JIRA)
Juraj Húska created RF-13546:
--------------------------------
Summary: Forge plugin: support for Servlet or JavaEE containers
Key: RF-13546
URL: https://issues.jboss.org/browse/RF-13546
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 5.0.0.Alpha3
Reporter: Juraj Húska
Priority: Minor
There should be taken similar approach as in RF-13545 for RichFaces Forge plugin.
That is to ask whether an user wants Servlet or Java EE container, and then create a profile for it.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13545) Simpleapp: Support for servlets/Java EE containers at generation time
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13545?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13545:
-----------------------------
Priority: Minor (was: Major)
> Simpleapp: Support for servlets/Java EE containers at generation time
> ---------------------------------------------------------------------
>
> Key: RF-13545
> URL: https://issues.jboss.org/browse/RF-13545
> Project: RichFaces
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: archetype
> Affects Versions: 5.0.0.Alpha3
> Environment: simpleapp archetype
> Reporter: Juraj Húska
> Priority: Minor
>
> In [this|https://community.jboss.org/message/857393#857393] discussion [~bleathem] wrote:
> {quote}
> I'd like to see us support both servlet and EE containers with our archetypes at generation time. We'd build in the archetype conditional asking the user if the generated project should target EE or servlet containers. This should also be done in our Forge plugin.
> {quote}
> {quote}
> Taking a profile approach leaves a lot of unnecessary clutter in their pom.xml. whereas asking at archetype evaluation time we can trim the unnecessary pieces out of the pom.xml.
> {quote}
--
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
10 years, 4 months
[JBoss JIRA] (RF-13545) Simpleapp: Support for servlets/Java EE containers at generation time
by Juraj Húska (JIRA)
Juraj Húska created RF-13545:
--------------------------------
Summary: Simpleapp: Support for servlets/Java EE containers at generation time
Key: RF-13545
URL: https://issues.jboss.org/browse/RF-13545
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: archetype
Affects Versions: 5.0.0.Alpha3
Environment: simpleapp archetype
Reporter: Juraj Húska
In [this|https://community.jboss.org/message/857393#857393] discussion [~bleathem] wrote:
{quote}
I'd like to see us support both servlet and EE containers with our archetypes at generation time. We'd build in the archetype conditional asking the user if the generated project should target EE or servlet containers. This should also be done in our Forge plugin.
{quote}
{quote}
Taking a profile approach leaves a lot of unnecessary clutter in their pom.xml. whereas asking at archetype evaluation time we can trim the unnecessary pieces out of the pom.xml.
{quote}
--
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
10 years, 4 months
[JBoss JIRA] (RF-12762) Duplicate id problem in ExtendedDatatable with dynamic columns
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12762?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak reassigned RF-12762:
----------------------------------
Assignee: Matej Novotny (was: Pavol Pitonak)
> Duplicate id problem in ExtendedDatatable with dynamic columns
> --------------------------------------------------------------
>
> Key: RF-12762
> URL: https://issues.jboss.org/browse/RF-12762
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.CR1
> Environment: Windows 7 , weblogic10.4.3, Myfaces 2.1.10, IE 9, FireFox 14.0.1
> Reporter: blam lam
> Assignee: Matej Novotny
>
> When the ExtendedDataTable contains dynamic columns (i.e. using for:each), "java.lang.IllegalStateException: component with duplicate id" will occur after the second submit from a commandButton.
> The problem does not appear in 4.2.3 Final but found in 4.3 CR1
> Sample source code:
> {code}
> <h:form id="frmMarkUpdate">
> <a4j:outputPanel id="resultPanel">
> <rich:extendedDataTable id="studentVoMarkInputTab"
> value="#{updateMarkBean.studentVoMarkAmends}"
> var="studVo"
> selectionMode="none"
> height="100%">
>
> <rich:column width="200px" >
> <f:facet name="header">
> Status
> </f:facet>
> <h:outputText value="#{studVo.student.markAmendStatus}" />
> </rich:column>
>
> <c:forEach items="#{updateMarkBean.taskVos}" var="tvo" varStatus="s">
> <rich:column width="100px">
> <f:facet name="header">
> <h:outputText value="#{tvo.task.taskName}" />
> </f:facet>
> <h:inputText id="task#{s.index}_amk"
> value="#{studVo.getTaskMarkMap().get(tvo.task.taskId).amendedMark}"
> size="1" maxlength="3"/>
> </rich:column>
> </c:forEach>
> </rich:extendedDataTable>
>
> <a4j:commandButton id="btnSave" value="Save"
> action="#{updateMarkBean.doBeforeSave}"
> styleClass="button blue">
> </a4j:commandButton>
>
> </a4j:outputPanel>
> </h:form>
> {code}
--
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
10 years, 4 months
[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel
by Kaveh A. (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
Kaveh A. commented on RF-12682:
-------------------------------
Hi Pavol
There is really no need to create another issue. This issue was never fixed. With every new release of RichFaces we have to open the jars and make the above modifications to get it to work for us. This issue is more of a display issue for extended data table where some columns (usually non-forzen columns) will disappear.
This only happens when the table is hidden during the load and then it is made visible. Feel free to use the attached program to reproduce. In this particular case the extended data table is hidden in one of the tabs of tabPanel but any parent component that hides the extended data table during the load and then un-hides it will have this issue. It is critical to note that extended data table should be empty to reproduce this error.
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1, 4.3.0.Final
> Reporter: Kaveh A.
> Labels: extendedDataTable, render, richfaces, tabpanel, testcase_provided
> Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
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
10 years, 4 months
[JBoss JIRA] (RF-13531) selects: cannot select option on IE11
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13531:
------------------------------------
Sorry, I missed that the keyboard was broken to when reading the description.
I've removed use of the keypress event for listening for "special" keys. I tested in recent Chrome, Firefox and IE and it works. There is a chance this breaks in old Firefox, but I don't have access to it. @QE please take this into consideration when testing the fix.
> selects: cannot select option on IE11
> -------------------------------------
>
> Key: RF-13531
> URL: https://issues.jboss.org/browse/RF-13531
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3
> Environment: IE 11
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Labels: IE11
> Fix For: 4.3.6
>
>
> Components: autocomplete, select, inplaceSelect.
> Works on IE 10.
> ----
> Issues:
> * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class.
> ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}.
> ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller.
> * User cannot select option with keyboard.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13531) selects: cannot select option on IE11
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13531?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13531:
-------------------------------
Labels: IE11 needs-qe (was: IE11)
> selects: cannot select option on IE11
> -------------------------------------
>
> Key: RF-13531
> URL: https://issues.jboss.org/browse/RF-13531
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.3.5, 4.5.0.Alpha2, 5.0.0.Alpha3
> Environment: IE 11
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Labels: IE11, needs-qe
> Fix For: 4.3.6
>
>
> Components: autocomplete, select, inplaceSelect.
> Works on IE 10.
> ----
> Issues:
> * User cannot visually select an option from the popup list == moving mouse over the items in the list will not change theirs class.
> ** however clicking on the item will select the option correctly. {color:red}EXCEPT autocomplete (RF4), where it will not select anything{color}.
> ** workaround: the item can be selected, when moving off the list and back to it on the correct item, but the cursor should not move through scroller.
> * User cannot select option with keyboard.
--
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
10 years, 4 months
[JBoss JIRA] (RF-13543) When r:ajax nested in r:select and event=keyup then error is thrown
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13543?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13543:
-------------------------------
Fix Version/s: 5.0.0.Alpha4
> When r:ajax nested in r:select and event=keyup then error is thrown
> -------------------------------------------------------------------
>
> Key: RF-13543
> URL: https://issues.jboss.org/browse/RF-13543
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 5.0.0.Alpha2, 5.0.0.Alpha3
> Reporter: Juraj Húska
> Labels: regression
> Fix For: 5.0.0.Alpha4
>
>
> Nested {{r:ajax}} with event set to {{keyup}} in {{r:select}} component causes this error being thrown when rendering such a page:
> {code}
> javax.faces.view.facelets.TagException: /index.xhtml @21,62 <r:ajax> keyupevent is not supported for the UISelect
> org.richfaces.ui.ajax.ajax.AjaxHandler.resolveEventName(AjaxHandler.java:209)
> org.richfaces.ui.ajax.ajax.AjaxHandler.applyNested(AjaxHandler.java:190)
> org.richfaces.ui.ajax.ajax.AjaxHandler.apply(AjaxHandler.java:133)
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190)
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190)
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
> com.sun.faces.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:106)
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:201)
> com.sun.faces.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:395)
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:366)
> com.sun.faces.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:111)
> javax.faces.view.facelets.DelegatingMetaTagHandler.applyNextHandler(DelegatingMetaTagHandler.java:137)
> org.richfaces.ui.behavior.BehaviorsAddingComponentHandlerWrapper.applyNextHandler(BehaviorsAddingComponentHandlerWrapper.java:53)
> com.sun.faces.facelets.tag.jsf.ComponentTagHandlerDelegateImpl.apply(ComponentTagHandlerDelegateImpl.java:190)
> javax.faces.view.facelets.DelegatingMetaTagHandler.apply(DelegatingMetaTagHandler.java:120)
> javax.faces.view.facelets.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:95)
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:312)
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:371)
> com.sun.faces.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:350)
> com.sun.faces.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:199)
> com.sun.faces.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:169)
> com.sun.faces.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:93)
> com.sun.faces.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:87)
> com.sun.faces.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:161)
> com.sun.faces.application.view.FaceletViewHandlingStrategy.buildView(FaceletViewHandlingStrategy.java:980)
> com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:99)
> com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
> com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:219)
> javax.faces.webapp.FacesServlet.service(FacesServlet.java:647)
> {code}
> Issue is regression in 5.0.0.Alpha2, in other words it worked in older releases.
--
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
10 years, 4 months