Re: ERDistribution
Re: ERDistribution
- Subject: Re: ERDistribution
- From: John Huss <email@hidden>
- Date: Tue, 15 Sep 2015 14:16:42 +0000
It's intended for JavaClient apps that aren't DirectToJC. It is mostly to add logging and enable easier debugging.
The deserialization fails randomly in my experience, and I needed the logging to see that. EODistribution COULD be used without Swing to enable remote EOF operations between servers (or in Android!), which is kind of cool.
However, I don't recommend using EODistribution or JavaClient -- there are bugs in it and they will never be fixed.
Cayenne has a similar technology that works better, but it also has some issues, mostly just because of a small user base. The big advantage Cayenne has is that any bugs you find can actually be fixed.
John
On Tue, Sep 15, 2015 at 6:42 AM John Pollard <
email@hidden> wrote:
Can anyone say what ERDistribution adds and whether it should be used as a drop in replacement for EODistribution for Java Client apps? Is there any documentation around it, the wodev list seems to draw a blank on this topic. I currently use EODistribution.
I spotted it only because after updating my copy of Wonder, the only error I see relates to ERDistribution, JavaClient WO saying: Either one of 'applicationClassName' or 'interfaceControllerClassName' should be bound. If anyone can explain why that error is present, that would also be of interest.
Many thanks,
John
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden