[jira] Created: (TUSCANY-1515) The JavaBeansDataBinding does not provide an exception handler

Components: Java SCA Data Binding Runtime Affects Versions: Java-SCA-0.90, Java-SCA-0.91, Java-SCA-Next Environment: svn revision 563847 Reporter: Matthew Sykes Priority: Minor Fix For: Java-SCA-Next The DefaultDataBindingExtensionPoint does

[jira] Updated: (TUSCANY-1515) The JavaBeansDataBinding does not provide an exception handler

[ https://issues.apache.org/jira/browse/TUSCANY-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Sykes updated TUSCANY-1515: --- Attachment: javabeans-exception-handler.diff Patch to allow the JavaBeansDataBinding

[jira] Updated: (TUSCANY-1452) InterfaceContract and its associated objects should be Cloneable

[ https://issues.apache.org/jira/browse/TUSCANY-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Sykes updated TUSCANY-1452: --- Attachment: (was: clone.diff) InterfaceContract and its associated objects should

[jira] Updated: (TUSCANY-1452) InterfaceContract and its associated objects should be Cloneable

[ https://issues.apache.org/jira/browse/TUSCANY-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Sykes updated TUSCANY-1452: --- Attachment: clone-2.diff Patch to make InterfaceContract, Interface, and Operation

[jira] Created: (TUSCANY-1452) InterfaceContract and its associated objects should be Cloneable

: Improvement Components: Java SCA Assembly Model, Java SCA Core Runtime Affects Versions: Java-SCA-0.90, Java-SCA-0.91, Java-SCA-Next Reporter: Matthew Sykes Given the current infrastructure in 0.90, it is difficult for a binding provider to setup a binding-specific databinding

[jira] Updated: (TUSCANY-1452) InterfaceContract and its associated objects should be Cloneable

[ https://issues.apache.org/jira/browse/TUSCANY-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Sykes updated TUSCANY-1452: --- Attachment: clone.diff Patch to make InterfaceContract, Interface, and Operation Cloneable

Re: Supporting callbacks across Web Services

: [EMAIL PROTECTED] -- Matthew Sykes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (TUSCANY-1344) Tuscany does not provide a loader for the binding.sca / elements in scdl

[ https://issues.apache.org/jira/browse/TUSCANY-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505380 ] Matthew Sykes commented on TUSCANY-1344: When the artifact processor is created, createSCABindings

[jira] Created: (TUSCANY-1344) Tuscany does not provide a loader for the binding.sca / elements in scdl

Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.90, Java-SCA-0.91 Environment: sca-java-0.90 Reporter: Matthew Sykes Priority: Trivial There doesn't appear to be a StAXArtifactProcessor capable of reading

[jira] Created: (TUSCANY-1345) Many StAXArtifactProcessor implementations read policy but do not write it

Issue Type: Bug Affects Versions: Java-SCA-0.90, Java-SCA-0.91 Environment: sca-java-0.90 Reporter: Matthew Sykes Priority: Minor While the 0.90 release was closing down, several changes were made to the StAXArtifactProcessor implementations used

[jira] Created: (TUSCANY-1346) Resolution to TUSCANY-1332 assumes a closed top-level composite that does not support addition of new components

://issues.apache.org/jira/browse/TUSCANY-1346 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model, Java SCA Core Runtime, Java SCA Embedded Runtime Affects Versions: Java-SCA-0.90, Java-SCA-0.91 Reporter: Matthew Sykes The resolution

[jira] Created: (TUSCANY-1331) createSelfReferences resultes in SCA binding references with $self$ style URIs

Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.90 Environment: sca-java-0.90, IBM JDK5 Reporter: Matthew Sykes Fix For: Java-SCA-Next, Java-SCA-0.90 During a discussion on the behavior of the implementation

Re: CompositeBuilderImpl.createSelfReferences creates a $self$ reference using the service binding

binding (not even SCA binding). And the component will be exposed as a json-rpc service. So invoking the json-rpc reference handler is the correct behavior from the client side. Thanks, Raymond -- Matthew Sykes - To unsubscribe

Re: CompositeBuilderImpl.createSelfReferences creates a $self$ reference using the service binding

have to. ;) Thanks. Jean-Sebastien Delfino wrote: Matthew Sykes wrote: I'm actually bumping up against one of the problems that ant has described - the creation of $self$ reference URIs. I don't believe a binding implementation should have to expect to deal with odd URI's that were generated

Re: Brief guide for extending Tuscany

PROTECTED] -- Matthew Sykes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r531727 - Bring up of helloworld-ws and helloworld-wsclient WS binding samples

] -- Matthew Sykes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Tuscany Java sca package names

PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Matthew Sykes - To unsubscribe, e-mail

Re: Monitoring, logging, and exceptions (was: Re: Notifcation of missing extensions)

installed the agent because a problem is expected. If aspect weaving is used, I believe it should be an optional part of the build environment and not force fit into the instrumentation agent infrastructure. Thanks. -- Matthew Sykes

Re: svn commit 496794

as it currently stands. If so, is the spec going to change to require the use of @OneWay for this purpose? At the moment, both the simplecallback and the inner.composite samples do not work properly. -- Matthew Sykes - To unsubscribe, e

Re: Callback methods w/ non-void return types

. In this use case, the client wants a sync response. I think the use case is going to be common, that's why it's in the spec. Dave -- Matthew Sykes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

[jira] Created: (TUSCANY-1052) Bi-directional intefaces are assumed to be non-blocking but are not required to be

: Tuscany Issue Type: Bug Components: Java SCA Core Affects Versions: Java-M2, Java-M3 Environment: Tuscany revision 495535 Reporter: Matthew Sykes Fix For: Java-M3 Tuscany assumes that the forward operation of a bi-directional interface

[jira] Updated: (TUSCANY-1052) Bi-directional intefaces are assumed to be non-blocking but are not required to be

[ https://issues.apache.org/jira/browse/TUSCANY-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Sykes updated TUSCANY-1052: --- Description: Tuscany assumes that the forward operation of a bi-directional interface

Re: Callback methods w/ non-void return types

Jim, I'm interested in the answer to this as well. I think we all understand that non-blocking operations must have void return types. The question really boils down to whether or not bidirectional services are considered non-blocking. I have a simple piece of code that uses a

Re: Callback methods w/ non-void return types

is void and thus returns a message with a null body, which is probably the cause of your NPE. Agreed. My point is that I don't think the NonBlockingBridgingInterceptor should have been used in my example as the client is expecting a synchronous result from FI.cf. Thanks again. -- Matthew Sykes

Re: Move SCA tools and wsdl-java plugins to SDO tree?

of the function to the Axis2 implementation and simply added a new emitter. Does it make sense to introduce that dependency on the SDO side? -- Matthew Sykes Jeremy Boynes wrote: Looking at modularizing the tree, it seems to me that the tools and java2wsdl/wsdl2java plugins don't actually have any

[jira] Created: (TUSCANY-978) Tuscany WSDL2Java can't handle WSDL fault messages

Tools Affects Versions: Java-M2 Environment: Tuscany Java-M2 and current trunk Reporter: Matthew Sykes I've been playing with the BigBank sample and have added a fault to the AccountService's withdraw operation. After changing the AccountService.wsdl (attached

[jira] Updated: (TUSCANY-978) Tuscany WSDL2Java can't handle WSDL fault messages

[ http://issues.apache.org/jira/browse/TUSCANY-978?page=all ] Matthew Sykes updated TUSCANY-978: -- Attachment: AccountService.wsdl WSDL in a more convenient form... Tuscany WSDL2Java can't handle WSDL fault messages

Tuscany WSDL2Java

) at org.apache.tuscany.tools.wsdl2java.generate.JavaInterfaceGenerator.generate(JavaInterfaceGenerator.java:174) ... 20 more -- Matthew Sykes ?xml version=1.0 encoding=UTF-8? !-- * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional

Re: maven-assembly-plugin version?

If Jervis hit the same issue I did, the problem was that the 2.2-SNAPSHOT is now dependent on org.codehaus.plexus:plexus-archiver:1.0-alpha-7-SNAPSHOT which wasn't available in any of the configured repositories. I ended up pulling it from snapshots.repository.codehaus.org to resolve the

Re: adding an interceptor

Jim, I'd be interested in contributing to this but I'm not sure I know exactly where to begin. If you're willing to spend a bit of time on the QA necessary to describe the intended flow through the bindings, wires invocation handlers, and policy handlers (using some of Jeremy's presentation

Re: How to use extensions with the standalone launcher?

FWIW, I think I've been running into a problem at build time because of this exact issue. There's a bit of code in the javascript sample HelloWorldTestCase.java test that gathers up all of the META-INF/sca/default.scdl resources it can find. The test then throws away the first resource in

[jira] Created: (TUSCANY-574) URISyntaxException from launcher when jars reside in windows Maven repository

Issue Type: Bug Components: Java SCA Core Environment: Win XP, J2RE 1.5.0 IBM Windows 32 build pwi32dev-20060511 (SR2) Reporter: Matthew Sykes Priority: Trivial When attempting to run maven from various samples directories: [INFO] [surefire:test