I suspect what's happening is that you have read a list of rows from your
database into a collection and stored the collection as a property of your page.
The most likely culprit is that you are not implementing initialize:
public void initialize()
{
_myDatabaseCollection = null;
}
What happens is that one the first request cycle, it does the query. You click
the delete link. The same page instance comes out of the pool (cause there's
just one user) and the collection is filled in already. Deleting the row from
the database doesn't affect the in-memory collection, so there it is.
A quick way to verify this is to turn caching off (see the FAQ). You'll
probably see correct execution because you are guaranteed to get a new page
instance each request cycle.
--
[EMAIL PROTECTED]
http://tapestry.sf.net
> I have a simple page with a dynamic list (ie., a list with content extracted
> from a db). Each row has its delete and update link (using DirectLink
> component).
> Update seems to work fine, since another page with a form to modify the row
> is shown, and after submiting the page list appears up to date (with the recent
> changes). The problem is the delete link: the list page is not updated. The only
> difference is: in the first case, the navigation starts in the list page, then
> goes to the form page, and finally to the list page again; in the second case,
> only the page list is visited.
> After performing the action associated with a direct link, which is the
> proper manner to navigate to another page? and how can I force that page to be
> regenerated? (I mean, I don't want to navigate to a cached page).
> Thanks,
> Dar�o
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
