Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] impact of javaagent with no aspects

The agent will have a look around for an aop.xml but if it doesnt find
one or there are no aspects, it  doesn't build any weaver instances
and just runs as a lightweight pass-thru for classes that get loaded.



On 05/12/2007, Ashley Williams <ashley.williams@xxxxxx> wrote:
>
> Hi,
>
> I would like to preconfigure our production system startup scripts to
> include the -javaagent:aspectjweaver-1.5.3.jar option, albeit with no
> aspects made visible to the weaver. That way if we have a problem then we
> can drop in our tracing/profiling aspect jar file into the lib directory
> without touching the script and just restart.
>
> However because we are at the early adoption stage, can we be sure that the
> mere inclusion of the javaagent option won't noticably impact performance?
>
> I haven't a clue what the weaver does in premain() behind the scenes and I
> really don't want to do anything that will affect anbody's confidence in
> AspectJ.
>
> Thanks
> - Ashley
>  ---
>
>  This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
>
>  Please refer to
> http://www.db.com/en/content/eu_disclosures.htm for
> additional EU corporate and regulatory disclosures.
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>


Back to the top