Use the loggerless profile for web application container which already embeds slf4j and log4j (like JBoss): mvn clean package -Ploggerless
Release History Build weasis-pacs-connectorĮxecute the maven command mvn clean package in the root directory of the project and get the package from /target/weasis-pacs-connector.war. (default template: /weasis.jnlp) building a jnlp file from a template (jnlp template path, jnlp properties and jnp arguments can be passed via URL parameters, see the JNLP Builder documentation) Launching Weasis at Patient and Study level, compliant to the IHE IID profileīuilding the xml manifest (containing the necessary UIDs) consumed by Weasis to retrieve all the images by WADO-URI requests New protocol to launch Weasis with requested images, replacing Java Webstart This component gathers different services ( ⚠️ => deprecated): Service It only works with Weasis 3.5 (or superior) installed on the system with a native installer. ❗As Java Webstart is deprecated, prefer to use the weasis protocol (defined below by the /weasis service) instead of Java Web Start because it has been removed from Java 11 release and because the end of public Oracle Java 8 updates from April 2019. This is the latest version working with dcm4chee 2.18.x. The 6.x branch requires Java 7+ and a servlet container 2.5.It works by default with dcm4chee-arc-light. The master branch requires Java 8+ and a servlet container 3.1.
#K pacs dicom viewer archive
Note: A simpler configuration without weasis-pacs-connector is possible if the DICOM archive has DICOMWeb services (see examples here). If you want to make your own connector without weasis-pacs-connector, follow these instructions. Weasis-pacs-connector provides the easiest way to launch the Weasis DICOM viewer from a web context (see URL examples) and to connect Weasis to any PACS supporting WADO-URI.