Page Comparison

...

...

• Add in /weasis/conf/ext-config.properties:

  Code Block
  felix.auto.start.80= \ ${weasis.codebase.url}/plugins/weasis-isowriter-2.0.03.jar

• Place the file "weasis-isowriter-2.0.03.jar" in the directory "/weasis/plugins"

...

• Build "weasis-ext.war" with the following structure:

  Code Block
  +--weasis-ext/ | +--WEB-INF/ | +--web.xml | +--conf/ | +--ext-config.properties | +--plugin1.jar | +--plugin2.jar

• In /weasis-ext/conf/ext-config.properties, add the plug-ins references:

  Code Block
  felix.auto.start.80= \ ${weasis.codebase.ext.url}-ext/plugin1.jar \ ${weasis.codebase.ext.url}-ext/plugin2.jar

  Info
  Note: Using "${weasis.codebase.ext.url}" requires to place weasis-ext.war in the same web container as weasis.war. The advantage is that the base URL is allows to keep the base URL abstract, so moving these two files the package to another server won't be a problem. Otherwise absolute URLs must be used.

  Add Java VM property to load weasis-ext.war:
  With weasis-pacs-connector: adapt this property in weasis-jnlp.xml (see

  The default value of "${weasis.codebase.ext.url}" is "${weasis.codebase.url}-ext".

• 'weasis-ext' is the default web context when launching Weasis, using another web context requires to modify the porerty weasis.ext.url in weasis-pacs-connector configuration).

  Code Block
  <argument>-VMPfelixweasis.extendedext.config.propertiesurl="${weasisserver.base.url}/weasis-newext

  or adding the code base for plugins (cdb-ext) directly in the URL: http://localhost:8080/weasis-pacs-connector/viewer?patientID=9702672&cdb-ext-config.properties"</argument> =http://localhost:8080/plugins/weasis-ext

Example with that make a package of weasis-isowriter plugin:

• Build "weasis-ext.war":

  Code Block
  +--weasis-ext/ | +--WEB-INF/ | +--web.xml | +--ext-config.propertiesconf/ | +--weasis-isowriter-2.0.0.jar

  In /weasis

  -ext

  /ext

  -config.properties

  :

  Code Block
  felix.auto.start.80= \ ${weasis.codebase.url}-ext/ | +--weasis-isowriter-2.0.03.jar

Build OSGI services

All the plug-in type described in the list above are OSGI services that are registered and aggregated in the GUI. Building the plug-in from the Maven archetype will configure automatically the OSGI service. For adding new OSGI services, here is the procedure:

...