Hi Johan
Is the conclusion that I will have to create a full configuration for
every WSDL I need to virtualize?
All my virtual services are virtualized based on a single set of rules
/ conventions and registry metadata, so I'm looking for a way to
create ONE gateway (synapse deployment) that will not need to change
until the rules / conventions changes. Virtualization of a new WSDL
should be a registry activity only ("systematic virtualization").
If a mediator fetches the wsdl, is there still "time" for applying
security policies to the incomming message or is there a
"bootstrapping" problem?
I think its possible to write an advanced mediator to apply the security
for the requested service looking up from the registry. However it will
not be easy as this is not a typical use case we try to address, and the
mediator would need to fetch new WSDLs/Policies, apply security during
mediation etc.. Additionally, to serve the ?wsdl request by the clients,
we could use some smart redirection to the real registry
cheers
asankha
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
