anchor.diff:  Map<String, WorkDefinitionImpl> workitemsFromRepo =
     WorkItemRepository.getWorkDefinitions("http://docs.jboss.org/jbpm/v6.0/repository/");
   ----
  -This will provide you with all serviced defined in the repository (and declared in your index.conf file). You can then get more detailed information about each of services in the repository using their name as deflared in the service wid file, for example when using the twitter wid configuration from above we could do:
  +This will provide you with all services defined in the repository (and declared in your index.conf file). You can then get more detailed information about each of services in the repository using their name as declared in the service wid file, for example when using the twitter wid configuration from above we could do:
   [source]
   ----
   workitemsFromRepo.get( "Twitter" ).getName();                 // "Twitter"
  
positive.code: 
  
  * The name property is the unique name for your service
  * The parameres property defines the service data inputs giving them a name and a type
  * You can similarly to input parameters also define the "results" property for service data ouputs (same structure applies)
  * The icon property should refer to a file with the given file name in the same folder as
    the extended configuration file (so it can be downloaded by the import wizard and used in the process
  
negative.code: entityManagerFactory
  ----
  * The documentation property defines a documentation file that describes what the service does and how it works. This property should refer to a HTML file with the given name in the same folder as the extended configuration file (so it can be shown by the import wizard when browsing the repository).
  * The dependencies property defines additional dependencies that are necessary to execute this service. This usually includes the handler implementation JAR, but could also include additional external dependencies. These dependencies should also be located on the repository on the given location (relative to the folder where the extended configuration file is located), so they can be downloaded by the import wizard when importing the service. If the necessary dependencies are located in a maven repository you can define them via the mavenDependencies property, for example:
  [source]
  ----
  "mavenDependencies" : [
  