[
https://wso2.org/jira/browse/ESBJAVA-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asankha Perera updated ESBJAVA-400:
-----------------------------------
Fix Version/s: FUTURE
(was: 1.7)
I don't think this could be a mediator.. but an enhancement to the endpoint to
do a check? Still would require more time to investigate and understand..as
this an enhancement and not high priority, I am deferring this
> Ws-i Mediator hepls to identify the Ws-i compatibility of ws calls when they
> go through the system.
> ---------------------------------------------------------------------------------------------------
>
> Key: ESBJAVA-400
> URL: https://wso2.org/jira/browse/ESBJAVA-400
> Project: WSO2 ESB
> Issue Type: New Feature
> Environment: all runtime environments for esb
> Reporter: Christian Brennsteiner
> Assignee: Asankha Perera
> Fix For: FUTURE
>
>
> when webservice enpoints from e.g. a third party are changed by the base
> components (for example application server change) and your company has
> agreed on ws-1 basic profile 1.0 you should be able to verify if the ws is
> basic profile 1.0 and log, alarm, drop etc. if it is not.
> i dont know if this is feasible but i would really be happy if it was.
> regards chris
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
