RE: [aspectwerkz-user] defining a new aspect at run-time

Hi guys,

Thanks for the response, I left on vacation the next day after my post so I couldn't get the chance to try your suggestions:

|You should definitely use a deployment scope. Your pointcut is very
|generic "call( bsh stuff)" and hence it will be quite expensive if you
|don't use one.

It's actually very specific - it only targets the single method 'bsh.This.toString'. 

However, I'd like to be able to work with a very large scope that would essentially allow me to aspect anything dynamically. Essentially, I'd like as close as possible to having a scope such as "* *(..)". I don't care much about startup performance. The context is testing of a large weblogic-based distributed system. So my goal is to be able to startup a big cluster and dynamically weave aspects (1) for monitoring (2) for the creation of distributed test cases. Do you think this is a feasible at all?

Bottom line: I need to be able to modify class behavior in a relatively arbitrary fashion, at run-time.

The other option I was playing with is recompiling classes locally and hotswaping them through the wire on the servers. But I'd be much more convenient to instrument them through aspects.

Thanks,
Boris

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.