You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2010/12/19 04:24:02 UTC
[jira] Updated: (AXIS2-2805) AxisDescription child/parent access
should be typesafe
[ https://issues.apache.org/jira/browse/AXIS2-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samisa Abeysinghe updated AXIS2-2805:
-------------------------------------
Issue Type: Improvement (was: Bug)
This is not a bug, but an improvement
> AxisDescription child/parent access should be typesafe
> ------------------------------------------------------
>
> Key: AXIS2-2805
> URL: https://issues.apache.org/jira/browse/AXIS2-2805
> 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(). Yuk.
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org