• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Creating a JavaVM with JNI & Re:JavaBridge
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Creating a JavaVM with JNI & Re:JavaBridge


  • Subject: Re: Creating a JavaVM with JNI & Re:JavaBridge
  • From: "James B. Tuley" <email@hidden>
  • Date: Sat, 5 Mar 2005 19:16:14 -0600


On Mar 3, 2005, at 2:45 AM, Phil wrote:

Since using the Java Bridge is depreciated (and liable to get you
flamed),

There's always been little documentation on the Java Bridge, but it doesn't look deprecated from the standpoint of calling Java API's from Obj-C I see no mention of deprecation or use at your own risk in the headers. (Whether it gets me flamed for saying so may be another story, although I'm not sure where that is coming from, I tried searching through older posts).


The documentation for wrapping your own objective-c classes with bridget so they can be called from java has been marked as legacy a while, and the headers for apis related to bridget generated code are marked use at your own risk, and I would agree that aspect of bridging is deprecated. However, using standard pre-wrapped cocoa API's from java still works, and doesn't have any disclaimers in the headers and there's a good deal of documentation for it, so .

I also found a small apple article on Java Bridge Last updated: 2004-08-31 ->
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaObjects/ Articles/JavaCocoa.html
That mentions using classes from both environments.


I personally would hate to see the java bridge deprecated for calling java api's from objective-c because it works really well, for most cases easy to use and very useful as it adds a ton of object oriented libraries at your disposal. I looked pretty hard to see if using java apis from objective-c was depreciated and haven't found anything to support that claim, if I'm wrong could someone please point me to where that aspect of the java bridge has been flagged as deprecated?

And for those asking about using the Java Bridge from an obj-c cocoa app (assuming it is indeed not deprecated), there is a cocoa dev article. And while it is 3 years old, is still valid in my experience of using the java bridge to call java apis, and I have had no problems using good java apis from objective-c, as long a they aren't missing accessors and require you to access public variables. http://www.cocoadevcentral.com/articles/000024.php

-Jay
http://indyjt.com

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Creating a JavaVM with JNI & Re:JavaBridge
      • From: Finlay Dobbie <email@hidden>
References: 
 >Creating a JavaVM with JNI (From: Phil <email@hidden>)

  • Prev by Date: [SOLVED] Re: cachImageInRect and Scrolling Views
  • Next by Date: bindings for nsmatrix
  • Previous by thread: Re: Creating a JavaVM with JNI
  • Next by thread: Re: Creating a JavaVM with JNI & Re:JavaBridge
  • Index(es):
    • Date
    • Thread