You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by Brian McCallister <mc...@forthillcompany.com> on 2004/01/13 18:51:10 UTC

[bug] Collection Proxy & OTM bug in CVS HEAD

With the following mapping:

<collection-descriptor
         name="entries"
         element-class-ref="com.forthillcompany.infra.time.Entry"
         proxy="true"
          
collection- 
class="org.apache.ojb.broker.util.collections.ManageableArrayList"
     >
         <orderby name="start" sort="DESC"/>
         <inverse-foreignkey field-ref="accountId"/>
     </collection-descriptor>

Changes to elements in this collection are not stored if the parent is  
retrieved via OTM and an OQLQuery. If the proxy attribute is removed  
(or set to false) changes to elements in the collection are stored.

No test case available yet (well, there is in the app i am working on,  
but none in our cvs yet).

-Brian



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

Re: [bug] Collection Proxy & OTM bug in CVS HEAD

Posted by Oleg Nitz <on...@ukr.net>.
Hi Brian,

I think I've fixed this bug, at least my test succeeds, could you re-run your 
test? 

Thanks,
 Oleg

On Tuesday 13 January 2004 17:51, Brian McCallister wrote:
> With the following mapping:
>
> <collection-descriptor
>          name="entries"
>          element-class-ref="com.forthillcompany.infra.time.Entry"
>          proxy="true"
>
> collection-
> class="org.apache.ojb.broker.util.collections.ManageableArrayList"
>
>          <orderby name="start" sort="DESC"/>
>          <inverse-foreignkey field-ref="accountId"/>
>      </collection-descriptor>
>
> Changes to elements in this collection are not stored if the parent is
> retrieved via OTM and an OQLQuery. If the proxy attribute is removed
> (or set to false) changes to elements in the collection are stored.
>
> No test case available yet (well, there is in the app i am working on,
> but none in our cvs yet).
>
> -Brian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

Re: [bug] Collection Proxy & OTM bug in CVS HEAD

Posted by Oleg Nitz <on...@ukr.net>.
Hi Brian,

Thanks for reporting, I will fix this ASAP.

Regards,
 Oleg

On Tuesday 13 January 2004 17:51, Brian McCallister wrote:
> With the following mapping:
>
> <collection-descriptor
>          name="entries"
>          element-class-ref="com.forthillcompany.infra.time.Entry"
>          proxy="true"
>
> collection-
> class="org.apache.ojb.broker.util.collections.ManageableArrayList"
>
>          <orderby name="start" sort="DESC"/>
>          <inverse-foreignkey field-ref="accountId"/>
>      </collection-descriptor>
>
> Changes to elements in this collection are not stored if the parent is
> retrieved via OTM and an OQLQuery. If the proxy attribute is removed
> (or set to false) changes to elements in the collection are stored.
>
> No test case available yet (well, there is in the app i am working on,
> but none in our cvs yet).
>
> -Brian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org