You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2011/01/26 10:16:46 UTC

[jira] Created: (YOKO-431) Classloader issue when initializing a corba skeleton for EJB object

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


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.


[jira] Updated: (YOKO-431) Classloader issue when initializing a corba skeleton for EJB object

Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Closed: (YOKO-431) Classloader issue when initializing a corba skeleton for EJB object

Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/YOKO-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Forrest Xia closed YOKO-431.
----------------------------

    Resolution: Fixed

> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (YOKO-431) Classloader issue when initializing a corba skeleton for EJB object

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/YOKO-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994682#comment-12994682 ] 

David Jencks commented on YOKO-431:
-----------------------------------

This looks fine to me.  Can you remove the commented out "old" code lines before you commit?

> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira