Re: Differences in path handling in ikvmc DLL vs. Java jar execution
Volker Berlin <[email protected]> Mon, 21 Nov 2016 09:32:09 +0100
| Newsgroups | gmane.comp.java.ikvm.devel |
|---|---|
| Message-ID | <[email protected]> |
--===============1783962865138189934== Content-Type: multipart/alternative; boundary="------------1A2CDB0F90D907695A84B815" --------------1A2CDB0F90D907695A84B815 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit It look like that your framework try to access the stream of com.datastax.driver.core.Cluster$Builder.class. Because class resources are not available IKVM that it try to generate a stub of the stream which is failing. If this is the case then it look like a bug in IKVM. Which version of IKVM do you use? Volker Am 18.11.2016 um 20:39 schrieb Paul Chambre: > Hi folks, > > I noticed some differences in file access from code within an ikvmc > DLL vs. that same code executed by Java from a jar. > > One particular example is a properties file that is passed to one of > our classes with a -D. > > Initially, whether local to the application (next to the jar/dll) or > fully qualified, the file was inaccessible to the jar code. I then > added . to the classpath in the manifest of the jar, and that allowed > the jar code, when run through Java -jar, to access properties files > in the same directory as the jar.However, this change did not help > DLLs make with ikvmc from that jar. Those dlls still cannot access the > properties file when it's in the same directory as the DLL (or fully > qualified). > > Are there other properties to be set specifically for ikvmc, to define > the classpath or other "local" path configurations? > > Thanks, > Paul > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Ikvm-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/ikvm-developers --------------1A2CDB0F90D907695A84B815 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: 7bit <html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <p>It look like that your framework try to access the stream of com.datastax.driver.core.Cluster$Builder.class. Because class resources are not available IKVM that it try to generate a stub of the stream which is failing. If this is the case then it look like a bug in IKVM.</p> <p>Which version of IKVM do you use?</p> <p>Volker<br> </p> <br> <div class="moz-cite-prefix">Am 18.11.2016 um 20:39 schrieb Paul Chambre:<br> </div> <blockquote cite="mid:CAJwVo5HGVTc6PWarvT5q-2u9hpXsExps_-5A-BonUKdLjbAaew@mail.gmail.com" type="cite"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <div dir="ltr"> <div>Hi folks,</div> <div><br> </div> <div>I noticed some differences in file access from code within an ikvmc DLL vs. that same code executed by Java from a jar.</div> <div><br> </div> <div>One particular example is a properties file that is passed to one of our classes with a -D. </div> <div><br> </div> <div>Initially, whether local to the application (next to the jar/dll) or fully qualified, the file was inaccessible to the jar code. I then added . to the classpath in the manifest of the jar, and that allowed the jar code, when run through Java -jar, to access properties files in the same directory as the jar.However, this change did not help DLLs make with ikvmc from that jar. Those dlls still cannot access the properties file when it's in the same directory as the DLL (or fully qualified).</div> <div><br> </div> <div>Are there other properties to be set specifically for ikvmc, to define the classpath or other "local" path configurations?</div> <div><br> </div> <div>Thanks,<br> Paul</div> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">------------------------------------------------------------------------------ </pre> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Ikvm-developers mailing list <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ikvm-developers">https://lists.sourceforge.net/lists/listinfo/ikvm-developers</a> </pre> </blockquote> <br> </body> </html> --------------1A2CDB0F90D907695A84B815-- --===============1783962865138189934== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ --===============1783962865138189934== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ikvm-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ikvm-developers --===============1783962865138189934==--