Hi,

According to the docs [1], it should be enough to add this to your spring
XML configuration file:

<context:load-time-weaver/>

[1]  
http://static.springframework.org/spring/docs/2.5.x/reference/aop.html#aop-aj-ltw

Maarten



On Wed, Jun 10, 2009 at 3:19 PM, Kent Larsson <kent.lars...@gmail.com>wrote:

> I skipped the AJDT plugin and am doing LTW (Load-Time Weaving) now, it
> works.
>
> In my case I added: (It might be of use to someone)
>
>
>  
> -javaagent:"/home/kent/.ivy2/cache/org.springframework/spring-agent/jars/spring-agent-2.5.6.SEC01.jar"
>
> To the Server Overview / Open launch configuration / Arguments.
>
> I'll investigate if I can use a classloader for Tomcat which I specify
> in my Spring XML configuration instead, as it would mean that the
> developers of the project won't have to mess with the server
> configuration.
>
> On Wed, Jun 10, 2009 at 10:11 AM, Kent Larsson<kent.lars...@gmail.com>
> wrote:
> > By the way. When using @Configured one has to get AspectJ working if
> > I'm not mistaken?
> >
> > I've been messing with it for a while now and it's not going great.
> > :-/ What I did was install the AJDT plugin for Eclipse and converted
> > my project to a AspectJ project, then I got stuck. How are you who
> > have it working solve the AspectJ part with Eclipse problem? Do you
> > use load time weaving? I can't find a decent manual for the AJDT
> > plugin.
> >
> > On Fri, May 29, 2009 at 12:59 PM, Kent Larsson<kent.lars...@gmail.com>
> wrote:
> >> Ah, interesting. Thanks for elaborating!
> >>
> >> On Fri, May 29, 2009 at 12:31 PM, James Carman
> >> <jcar...@carmanconsulting.com> wrote:
> >>> On Fri, May 29, 2009 at 4:04 AM, Kent Larsson <kent.lars...@gmail.com>
> wrote:
> >>>>> I try not to design my domain models in such a way
> >>>>
> >>>> Could you elaborate on this a bit, please?
> >>>
> >>> I kind of "cheat" a bit.  When there needs to be something done that
> >>> involves multiple domain entities, I usually push that logic into a
> >>> "service" class rather than into the entities themselves.  For
> >>> operations solely involving an entity and its aggregated entities, I
> >>> usually put that into the entity class itself.
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >>> For additional commands, e-mail: users-h...@wicket.apache.org
> >>>
> >>>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Reply via email to