geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick McGuire (JIRA)" <j...@apache.org>
Subject [jira] Closed: (GERONIMO-2862) Detect Yoko classes are not endorsed
Date Wed, 21 Feb 2007 21:50:06 GMT

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

Rick McGuire closed GERONIMO-2862.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta1
                   1.2

Committed revision 510163 -- Geronimo 1.2 (note, commit was to openejb). 
Committed revision 510248. -- Geronimo 2.0 

> Detect Yoko classes are not endorsed
> ------------------------------------
>
>                 Key: GERONIMO-2862
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2862
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: CORBA
>            Reporter: Dain Sundstrom
>         Assigned To: Rick McGuire
>             Fix For: 1.2, 2.0-beta1
>
>
> When the Yoko classes are not installed in the endorsed directory, we get  non-obvious
exceptions like the following from the Yoko code.
> java.lang.NoSuchMethodError: org.omg.PortableInterceptor.IORInterceptor_3_0.adapter_manager_state_changed(Ljava/lang/String;S)V
>         at org.apache.yoko.orb.OB.PIManager.adapterManagerStateChange(PIManager.java:532)
>         at org.apache.yoko.orb.OBPortableServer.POAManager_impl.activate(POAManager_impl.java:213)
>         at org.apache.yoko.orb.CosNaming.tnaming.TransientNameService.initialize(TransientNameService.java:130)
> We should be able to detect that the Yoko specs are not endorsed and throw an specific
exception informing the user how to fix the problem.

-- 
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