Re: JavaClient Common classes
Re: JavaClient Common classes
- Subject: Re: JavaClient Common classes
- From: John Huss <email@hidden>
- Date: Wed, 25 Mar 2009 14:02:28 -0500
On Wed, Mar 25, 2009 at 12:36 PM, David Avendasora
<email@hidden> wrote:
I've tried several times to use common classes with one class that both server and client inherit from, but I've never been able to get it to work correctly. Mike was kind enough to add some features to Entity Modeler to allow for defining the name of the common class and such, but I ran into all sorts of problems with actually getting an application to run.
Interesting. Having a common class seems to be recommended in the
WO documentation, so I would expect to work without much effort.
There is a wojavaclient.jar that has all the WO client-side framework jars together in it that you can simply add to your client-side classpath, but if you use other frameworks that have client-side jars, you'll still have to manage them yourself.
Hmm, it didn't know that. It's the file here, right: /Library/WebServer/Documents/WebObjects/Java/wojavaclient.jar. That jar is rather large (10 mb). It looks like maybe everything is included twice, once in extracted form and once in an embedded jar. The jar I built with eclipse using the individual jars from WebServerResources was half the size (5 mb).
Apart from the WOComponent classes like WOString, is it true that pretty much all of WO can be used on the client except EOAccess?
_______________________________________________
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