Hi,
As a user and a consumer of Tuscany that has had to debug problems, I
have a couple of comments.
Raymond Feng wrote:
It seems to me that we could use the EventManagement in the core to
handle these in the event/listener pattern.
If possible, I would like to see Tuscany focus on the higher level event
model for component management, on enhancing the exception formatter
framework for diagnostics, and improving the wiring, contribution, and
assembly validation in a way that would surface errors and an error
context to extensions that could be implemented by a consumer.
I was referring to the fact that the apsectj-based tracing can be
enabled or disabled simply by turning on/off the JVM agent. The
annotation-based aspect doesn't require a compiler for the aspectj and
it's not invasive.
On using aspects for trace, I'm not a huge fan of performing any weaving
at runtime during class loading nor in requiring consumers to install an
instrumentation agent to turn on trace emission. Not only does dynamic
instrumentation lengthen the class load time and effect the benefits of
class sharing (in JVM's that support the technology), it assumes that
the user has installed the agent because a problem is expected. If
aspect weaving is used, I believe it should be an optional part of the
build environment and not force fit into the instrumentation agent
infrastructure.
Thanks.
--
Matthew Sykes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
