Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  Web & Software Development  |  IDEs  |  Apple WebObjects Developer  |  WO's future?

Apple WebObjects Developer

Apple WebObjects Developer

web app development

Version:  5.4.3

   [ Views: 811 ]

WO's future?

Feedback Type:  Commentary

Contributed by: libertyforall1776 Monday, August 14 2006 @ 05:02 PM PDT

Product Platform: MacOSX

Used Product For: 1-6 months

Recommend Product: YES

Xcode 2.4 release notes states the following which raises WO's future concerns?

Deprecation Notice
NOTE: As of the release of Xcode 2.4, the Cocoa Java bridge has been deprecated. This means that,
while still supported with Xcode 2.4, future releases of Xcode may not support the bridge or other
dependent features. Due to this, the following additional WebObjects developer applications are also
being deprecated:
EOModeler
EOModeler Plugin
WebObjects Builder
WebServices Assistant
RuleEditor
WOALauncher
This also means that the Xcode Java bridge templates have been deprecated, and should not be used
for new Java bridge-based development.   

Rate this Commentary

Was this Commentary helpful? Yes | No

Comments

2 comments |

So long Java... - zunipus

For those who don't know it already, the use of Java to program WO has been dropped. IMHO this was inevitable as Java has never lived up to its promise and has instead been annoying if not outright insecure in some instances. (Yeah, you can hit me. I know there are some excellent Java apps. I still love Azureus, the heart of the marketing mess now known as Vuze).

Result: You gotta program WO with the same language you use for any contemporary Mac app: Objective C. I personally won't miss Java. (You can stop hitting me now.)

Meanwhile, WO continues to evolve and gain in power, totally for free.

Reply to This

Monday, September 15 2008 @ 08:28 PM PDT


So long Java... - Xdave--2008

Your comments are plain wrong.

WO remains Java. What changed some time ago is that support for programming *Cocoa* using Java and mixing ObjectiveC with Java goes away. This doesn't affect WO at all (which remains a fully java based component oriented web application server with HTML templating library and OR-Mapping). And all this has nothing to do with java being secure or not. Btw java's security track record is pretty good..

The ONLY effect on WO is that many of the WO developer tools seem to have used the java bridge and are depreciated now - but the WO community provides Eclipse based replacements which are better than the original tools in many respects.

Reply to This

Tuesday, September 16 2008 @ 12:57 PM PDT