Oh I see what you are saying. You mean there may be a configuration to make is so XCF will be compatible with the existing clients? That would be wonderful.
The XCF wsdl looks like this <wsdl:operation name="connectionCheck"> <wsdl:input message="tns:connectionCheck" name="connectionCheck"></wsdl:input> <wsdl:output message="tns:connectionCheckResponse" name="connectionCheckResponse"></wsdl:output> </wsdl:operation> The Metro looks like this <operation name="connectionCheck"> <input wsam:Action="http://server.synchronizer.compass.ciminc.com/SynchronizerService/connectionCheckRequest"; message="tns:connectionCheck"/> <output wsam:Action="http://server.synchronizer.compass.ciminc.com/SynchronizerService/connectionCheckResponse"; message="tns:connectionCheckResponse"/> </operation> When a client tries to perform the connectionCheck operation there is an error that says. The given SOAPAction http://server.synchronizer.compass.ciminc.com/SynchronizerService/connectionCheckRequest does not match an operation. Is this something that can be fixed with configuration? -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/Glassfish-to-TomEE-Webservices-tp4672146p4672163.html Sent from the TomEE Users mailing list archive at Nabble.com.
