[
https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s...
]
John Yeary commented on RF-12675:
---------------------------------
This issue is extremely critical on WebSphere. If you choose to use JSF + CDI, you only
have one choice MyFaces + OpenWebbeans. As a result, you can not navigate around the issue
using Mojarra. That is not an option, and is unsupported on Websphere. It is noted in the
[IBM Websphere 8 Network Deployment Manual|
http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm...]
{quote}
Only the default JSF implementation (based on MyFaces) is supported for use with CDI.
{quote}
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
Priority: Critical
Labels: Drag, drop, myfaces
Fix For: 5-Tracking
Attachments: dragAndDrop.zip
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