[JBoss JIRA] (RF-13098) Regression: mediaOutput broken for CDI MediaData beans
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13098?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-13098:
-------------------------------
Original Estimate: 1 hour (was: 2 hours)
Remaining Estimate: 1 hour (was: 2 hours)
> Regression: mediaOutput broken for CDI MediaData beans
> ------------------------------------------------------
>
> Key: RF-13098
> URL: https://issues.jboss.org/browse/RF-13098
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core
> Affects Versions: 4.3.3
> Reporter: Marek Schmidt
> Assignee: Brian Leathem
> Labels: regression
> Fix For: 4.3.4
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> https://issues.jboss.org/browse/RF-13089 introduced a regression for a4j:mediaOutput component
> Having a
> {code}
> <a4j:mediaOutput element="img" cacheable="true" session="true" createContent="#{mediaBean.paint}" value="#{mediaData}" mimeType="image/jpeg"/>
> {code}
> with mediaData being a CDI bean, e.g.
> {code}
> @javax.inject.Named("mediaData")
> @javax.enterprise.context.RequestScoped
> public class MediaData implements Serializable
> {code}
> the following exception occurs:
> {code}10:39:27,997 SEVERE [org.richfaces.log.Resource] (http-/127.0.0.1:8080-1) Input error for deserialize data : java.io.InvalidClassException: Unauthorized deserialization attempt; org.jboss.weld.bean.proxy.util.SerializableClientProxy
> at org.richfaces.util.LookAheadObjectInputStream.resolveClass(LookAheadObjectInputStream.java:93) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1610) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1515) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1989) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1913) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1796) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1348) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1704) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1342) [rt.jar:1.7.0_25]
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) [rt.jar:1.7.0_25]
> at org.richfaces.util.Util.decodeObjectData(Util.java:237) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.DefaultCodecResourceRequestData.getData(DefaultCodecResourceRequestData.java:97) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceFactoryImpl.createResource(ResourceFactoryImpl.java:337) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at org.richfaces.resource.ResourceHandlerImpl.handleResourceRequest(ResourceHandlerImpl.java:156) [richfaces-core-impl-4.3.3.Final.jar:4.3.3.Final]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:591) [jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar:2.1.19.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> {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
12 years, 7 months
[JBoss JIRA] (RF-11275) showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11275?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-11275.
--------------------------------
Resolution: Done
Added an omitted setting of the shadow height in the show method.
> showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-11275
> URL: https://issues.jboss.org/browse/RF-11275
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.1.0.Milestone2
> Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
> container - JBoss AS 6.0.0.Final
> browser - Chrome 13, IE 9, FF 3.6
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: popupShadowWrong.png
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When I call the popup first, everything is OK. But when I change the size of popup panel, next invoked popup has double shadow at some particular part of the page. Please see the attachment.
--
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
12 years, 7 months
[JBoss JIRA] (RF-12989) Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12989?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12989:
------------------------------------
[~ciaccia] you annotated your code sample as not working, yet you used the _name_ attribute which your problem report states as working.
Assuming it's just a typo, what happens if you use the clientId of the _togglePanelItem_ in the _targetItem_ attribute?
> Documentation for togglePanelItem is wrong and 4.2.2 components are not working anymore in 4.3.0.Final
> ------------------------------------------------------------------------------------------------------
>
> Key: RF-12989
> URL: https://issues.jboss.org/browse/RF-12989
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: doc
> Affects Versions: 4.3.0.Final
> Environment: JBossAS 7.1.1
> Reporter: Andrea Martino
> Assignee: Brian Leathem
> Priority: Minor
> Labels: togglePanel, waiting_on_user
> Fix For: 4.3.4
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> In RichFaces 4.2.2 it was possible to define togglePane items using id as attribute, as following {code}<rich:togglePanelItem id="item1">{code}
> With RichFaces 4.3.0 the page does not work anymore, I had to change the attribute to name {code}<rich:togglePanelItem name="item1">{code}
> The docs still say id is valid, even when it's not [http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...]. Either the docs should be changed or id attribute should be accepted as it was before.
--
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
12 years, 7 months
[JBoss JIRA] (RF-13095) extendedDataTable tableState setter not called on column resize/reorder
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13095?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-13095.
--------------------------------
Labels: (was: waiting_on_user)
Fix Version/s: (was: 4.3.4)
Resolution: Cannot Reproduce Bug
Thanks for the confirmation [~salvois].
> extendedDataTable tableState setter not called on column resize/reorder
> -----------------------------------------------------------------------
>
> Key: RF-13095
> URL: https://issues.jboss.org/browse/RF-13095
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and Chrome 28.
> Reporter: Salvo Isaja
> Assignee: Brian Leathem
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> Not sure if this qualifies as a bug or a feature request.
> I have an extendedDataTable with the tableState attribute bound to a String property of a backing bean (tried both a request scoped bean on a transient view and a session scoped bean on a stateful view).
> When resizing or reordering columns, an Ajax request is posted to the server, and I correctly see the new column layouts in the request, but the setter of the tableState property in the backing bean is not called. If I execute @form on a a4j:commandLink or commandButton, it is called instead.
> Thanks
--
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
12 years, 7 months
[JBoss JIRA] (RF-11275) showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-11275?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-11275:
----------------------------------
Assignee: Brian Leathem
> showcase - rich:popup - Sample Modal panel - after changing the size of popup there is double shadow
> ----------------------------------------------------------------------------------------------------
>
> Key: RF-11275
> URL: https://issues.jboss.org/browse/RF-11275
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: showcase
> Affects Versions: 4.1.0.Milestone2
> Environment: richfaces-showcase-4.1.0.20110805-M1-jee6.war
> container - JBoss AS 6.0.0.Final
> browser - Chrome 13, IE 9, FF 3.6
> Reporter: Juraj Húska
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: popupShadowWrong.png
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> When I call the popup first, everything is OK. But when I change the size of popup panel, next invoked popup has double shadow at some particular part of the page. Please see the attachment.
--
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
12 years, 7 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12675:
----------------------------------
Assignee: Brian Leathem (was: Lukáš Fryč)
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Assignee: Brian Leathem
> Labels: Drag, drop, myfaces, waiting_on_user
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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
12 years, 7 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12675:
------------------------------------
The test passes fine with MyFaces 2.1.10 and Tomcat 6 with no console errors.
If you want to run the test yourself, here are the steps:
# Follow the container setup instructions here: https://github.com/richfaces/richfaces/blob/master/TESTS.md#tomcat-6---re...
#* (Note: the rest of the instructions on that page pertain to RF 5 and are not relevant for RF 4)
# From the components/dnd/ui folder, run the command:
{code}
mvn -Dtest=TestDnd -Darquillian.richfaces.jsfImplementation=org.apache.myfaces.core:myfaces-impl:2.1.10 -Pintegration-tests,tomcat-remote-6,browser-chrome,browser-remote-reusable test
{code}
If you can direct me in creating an environment where this test fails, then we can proceed with finding a fix. Even better would be a PR with appropriate changes to the test ;-)
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Assignee: Lukáš Fryč
> Labels: Drag, drop, myfaces
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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
12 years, 7 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12675:
-------------------------------
Labels: Drag drop myfaces waiting_on_user (was: Drag drop myfaces)
> Drag and drop doesn't work with MyFaces
> ---------------------------------------
>
> Key: RF-12675
> URL: https://issues.jboss.org/browse/RF-12675
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-drag/drop
> Affects Versions: 4.2.3.Final
> Environment: tomcat6
> Reporter: Anton Zukovskij
> Assignee: Lukáš Fryč
> Labels: Drag, drop, myfaces, waiting_on_user
> Fix For: 4.3.4, 5-Tracking
>
> Attachments: dragAndDrop.zip, dragdrop-test.zip
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When using simple drag and drop with myfaces JSF implementation, javascript fails on drop event:
> Uncaught clientError: Sourceform could not be determined, either because element is not attached to a form or we have multiple forms with named elements of the same identifier or name, stopping the ajax processing (jsf.js...lopment (line 8277)).
> This is caused by drag indicator is being detached from <form> and appended to body (dnd-draggable.js @ dragStart). Please see attached demo app. This issue is also reproducible on showcase application if you replace mojarra jar files with myfaces.
--
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
12 years, 7 months