axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels (JIRA)" <>
Subject [jira] Created: (AXIS2-2805) AxisDescription child/parent access should be typesafe
Date Thu, 14 Jun 2007 16:12:25 GMT
AxisDescription child/parent access should be typesafe

                 Key: AXIS2-2805
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
            Reporter: Glen Daniels
            Assignee: Glen Daniels
             Fix For: 1.3

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