hi michael,
it should work with just @Inject. You can take a look at the
BeanEditForm component... it uses a bunch of @Injects.
(T5.0.4)
g,
kris
Michael Maier [EMAIL PROTECTED]
04.05.2007 11:37
Bitte antworten an
Tapestry users users@tapestry.apache.org
An
Tapestry users
ok, I solved... requestPageCache must be private...I don't know why
the variable to be injected must be declared private but tapestry
could log a warning, that the instance variable is not private and
therefor it won't be injected...
Am 04.05.2007 um 11:37 schrieb Michael Maier:
I wonder why this is as well, it's happened at least a couple times now -
at least enough that this idea may need to be re-evaluated. (I can help if
it's just reflection stuff)
On 5/4/07, Michael Maier [EMAIL PROTECTED] wrote:
ok, I solved... requestPageCache must be private...I don't know
On 5/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
I wonder why this is as well, it's happened at least a couple times now -
at least enough that this idea may need to be re-evaluated. (I can help if
it's just reflection stuff)
This way the framework (inner javassist stuff) only need to
I hope that's not the only reason. ...The framework should be working hard -
not the users. ;)
On 5/4/07, Massimo Lusetti [EMAIL PROTECTED] wrote:
On 5/4/07, Jesse Kuhnert [EMAIL PROTECTED] wrote:
I wonder why this is as well, it's happened at least a couple times now
-
at least enough
You should be seeing some logged console messages about private variables.
Only private instance variables may have annotations on them; yours is
package private not private.
On 5/4/07, Michael Maier [EMAIL PROTECTED] wrote:
Hi List,
I'm trying to inject via @Inject annotation a service
Tapestry works by identifying the points at which a variable is read or
updated and often replaces that with a method invocation that does something
more complicated (such as persistent field values or component parameters).
If the field is private, Tapestry is able to make the changes within a
Sure beats abstract properties, though!
On 5/4/07, Howard Lewis Ship [EMAIL PROTECTED] wrote:
Tapestry works by identifying the points at which a variable is read or
updated and often replaces that with a method invocation that does something
more complicated (such as persistent field values
