See my other reply regarding fundamental modifiers of the Java Language.
As for frameworks such as tapestry you are dealing with a Component and
Object Model (COM).
In addition, tapestry uses plastic to induce synthetic methods such as
getters and setters into your classes. See for example Objec
.1045711.n5.nabble.com/Sevice-State-Stateless-tp5716278p5716287.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apach
AFAIK, all service instances are singletons and shared across threads of
the VM unless you declare them perthread as you do with your UserService.
Having multiple independent instances of that service is your actual
problem, as you would have to declare them in source using modifiers,
which is no
> I am also intrigued by the "generic DAO" concept in the tawus blog, but
> fail to see how to implement, so far.Would be great if this concept,
> if
> I am understanding correctly, could be standardized to pick up directly
> from
> the entities directory for basic CRUD. And similarly pick
This should have gone to the mailing list so I will repost it here:
Hi Russell,
see http://tapestry.apache.org/using-select-with-a-list.html for a
thorough explanation on how to do this.
The problem I see in your approach is that you a an arbitrary number of
select components having the same na
