[ https://issues.apache.org/jira/browse/TUSCANY-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Kurz resolved TUSCANY-3819. --------------------------------- Resolution: Fixed > Multiple problems with multiple outputs (Holder support) > -------------------------------------------------------- > > Key: TUSCANY-3819 > URL: https://issues.apache.org/jira/browse/TUSCANY-3819 > Project: Tuscany > Issue Type: Bug > Components: SCA Java Runtime > Affects Versions: Java-SCA-2.0-M5 > Reporter: Scott Kurz > Assignee: Scott Kurz > Attachments: 3819.1.patch, holder-ws-service-multiple-outputs.zip > > > It seems like there are a few related problems when a Java method has > multiple outputs, as my test will show. > I think the history here is: > - We first added support for using a single Holder parm (with INOUT or OUT) > but only in the case in which there was only one output altogether, (i.e. the > return type was void). > - Brent recently added some support for truly using multiple outputs. > I'm not sure what if any tests we have though using multiple outputs. For > example, the test in > samples/learning-more/binding-ws/holder-ws-service only has a single output. > However, I do have a guess at how this might have worked at some point (maybe > for Brent). > I think if we have a binding/wire configuration which uses > MediatorImpl.copyInput, etc, it might work with the existing code. However, > I think when we use the DataTransformationInterceptor which in a typical > Java<->XML transform uses the Input2InputTransformer, etc., it exposes holes > in the wrapping that need to be more fully implemented. > I'll attach a test. > In the meantime I've assigned to myself as I have started working on a few > areas including the Input2Input, Output2Output transformers, the JAXWS > interface processor. Also the wsdlgen will need some tweaking I think. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.