Originally posted by Roland Maurer:
GWT, and now I should provide a WS interface for the same stuff
Originally posted by Peer Reynders:
[QB]
Have you considered that SOAP web services are not necessarily an optimal fit to support your particular requirements?
Yes ! But
I really like to get away from http session.
And the implementation we do is something like an "easy access layer" for a lot of different frontends ( we use GWT, others use JSF or maybe swing,.. ) to a really complex and big "standard community" ( http://www.ihe.net/ ) .
Behind the WS there are a lot of different network access methods used, like DCM or Hl7 uses TCP / IP directly, XDS uses OASIS ebXML over SOAP , ..... but nearly all of them provide at least some WS interfaces.
It seems that the whole community is going more and more to the direction of SOAP WS !
We also must provide our "easy access layer" to external companies.
So after considering a lot of things I hope that SOAP WS will match my requirements the best way.
I will put the services to one endpoint for now that the others can continue their testing , afterwards we will have time to fix the httpSession dependency problem !
thanks a lot
roland
Originally posted by Roland Maurer:
I will put the services to one endpoint for now that the others can continue their testing , afterwards we will have time to fix the httpSession dependency problem !
Originally posted by Roland Maurer:
It seems that the whole community is going more and more to the direction of SOAP WS !
We also must provide our "easy access layer" to external companies.