Are you saying that every open source and commercial ORB that wants to run under JDK 1.5.0 requires one of these two approaches? That no one has come up with a workaround that doesn't require user intervention?
Thanks, Aaron On 8/11/06, Mosur Ravi, Balaji <[EMAIL PROTECTED]> wrote:
The JDK class http://java.sun.com/j2se/1.5.0/docs/api/org/omg/PortableInterceptor/IORI nterceptor_3_0Operations.html#adapter_manager_state_changed(int,%20short ) doesn't correctly implement the corba 3.0 spec... This method should have a string as the manager ID. Anyways, there are 2 ways to handle this... 1) java.endorsed.dirs setting 2) xbootclasspath - Balaji -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron Mulder Sent: Friday, August 11, 2006 10:57 AM To: dev@geronimo.apache.org Subject: Re: Yoko and Geronimo On 8/11/06, Rick McGuire <[EMAIL PROTECTED]> wrote: > ... > Any thoughts on how we should handle this particularly awkward situation? I vote "we" (e.g. Yoko) do whatever it takes to avoid the class conflict, and then Geronimo can forget about the JVM ORB forever. Do "we" know how other open source ORBs handle the conflict? Thanks, Aaron
