Community
Participate
Working Groups
If a debug configuration for the current stylesheet hasn't been set, then the Debug As -> XSLT Transformation should either: 1. Prompt to use one of the XML Source documents that may already be open. 2. Prompt to use an XML document that may reside within the workspace 3. Prompt to use an XML Document that may reside externally (i.e. on the web or external file system). It would also be nice to be able to switch which file is used as input once in the debugger. Currently the debugger just creates a new launch configuration, without prompting for which XML input file to be used.
Doug, re-asssigning to you as you noted in the requirements page on 1/09/08 that this was completed. Does it have a unit test? I've put into the whiteboard, an M1 to indicate that this is target for our M1 build.
I've changed the launch shortcut to behave as follows depending on the current selection: Exactly 1 XML file, 0 XSL files: Launch assuming embedded stylesheet instruction 0 XML files, 1 or more XSL files: Open dialog - prompt for input file Exactly 1 XML file, 1 or more XSL files: Launch Of course, other situations are possible with XSLT 2.0, but this is too complicated to implement at the moment.
Mass Migration to wtp.inc.xsl
Closing
mass update to 3.1 target due to movement from wtp incubator to wtp source editing lost the original milestones.
