[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:
------------------------------------
Thanks for digging in [~jyeary], the additional info you provided will help us in resolving the issue.
> 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, dragdrop-test.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
11 years, 7 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by John Yeary (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
John Yeary commented on RF-12675:
---------------------------------
One of our engineers confirmed the issue, but also confirmed a work-around. If you remove the rich drag indicator from the application it will function normally. So the issue appears to be focused on the DnD indicator.
> 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, dragdrop-test.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
11 years, 7 months
[JBoss JIRA] (RF-12675) Drag and drop doesn't work with MyFaces
by John Yeary (JIRA)
[ https://issues.jboss.org/browse/RF-12675?page=com.atlassian.jira.plugin.s... ]
John Yeary updated RF-12675:
----------------------------
Attachment: dragdrop-test.zip
The dragdrop-test example is based off of the RichFaces Showcase and does not have any Spring related libs/configuration to confuse the issue.
> 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, dragdrop-test.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
11 years, 7 months
[JBoss JIRA] (RF-13056) Showcase - delete unused configuration for GAE
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13056?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13056:
-----------------------------
Description:
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{src/main/java-gae}}
* {{src/main/webapp-gae}}
* {{src/main/resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}} to avoid worse consequences in the future.
was:
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{src/main/java-gae}}
* {{src/main/webapp-gae}}
* {{src/main/resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
> Showcase - delete unused configuration for GAE
> ----------------------------------------------
>
> Key: RF-13056
> URL: https://issues.jboss.org/browse/RF-13056
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
>
> There are some files and configuration for Google App Engine in the showcase.
> IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
> Here is the list of files/configs which are redundant IMHO:
> * {{src/main/java-gae}}
> * {{src/main/webapp-gae}}
> * {{src/main/resources/logging.properties}}
> * {{pom.xml}} - profile for gae
> There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
> {code}
> 13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
> {code}
> According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}} to avoid worse consequences in the future.
--
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
11 years, 7 months
[JBoss JIRA] (RF-13056) Showcase - delete unused configuration for GAE
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13056?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13056:
-----------------------------
Description:
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{src/main/java-gae}}
* {{src/main/webapp-gae}}
* {{src/main/resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
was:
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{java-gae}}
* {{webapp-gae}}
* {{resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
> Showcase - delete unused configuration for GAE
> ----------------------------------------------
>
> Key: RF-13056
> URL: https://issues.jboss.org/browse/RF-13056
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
>
> There are some files and configuration for Google App Engine in the showcase.
> IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
> Here is the list of files/configs which are redundant IMHO:
> * {{src/main/java-gae}}
> * {{src/main/webapp-gae}}
> * {{src/main/resources/logging.properties}}
> * {{pom.xml}} - profile for gae
> There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
> {code}
> 13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
> {code}
> According [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
--
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
11 years, 7 months
[JBoss JIRA] (RF-13056) Showcase - delete unused configuration for GAE
by Juraj Húska (JIRA)
[ https://issues.jboss.org/browse/RF-13056?page=com.atlassian.jira.plugin.s... ]
Juraj Húska updated RF-13056:
-----------------------------
Description:
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{src/main/java-gae}}
* {{src/main/webapp-gae}}
* {{src/main/resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
was:
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{src/main/java-gae}}
* {{src/main/webapp-gae}}
* {{src/main/resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
> Showcase - delete unused configuration for GAE
> ----------------------------------------------
>
> Key: RF-13056
> URL: https://issues.jboss.org/browse/RF-13056
> Project: RichFaces
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: build/distribution, showcase
> Affects Versions: 5.0.0.Alpha1
> Reporter: Juraj Húska
> Priority: Minor
>
> There are some files and configuration for Google App Engine in the showcase.
> IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
> Here is the list of files/configs which are redundant IMHO:
> * {{src/main/java-gae}}
> * {{src/main/webapp-gae}}
> * {{src/main/resources/logging.properties}}
> * {{pom.xml}} - profile for gae
> There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
> {code}
> 13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
> {code}
> According to [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
--
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
11 years, 7 months
[JBoss JIRA] (RF-13056) Showcase - delete unused configuration for GAE
by Juraj Húska (JIRA)
Juraj Húska created RF-13056:
--------------------------------
Summary: Showcase - delete unused configuration for GAE
Key: RF-13056
URL: https://issues.jboss.org/browse/RF-13056
Project: RichFaces
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: build/distribution, showcase
Affects Versions: 5.0.0.Alpha1
Reporter: Juraj Húska
Priority: Minor
There are some files and configuration for Google App Engine in the showcase.
IMHO now when we are promoting OpenShift instead we should get rid of these files/configs.
Here is the list of files/configs which are redundant IMHO:
* {{java-gae}}
* {{webapp-gae}}
* {{resources/logging.properties}}
* {{pom.xml}} - profile for gae
There is one trivial consequence of this files being there. When deploying showcase on EAP 6.1.0 there is a warning:
{code}
13:31:55,800 WARN [org.jboss.as.logging] (MSC service thread 1-6) JBAS011510: The configuration file in 'logging.properties' appears to be a J.U.L. configuration file. The log manager does not allow this type of configuration file.
{code}
According [this|https://github.com/wildfly/wildfly/pull/3252] pull request it is expected. IMHO we should at least delete the mentioned {{logging.properties}} as it is used only for {{showcase-gae.war}}.
--
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
11 years, 7 months
[JBoss JIRA] (RF-13046) EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
by Jiří Štefek (JIRA)
[ https://issues.jboss.org/browse/RF-13046?page=com.atlassian.jira.plugin.s... ]
Jiří Štefek edited comment on RF-13046 at 6/10/13 3:23 AM:
-----------------------------------------------------------
+1 for the 2nd.
When a single EDT is used:
# and @frozenColumns=#total columns
** vertical scrollbar is there (OK)
** no horizontal scrollbar (should be OK without yours 2nd proposal)
** 'footer' facet is rendered (page scroller in the sample) (OK)
** all is OK
When 2 EDTs are used:
# and @frozenColumns=#total columns
** no vertical scrollbar (BAD)
** 'footer' facet is not -rendered- visible (page scroller in the sample) (BAD)
** no horizontal scrolbar (should be OK without yours 2nd proposal)
** no custom columns from the outer EDT (BAD)
Added screenshot EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols (red color marked areas are missing when @frozenColumns= #total columns).
was (Author: jstefek):
+1 for the 2nd.
When a single EDT is used:
# and @frozenColumns=#total columns
** vertical scrollbar is there (OK)
** no horizontal scrollbar (should be OK without yours 2nd proposal)
** 'footer' facet is rendered (page scroller in the sample) (OK)
** all is OK
When 2 EDTs are used:
# and @frozenColumns=#total columns
** no vertical scrollbar (BAD)
** 'footer' facet is not rendered (page scroller in the sample) (BAD)
** no horizontal scrolbar (should be OK without yours 2nd proposal)
** no custom columns from the outer EDT (BAD)
Added screenshot EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols (red color marked areas are missing when @frozenColumns= #total columns).
> EDT in EDT: when @frozenColumns is equal to number of columns then there is no vertical scroller in EDT
> -------------------------------------------------------------------------------------------------------
>
> Key: RF-13046
> URL: https://issues.jboss.org/browse/RF-13046
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Environment: RichFaces 5.0.0-SNAPSHOT
> Metamer 5.0.0-SNAPSHOT
> GlassFish Server Open Source Edition 3.1.2.2
> Java(TM) SE Runtime Environment 1.7.0_21-b11 @ Linux
> Firefox 18.0 @ Linux x86_64
> Reporter: Jiří Štefek
> Assignee: Brian Leathem
> Attachments: EDTinEDTmaxFrozenColumnsNoScrollers.png, EDTinEDTmaxFrozenColumnsScrollersAfterColumnReposition.png, EDTinEDTWhenNoFrozenColsOrWhenFrozenColsLesserThanMaxCols.png
>
>
> EDT(1st) in EDT(2nd), when @frozenColumns (of 1st) is equal to number of columns (of 1st), then there is no vertical scroller in EDT (1st). But when you reorganize the columns (of 1st), the scroller and the 'footer' facet appears (1st).
--
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
11 years, 7 months