Posts by Nicolas Roduit

With KPACS and EFILM, I guess it gets the images by DICOM Retrieve not by http GET (WADO).

If Weasis build the WADO url for downloading the images, it means weasis-pacs-connector works correctly (get the image references by DICOM C-Find).

I am surprised that you have this problem by upgrading Weasis 2.0.3 to 2.0.4 because there is no modification in the class which handles the WADO URL and connection. Have you tried to rollback to 2.0.3?

In the http connection, I don't understand from where comes the cookie reference. Is there a cache in the WADO service?

I installed 1.4.17d and made some adjustments for the IIS web server (handling dgate.exe as cgi, add the mime types jnlp and properties).

To make working Weasis 2.0, I simply extracted weasis-war in the webserver directory and then I went on the web page and clicked on the view link at study level.

However, there is a bug when the patient birthdate is empty or has a non valid value. This has already been fixed in 2.0.1 (see http://www.dcm4che.org/jira/se…ectId=10090&version=11280). I would recommend in the xml script to not insert empty dates (like PatientBirthDate="") as it is not consider as valid by xsd schema.

I've also seen in the manifest overrideDicomTagsList="0x00000000" that was used as a workaround but this issue should be fixed in version 2.0, see http://www.dcm4che.org/jira/browse/WEA-262

The version 2 have a higher level of customization, it let you change some default configurations in "weasis-ext-config.properties" and "resources.zip" which contains the application resource files (logo, presets, LUTs...).
http://www.dcm4che.org/conflue…ay/WEA/Weasis+Preferences