axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2642) Inconsistencies in getting engaged modules
Date Thu, 21 Jun 2007 17:49:26 GMT

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

Glen Daniels resolved AXIS2-2642.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

Factored most of the module code up to AxisDescription, which now keeps track of engaged modules,
handles engage/disengage, etc.  There are now overridable "onEngage()" and "onDisengage()"
methods which subclasses use to do individual things (for AxisService, to engage to all operations,
etc).


> Inconsistencies in getting engaged modules 
> -------------------------------------------
>
>                 Key: AXIS2-2642
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2642
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>         Environment: Any
>            Reporter: Saminda Wishwajith Abeyruwan
>            Assignee: Glen Daniels
>            Priority: Blocker
>             Fix For: 1.3
>
>
> We've came across the following inconsistencies when calling getEngagedModules() method,
in
> 1. AxisOperation
> 2. AxisService
> 3. AxisServiceGroup
> AxisOperation has,
> public Collection getEngagedModules() {...} --> This will give an instance of ArrayList
which has AxisModule  objects.
> AxisService has,
> public Collection getEngagedModules() {...} --> This will give an instance of ArrayList
which has String objects.
>                                                                              String objects
are the names of engaged modules.
> AxisServiceGroup has,
> public ArrayList getEngagedModules() {...} --> This will give an instance of ArrayList
which has String objects.
>                                                                             String objects
are the names of engaged modules.
> This will lead to difficulties when working with them.
> IMHO  getEngagedModules() should be an abstract method in AxisDescription;
> public List getEngagedModules(),
> and should return either AxisModule or Name of the module as String. IMHO AxisModule
would be preferable. Thus, others that extend from AxisDecription will be benefited too.

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


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


Mime
View raw message