Transformation code should allow for type conversion as a backup if an explicit transformation by type name is not defined -------------------------------------------------------------------------------------------------------------------------- Key: SWITCHYARD-303 URL: https://issues.jboss.org/browse/SWITCHYARD-303 Project: SwitchYard Issue Type: Bug Components: transformation Affects Versions: 0.1 Reporter: Len DiMaggio Follow on to JIRA switchyard-301: If the work-around to the WSDL issue described in switchyard-301 is used, this error is then seen when the service is invoked: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <SOAP-ENV:Fault> <faultcode>SOAP-ENV:Server</faultcode> <faultstring>Transformations not applied. Required payload type of 'java:java.lang.String'. Actual payload type is '{http://webservices.samples.jboss.org/}sayHello'. You must define and register a Transformer to transform between these types.</faultstring> </SOAP-ENV:Fault> </SOAP-ENV:Body> </SOAP-ENV:Envelope> Note from Keith: No transformer has been defined, but I think we need to make it easy to accept XML input as a String in your POJO without defining a transformer. Our transformation code needs to be tweaked to allow for type conversion as a backup if an explicit transformation by type name is not defined. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira