[
https://issues.jboss.org/browse/RF-10992?page=com.atlassian.jira.plugin.s...
]
Brian Leathem updated RF-10992:
-------------------------------
Fix Version/s: 4.Future
(was: 4.1.0.Final)
Description:
When the dragValue is set in a customcomponent, it's always evaluated to null.
(dropEvent.getDragValue() == null)
If a stringvalue is set instead, the value is submitted correctly.
Example:
{code}
<rich:dragSource type="sometype"
dragValue="#{cc.attrs.myvalue}"/>
{code}
same code outside of the customcomponent works fine.
was:
When the dragValue is set in a customcomponent, it's always evaluated to null.
(dropEvent.getDragValue() == null)
If a stringvalue is set instead, the value is submitted correctly.
Example:
<rich:dragSource type="sometype"
dragValue="#{cc.attrs.myvalue}"/>
same code outside of the customcomponent works fine.
Steps to Reproduce:
create a customcomponent like the following:
{code}
<composite:interface>
<composite:attribute name="myvalue" />
</composite:interface>
<composite:implementation>
<h:form>
<a4j:outputPanel>
<rich:dragSource type="sometype"
dragValue="#{cc.attrs.myvalue}"/>
...
</a4j:outputPanel>
</h:form>
</composite:implementation>
{code}
and a <rich:dropTarget ... somewhere else.
was:
create a customcomponent like the following:
...
<composite:interface>
<composite:attribute name="myvalue" />
</composite:interface>
<composite:implementation>
<h:form>
<a4j:outputPanel>
<rich:dragSource type="sometype"
dragValue="#{cc.attrs.myvalue}"/>
...
</a4j:outputPanel>
</h:form>
</composite:implementation>
and a <rich:dropTarget ... somewhere else.
Labels: customcomponent (was: customcomponent draganddrop needs-qe
richfaces)
Assignee: (was: Brian Leathem)
Component/s: third-party
Looks like the problem stems from upstream with JAVASERVERFACES-2009/MYFACES-3283:
{quote}
The main problem is that if you reference a property of child component anywhere outside
of the composite (i.e. in an action method, a component system event, etc.), it simply
will not work if it was set to a composite component attribute (i.e.
_#\{cc.attrs.property}_).
{quote}
Confirmed by taking the _dragValue_ assigned to the composite component, and applying it
directly to the _dragSource_ (iow not using the _cc.attrs.dragSource_ peroperty), and the
metamer sample works.
Feel free to comment/vote on the upstream issue, to see it resolved.
dragValue expression is evaluated to null in customcomponent
------------------------------------------------------------
Key: RF-10992
URL:
https://issues.jboss.org/browse/RF-10992
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-drag/drop, third-party
Affects Versions: 4.0.0.Final
Environment: JSF2 environment with Richfaces 4 Final
Reporter: Adrian Höhn
Labels: customcomponent
Fix For: 4.Future
Attachments: dnd.png
When the dragValue is set in a customcomponent, it's always evaluated to null.
(dropEvent.getDragValue() == null)
If a stringvalue is set instead, the value is submitted correctly.
Example:
{code}
<rich:dragSource type="sometype"
dragValue="#{cc.attrs.myvalue}"/>
{code}
same code outside of the customcomponent works fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira