[
https://issues.apache.org/jira/browse/PB-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462761
]
James May commented on PB-49:
-----------------------------
Hi Ate. Please see my responses below. Let me know if you have any further
questions.
Thanx
James
>>But, there is another, portlet spec compliant way, to obtain the windowid,
>>although it requires (temporarily)usage of the PortletSession.
>>I will use that solution instead.
Good point. I thought that the pluto imports may be a problem.
>>Furthermore, I will use the name WindowId instead of EntityId as
>>PortletWindow != PortletEntity.
Good point.
>>Secondly, your PortletActionMappingImpl extends
>>com.fmr.eps.struts.action.FMRModelDispatchActionMapping.
>>As I can't have (nor can use) the FMRModelDispatchActionMapping, I
>>removed the extends bit for now.
>>I haven't really interpreted its functionality (will do so later this
>>weekend), but if your FMRModelDispatchActionMapping provides
>>functionality I would need, please let me know ASAP.
This is my mistake. I forgot the remove that. The action mapping class should
extend the struts ActionMapping directly. I was testing in an application that
needed the FMRModelDispatchActionMapping and forgot to change it back. As far
as the functionality of PortletActionMappingImpl, it is not required for the
fix but is merely another way of declaring render attributes. Maybe having two
places to declare attributes is a
bad idea but it seems more natural to me to do this at the actionMapping level.
The PortletActionMapping can be removed all together if need be.
> Multiple instances of a struts portlet should be able to coexist on a single
> page.
> ----------------------------------------------------------------------------------
>
> Key: PB-49
> URL: https://issues.apache.org/jira/browse/PB-49
> Project: Portals Bridges
> Issue Type: Bug
> Components: struts
> Affects Versions: 1.0
> Environment: Any.
> Reporter: James May
> Assigned To: Ate Douma
> Attachments: patch-2007-01-04.zip, patch.zip
>
>
> When including multiple instances of a struts portlet on a page, form data
> for the portlet instances gets clobbered because there is a single form bean
> that is shared by all instances. Each portlet instance should be able to
> maintain its state independently of other instances.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
