Community
Participate
Working Groups
jkca (7/24/2001 4:40:29 PM) While working on the JSP breakpoints, DW suggested I add an attribute to the JSP breakpoint named "classFilePattern". This is used by the JDIDebugTarget to install breakpoints in JSPs. It would be a useful optimization for all breakpoint factories to add this attribute as it would simplify the getTopLevelTypeName code. If we use this mechanism as the sole class file pattern provider, then each debug model could add it's own breakpoints without having to modify the JDIDebugTarget code. This enables us to debug many languages which eventually get compiled to java byte code without futher modifying the Debug Model.
Work is complete. The JDI debug model now supports "pattern breakpoints". The pattern of the runtime class file is specified as an attribute of the breakpoint. When a class is loaded at runtime that matches the pattern, and the resource name with which the breakpoint is associated matches the debug attribute "source file name", the breakpoint is installed. This is generic for non-Java-Source -> Java Source -> Class File debugging. The current limitation is that the class file must point back to the original non-java source for debug attributes. The breakpoint is associated with the non-java source resource.
verified.
