[ 
http://issues.apache.org/jira/browse/TUSCANY-833?page=comments#action_12441857 
] 
            
Jeremy Boynes commented on TUSCANY-833:
---------------------------------------

Jim's proposal to the mailing list sounds like a better long-term solution but 
I am concerned that doing it this close to the release of M2 will be 
destabilizing. Propogating the approach used by the script containers does not 
provide the full function that we need from sidefiles - for example, it does 
not support scope and lifecycle method configuration that is available via 
annotation.

I think we should tackle this problem as follows:
1. Create the branch using the code as it is today and document that sidefiles 
are not supported for Java components. This is the status quo.
2. Fix this in head the "right way" (whatever that is), assess the impact of 
that patch and consider applying it to the M2 branch before release.
3. Create a patch for the M2 branch that provides sidefile support with minimal 
destablization (however that can be done).

The patches from 2 and 3 provide concrete implementations that we can evaluate 
for incorporation into M2, balancing the benefit of fixing the bug vs. the 
potential destabilization.

> ComponentType sidefiles do not work for Pojo Implementation
> -----------------------------------------------------------
>
>                 Key: TUSCANY-833
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-833
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA POJO Container
>    Affects Versions: Java-M2
>            Reporter: Venkatakrishnan
>         Assigned To: Jim Marino
>            Priority: Critical
>
> If you have a component type sidefile for a Pojo implementation we end up 
> with an exception.  The reason for this is that the JavaComponentTypeLoader 
> passes the PojoComponenType.class to the loader registry to be returned as a 
> result.  However what gets created is an instance of the base ComponentType 
> and then there is an attempt to narrrow this to a PojoComponentType which 
> results in an exception.
> A quick alternative in the interest of M2 fast approaching would be to take 
> the approach that the containers have to get over this problem which is for 
> the containers to get the base ComponentType and copy it over to the special 
> ones.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to