Starting in 12.2.1, you can debug your XSLT maps using the SOA Debugger. You can add breakpoints at strategic locations in the XSLT map. When debugging, the debugger halts execution at the breakpoints, enabling you to verify the data and output.

XSLT maps can be complex, making them difficult to debug. For example, you may have a Java function or other functionality that is best tested in the application server. Also, you might find it easier to debug in the application environment, as the XSLT may be invoked from many different applications in the server. The SOA debugger provides remote debugging capability for XSLT maps that have been deployed in the application server.

You can debug any XSLT transformation used in a BPEL process or Mediator. When the BPEL process or Mediator is invoked in the composite, the debugger pauses at the breakpoints defined in the map. The XSLT map opens in JDeveloper and user data corresponding to the XSLT processing appears in the Data window.

You can also use the debugger with your Oracle Service Bus projects. For more details on using the debugger with Service Bus projects, see Debugging Oracle Service Bus Applications.