The thing is, you can inject the Request object itself. The proxy
encapsulates the service scope ... so any thread can invoke methods on
the proxy, but will end up accessing the per-thread Request
implementation. Actually, no different than injecting RequestGlobals,
the proxy handles delegation t
That solves the problem, thanks, folks.
I put my contribute code in AppModule here for later reference.
===
public static void contributeBindingSource( MappedConfiguration configuration,
@InjectService("RequestGlobals")
RequestGlobals request
Remember that service injection is ONLY through the constructor,
whereas component injection is ONLY through private instance
variables.
On Nov 27, 2007 2:57 PM, Filip S. Adamsen <[EMAIL PROTECTED]> wrote:
> Hi Jeffrey,
>
> Try injecting org.apache.tapestry.service.Request:
> http://tapestry.apach
Hi Jeffrey,
Try injecting org.apache.tapestry.service.Request:
http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry/services/Request.html
That should do the trick.
-Filip
jeffrey ai skrev:
Thanks, Filip.
I tried to inject RequestGlobals, like I did for normal component, but that
d
Thanks, Filip.
I tried to inject RequestGlobals, like I did for normal component, but that
doesn't work.
It's not correctly injected.
Filip S. Adamsen-2 wrote:
>
> Have you tried injecting the request directly into your BindingFactory?
>
> -Filip
>
> jeffrey ai skrev:
>> Hi Folks,
>>
>> I th
Have you tried injecting the request directly into your BindingFactory?
-Filip
jeffrey ai skrev:
Hi Folks,
I think I'm missing something here, but would appreciate a shove in the
right direction.
I created a new BindingFactory, introduced a new prefix, and successfully
contributed it to Bindin
Hi Folks,
I think I'm missing something here, but would appreciate a shove in the
right direction.
I created a new BindingFactory, introduced a new prefix, and successfully
contributed it to BindingSource.
I am trying to do the following things in my new BindingFactory,
=
public Bindi
