On Nov 12, 2007, at 1:53 PM, Jean Pierre Malrieu wrote:
I am not using it, so my question is just for curiosity.
I thought that dynamic D2JC apps were not using nib files, and that
swing interfaces where created out of xml descriptions, or by
programmatically creating controllers.
Is there a technical reason for deprecating D2JC, or is it that
without the possibility of mixing with nib-based interfaces, D2JC
looses so much interest that maintaining it becomes more costly than
useful?
If the reason for deprecating D2JC is not technical, I find it a
little bit sad that all this amount of code (and there seems to be
quite a lot code for controllers, etc.) just disappears. I
understand that Apple does not want to maintain a tool that is not
widely used, and that will be even less used now that the possiblity
of mixing dynamic and nib based interface is gone. But If xml-based
D2JC can still be used, maybe the relevant parts of the code could
be made public?
Of course, if there is a purely technical reason for deprecating
D2JC (like the reason for deprecating WOBuilder), please forget my
last question.
Because while D2JC sounds good in theory, in practice D2JC
applications are a nightmare to maintain. You end up factoring your
code 3 days:
.common
.server
.client
On top of whatever splitting EOGenerator does for you.
It's practically a given that you'll be in the wrong "Person.java"
when you go to do anything.
They're a royal bitch to debug, because you have the client talking
to the server talking to the client.
So I suspect Java Client just got given up as a bad idea. Just my
$0.02 at having to maintain a Java Client app, everyone in the company
hates it, and we decided to just drop it in the trash even before
Apple deprecated the whole idea.
Pierce
_______________________________________________
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]
