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/11/21 11:59:03 UTC
[jira] Created: (OPENEJB-338) CSSBean needs to use a second ORB
instance for accessing the NameService to resolve beans
CSSBean needs to use a second ORB instance for accessing the NameService to resolve beans
-----------------------------------------------------------------------------------------
Key: OPENEJB-338
URL: http://issues.apache.org/jira/browse/OPENEJB-338
Project: OpenEJB
Issue Type: Bug
Components: corba
Affects Versions: 2.2
Reporter: Rick McGuire
Assigned To: Rick McGuire
Fix For: 2.2
The CSSBean code was cleaned up to use a single ORB instance for retrieving the object instance from the NameService. However, the SecurityInterceptor configured for that ORB adds additional service contexts to the outgoing request that causes NO_PERMISSION errors to occur. A second, non-secured ORB needs to be used for the initial lookup attempt, and then the retrieved object needs to be activated on the ORB instance configured as the object host.
--
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
[jira] Closed: (OPENEJB-338) CSSBean needs to use a second ORB
instance for accessing the NameService to resolve beans
Posted by "Rick McGuire (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick McGuire closed OPENEJB-338.
--------------------------------
Resolution: Fixed
> CSSBean needs to use a second ORB instance for accessing the NameService to resolve beans
> -----------------------------------------------------------------------------------------
>
> Key: OPENEJB-338
> URL: https://issues.apache.org/jira/browse/OPENEJB-338
> Project: OpenEJB
> Issue Type: Bug
> Components: corba
> Affects Versions: 2.2
> Reporter: Rick McGuire
> Assigned To: Rick McGuire
> Fix For: 2.3
>
>
> The CSSBean code was cleaned up to use a single ORB instance for retrieving the object instance from the NameService. However, the SecurityInterceptor configured for that ORB adds additional service contexts to the outgoing request that causes NO_PERMISSION errors to occur. A second, non-secured ORB needs to be used for the initial lookup attempt, and then the retrieved object needs to be activated on the ORB instance configured as the object host.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENEJB-338) CSSBean needs to use a second ORB
instance for accessing the NameService to resolve beans
Posted by "Dain Sundstrom (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OPENEJB-338?page=all ]
Dain Sundstrom updated OPENEJB-338:
-----------------------------------
Fix Version/s: 2.3
(was: 2.2)
If this wasn't fixed in 2.2, it isn't getting fixed since 2.2 is wrapped.
> CSSBean needs to use a second ORB instance for accessing the NameService to resolve beans
> -----------------------------------------------------------------------------------------
>
> Key: OPENEJB-338
> URL: http://issues.apache.org/jira/browse/OPENEJB-338
> Project: OpenEJB
> Issue Type: Bug
> Components: corba
> Affects Versions: 2.2
> Reporter: Rick McGuire
> Assigned To: Rick McGuire
> Fix For: 2.3
>
>
> The CSSBean code was cleaned up to use a single ORB instance for retrieving the object instance from the NameService. However, the SecurityInterceptor configured for that ORB adds additional service contexts to the outgoing request that causes NO_PERMISSION errors to occur. A second, non-secured ORB needs to be used for the initial lookup attempt, and then the retrieved object needs to be activated on the ORB instance configured as the object host.
--
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