[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-users] To LTW or not to LTW? :-)
|
Nobody replied to this so far... are there no figures of this known? Or does it depend so heavily on how much aspects and how big your codebase is that this is hard to tell?
regards,
Wim
2006/10/10, Wim Deblauwe <wim.deblauwe@xxxxxxxxx>:
I am interested in the cost of LTW also. We are also considering using @Configurable of Spring 2.0. I suppose LTW only impacts startup-time of the JVM? Any figures on that somewhere?
regards,
Wim
2006/10/9, nlif <naaman@xxxxxxxxxxx![]()
>:
Thanks Wes.
We are not going to write aspects in the forseen future. We only use
pre-defined Spring Framework services, namely the auto-wiring of domain
objects upon instantiation (aspectJ provides the means to intercept the Java
<new> operation. So I guess we're not aspectJ developers per se. So, from
this perspective, we probably don't need the AJDT. Not that it would hurt us
either...
You mentioned time/space costs of LTW. Could you please elaborate on these?
Indeed we ran into OutOfMemory problems at first, which were solved by
increasing the JVM's maxPermSize.
Thanks again,
Naaman
--
View this message in context:
http://www.nabble.com/To-LTW-or-not-to-LTW--%3A-%29-tf2388608.html#a6713270
Sent from the AspectJ - users mailing list archive at
Nabble.com.
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx![]()
https://dev.eclipse.org/mailman/listinfo/aspectj-users
![]()
