Hi all,
as there is an open jira (
http://opensource.atlassian.com/projects/spring/browse/SPR-2484) for
pacthing @Configurable to support before-construction injection I decided to
wait for this fix instead of duplicating the provided aspects and
annotations just to change the advice type.
I hav
> Well, to be precise, there is this minor complication of redefining the
> advice to configure the bean before constructor execution. And you can take
> advantage of spring-annotations to avoid cluttering your xml app context
> (that's if you are reluctant to autowiring). What I can do is to updat
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
a project for what? there is nothing to do but to configure spring in the
> context xml file, put @Configurable on your page/component, and configure
> the aspectj agent in your launch config.
:) . Yep, that's everything .
Well, to be p
a project for what? there is nothing to do but to configure spring in the
context xml file, put @Configurable on your page/component, and configure
the aspectj agent in your launch config.
:) . Yep, that's everything .
-igor
On 3/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> > > I
Right.
Eelco
On 3/23/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> a project for what? there is nothing to do but to configure spring in the
> context xml file, put @Configurable on your page/component, and configure
> the aspectj agent in your launch config.
>
> -igor
>
>
> On 3/23/07, Eelco H
a project for what? there is nothing to do but to configure spring in the
context xml file, put @Configurable on your page/component, and configure
the aspectj agent in your launch config.
-igor
On 3/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> > It's cool that it can be done like that
> > It's cool that it can be done like that. However, it's still not clear
> > to me what the advantage (besides giving people more choice if they
>
> It isn't clear to me either. But as I know of some people (including myself)
> that i's using @Configurable to inject their domain objects (this is
It's cool that it can be done like that. However, it's still not clear
to me what the advantage (besides giving people more choice if they
It isn't clear to me either. But as I know of some people (including myself)
that i's using @Configurable to inject their domain objects (this is the
spring
thats why you use the aspectj weaver/loader, it weaves a deserialization
handler into the object to reinject the dependencies.
-igor
On 3/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
It's cool that it can be done like that. However, it's still not clear
to me what the advantage (besides
It's cool that it can be done like that. However, it's still not clear
to me what the advantage (besides giving people more choice if they
like) of this would be... Whereas wicket-spring works right out of the
box now, in your case users would have to do something extra (set up
AspectJ).
Also, for
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
heh, the biggest advantage of @SpringBean is that it is done _before_ the
> constructor. i use services in the constructor all the time. maybe you can
> tweak the aspectj aspect to also do it before as well.
(But do you explicitly invoke the
heh, the biggest advantage of @SpringBean is that it is done _before_ the
constructor. i use services in the constructor all the time. maybe you can
tweak the aspectj aspect to also do it before as well.
(But do you explicitly invoke these services from inside the constructor or
just delay exe
heh, the biggest advantage of @SpringBean is that it is done _before_ the
constructor. i use services in the constructor all the time. maybe you can
tweak the aspectj aspect to also do it before as well.
-igor
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
Here is an example of using @Con
Here is an example of using @Configurable to integrate spring with wicket as
some people has asked me for one. To launch it just:
1) set MAVEN_OPTS=-javaagent:/aspectjweaver.jar in
the env.
2) run 'mvn jetty:run'
Notice that dependencies are injected *after* constructor execution, so for
this si
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> i wouldnt be able to do this with @Configurable because since my
> genericdataprovider is not @Configurable and there is no way to make it so
> it cannot restore its, what would have to be a transient, reference to the
> genericfinder.
>
I c
> Yes, you need one prototype bean definition for each injected page
> and/or component. That's the spring way after all. You get all the power of
> XmlApplicationContext (with which you can do more that vanilla injection) at
> the expense of dealing with xmls.
>
in my apps i use a lot of panels
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
Hi Igor, I see your points. Here's what I think about them.
1) @Configurable is a type-level annotation. so if you want any control
> over what is injected you have to declare it in the applicationcontext. i
> have a ton of pages and components
Hi Igor, I see your points. Here's what I think about them.
1) @Configurable is a type-level annotation. so if you want any control over
what is injected you have to declare it in the applicationcontext. i have a
ton of pages and components that get injected and i would really hate to
have to ma
there are a couple of things i personally dont like about it
1) @Configurable is a type-level annotation. so if you want any control over
what is injected you have to declare it in the applicationcontext. i have a
ton of pages and components that get injected and i would really hate to
have to ma
On 23/03/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
> >
> > Maybe it's a silly question, but how did you find that page about Spring?
> I see nothing from the main wiki page that would lead to that page.
>
> I arrived there from a link in the wicket-spring demo applications :).
Hmm - I'll have to
Maybe it's a silly question, but how did you find that page about Spring?
I see nothing from the main wiki page that would lead to that page.
I arrived there from a link in the wicket-spring demo applications :).
Cheers,
Carlos
Robert
it provides proxies in order to make serialization for clustering and
backbutton support as cheap as possible.
Yep, that's why I suggested to keed dependencies transient (as the targets
of the wicket-spring proxies are). So you don't even need to serialize a
thin proxy.
. So you can declare
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrote:
I'm very new to Wicket (with no more than a few hours of fly). I would
like to integrate it with the spring AplicationContext/BeanFactory so I've
been reading the solutions described in
http://www.wicket-wiki.org.uk/wiki/index.php/Spring.
Ma
I think Igor and the others who have been working on Spring
integration can answer this better, but Wicket's special sauce is that
it provides proxies in order to make serialization for clustering and
backbutton support as cheap as possible.
Eelco
On 3/23/07, Carlos Pita <[EMAIL PROTECTED]> wrot
Hi all,
I'm very new to Wicket (with no more than a few hours of fly). I would like
to integrate it with the spring AplicationContext/BeanFactory so I've been
reading the solutions described in
http://www.wicket-wiki.org.uk/wiki/index.php/Spring. I've nothing to object
to them but I think it woul
25 matches
Mail list logo
