Bug 176546 - Allow custom aop.xml provider through IWeavingContext
Summary: Allow custom aop.xml provider through IWeavingContext
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: LTWeaving (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 1.6.1   Edit
Assignee: aspectj inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-06 19:42 EST by Matthew Webster CLA
Modified: 2008-06-11 12:51 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Webster CLA 2007-03-06 19:42:06 EST 
By default LTW is configured through aop.xml parsed by Xerces or a built-in JDK XML framework. An extension to IWeavingContext could allow an alternative mechanism.
Comment 1 Andrew Clement CLA 2007-10-26 06:40:24 EDT 
i think we might have done this now?
Comment 2 Andrew Clement CLA 2008-06-11 12:51:35 EDT 
Defined in version 1.2 of IWeavingContext:

	/**
	 * Allow custom parsing of aop.xml or alternative mechanism for providing 
	 * Definitions
	 * 
	 * @param loader
	 * @param adaptor
	 * @return List containing 0 or more Definition instances
	 */
    public List getDefinitions(final ClassLoader loader, WeavingAdaptor adaptor);