Does Weasis support RPCs like OsiriX?

[Tamás Sipos]

You may know OsiriX well for macOS. It has a feature through which it supports a kind of remote controlling (see https://www.osirix-viewer.com/resources/ris-integration/) from other Applications.

So for example this makes it possible that OsiriX automatically opens a Study when the user clicks on a button let's say "Open DICOM Study in OsiriX" in their RIS or in any other application. OsiriX receives the remote procedure call through HTTP and performs the operation.

Is this or something similar also with Weasis possible?

[Nicolas Roduit]

This is the role of weasis-pacs-connector which implements the IHE profile "Invoke Image Display" or by a simple URL.  

[Tamás Sipos]

I downloaded the newest weasis-pacs-connector.war and copied it in /server/default/deploy.

Now, in /server/default/log/server.log I see the following:

2018-07-31 11:42:01,768 ERROR -> (ScannerThread) [STDERR] SLF4J: Class path contains multiple SLF4J bindings.
2018-07-31 11:42:01,769 ERROR -> (ScannerThread) [STDERR] SLF4J: Found binding in [jar:file:/C:/dcm4chee-2.18.3-mysql/server/default/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2018-07-31 11:42:01,769 ERROR -> (ScannerThread) [STDERR] SLF4J: Found binding in [jar:file:/C:/dcm4chee-2.18.3-mysql/server/default/tmp/deploy/tmp3134848704745935498weasis-pacs-connector-exp.war/WEB-INF/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2018-07-31 11:42:01,769 ERROR -> (ScannerThread) [STDERR] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-07-31 11:42:01,773 ERROR -> (ScannerThread) [STDERR] SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Can this be a problem with the package itself or did I miss to configure something? I assume I shouldn't touch

/server/default/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class

so should I somehow get rid of 

/server/default/tmp/deploy/tmp3134848704745935498weasis-pacs-connector-exp.war/WEB-INF/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class

?

[Tamás Sipos]

I extracted the war, removed the slf4j* and log4j* files from its \WEB-INF\lib folder, compressed it again (I guess it's not the right way to eliminate the logger framework as there are also maven files and others that might be relevant) and now I have these two exceptions in the server.log:

java.io.FileNotFoundException: C:\dcm4chee-2.18.3-mysql\server\default\tmp\deploy\tmp7288139504563035987weasis-pacs-connector-exp.war\WEB-INF\classes\weasis.jnlp

java.io.FileNotFoundException: C:\dcm4chee-2.18.3-mysql\server\default\tmp\deploy\tmp7288139504563035987weasis-pacs-connector-exp.war\WEB-INF\classes\weasisApplet.jnlp

Can I get maybe a war file without the logger?

[Nicolas Roduit]

These errors are not relevant. However, you can build weasis-pacs-connector without logger, see https://github.com/nroduit/weasis-pacs-connector#build-weasis-pacs-connector

If you use dcm4chee-2.x, you need to build from the 6.x branch.

Considering the errors below, I guess you have not rezipped correctly the war file.

[Tamás Sipos]

Thanks Nicolas, you were right, I corrupted the war. Btw since then I found this answer of yours so I just dismiss this error then.

Do you know what confused me?

On the pacs-connector's GitHub page the Installation section is incomplete. It only says to download some files and that's it. I didn't read the other installation guide which is very well-written, so I tried to figure it out myself what to do, where to copy the files etc, and I only made it that far, to deploy the package and after it didn't work I thought it's because this error thrown during deployment, and not because I haven't done a bunch of other necessary steps yet:)

I still have one problem left but for that I'll open another topic...