Dan Haywood created ISIS-1229:
---------------------------------

             Summary: Calling nextRequest() in an integration test should clear 
any @RequestScoped services.
                 Key: ISIS-1229
                 URL: https://issues.apache.org/jira/browse/ISIS-1229
             Project: Isis
          Issue Type: Bug
          Components: Core
    Affects Versions: core-1.8.0
            Reporter: Dan Haywood
            Assignee: Dan Haywood
            Priority: Minor
             Fix For: 1.10.0


Raised by Oscar:
Related with this, I’m trying to test the following:

   @Test
    public void totalOrRatio() {

        // given
        kit.assignToPerson(account.getAccountOwner());

        this.nextRequest();

        kit.getRegisteredForPerson().setSex(Sex.Man);

….
}

Where the Kit.getRegisteredForPerson() is cached:

    // {{ RegisteredForPerson (property)
    @Property(editing = Editing.DISABLED, notPersisted = true)
    @MemberOrder(sequence = "1")
    public Person getRegisteredForPerson() {
        return this.queryResultsCache.execute(new Callable<Person>() {
            @Override
            public Person call() throws Exception {
                return Kit.this.findRegisteredToPerson();
            }
        }, this.getClass(), "findRegisteredToPerson");
    }

    // }}


Despite invoking “this.nextRequest()” on the integtest, seems that the cache is 
still alive (being it a @RequestScoped service).

Would this also need to be improved for testing @RequestScoped services? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to