Hi Again -
Is there a specific reason why watch parameter for @Cached annotation
requires public property when using default prop binding? This is an
inconvenient limitation IMO, as I don't necessarily want to expose my
watch property publicly. For example, my watch on getShoppingCart may
be something like this:
@Cached(watch=cartWatch)
public ShoppingCartBean getShoppingCart() {
Long userId = getUserId();
Long cartId = getCartId();
log.debug(cartId: {}, userId: {}, cartId, userId);
return cartService.findShoppingCart(cartId, userId);
}
private long getCartWatch() {
Long userId = getUserId();
Long cartId = getCartId();
if(userId == null) userId = 0L;
if(cartId == null) cartId = 0L;
return userId + cartId;
}
Minor issue, but unless there is a strict reason behind it, I thing
watch should allow any scope.
Adam
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
