[JBoss JIRA] (RF-13582) Revert the core package re-factoring
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ]
Michal Petrov commented on RF-13582:
------------------------------------
I've compared the framework with richfaces4/core and put back the classes I could. There are a few classes missing - former {{org.richfaces.webapp}} package is missing entirely, {{org.richfaces.resource}} classes were renamed/refactored. Some classes that were deprecated in 4.3.x were removed in 5.
> Revert the core package re-factoring
> ------------------------------------
>
> Key: RF-13582
> URL: https://issues.jboss.org/browse/RF-13582
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Brian Leathem
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to):
> * .servlet (PushServlet, ResourceServlet)
> * .push.cdi (@PUsh)
> * .push. (TopicContext)
> * FileUploadException
> A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures.
--
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, 2 months
[JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent"
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek commented on RF-11736:
----------------------------------
Verified. It is working with RF 5.x.
Ready to close.
----
Just one thing, what should be the behaviour of popupPanel when @top=auto and @left=auto (default attributes values)? Should not it be centered to view similarly like the `center` function here in the workaround? I have not found it in documentation (VDL, Component reference).
> rich:popupPanel x domElementAttachment="parent"
> -----------------------------------------------
>
> Key: RF-11736
> URL: https://issues.jboss.org/browse/RF-11736
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final
> Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3
> Reporter: Edilmar Alves
> Assignee: Michal Petrov
> Fix For: 5-Tracking
>
>
> rich:popupPanel repositions after second click when we use domElementAttachment="parent"
--
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, 2 months
[JBoss JIRA] (RF-13607) Tables/Menus logged warnings for invalid children
by Michael Colin (JIRA)
Michael Colin created RF-13607:
----------------------------------
Summary: Tables/Menus logged warnings for invalid children
Key: RF-13607
URL: https://issues.jboss.org/browse/RF-13607
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-menu, component-tables
Affects Versions: 4.3.4
Environment: JBoss EAP 6.1.1
Reporter: Michael Colin
Whenever you put an invalid child into a component like the rich:extendedDataTable I would expect to get an exception or a warning at the very least. Currently the component just seems to ignore those false children which makes debugging difficult (when trying to create a composite component of rich:column, for example) and might lead to false code to just stay where it is because it doesn't generate an error and is simply "forgotten".
Wrong code should generate harsh exceptions so it shows and can be fixed in a timely manner.
--
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, 2 months
[JBoss JIRA] (RF-13582) Revert the core package re-factoring
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-13582?page=com.atlassian.jira.plugin.s... ]
Michal Petrov reassigned RF-13582:
----------------------------------
Assignee: Michal Petrov
> Revert the core package re-factoring
> ------------------------------------
>
> Key: RF-13582
> URL: https://issues.jboss.org/browse/RF-13582
> Project: RichFaces
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 4.5.0.Alpha3
> Reporter: Brian Leathem
> Assignee: Michal Petrov
> Fix For: 4.5.0.Alpha3
>
>
> To improve compatibility with RichFaces 4.3, the package re-factorings introduced should be reverted. These include (but are not limited to):
> * .servlet (PushServlet, ResourceServlet)
> * .push.cdi (@PUsh)
> * .push. (TopicContext)
> * FileUploadException
> A good test for this would be to compile and run the RichFaces 4.3 showcase and metamer samples against RichFaces 4.5 looking for failures.
--
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, 2 months
[JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent"
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-11736:
------------------------------------
[~jstefek], please verify the fix.
[~christoph_w], yes, we will verify it in 5.x and then it should be backported to 4.3.
> rich:popupPanel x domElementAttachment="parent"
> -----------------------------------------------
>
> Key: RF-11736
> URL: https://issues.jboss.org/browse/RF-11736
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final
> Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3
> Reporter: Edilmar Alves
> Assignee: Michal Petrov
> Fix For: 5-Tracking
>
>
> rich:popupPanel repositions after second click when we use domElementAttachment="parent"
--
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, 2 months
[JBoss JIRA] (RF-11736) rich:popupPanel x domElementAttachment="parent"
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/RF-11736?page=com.atlassian.jira.plugin.s... ]
Michal Petrov resolved RF-11736.
--------------------------------
Resolution: Done
I've made the panel show before the sizing is determined so the sizes are obtained from the now-visible header. This shouldn't affect other things.
> rich:popupPanel x domElementAttachment="parent"
> -----------------------------------------------
>
> Key: RF-11736
> URL: https://issues.jboss.org/browse/RF-11736
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.0.0.Final
> Environment: NetBeans 7.0.0 + GlassFish 3.1.1 + JSF2 + CDI + RF4 + Hibernate3
> Reporter: Edilmar Alves
> Assignee: Michal Petrov
> Fix For: 5-Tracking
>
>
> rich:popupPanel repositions after second click when we use domElementAttachment="parent"
--
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, 2 months
[JBoss JIRA] (RF-12790) EDT/DT is broken after postback request with Mojarra 2.1.18
by Pavol Pitonak (JIRA)
[ https://issues.jboss.org/browse/RF-12790?page=com.atlassian.jira.plugin.s... ]
Pavol Pitonak commented on RF-12790:
------------------------------------
For the record:
RichFaces 4.3.6-SNAPSHOT work fine in EAP 6.2.2 and WildFly 8.0.0.
> EDT/DT is broken after postback request with Mojarra 2.1.18
> -----------------------------------------------------------
>
> Key: RF-12790
> URL: https://issues.jboss.org/browse/RF-12790
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables, regression
> Affects Versions: 4.2.3.Final, 4.3.0.Final
> Environment: RichFaces 4.3.1-SNAPSHOT
> Metamer 4.3.1-SNAPSHOT
> Mojarra 2.1.18
> JBoss AS 7.2.0.Alpha1-SNAPSHOT, Tomcat 7.0.32
> OpenJDK Runtime Environment 1.7.0_09-icedtea-mockbuild_2013_02_07_23_07-b00 @ Linux
> Chrome 24.0.1312.69 @ Linux x86_64
> Reporter: Pavol Pitonak
> Priority: Critical
> Attachments: brokenresources.zip, edt.png
>
>
> # download JBoss AS 7.2.0.Alpha1-SNAPSHOT from https://ci.jboss.org/jenkins/job/JBoss-AS-7.x-latest/lastSuccessfulBuild/...
> # deploy Metamer to the JBoss AS
> # open http://localhost:8080/metamer/faces/components/richExtendedDataTable/froz...
> # set parameter frozenColumns to 2
> result:
> * EDT is totally broken, there are JS errors in browser console
> * EDT and dataScroller resources (ecss and js) disappear from the page after postback request
> * example works fine when I remove attribute binding from the xhtml
> * worked fine with JBoss AS 7.1.1 (Mojarra 2.1.7)
> * it's not a JBoss AS bug, I can reproduce also on Tomcat with Mojarra 2.1.18
> * works fine with Mojarra 2.1.17
--
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, 2 months
[JBoss JIRA] (RF-13605) a4j:ajax button click event gets lost
by abhishek vijra (JIRA)
[ https://issues.jboss.org/browse/RF-13605?page=com.atlassian.jira.plugin.s... ]
abhishek vijra updated RF-13605:
--------------------------------
Attachment: queue.zip
> a4j:ajax button click event gets lost
> -------------------------------------
>
> Key: RF-13605
> URL: https://issues.jboss.org/browse/RF-13605
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.6
> Reporter: abhishek vijra
> Attachments: queue.zip
>
>
> Clicking on the submit button of a form containing input elements with valuechange event listeners triggers only the execution of the event listeners of the corresponding input elements, but the button click event apparently gets lost and the form isn't actually being submitted. The user has to click on the button again to finally submit it. Explicitly setting the requestDelay of an associated a4j:queue to say 200ms for all events seems to preserve the click event and the form gets submitted as expected in our specific test environment. This isn't a generally acceptable workaround though, as it introduces redundant global delay and hardly preserves the click event reliably across environments with different timing constraints.
> Attached a testcase to isolate the problem, see the attached zip file containing a minimal JSF application with a simple RichFaces-enabled form which reproduces the undesired behavior.
--
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, 2 months
[JBoss JIRA] (RF-13606) WebSphere/MyFaces in 4.3.6
by Konstantin Morozov (JIRA)
Konstantin Morozov created RF-13606:
---------------------------------------
Summary: WebSphere/MyFaces in 4.3.6
Key: RF-13606
URL: https://issues.jboss.org/browse/RF-13606
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: compatibility
Affects Versions: 4.3.6
Environment: WebSphere AS 8.0.0.8
Reporter: Konstantin Morozov
Application started successfully, but throws exception when launched:
org.richfaces.resource.external.MyFacesExternalResourceTracker handleException error while delegating resource handling to myfaces impl
java.lang.NoSuchMethodException: org.apache.myfaces.shared_impl.renderkit.html.util.ResourceUtils.isRenderedStylesheet(javax.faces.context.FacesContext, java.lang.String, java.lang.String)
at java.lang.Class.throwNoSuchMethodException(Class.java:325)
at java.lang.Class.getMethod(Class.java:939)
at org.richfaces.resource.external.MyFacesExternalResourceTracker.<init>(MyFacesExternalResourceTracker.java:52)
at org.richfaces.resource.external.ExternalResourceTrackerWrapper.getWrapped(ExternalResourceTrackerWrapper.java:94)
at org.richfaces.resource.external.ExternalResourceTrackerWrapper.markExternalResourceRendered(ExternalResourceTrackerWrapper.java:78)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.richfaces.application.ServiceTracker$1.invoke(ServiceTracker.java:153)
at com.sun.proxy.$Proxy284.markExternalResourceRendered(Unknown Source)
at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:358)
at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:270)
at org.richfaces.resource.ResourceHandlerImpl.createResource(ResourceHandlerImpl.java:280)
at com.sun.faces.renderkit.html_basic.StylesheetRenderer.encodeEnd(StylesheetRenderer.java:97)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:915)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeHeadResources(HeadRenderer.java:105)
at com.sun.faces.renderkit.html_basic.HeadRenderer.encodeEnd(HeadRenderer.java:92)
at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:915)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786)
at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782)
at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:447)
at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:124)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:286)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:120)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1071)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3774)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:981)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:277)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1702)
--
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, 2 months