You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2006/11/17 08:46:58 UTC

[jira] Closed: (WW-115) Circularity check in AbstractWalker when objects in list referrences common object

     [ http://issues.apache.org/struts/browse/WW-115?page=all ]

Don Brown closed WW-115.
------------------------

    Resolution: Not A Problem

> Circularity check in AbstractWalker when objects in list referrences common object
> ----------------------------------------------------------------------------------
>
>                 Key: WW-115
>                 URL: http://issues.apache.org/struts/browse/WW-115
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Views
>    Affects Versions: WW 1.4
>         Environment: JBoss 3.0.4; xdoclet 1.2.
>            Reporter: Peter Antman
>         Assigned To: Dick Zetterberg
>
> This problem shows up under the following conditions:
> 1. Trying to create a HTML table with XSLT (for example).
> 2. Having a method in the actions that returns a collection.
> 3. The collection returned contains xdoclet created "value objects" for EJB 2.0
> 4. Each value object holds a (many)-to one relationship with another EJB, whose value object is part of the value objects in list.
> 5. The entity on the other side of the relation may belong to more than one of the entities in the list.
> 6. The value object returned from the entity on the foreign side will be the same object instance for all objects that holds this releation.
> The net result is that one will only get at the same value object once: and it is therefore not possible to list the values in a simple way.
> Example: say we have Party and PartyType. We have A party A with a relation to PartyType 1 and we have a Party be also with a relation with  PartyType 1. When the walker walks a list a Partys the relation will only be walked the first time. When the walker walks Party B and finds a PartyType 1 it will log and return:
>       if (walkedInstances.contains(value))
>       {
>          LogFactory.getLog(this.getClass()).debug(attributeName + " alreay walked, cutting circular reference.");
>          return;
>       }
> This I would guess it not correct behaviour in circumstances like the one described above.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira