Re: Jenkins build is back to normal : Tuscany-2x #334

Woohoo. First time in a while. ...ant On Thu, Aug 25, 2011 at 2:04 AM, Apache Jenkins Server wrote: > See > > >

Re: Jenkins build is back to normal : Tuscany-2x #334

On Thu, Aug 25, 2011 at 8:21 AM, ant elder wrote: > Woohoo. First time in a while. > >   ...ant > > On Thu, Aug 25, 2011 at 2:04 AM, Apache Jenkins Server > wrote: >> See >> >> >> > Nice. Looks like the move to 1.427 fixed it. Simon -- Ap

Re: async service implementation and runtime exceptions

Hi Greg Good questions. Had some discussion with Mike about this off-line. I'm sure he'll pitch in. My 2c. On Wed, Aug 24, 2011 at 10:02 PM, Greg Dritschler wrote: > I have a couple of questions about how to handle runtime exceptions from an > asynchronous service implementation. > 1)  Can the s

[jira] [Created] (TUSCANY-3932) Callbacks don't work in the distributed domain

Callbacks don't work in the distributed domain -- Key: TUSCANY-3932 URL: https://issues.apache.org/jira/browse/TUSCANY-3932 Project: Tuscany Issue Type: Bug Components: SCA Java Runtime

[jira] [Assigned] (TUSCANY-3932) Callbacks don't work in the distributed domain

[ https://issues.apache.org/jira/browse/TUSCANY-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-3932: --- Assignee: Simon Laws > Callbacks don't work in the distributed domain > ---

[jira] [Created] (TUSCANY-3933) A reference to a service thats not yet active in the domain when the reference is created fails on invoke

A reference to a service thats not yet active in the domain when the reference is created fails on invoke - Key: TUSCANY-3933 URL: https://issues.apache.org/ji

What should the Tuscany generated WSDL contract look like for an async service?

Looking to fix TUSCANY-3931 about the clients not working with the wsdl in the domain registry for async services and i wonder what the wsdl should really look like. For example with the service interface: @AsyncInvocation public interface Service1AsyncServer { @AsyncFault( {BusinessFault1

Callback endpoints in the distributed domain

I've come across an interested collection of interconnected issues while looking at callbacks in the distributed domain (TUSCANY-3932). While we've done plenty of testing of this feature in the single node domain it's not had much exercise in the distributed domain. This is a little involved so bea

Re: Callback endpoints in the distributed domain

On Thu, Aug 25, 2011 at 3:50 PM, Simon Laws wrote: > I've come across an interested collection of interconnected issues > while looking at callbacks in the distributed domain (TUSCANY-3932). > While we've done plenty of testing of this feature in the single node > domain it's not had much exercise

Re: Callback endpoints in the distributed domain

>> > > A lot of the these other issues follow on from this issue so I'd like I think we need to solve the other issues regardless of issues1 as it's possible to use interoperable bindings in both the forward and callback wires. > to understand if this is really the case, so could you explain what

Re: What should the Tuscany generated WSDL contract look like for an async service?

On Thu, Aug 25, 2011 at 2:49 PM, ant elder wrote: > Looking to fix TUSCANY-3931 about the clients not working with the > wsdl in the domain registry for async services and i wonder what the > wsdl should really look like. For example with the service interface: > > @AsyncInvocation > public interf

Re: What should the Tuscany generated WSDL contract look like for an async service?

I agree that the DomainRegistry should have the equivalent synchronous version. While we're on this subject, I happened to be wondering today whether @AsyncInvocation obligates the service implementation to use the async service interface? Obviously it makes the most sense to use them together, b

[jira] [Updated] (TUSCANY-3925) AccessControl Exception originating from DefaultFactoryExtensionPoint.getFactory, JDKProxyFactory.createCallbackProxy, WSDLHelper.createWSDLInterfaceContract

[ https://issues.apache.org/jira/browse/TUSCANY-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jennifer A Thompson updated TUSCANY-3925: - Description: When running with Java 2 security enabled the following AccessCont