Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Message-ID: <1647282120.1114427127064.JavaMail.jira@ajax.apache.org>
Date: Mon, 25 Apr 2005 13:05:27 +0200 (CEST)
From: "Martin Taal (JIRA)" <jira@apache.org>
To: ojb-dev@db.apache.org
Subject: [jira] Commented: (OJB-20) Allow the use of collection-factory
In-Reply-To: <815012224.1113331276551.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/OJB-20?page=comments#action_63645 ]
     
Martin Taal commented on OJB-20:
--------------------------------

Hi Thomas,
Thanks alot, 
I checked and it works for my testcases. I noted that the collection-factory can not be specified on the collection-descriptor but had to be specified globally, or did I miss something? 
What I did is set my collection factory on global level (ojb.properties) and forward all non-emf objects to the CollectionFactoryDefaultImpl. This works fine also.

Btw I will also try to find out if I can integrate emf collections with ojb 1.0.3 using a specific persistent field implementation (but this takes some time to research/test). 

gr. Martin

> Allow the use of collection-factory
> -----------------------------------
>
>          Key: OJB-20
>          URL: http://issues.apache.org/jira/browse/OJB-20
>      Project: OJB
>         Type: New Feature
>   Components: PB-API
>     Versions: 1.1 CVS
>     Reporter: Martin Taal
>     Assignee: Thomas Dudziak
>  Attachments: patch_coll_factory.txt
>
> Hi,
> This is a request for allowing a user to specify a collection-factory for a collection-descriptor. The collection factory is used to create collection instances when the owner of the collection is read from the database. 
> In my usecase I need to pass runtime information to the constructor of the collection (i.e. the collection needs its owning object). This is for example for handling a notification infrastructure in which changes to the collection are broadcasted to listeners who need to know from which object the notification comes. The current collection-class implementation in ojb 'only' supports zero-argument constructors which do not handle my usecase.
> I have made an implementation of the collection-factory in ojb which I will try to attach (as a patch) to this request or otherwise send to the ojb-dev mailing list. If I can be of help to get this implemented then please let me know. 
> gr. Martin Taal

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


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