You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Rick McGuire (JIRA)" <ji...@apache.org> on 2006/10/09 11:50:20 UTC
[jira] Commented: (OPENEJB-267) Reduce the number of places where
CORBA config parameters are specified.
[ http://issues.apache.org/jira/browse/OPENEJB-267?page=comments#action_12440841 ]
Rick McGuire commented on OPENEJB-267:
--------------------------------------
This issue can be closed now. I don't have sufficient Jira karma to close it.
> Reduce the number of places where CORBA config parameters are specified.
> ------------------------------------------------------------------------
>
> Key: OPENEJB-267
> URL: http://issues.apache.org/jira/browse/OPENEJB-267
> Project: OpenEJB
> Issue Type: Improvement
> Components: corba
> Affects Versions: 2.2
> Reporter: Rick McGuire
> Fix For: 2.2
>
>
> The CORBA configuration situation is a bit of a mess currently, with information scattered over multiple locations. Much of this information is ORB implementation specific, which makes it very difficult to switch between ORBs. For example, various CORBABean configurations manage bits of the ORB configuration using:
> 1) The name of an ORB config adapter class.
> 2) ORB.init() properties specified on the CorbaBean declaration
> 3) ORB.init() arguments specified on the
> 4) CORBASystemProperties values that must be set in System.properties before initializing the ORB.
> 2), 3), and 4) above are values that are handled in a non-portable fashion, and are scattered over seemingly unreleated portions of the configs.
> A better solution would be to have GBeans that encapsulate the knowledge about what ORB is going to be used as the server and pull these pieces together into a simple GBean declaration, which would make it much easier to switch between ORB implementations. The ORB config adapter seems tailor made for this. It just needs to be turned into a GBean rather than a classname argument to CorbaBean and CSSBean.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira