For the time being this is not possible, and we need an improvement to
axis2 to differentiate the protocol name and the transport definition
name in the axis2.xml, then we need the default transports parameter
introduction to axis2.
With those 2 features we can do the following, basically we specify the
admin services to be deployed only on admin-https, and remove
admin-https from default transports.
Thanks,
Ruwan
On 12/1/10 8:34 AM, Prabath Siriwardana wrote:
IIRC this was discussed before..
ESB does this - but still both types published on both ports...
Having the $subject is useful to restrict external access to admin
services via a firewall.. WDYT?
--
Thanks & Regards,
Prabath
P.S: In the process of writing a best practices guide to putting WSO2
ESB in a DMZ
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Ruwan Linton
Software Architect& Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware
phone: +1 408 754 7388 ext 51789
email: [email protected]; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton
_______________________________________________
Carbon-dev mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
