Stop tracing at defined boundary methods

The omit parameter filters out the defined methods, but leaves the sub-calls, which are included in the resulting sequence diagram. In contrast, the boundary parameter 'upto=<regex>' excludes the given method and all its consecutive callees.

Example

Given the class net.sf.jsequnit.example.SequenceSample containing a method boundaryMethod that consecutively calls the methods.

  • net.sf.jsequnit.example.SequenceSample.callingMethod
  • net.sf.jsequnit.example.SequenceSample.calledMethod

where the JavaDoc of the method contains a sequence diagram tag with the following boundary parameter: 

    @sequence.diagram
      test=net.sf.jsequnit.example.SequenceSampleTest#testBoundaryMethod()
      upto=net.sf.jsequnit.example.SequenceSample.callingMethod

we get a sequence diagram containing the call to the method callingMethod, but no references to the method calls of the method body (i.e. calledMethod).