Hi Michael
I agree that the response shoud be consistent with the original request. I
will raise a Jira issue for this.
thanks, will make it a priority to go into the next release for sure
1. using an xpath expression to test for an error condition in the POX
response to cause a SOAP fault to be generated
I think we already have support to do this, using the filter mediator,
and the makefault mediator. If these are not adequate, can you give me
an example to illustrate your requirement?
2. ability to generate SOAP header elements in the response based on HTTP
response headers or via xpath extraction from the POX response
You should be able to use the header mediator. HTTP transport header
reading is a pending issue in our JIRA that we are hoping to address
with the next release. Again, this is a high priority issue we want to
fix with the NIO transport
3. ability to use SOAP header elements or xpath extractions from the SOAP
body to set HTTP request headers in the call to the POX service.
I agree on this, and we currently do not have support for this. Could
you raise a JIRA for this as well?
And to your email regarding improving Synapse and current plans for
utilization.
transport security in the form of HTTPS (I believe the next release's NIO
based http listener will support)
yes
authorization / authentication using credentials passed as part of the SOAP
header (i've written a simple ClassMediator that does this for now as I
don't think my integration partners are ready for WS-Security)
Sounds cool
audit logging of message traffic to a database
This was something we wanted to implement at a later release - i.e. a
mediator that can report to a DBMS, SNMP etc..
So if you would like to contribute some of this code to Synapse, it
would be welcome.
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
