axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2-2805) AxisDescription child/parent access should be typesafe
Date Sun, 19 Dec 2010 03:26:01 GMT


Samisa Abeysinghe resolved AXIS2-2805.

    Resolution: Won't Fix

This has been hanging there for three years and does not look that it will get implemented.

> AxisDescription child/parent access should be typesafe
> ------------------------------------------------------
>                 Key: AXIS2-2805
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>            Reporter: Glen Daniels
>            Assignee: Glen Daniels
> AxisDescription is the parent class of AxisService, AxisOperation, etc.   It does some
handy things, but I think it oversteps good design boundaries.  In particular, the Configuration/ServiceGroup/Service/Operation/Message
hierarchy is fixed and should be respected - as long as AxisDescription is the place getChild/getParent
and related methods live, we are losing valuable information.  The compiler can't type check
for us so we're stuck doing it at run time, and we need to typecast all returns from getChild()/getParent().
> We should remove child/parent management from AxisDescription, and replace it with type-safe
methods - for instance, "AxisOperation getParent()" on AxisMessage.  If we really need to
walk the hierarchy in a generic way we can also provide another API for that, but this will
really help devs using AxisService/AxisOperation/etc....

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:
For additional commands, e-mail:

View raw message