You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2017/02/19 03:20:44 UTC
[jira] [Comment Edited] (YOKO-442) Make the NameService run in the
main orb, with csiv2 security and other policies
[ https://issues.apache.org/jira/browse/YOKO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873425#comment-15873425 ]
David Jencks edited comment on YOKO-442 at 2/19/17 3:20 AM:
------------------------------------------------------------
commit a6f9c980c6ca90648866e204899335d1bd0202b6
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Thu Nov 13 15:16:09 2014 +0000
Improve encapsulation of NameService artifacts.
Move Core and POAServant classes for NamingContext and BindingIterator
to be nested (static) classes under their LocalObject variants, which
are renamed to be simply NamingContextImpl and BindingIteratorImpl.
NB: The setup using post_init() in the example TransientNameService code
is still not right, I believe - it's too soon to be activating POAs.
commit c7fd87013003d17946b270757a9f93d70d78facc
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Tue Oct 7 14:32:27 2014 +0100
Separated name service NamingContext and BindingIterators into local and
remote addressable versions, backed by common core function.
Demonstrate initialization if naming service by ORBInitializer impl in
TransientNameService.
NB: ORBInitializer.post_init() is currently driving
POA.POAManager.activate() and POA.activate_object(), which is dodgy, as
they drive IORInterceptors, which may not all be registered at that
point (as there's no control over ORBInitializer ordering).
was (Author: djencks):
commit f858f9d94dde30c94721dc55c04930f6784be42b
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Fri Jan 9 10:15:08 2015 +0000
Replace TestBase.TEST() with calls to Assert.assertTrue()
commit ffc93ca85367052e6ef27acc19ae399def781d0f
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Thu Jan 8 17:26:14 2015 +0000
refactor to simplify iteration a bit
commit d5fd9d41e46cd0bf09aea832474ac5cfbd7df200
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Thu Jan 8 16:59:02 2015 +0000
upgrade to Java 7 and Junit 4.12
commit b80b4112214452cba2250675aaa769a64e279c7f
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Wed Nov 19 17:49:20 2014 +0000
Avoid potential ClassLoader lifecycle issues.
Utilize ClassValue mechanics in TypeRepository.
commit a6f9c980c6ca90648866e204899335d1bd0202b6
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Thu Nov 13 15:16:09 2014 +0000
Improve encapsulation of NameService artifacts.
Move Core and POAServant classes for NamingContext and BindingIterator
to be nested (static) classes under their LocalObject variants, which
are renamed to be simply NamingContextImpl and BindingIteratorImpl.
NB: The setup using post_init() in the example TransientNameService code
is still not right, I believe - it's too soon to be activating POAs.
commit c7fd87013003d17946b270757a9f93d70d78facc
Author: Neil Richards <ng...@linux.vnet.ibm.com>
Date: Tue Oct 7 14:32:27 2014 +0100
Separated name service NamingContext and BindingIterators into local and
remote addressable versions, backed by common core function.
Demonstrate initialization if naming service by ORBInitializer impl in
TransientNameService.
NB: ORBInitializer.post_init() is currently driving
POA.POAManager.activate() and POA.activate_object(), which is dodgy, as
they drive IORInterceptors, which may not all be registered at that
point (as there's no control over ORBInitializer ordering).
> Make the NameService run in the main orb, with csiv2 security and other policies
> --------------------------------------------------------------------------------
>
> Key: YOKO-442
> URL: https://issues.apache.org/jira/browse/YOKO-442
> Project: Yoko - CORBA Server
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: orb core, RMI-IIOP
> Reporter: David Jencks
>
> Previously the NameService ran in a dedicated orb, with no particular support for adding more policies easily. This rewrites the NameService to run in the main orb and to provide read-write local access and configurable remote read-only or read-write access. This reduces the number of open ports needed and allows the NameService to easily be run under the same security policy as the rest of the orb.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)