Announcement Announcement Module
Collapse
No announcement yet.
Is there a way to physically separate Spring-ws layer from actual services? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Is there a way to physically separate Spring-ws layer from actual services?

    For security reasons, I'm trying to find out if Spring-ws can be tweaked to have the core spring-ws layer on one node (i.e. receiving requests, dealing with certificates, signatures, and deserializing the XML), and then the actual application layer services on another node.

    As I'm asking a possibility comes to mind, maybe define dummy services in the spring-ws node that would just pass on the request via some other transport to the application layer (maybe http invoker?).

    But has anyone done something like this? What approach did you take? Anything built into spring-ws to facilitate this type of setup? The idea here is that the spring-ws layer would be deployed in a DMZ, so that any requests that aren't good don't make it very far. Only requests that have been validated and passed security would go on to the actual application layer in a MZ.

  • #2
    You can simply expose your service layer with http invoker, rmi or any other remoting protocol and invoke it from your spring-ws endpoits (nothing specific to spring-ws here) but beware of the impact on performance because you're adding a new layer and a new network round-trip for every invocation.

    Comment

    Working...
    X