Re: [Ikvm-developers] OpenJDK

[Jeroen F. <je...@su...>]

Hi Phil,

The most likely cause is that change in class loader architecture. See http://weblog.ikvm.net/PermaLink.aspx?guid=4e0b7f7c-6f5d-42a3-a4d6-5d05a99c84ff

See http://weblog.ikvm.net/PermaLink.aspx?guid=8a457a80-1e5f-4182-8f78-b2cd67845553 for ways to change the class loading. Your best bet is probably for the main executable to use an AppDomainAssemblyClassLoader.

Regards,
Jeroen

> -----Original Message-----
> From: ikv...@li... [mailto:ikvm-
> dev...@li...] On Behalf Of Philip Sacca
> Sent: Wednesday, June 18, 2008 18:38
> To: Ikv...@li...; JAMES MCCLELLAND
> Subject: [Ikvm-developers] OpenJDK
>
> Jeroen,
>
> We started using ikvm 3.0 with the classpath dll about 2 years ago with
> no problems. We downloaded version 36.0.11
>
> with the OpenJDK dll, recompiled all our jar files into a .net dll and
> are getting run-time errors.
>
> The errors occur when trying to create an Initial Context to connect to
> a sybase database.
>
> The error is "can't instantiate com.sybase.ejb.InitialContextFacory".
> We used the object browser and found
>
> the com.sybase.ejb.InitialContextFacory in the class hierarchy. The
> JNDI looked-up worked on version 3.0.
>
> Any Suggestions?
>
> Note: the jar files we convert into a .net assembly are from a third
> party. We do not have any control of the code.
>
> The jar files are a middle tier business layer that we have to go
> through to pull and update data (Sybase). The jar files are
>
> written in Java 1.4.
>
> Thanks
>
> Phil Sacca