Thank you for your feedback.
Quote:
Originally Posted by joshmoore
Our initial implementation of the OMERO server was a Spring context within a JBoss server. We currently support both a JBoss and an Ice-based server, which was relatively straight-forward using Ice's tie classes and the Spring interceptors which were already in place within JBoss.
If you have JBoss with Spring, I can explain how to go about this.
|
Actually, I am in the position of recommending how to structure the application server. So far, I am kind of fixed on Spring, but as I may have to expose some services as web services, something beside ICE may have to be used as server. It could be JBOSS (or similar) or it could be a SOAP/web service wrapper for the ICE-based application.
Quote:
|
If not, keep things simple. Using Ice and Spring together is really no issue at all. The only way to get Ice and JBoss to work together short of significant work on the JBoss remoting library is to have the Ice thread pool active "symbiotically" within JBoss. This works and we've done it, but it's not really sensible.
|
Violates the KISS principle...
Just curious, If you have an ICE-based OMERO server, why do you also offer a JBOSS based version?
Karl