| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
UnknownEndpointHandler thats called when an endpoint isn't found in the registry. Don't know if this is the best approach yet but it gives something to try with itests too see how it works
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1043464 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
the "process" methods I added as a convenience for sharing invoker implementation. Asl get rid of "throws" from Invocable
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1043447 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
non-native async at the service end. Not actually used yet.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1043436 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
async response handler so that the invokerAsyncResponse can have a void return type.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1042976 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1042609 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
binding doesn't support asycn interactions natively
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1041872 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
enpoints/endpointreferences that call it, to allow async response messages to be processed backwards along the response part of the chain independently of the forward message processing.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1041866 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
backwards. Also add an implementation that can hold generic interceptor implementation that to date, for the forward chain, has been repeated in each interceptor.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1041858 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
resolved then so that async response services can be established at that point. In a reliable situation the response service is then available as soon as reference is resolved and doesn't depend on the reference actually being used. Also start adding interfaces to allow the implementation provider to make an async invocation explicitly.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1040444 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
available services
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1036030 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1035090 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1034818 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1032864 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1032555 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1031483 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1001665 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
registry is actually chosen based on the domain scheme but I've been running with this without adverse effects but can we remove all the registry rankings now?
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1000978 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
RuntimeEndpontImpl
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1000975 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
distro is causing OSGi wiring conflicts
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@1000968 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@998309 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
methods and multiple Holders
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@998232 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@996960 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@995627 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@993614 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
what I think is the right thing but it doesn't necessarily do it in an optimal way yet.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@989157 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
as the latest code which just looks for matching operation names breaks the support for dynamic interfaces.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@988368 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@987094 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
an invalid property name
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@986947 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
(JAXWSJavaIntefaceProcessor) and, in the JavaIntefaceProcessor, post process these to reconfigure the Java interface based on what is found. The case where WSDL is referenced is tricky and still has holes. The WSDL is read and is attached to the Java interface as a normalized interface and is used during interface matching. Binding implementations that care about WSDL should really check the normalized interface rather than the service interface itself. This is still a TODO.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@986740 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
JCA 9006, 9008, 9009 9010, and 9012
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@982710 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
businessInterface that is not valid for any service in the component (JCA-9011)
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@982693 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
JCA_9008_TestCase to receive the required IllegalArgumentException when the contracts are incompatible. In some cases we can't reliably introspect in a platform neutral way to discover the implementation's interface contract, so in this case we fluff up an interface contract on the basis of the business interface, just as we have done more generally in the past.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@981859 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
the binding wire is created
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@980474 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
due to previous error message output changes
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@979633 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@979150 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@966983 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@966527 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@964980 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@964852 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
the @Callback WSDL annotations is processed. Makes BWS_2022 work.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@963756 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
and reference binding and at service and service binding match. Motivated by BWS_2007. TO do this properly we have to test that the interfaces are described using the same IDL and if not convert to WSDL1.1 are required by the SCA specifications. There are a lot of changes here as doing this upset quite a few tests. Further work is required to look at the details of our WSDL generation process which looks a little suspect around wrapper namespaces.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@963624 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
asynchronous services and @asyncInvocation as described in TUSCANY-3608, 3611 & 3612
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@963034 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
Phase II of TUSCANY-3612
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@960545 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
TUSCANY-3612
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@960540 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@960521 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
| |
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@960157 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
fully support the JAXWS async client API pattern as described in TUSCANY-3612
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@959131 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
incoming Web service invocation of a bidirectional service, transmit this data to the callback invocation from the service and embed into a wsa:RelatesTo SOAP header in the callback Wen service message, as required by the OASIS Web Service Binding spec, described in TUSCANY-3592
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@956127 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
called from a new thread.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@955860 13f79535-47bb-0310-9956-ffa450edef68
|
|
|
|
|
|
| |
regenerated. Also rename the methods for getting/setting the generated data to make it more obvious that that's what it's doing.
git-svn-id: http://svn.us.apache.org/repos/asf/tuscany@955601 13f79535-47bb-0310-9956-ffa450edef68
|