tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Adams (JIRA)" <...@tapestry.apache.org>
Subject [jira] Assigned: (TAPESTRY-1612) Allow access to the PageTester registry
Date Sat, 01 Mar 2008 17:04:51 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dan Adams reassigned TAPESTRY-1612:

    Assignee: Dan Adams

> Allow access to the PageTester registry
> ---------------------------------------
>                 Key: TAPESTRY-1612
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1612
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.4
>            Reporter: Dan Adams
>            Assignee: Dan Adams
>         Attachments: TAPESTRY-1612.patch
> PageTester creates it's own registry but then you don't have any access to it on order
to get services. I've got other tests set up which create a registry, load tapestry-hibernate
and my app module, and then allows me to use @Inject to inject services directly into my test
classes (it's really very cool). This is great because I can start up an hsqldb in-memory
db and then test my dao services for real very quickly. Now I want to take it a step further
and be able to use PageTester to test pages that make use of dao services. The problem is
that I can't do this if I can't access the registry to retrieve services. I could create a
separate registry just so that I could use my dao services in my test to load data but that
doesn't seem very clean.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message