[
https://issues.apache.org/jira/browse/JS2-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710581#action_12710581
]
Randy Watler commented on JS2-1015:
-----------------------------------
The change to PersistenceBrokerPortletRegistry.java is not strictly necessary,
but it is more in line with the existing PA and PD APIs. I had originally made
this change to ensure that construction of the cloned PD followed existing PD
creation paradigms while debugging. We can remove it if desired.
> Unattached portlet definitions left in DB after registry unit tests run
> -----------------------------------------------------------------------
>
> Key: JS2-1015
> URL: https://issues.apache.org/jira/browse/JS2-1015
> Project: Jetspeed 2
> Issue Type: Bug
> Components: Portlet Registry, Testing
> Affects Versions: 2.2.0
> Environment: J2 2.2 trunk
> JDK6/Linux/x86_64
> Reporter: Randy Watler
> Assignee: Randy Watler
> Fix For: 2.2.1
>
> Attachments: page-manager-ojb-collections.patch,
> registry-ojb-collections.patch
>
>
> Portlet definition clone tests fail to properly clean up after cloned portlet
> definition is removed in unit tests. On the next unit test case invocation
> w/o clearing the database, queries for all portlet definitions fail when
> orphaned portlet definitions w/o a portlet applications are added to the
> registry cache and fail.
> Preliminary investigation indicates that the registry OM is not utilizing
> removal aware collections for persistent collections, but the test cases are
> trying to remove persistent members using operations on the transient
> collection implementations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-dev-h...@portals.apache.org
