• 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: Storing EOQualifiers in an EO
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Storing EOQualifiers in an EO


  • Subject: Re: Storing EOQualifiers in an EO
  • From: Alexis Tual <email@hidden>
  • Date: Sat, 20 Oct 2012 15:41:56 +1100

Hi David,

I did something similar a while ago : we gave the hability to create rules for defining dynamic groups of users. The rules are made of pre-defined basic operators ("is member of", "has role"...) but can be combined by the user to define complex rules.
So to do that, we created a model for storing these rules and then we convert these rules to EOF qualifiers when evaluating.

I'm not sure it will help but you can take a look at eos EORegle, EORegleNode, EORegleOperateur : https://subversion.renater.fr/cocktail/FRAMEWORKS/FwkCktlPersonne/trunk/Sources/org/cocktail/fwkcktlpersonne/common/metier/
...and components to edit rules like there was back then in the EOModeler : 
https://subversion.renater.fr/cocktail/FRAMEWORKS/FwkCktlDroitsUtilsGuiAjax/trunk/Sources/org/cocktail/fwkcktldroitsutilsguiajax/serveur/components/

Cheers,

Alexis

2012/10/20 David Avendasora <email@hidden>
Hey all,

I've got a situation where I'm allowing the user to create some basic business rules within the application at runtime. I'm planning on creating EOQualifiers based on their input that will then be used to determine how to categorize EOs in one of our Entities. Kinda like:

boolean studentMeetsRequirements = aSchool().enrollmentRequirement().evaluateWithObject(aStudent());
if(studentMeetsRequirements) {
aStudent().setStatus(StudentStatus.ACCEPTED);
} 

In this example the user would be able to create an arbitrarily complex set of rules that I will then turn into the enrollmentRequirement() EOQualifier, and each School can have it's own set of rules which will be stored in the database just like any other attribute of a School.

What I want  to know is if anyone has done something similar and has a good design pattern for it. I've got a decent idea of how to do it, but before I go creating it I figured I'd ask if anyone has any experience they care to share. I'm specifically looking for ideas on how to store EOQualifiers in the database.

Thanks!

Dave

—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™
—————————————————————————————
David Avendasora
Senior Software Abuser
Kaiten, Inc.





 _______________________________________________
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

References: 
 >Storing EOQualifiers in an EO (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: WOWODC 2013?
  • Next by Date: Re: Storing EOQualifiers in an EO
  • Previous by thread: Re: Storing EOQualifiers in an EO
  • Next by thread: Re: Storing EOQualifiers in an EO
  • Index(es):
    • Date
    • Thread