[
https://issues.apache.org/jira/browse/YOKO-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed YOKO-417.
-----------------------------
Resolution: Fixed
It would also be nice if the interfaces used by a lot of these internal
components were cleaned up remove the extra *Operations classes that the
interfaces extended. That's another item that really adds to the clutter and
makes it difficult to find things in the core ORB.
> Simplify class hierarchies in org.apache.yoko.orb.OB (remove operations,
> helper and holder classes)
> ---------------------------------------------------------------------------------------------------
>
> Key: YOKO-417
> URL: https://issues.apache.org/jira/browse/YOKO-417
> Project: Yoko - CORBA Server
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: orb core
> Reporter: Lars Kühne
> Assignee: Lars Kühne
> Fix For: v1.1.0
>
>
> See yoko-dev dicussion in
> http://mail-archives.apache.org/mod_mbox/incubator-yoko-dev/200707.mbox/[EMAIL
> PROTECTED]
> Core bits of the ORB code appear to have been once generated from IDL, but
> are no longer. These classes follow the IDL generated conventions of having
> operations classes, helpers, holders, etc., even though these classes are
> only used internally within the ORB and are never accessed as CORBA objects.
> The org.apache.yoko.orb.OB package has a lot of these, for example. The code
> is there, and follows the conventions used with idl-generated classes. The
> original IDL is no longer available, which makes enhancing some of these
> classes a royal pain to deal with.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
