Just to discus: No solution yet, but sooner than later I am in the same boat.
Why not starting with this End Point Reading = EPR End point Writing = EPW EPR = "http://yournode:8080/axis2/services/yourReadservice EPW ="https://yournode:8443/axis2/services/yourWriteService In this case you have a secure transport via HTTPS, and can issue certificates to those which need access to "yourWriteService" Or you may consider engaging Rampart and you do not secure the transport level but go for WS-Security é all .... In this case, the harder one, you are open for re-routing at the transport level later, but still allow for fine granular access control to services and methods at the axis2 level Comments welcome Josef Von: Rune Sindahl [mailto:r...@lpt.dk] Gesendet: Dienstag, 28. Juni 2011 13:17 An: c-user@axis.apache.org Betreff: Separate Axis2C services at different ports Hi. I have developed a service that has two publicly available methods. One for inserting data to a system, and another for fetching information from the system. For security reasons I would like to separate these two services at different ports, where it should be possible to only access one of the methods at each of those ports. My web service server is using Apache as http-server. I am of course able to make the web services available at two different port by setting Listen parameter to two different ports in Apache configuration file, but how do I diverse the access for each of those ports ? It is not possible to set "Axis2RepoPath" inside a <VirtualHost> neither do I believe there exist an option to set path for the Service-directory only. Have any of you had such an issue and found a solution ? Best regards Rune Sindahl
