[ https://jira.jboss.org/jira/browse/JBESB-1936?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBESB-1936: ------------------------------------- What did you have in mind here Kev? Are you just talking about exposing the wsdl for the remote WS, or are you talking about creating an actual proxy (on the ESB) to the remote WS endpoint? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1936?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-1936: ------------------------------------- At the moment we have two publishers, the WebserviceContractPublisher (an action publisher which I am in the middle of changing) and ESBServiceContractPublisher. The WebserviceContractPublisher only works for co-located webservices and is paired with SOAPProcessor. The purpose of this task is to create a contract publisher which enables the publishing of those remote WSDLs which we are proxying, in a similar manner to WebserviceContractPublisher. I'll take this for now, at least until I have tidied up the schema dependencies spread through out the current codebase. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1936?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBESB-1936: ------------------------------------- After talking to Kev... what we're going to implement for this (for now anyway) is simply exposing the WSDL's of the SOAPClient actions. It will be up to the pipeline to to transform the incoming SOAP into the appropriate Java Object Graph before passing it to the SOAPClient action. Of source, the pipeline isn't going to receive the SOAP request until after JBESB-2334 is done. Without JBESB-2334, the SOAP client will see the actual WS endpoint. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1936?page=com.atlassian.jira.plu... ] Tom Fennelly closed JBESB-1936. ------------------------------- Resolution: Done trunk: 25124 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-1936?page=com.atlassian.jira.plu... ] Tom Fennelly reassigned JBESB-1936: ----------------------------------- Assignee: Tom Fennelly (was: Daniel Bevenius) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira