I used the JavaConverter described here about 7 or 8 years ago, in
2000, I think. It did a pretty decent job of converting WebObjects
Objective C code to WebObjects Java code, at about the 95% level
IIRC. The rest we did by hand.
On Nov 22, 2007, at 12:32 PM, Michael Hall wrote:
On Nov 21, 2007, at 10:07 AM, Duncan McGregor wrote:
With the demise of the Cocoa-Java Bridge, I've had a little success
writing the start of a generic framework using JNA.
This got me wondering if there were any javacc grammars for
ObjectiveC out there anywhere.
I have yet to figure out javacc well enough to do anything useful
with it myself but had thought sometime I would figure it out and
do my own JNIDirect header parsing based off of it.
Checking now I came across... http://developer.apple.com/documentation/LegacyTechnologies/
WebObjects/WebObjects_5.1/JavaConverter.pdf
Which if I'm understanding correctly, and I know less of WebObjects
than I do javacc, it is a tool for converting arbitrary ObjectiveC
to java. (Apparently including just such a ObjectiveC javacc
grammar) It could possibly be used in that way instead of a Cocoa-
Java bridge. _Or_ it could be modified to form the basis of your
own Cocoa-Java bridge.
Understand that WebObjects comes with the JavaFoundation and
JavaWebObjects frameworks which provide NSArray and NSDictionary
collection classes (among others) that were retained for WebObjects
development during the conversion of WebObjects from Objective C to
Java.
So rather than convert the use of an NSArray to a Java array, or
NSDictionary to a Java class with the Map interface, it would simply
carry the references across to the Java target. This is typically not
what a Java programmer would be looking for.
Furthermore, I'm pretty sure that Apple is no longer distributing the
tool and, to find it, you would have to find someone with an old
WebObjects installation (probably WO v4.5 or 5.0).
I'm thinking this might be a possibility because some of the
WebObjects tools have indicated to have been deprecated and
supposedly open sourced.
Apple has dropped the JavaBridge (well known on this list) and
consequently has deprecated the WebObjects development tools that
depend on the JavaBridge, such as EOModeler, WebObjects Builder and a
couple others. Rather than open source these tools, they have opened
up the tool interfaces so that the developers in the WebObjects
community could substitute their own tools that could work together
as seamlessly as the old Project Builder/EOModeler/WebObjects Builder
trio used to.
Apple HAS NOT open sourced the tools themselves NOR the WebObjects
frameworks. They critically depend on the latter and have completely
dropped the former in the upgrade to Leopard (and WebObjects v5.4).
I'm not an Apple insider, but my understanding is that the Apple
development teams have been using Eclipse/WOLips and other of the
open sourced tools for a while now in lieu of Xcode and the Apple
development tools. That was one fact that led to their dropping
support for their own tools. Xcode has never played well with Java.
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
