• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO version from code (was: Qualifier creation)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO version from code (was: Qualifier creation)


  • Subject: Re: WO version from code (was: Qualifier creation)
  • From: "Mr. Pierre Frisch" <email@hidden>
  • Date: Sat, 2 Feb 2008 15:29:13 -0800

I am scratching my head at the purpose of being WO independent but depending on other projects. For deployment WO is essentially free so I do not really see the gain.

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.

Cheers

Pierre
--
Pierre Frisch
email@hidden


On Feb 2, 2008, at 6:40, Florijan Stamenkovic wrote:

Like Mike said, JBND is made so to be as data storage type independent as possible, even though it's primary purpose always was to bind WO and Swing. I will make sure that translations for WO qualifiers are provided.

Talking about WO evolution, I already have a few places in my code where it might be beneficial to have different behavior depending on the WO version. Is there a simple and fail-proof way to check the version of the libraries (in my case those would be client libraries) during runtime? If not, I'd be happy to make a feature request, and urge others to do the same.

My best,
Flor

On Feb 01, 2008, at 18:16, Mr. Pierre Frisch wrote:

Why not use the WebObjects one? As least it would stay compatible as we make it evolve for the next version…

Pierre
--
Pierre Frisch
email@hidden


On Feb 1, 2008, at 12:54, Florijan Stamenkovic wrote:

Lachlan, Mike,

Thanks for your replies.

On Feb 01, 2008, at 16:25, Mike Schrag wrote:

Entity Modeler has an EOQualifier format parser in it (that is not currently the one being used), and Cayenne has its expression parser. Both of these are open-source and could be easily adapted. In Entity Modeler, look in org.objectstyle.eomodeler.model.qualifiers.

Sounds great, didn't think of that...

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



_______________________________________________ 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
  • Follow-Ups:
    • Re: WO version from code (was: Qualifier creation)
      • From: Florijan Stamenkovic <email@hidden>
References: 
 >Qualifier creation (From: Florijan Stamenkovic <email@hidden>)
 >Re: Qualifier creation (From: Lachlan Deck <email@hidden>)
 >Re: Qualifier creation (From: Mike Schrag <email@hidden>)
 >Re: Qualifier creation (From: Florijan Stamenkovic <email@hidden>)
 >Re: Qualifier creation (From: "Mr. Pierre Frisch" <email@hidden>)
 >WO version from code (was: Qualifier creation) (From: Florijan Stamenkovic <email@hidden>)

  • Prev by Date: Re: WOLips Entity Modeler and Derby SQL generation issue. (drop table cascade)
  • Next by Date: Re: Deploying a simple web application on Tomcat
  • Previous by thread: WO version from code (was: Qualifier creation)
  • Next by thread: Re: WO version from code (was: Qualifier creation)
  • Index(es):
    • Date
    • Thread