geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (JIRA)" <j...@apache.org>
Subject [jira] Updated: (YOKO-431) Classloader issue when initializing a corba skeleton for EJB object
Date Wed, 26 Jan 2011 09:24:45 GMT

     [ https://issues.apache.org/jira/browse/YOKO-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Forrest Xia updated YOKO-431:
-----------------------------

    Attachment: yoko-431.patch

The patch updates these:
1. the mistyped(?) provider bean key name from "org.omg.CORBA.ORBSingleton" to "org.omg.CORBA.ORBSingletonClass",
according to old version corba code in geronimo
2. the classloader logic change to search class name from blueprint service bean with the
corba property key, then search the impl. class from other classloader.

I tried this patch on the tck case, the CNF exception disappeared.

> Classloader issue when initializing a corba skeleton for EJB object
> -------------------------------------------------------------------
>
>                 Key: YOKO-431
>                 URL: https://issues.apache.org/jira/browse/YOKO-431
>             Project: Yoko - CORBA Server
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: RMI-IIOP
>    Affects Versions: v1.1.0
>         Environment: windows 7
> oracle jdk 1.6.0_20
>            Reporter: Forrest Xia
>            Assignee: Forrest Xia
>             Fix For: v1.2.0
>
>         Attachments: yoko-431.patch
>
>
> When doing tck failure debug, I found the the case which is calling from RI to VI failed
with a ClassNotFoundException, after debug and asking in the mailing list, I tried to make
a patch for the issue.
> Attach here for review. thanks!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message