[
https://issues.jboss.org/browse/RF-12671?page=com.atlassian.jira.plugin.s...
]
Ken H commented on RF-12671:
----------------------------
I just wanted to add a minor note that I have used the majority of the other input
components inside this ajax-switched dynamic tab configuration without any issue. The
issue appears to be something specific to the handling of dropListener.
dropTarget does not work inside dynamic tabs when switchType is ajax
or server
------------------------------------------------------------------------------
Key: RF-12671
URL:
https://issues.jboss.org/browse/RF-12671
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.0.M3
Reporter: Ken H
The following works fine:
{code}
<rich:tabPanel switchType="client">
<a4j:repeat value="#{bean.thingsToIterate}" var="thing">
<rich:tab header="Tab #{thing}">
<rich:panel style="width: 100px;">
<rich:dragSource dragValue="drag-#{thing}" type="term"
/>
drag #{thing}
</rich:panel>
<rich:panel style="width: 100px;">
<rich:dropTarget dropValue="drop-#{thing}"
acceptedTypes="term" dropListener="#{bean.processDrop}"
execute="@form" render="@form" />
drop #{thing}
</rich:panel>
</rich:tab>
</a4j:repeat>
</rich:tabPanel>
public void processDrop(DropEvent evt) {
log.info("processDrop called - dragVal: "+evt.getDragValue()+", dropVal:
"+evt.getDropValue());
}
{code}
However, changing the switch type to ajax or server results in processDrop not being
called. The POST data appears to be identical.
--
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