Hi,
I changed the subject of the mail because your mail content was no
more appropriate ;-)
I completely agree with your mail. In the WO FF session of the last
WWDC, I explained that the lack of support of Java Client is a very
bad thing for some developpers because we are working on very big
projects.
For my part, we have worked on several applications with Java Client
for a very well known bank. And there is a big project in France
involving 50 universities. There is a web site (http://
www.cocktail.org) only in french. The home page lists a part of
applications developed with Java Client and there are a lot ... And
there is a developer in this team who makes incredible stuff with
Java Client.
The Apple WO team needs to know how Java Client is used. So the best
thing is to send an email to Pierre Frisch, the manager of WO team
with a description of the project. And if you are allowed to speak
publicly about your project, please, send it to the list too.
Philippe Rabier
On 22 juin 07, at 21:10, [EMAIL PROTECTED] wrote:
Subject: Re: Java Client refuses to use Client-Side classes once
deployed
To: Robert Walker <[EMAIL PROTECTED]>
Cc: Development WebObjects <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Hi all,
There seems to be a lack of distinction in different ways to use WO
JavaClients. It seems that most people see this being done as either
the direct or non-direct approaches described by Apple. BUT, there is
another approach that does not utilize large portions of WO's
JavaClient support code, where most trouble comes from.
This approach comes down to using client side EOF only for data
persistence, within any kind of a Java app. There is no D2JC auto-
generated GUI, rule systems, translations from nib to Swing etc. All
the places where WO's JavaClient capabilities become difficult and
error prone.
I feel it is important to point this out, as the whole "dropping of
WO Java Client" by either Apple or users of it, can imply different
things:
1. Dropping direct-to stuff
2. Dropping Nib to Swing
3. Dropping ALL of the JavaClient code including data distribution
classes
The first two causes most of the trouble (IMHO), but dropping it does
not have to imply dropping the third. I also think that part of the
JC code base is relatively small, not difficult to maintain, and yet
opens a door for WO to be used in a not very popular, but powerful
way.
I know that I am speaking for a very small percentage of a very small
community, but I hope Apple has mercy on us there.
Two cents,
Flor
_______________________________________________
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]
