and the future of the Java Client development ? I find very nice the
integration between Interface Builder and the Xcode in order to build
the view side of Java Client. I suppose that when the JavaBridge
will disappear will be very hard to develop Java Client
I'm anxious, we are working heavy with Java Client technology
Regards
Paolo Sommaruga
Il giorno 12/ago/06, alle ore 19:57, Arturo Pérez ha scritto:
On Aug 12, 2006, at 1:18 PM, Michael Halliday wrote:
The following paragraph that Jeremy wrote is really scarring
me ... I am reading a lot into this statement as to the future of
WebObjects as we know it today.
Michael.
On 12-Aug-06, at 12:46 PM, Jeremy Rosenberg wrote:
... but given that this community is now tasked with developing
the future of WebObjects tools and as a result, the future of
WebObjects, perhaps we should be looking at this possibility.
Here's my speculation. I imagine as a Select member I'll be
properly informed soon enough but reading between the lines of the
commentary I've seen so far.
Apple is leaving the Java Tools business. There is no way they can
compete with the juggernaut that is Eclipse, their core competency
is Cocoa, and, frankly, their heart isn't in it. They will,
however, continue to give Java runtime etc a great deal of support
etc, as they have in the past. In particular, their server
strategy is seriously dependent on Java applications remaining
first class citizens in a Mac OS X environment. In other words,
they cannot offer anything distinctive/compelling to the Java IDE
market so they will let others pick up that slack.
Now, this begs two questions. Exactly what is the runtime
environment for WO? And how will they support a WO toolchain?
I think they will continue to offer WO as its own standalone
application server. The effort to do so is minimal, it allows them
to provide distinctly easier to use etc WO deployment and frankly
the J2EE deployment scenario is a complete mess/farce/what have you.
I have no idea what they'll do in the WO toolchain space. Some
lead me to believe that they are endorsing the WOLips toolchain. I
can't see how they can do that and yet still claim to support WO as
a development choice. OOMA, I'll say that they have committed to
providing tools that will plug-in to an Eclipse environment that
will "compete" with those provided by the WOLips crowd but that
they have suggested people become familiar with that toolchain in
order to prepare for the transition.
my farthings, offered generously
arturo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/psomma%
40jpaso.com
This email sent to [EMAIL PROTECTED]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
