anchor.diff:  ----
   
   The next phrase to process includes now the "same" action with no need of stopping the console application.
  +
  +Note: use RelProxy 0.8.7 or upper, this release adds an improvement when embedding by this way.
  +
  
positive.code: The second option is preferred to embed RelProxy Java in your Java framework because it is based on interfaces, no public class of RelProxy is needed to expose
  in your API, because bootstrap can be executed into your framework. We are going to use the simplified version of the API using `JProxyScriptEngineFactory.create()`.
  
  The `JProxyScriptEngine` has been designed to provided the same functionality than `JProxy`, that is, the same methods, but in this case using a pure interface.
  
  A simple example is the best path to show how to embed RelProxy, this example, RelProxyBuiltin (project relproxy_builtin_ex), is included in the RelProxy Examples repository.
  It defines two listeners to be implemented and registered by code of end user, one listener to show the options and the other to execute the corresponding selected action.
  This mini framework and use example is developed using NetBeans and Maven.
  
  There are two packages:
  
negative.code:     }
  ----
  
  The public method `RelProxyBuiltin.getJProxyScriptEngine()` must be called in starting time to configure RelProxy. If RelProxy is not configured and enabled there is no performance penalty.
  
  Remember that the proxy object returned by `create(...)` method correctly calls the method `hashCode()` and `equals(Object)` in the internal true listener object for
  identity purposes required by the listener collection/registry.
  
  
  This is the example code of this console based program (names are inspired on JUnit but is not really a JUnit test example):
  
  [source,java]
  .Main.java
  