[jira] Commented: (PLUTO-133) ServiceManager - Javadoc

["Ulrich Küster (JIRA)" <pl...@jakarta.apache.org>]

    [ http://issues.apache.org/jira/browse/PLUTO-133?page=comments#action_12315250 ] 

Ulrich Küster commented on PLUTO-133:
-------------------------------------

I'm pretty sure, the javadoc of the ServiceManager  is wrong. It should state that all services have to derive from org.apache.pluto.portalImpl.services.Service. An example is org.apache.pluto.portalImpl.services.config.ConfigService or ConfigServiceImpl which derive from org.apache.pluto.portalImpl.services.Service, but do not implement org.apache.pluto.services.ContainerService. Services need to implement ContainerService only if they are intended to be registered at the container, which is not true for all services managed by the ServiceManager class (see ConfigService).

> ServiceManager  - Javadoc
> -------------------------
>
>          Key: PLUTO-133
>          URL: http://issues.apache.org/jira/browse/PLUTO-133
>      Project: Pluto
>         Type: Bug
>   Components: documentation
>     Versions: 1.0.1-rc2
>     Reporter: Nico Max
>     Priority: Minor

>
> The class description of the ServiceManager class states that services have to derive from org.apache.pluto.services.ContainerService.
> But the service instantiation logic casts new instances to the type org.apache.pluto.portalImpl.services.Service which fails at runtime because these types are not related to each other regarding the type hierarchy.

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