You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2009/12/31 09:55:30 UTC

[jira] Assigned: (SLING-1195) Make AdapterManager implementation somehow accessible for junit tests

     [ https://issues.apache.org/jira/browse/SLING-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler reassigned SLING-1195:
---------------------------------------

    Assignee: Carsten Ziegeler

> Make AdapterManager implementation somehow accessible for junit tests
> ---------------------------------------------------------------------
>
>                 Key: SLING-1195
>                 URL: https://issues.apache.org/jira/browse/SLING-1195
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Adapter 2.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Adapter 2.0.6
>
>
> The SlingAdaptable directly uses the internal AdapterManagerImpl class to get adapter factories. This works fine in an OSGi context.
> Using a SlingAdaptable within a junit test is harder, especially if one wants to use an adapter factory. This requires manual instantiation of the adaptermanager impl and some reflection tricks etc. to get the factory registered.
> We should find a better way which makes writing junit tests easier.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.