Re: D2W & Strategy Design Pattern
Re: D2W & Strategy Design Pattern
- Subject: Re: D2W & Strategy Design Pattern
- From: Mark Wardle <email@hidden>
- Date: Wed, 13 Oct 2010 22:07:33 +0100
I have an entity called Relationship that clashes badly with the
heuristics in the rule system. I need to change it.
However, you could do what I do presently for these awkward spots.
pageConfiguration=xxxxx entity.name=blah
--
Dr. Mark Wardle
Specialist registrar, Neurology
(Sent from my mobile)
On 13 Oct 2010, at 20:49, David Avendasora <email@hidden> wrote:
> Okay, bear with me. I'm a D2W-novice...
>
> I must be missing something. How does D2W know what Entity that this new page configuration will be for?
>
> I'm currently getting:
>
> IllegalStateException: Couldn't find the dynamic page named QueryTeacherPerson in your DirectToWeb model.entity is null, it seems that one model, maybe ERDirectToWeb d2w.d2wmodel is not loaded!
> at er.directtoweb.ERD2WFactory.pageForConfigurationNamed(ERD2WFactory.java:179)
> at com.k12.totalview.ui.controllers.TVNavigationController.queryTeacherPersonAction(TVNavigationController.java:170)
> ... skipped 23 stack elements
> at er.extensions.appserver.navigation.ERXNavigationMenuItem.menuItemSelected(ERXNavigationMenuItem.java:131)
> ... skipped 20 stack elements
> at ognl.helperfunction.WOHelperFunctionKeyValueAssociation.valueInComponent(WOHelperFunctionKeyValueAssociation.java:50001)
> ... skipped 76 stack elements
> at com.k12.totalview.app.TVWApplication.dispatchRequest(TVWApplication.java:213)
> at com.k12.totalview.app.Application.dispatchRequest(Application.java:42)
> ... skipped 3 stack elements
>
> Dave
>
>
> On Oct 13, 2010, at 6:21 AM, Anjo Krank wrote:
>
>> pageConfiguration = "QueryStudentPerson" => displayPropertyKeys = (..)
>> pageConfiguration = "QueryTeacherPerson" => displayPropertyKeys = (..)
>> ...
>>
>>> D2W.factory().pageForConfigurationNamed("QueryStudentPerson", session())
>>
>> Obviously, you need to know what exactly you are looking for in advance.
>>
>> Cheers, Anjo
>>
>> Am 13.10.2010 um 12:08 schrieb David Avendasora:
>>
>>> Hi D2Wers,
>>>
>>> I've got the Entity "Person" in my model that can have a type of Student, Teacher, Parent, etc. They are not subclasses because it is entirely possible for a Person to be both a Teacher and a Parent simultaniously. I want to have individual search screens for each with different search criteria, but since they are all the same entity I don't see how I can follow the normal D2W convention of D2W.factory().queryPageForEntityNamed(entityName, session()) because they are all really the Person Entity.
>>>
>>> What's the best way to approach this with D2W?
>>>
>>> Thanks,
>>>
>>> Dave
>>> _______________________________________________
>>> 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
>>
>>
>
> _______________________________________________
> 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