I've uploaded a new version, which uses an Interceptor to fake the
GuiceFilter. Now only 3 init parameters are needed for the StripesFilter.
Also, injection is possible in interceptors. Check out the new documentation
at http://code.google.com/p/stripes-guicer/
--
View this message in context:
Looks much better Sam. :) I'm curious as to why you needed a custom
action resolver. Was it to get Guice available in the ActionBeanContext?
Gregg
Sam Beran wrote:
> I've uploaded a new version, which uses an Interceptor to fake the
> GuiceFilter. Now only 3 init parameters are needed for the
2008/6/5, Gregg Bolinger <[EMAIL PROTECTED]>:
> Looks much better Sam. :) I'm curious as to why you needed a custom
> action resolver. Was it to get Guice available in the ActionBeanContext?
>
I think it's because Guice AOP works only on objects instanciated by
Guice. So I guess the ActionResolve
Gregg Bolinger-7 wrote:
>
> Looks much better Sam. :) I'm curious as to why you needed a custom
> action resolver. Was it to get Guice available in the ActionBeanContext?
>
Thanks Gregg. The custom ActionResolver is to allow constructor injection.
It lets Guice create the ActionBean instanc
gerald.quintana wrote:
>
>
> I think it's because Guice AOP works only on objects instanciated by
> Guice. So I guess the ActionResolver uses Guice to instanciate
> Actions.
>
That's correct.
gerald.quintana wrote:
>
> Can we get source code? Subversion seems to be empty and
> svn checkou
I really wish there was a cleaner way to create the ActionBean, I generally
dislike inheritance and it seems heavy handed to force my ActionResolver on
someone. I really like constructor injection though, as it makes it trivial
to identify dependencies at test-time.
Do it all
Sam Beran wrote:
By the way thanks for your work,
Stripes+Guicer+Stripernate+Hibernate=the perfect stack!
You're welcome! I need to try Stripernate sometime. Does it work with JPA at
all?
Sam
Stripernate requires Hibernate but it works with JPA annotations.
Stripersist is pure JPA -
Sam Beran
Sent: Thursday, June 05, 2008 1:19 PM
To: stripes-users@lists.sourceforge.net
Subject: Re: [Stripes-users] Ann: Stripes-guicer (new version)
Gregg Bolinger-7 wrote:
>
> Looks much better Sam. :) I'm curious as to why you needed a custom
> action resolver. Was it to ge
I double checked the SVN trunk and the standard lifecycle stages seem to
look up the actionBean if they need it. From the test I remember doing
of this a few months ago, I recall it working fine when you create the
ActionBean and save it appropriately BEFORE the standard point where it
would h
David G Friedman wrote:
>
> You need to have your Interceptor run @Before the
> LifecycleStage.ActionBeanResolution stage. This is where you do your
> Guice constructor instantiation and save your new bean into the request
> scope (or the session scope if you used the @SessionScope annotation)
ubject: Re: [Stripes-users] Ann: Stripes-guicer (new version)
David G Friedman wrote:
>
> You need to have your Interceptor run @Before the
> LifecycleStage.ActionBeanResolution stage. This is where you do your
> Guice constructor instantiation and save your new bean into the request
>
On Jun 5, 2008, at 1:13 PM, Aaron Porter wrote:
> Sam Beran wrote:
>>
>>> By the way thanks for your work, Stripes+Guicer+Stripernate
>>> +Hibernate=the perfect stack!
>> You're welcome! I need to try Stripernate sometime. Does it work
>> with JPA at all? Sam
> Stripernate requires Hibernate b
12 matches
Mail list logo
