I would seriously consider continuing to use WO (but in Java) for your projects. I went through the same thought process a couple of years ago and the ease of what WO offers combined with what EOF offers is really tough to beat. I don't regret the decision at all to port our WO4 (Obj-C) apps to WO5 at all (although we're still in the process).
In terms of support, I would say that it's in a better state then it's been in a long time. The community is very active and I rarely have a situation that someone else hasn't encountered and has found a fix. Project WOnder (the open source project designed to ease the development of WebObjects applications) has made the development of these rewrites really fun. According to the license (at least my understanding) is that you are required to develop on Apple hardware (although there are no Apple tools in the mix, just frameworks), but you can deploy anywhere Java can be deployed. My company currently deploys on Red Hat, but I've deployed independently on several other flavors of Linux. Here are a couple of links to checkout: http://www.wocommunity.org http://projectwonder.blogspot.com/ Good luck on your decision making, Lon On Mon, Oct 18, 2010 at 9:30 AM, <[email protected]> wrote: > I am sure this question has been answered before but .... > > We have been asked to convert a large WebObjects / Objective C app that > was last modified in the year 2000 to a technology that is supportable today > and, hopfully, for the next 10 years. We are also looking for > something simple and robust to use as WebObjects and would require minimial > amount of effort to port. > > The application has about 60 pages, 150 persistent objects and lots of logic > in between. It currently runs on Windows and Solaris with an Oracle back > end. > > We have explored JSF, Struts, Groovy, Rails, Python, Spring, Hybernate, JDO, > J2EE, etc., etc. In the end though, while most of these technologies score > high on the current/future support criteria, some of them not as easy to > develop in as WebObjects and each entails a complete rewrite of the > application. > > So, back to Apple as an option. From what we have learned, the is still a > Java version of the WebObjects frameworks available (and a facility to > convert the old WebObjects/Objective C artifacts) that runs on Mac OS > X. Are there any other options or advice you can share or point us to (e.g. > latest versions, support issues, successes? > > Kindest regards, > -David > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/varscsak%40smarthealth.com > > This email sent to [email protected] > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
