I will take this as a work item and follow up on what is the latest status on "don't look for JNI code until it really is needed". In any case, as you stated, even if 7.1 API forcibly looking for JNI code (althought your code does not invoke any of such functionality) -- it would not be considered as a defect from a product support perspective. However, from the eventual expected feature standpoint, I do consider it to be some thing we need to look into. Appajee
________________________________ From: Action Request System discussion list(ARSList) on behalf of Hugo Visser Sent: Fri 2/1/2008 1:01 AM To: [email protected] Subject: Re: Pure Java 7.1 API: Am I missing something? ** OK, but my code isn't using any of the things you mention. In fact the code that I tested ran on 7.1 beta without any native dependencies. The following snippet triggers JNI loading stuff and errors if it fails: ARServerUser context = new ARServerUser("Demo","","","ltvisserh71"); context.setPort(8001); context.login(); Which is about as trivial as it gets... But if I understand correctly BMC wouldn't consider this a bug as the goal was not to eliminate the native libs right? Well I guess it's too bad for me then, I'd hoped for the day that I would not need all the native libs deployed with my apps. This also means that for now 7.1 API code won't run on non-supported platforms such as the Mac, I was under the impression that someone stated earlier that it would be possible now, if you'd avoid the functions that require JNI. But thanks for the clarification and confirmation. Hugo _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
