Re: WO version from code (was: Qualifier creation)
Re: WO version from code (was: Qualifier creation)
- Subject: Re: WO version from code (was: Qualifier creation)
- From: Florijan Stamenkovic <email@hidden>
- Date: Sun, 3 Feb 2008 01:32:55 -0400
I am scratching my head at the purpose of being WO independent but
depending on other projects.
JBND is not dependent on any other project, completely standalone.
For deployment WO is essentially free so I do not really see the gain.
Well, providing Cayenne users with a data binding library (if they
choose to implement the support). The same for other systems that
might be out there. And last but not the least, making the codebase
of a fairly large client application as less depending on whomsoever
as possible. Nothing against WO, but the tough times for JC just
before 5.4 was released made me realize that betting on one horse is
not the smartest thing to do. And making JBND WO agnostic was not so
difficult.
The only way to determine the WebObjects version is to check the
plist of the JavaWebObjects bundle, this is how the installer clue
in. Starting with WO 5.4 there is a cover method in WOApplication
that returns the version of WebObjects.
Nice. I suppose some reflection could do the trick then, for versions
prior to 5.4.
Thanks,
Flor
_______________________________________________
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