Mailing-List: contact felix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: felix-dev@incubator.apache.org
Message-ID: <161989.1153824914229.JavaMail.jira@brutus>
Date: Tue, 25 Jul 2006 03:55:14 -0700 (PDT)
From: "Clement Escoffier (JIRA)" <jira@apache.org>
To: felix-dev@incubator.apache.org
Subject: [jira] Updated: (FELIX-99) Insertion of the component manager
 inside component classes
In-Reply-To: <21016281.1153823474817.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/FELIX-99?page=all ]

Clement Escoffier updated FELIX-99:
-----------------------------------

    Attachment: patch_cm_core.txt
                patch_cm_plugin.txt

The first patch (patch_cm_plugin) modify the bytecode transformation to add a new argument to each constructor of the class. This new argument is the component manager. So each component instance will have the correct component manager. It change the access to the old _cm field too.

The second patch (patch_cm_core) change the createInstance method to call the new constructor. 

> Insertion of the component manager inside component classes
> -----------------------------------------------------------
>
>                 Key: FELIX-99
>                 URL: http://issues.apache.org/jira/browse/FELIX-99
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>            Reporter: Clement Escoffier
>         Attachments: patch_cm_core.txt, patch_cm_plugin.txt
>
>
> iPOJO manipulation inserts a field inside the component classes. This field is the component manager of the component. It is used to interact with the container. 
> This field is a static field. As a consequence, two components created from the same class share the same component manager. This is problematic in the case of component factory where it must be possible to create 2 components from the same class but with different metadata (container configuration).

-- 
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