I like descriptive names... and less acronyms. For all I knew these
were CascadingStyleSheetBean and TheServerSideBean...
--jason
On Jul 20, 2006, at 3:28 AM, Rick McGuire wrote:
After spending a good year+ dealing with issues involving
CorbaBean, CSSBean, and TSSBean I've come to the realization that
part of the problem with understanding how these work is the names
are misleading...particularly CSSBean and TSSBean.
TSSBean calls itself the "CORBA Target Security Service". While
some aspects of its configuration involve defining transport level
security, this bean is really a proxy that manages a POA instance
for exposing an EJB container as a CORBA object. The TSSBean name
somehow obscures the fact that there is a TSSBean instance for
every exported EJB. CorbaObjectProxy or EjbPoaProxy might be
better names.
CSSBean calls itself the "CORBA Client Security Server". Similar
problem with TSSBean. Security is only one aspect of this
bean....and it's not really a "Server". CorbaClientObject might
make it a little clearer what's being configured.
CorbaBean is not too bad, but it seems to imply a global CORBA
configuration rather than configuring a single ORB instance.
CorbaServerOrb would capture the essential server-side ORB nature
of this.
Rick
