Re: WO JavaCocoa
Re: WO JavaCocoa
- Subject: Re: WO JavaCocoa
- From: Ricardo Strausz <email@hidden>
- Date: Wed, 30 Mar 2005 11:45:12 -0600
Hola!
On Mar 29, 2005, at 14:02, Florijan Stamenkovic wrote:
Hey
Thanks for your reply. For the time being we still have not decided
what approach to take to our application.
There are two things that bug me about this all:
1. Security - if I write in Java then it should be as I understand
tragically easy to decompile and thereby see ALL of my app
If someone "undesired" have access to your app, and she has the
knowledge, no mater how it was done it can be decompiled. It is certain
that Java is easer to decompile (the JVM is an "interpreter"), but she
*most* have access to the app ---the set of jars and so on--- in order
to decompile it. In the client/server (intranet) scenario, an
"undesired agent" is unlikely to exists; on the oder hand, if you are
planning to traverse the internet with your app, it is not your logic
which traverses it, but your data: in a Cocoa/EO app, the logic is
performed ONLY locally ---in contrast to the three-tier Java Client
approach.
2. I haven't heard of many Cocoa apps written in Java, and am a tad
skeptical.
Well, this is because if it is done in pure-Java (using Swing) the it
will run in OSX as in any other JVM; if it is purely for OSX ---it is
not intended to run any were else--- then it is better/faster to write
it in Objective-C which is the native language of Cocoa. However it can
be done!
Please comment on those points.
As for the Java Bridge, well, I haven't worked with it before and have
no idea what it is. As I understand it makes it possible to write all
manipulation logic in Obj-C and the EOF part (graph management,
accessing objects) in Java???
The main porpoise of the Java Bridge was to make possible to
communicate from the Objective-C-Side of Cocoa to the Java-Side in
which the EOF lives (since WO 5.0). It is also possible to use it in
the other direction but is more difficult/laborious. The main idea
behind is that you can allocate Java objects from your Obj-C code, and
treat them as if they were any other object (written in Obj-C). The use
of it is quite transparent to the programmer; you only have to be aware
of some "NS-functors".
If you have a complete installation of OSX 10.3.8 you can click in (or
copy-paste into a browser) the following link to learn more about it:
file:///Developer/Documentation/Cocoa/Conceptual/Legacy/JavaBridge/
JavaBridge.html
Suerte!
Dino
Great to see that at least someone is working with this!
Cheers
Florijan
On Mar 29, 2005, at 21:32, Ricardo Strausz wrote:
Hola!
If by WO JavaCocoa you mean a desktop app which uses EOF and, while
using Cocoa, it is implemented mainly in Java, then you are asking
for a Cocoa Enterprise Objects Application ---aka Cocoa/EOF app. It
definitely can be done ---and is the best tech I know to build
client/server apps--- but it have some little cons:
1. it is not supported ---yet!!!!--- by Apple; therefore you are
*alone* on the project ---well, you are with me and a few others out
there.
2. you will get married with Cocoa, and therefore with OSX.
3. if you want to use Objective-C as your primary language, then you
most learn some tricky tricks to manage the so-called Java Bridge.
However if your main language will be Java ---which is possible---
Cocoa/EOF runs quite smoothly and I highly recommend it ---indeed I
use it all the time.
You can find more info in
http://wodev.spearway.com/cgi-bin/WebObjects/WODev.woa/wa/Main?
wikiPage=CocoaEOApplication
If you stock your self, do not hesitate in give me an e-mail.
Suerte!
Dino
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden