[jira] Commented: (TUSCANY-2388) Data binding does not work when Java interface & implementation (where method param is not String, primitive) exposed with a web services binding

[ https://issues.apache.org/jira/browse/TUSCANY-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604421#action_12604421 ] Scott Kurz commented on TUSCANY-2388: - This looks like it should work, since though y

[jira] Commented: (TUSCANY-2109) Conflicts between component reference interface and promoted composite reference interface are not detected

[ https://issues.apache.org/jira/browse/TUSCANY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603900#action_12603900 ] Scott Kurz commented on TUSCANY-2109: - Based on where our discussion ended up here: h

[jira] Updated: (TUSCANY-2377) problem reading complex property from @file

[ https://issues.apache.org/jira/browse/TUSCANY-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2377: Attachment: 2377.itest.example.diff Same file.. I meant to say it could be included in ASF > pro

[jira] Updated: (TUSCANY-2377) problem reading complex property from @file

[ https://issues.apache.org/jira/browse/TUSCANY-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2377: Attachment: 2377.itest.example.diff I didn't see an example for using XJC, so I just hand-gen'd t

[jira] Created: (TUSCANY-2377) problem reading complex property from @file

problem reading complex property from @file --- Key: TUSCANY-2377 URL: https://issues.apache.org/jira/browse/TUSCANY-2377 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime

[jira] Updated: (TUSCANY-2332) reconsider non-support for Holders

[ https://issues.apache.org/jira/browse/TUSCANY-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2332: Attachment: guessAndGreet.wsdl > reconsider non-support for Holders > ---

[jira] Created: (TUSCANY-2332) reconsider non-support for Holders

reconsider non-support for Holders -- Key: TUSCANY-2332 URL: https://issues.apache.org/jira/browse/TUSCANY-2332 Project: Tuscany Issue Type: Improvement Components: Java SCA Data Binding Runtime

[jira] Created: (TUSCANY-2324) InterfaceContract is not pushed down to an inner, promoted component reference only with Axis2 binding

InterfaceContract is not pushed down to an inner, promoted component reference only with Axis2 binding --- Key: TUSCANY-2324 URL: https://issues.apache.org/jira/b

[jira] Commented: (TUSCANY-2316) Axis2 Binding Provider does not handle services & references with WSDL interfaces correctly

[ https://issues.apache.org/jira/browse/TUSCANY-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596503#action_12596503 ] Scott Kurz commented on TUSCANY-2316: - The binding-ws-axis2 is overwriting the databi

[jira] Commented: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?

[ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589777#action_12589777 ] Scott Kurz commented on TUSCANY-2113: - I'm sorry I don't have a test case handy. If

[jira] Updated: (TUSCANY-2217) Some null guards needed in MediatorImpl

[ https://issues.apache.org/jira/browse/TUSCANY-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2217: Attachment: 2217.patch > Some null guards needed in MediatorImpl > --

[jira] Created: (TUSCANY-2217) Some null guards needed in MediatorImpl

Some null guards needed in MediatorImpl --- Key: TUSCANY-2217 URL: https://issues.apache.org/jira/browse/TUSCANY-2217 Project: Tuscany Issue Type: Bug Components: Java SCA Data Binding Runtime

[jira] Commented: (TUSCANY-2193) NPE when configuring WSDL interface on component ref when the component has a Composite impl

[ https://issues.apache.org/jira/browse/TUSCANY-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585135#action_12585135 ] Scott Kurz commented on TUSCANY-2193: - I found the problem. In CompositeConfigur

[jira] Created: (TUSCANY-2193) NPE when configuring WSDL interface on component ref when the component has a Composite impl

NPE when configuring WSDL interface on component ref when the component has a Composite impl Key: TUSCANY-2193 URL: https://issues.apache.org/jira/browse/TUSCANY-2193

[jira] Created: (TUSCANY-2189) Problems building the wire for a service implemented by Composite

Problems building the wire for a service implemented by Composite - Key: TUSCANY-2189 URL: https://issues.apache.org/jira/browse/TUSCANY-2189 Project: Tuscany Issue Type: Bug

[jira] Updated: (TUSCANY-2189) Problems building the wire for a service implemented by Composite

[ https://issues.apache.org/jira/browse/TUSCANY-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2189: Attachment: test.2189.jar Sorry this doesn't exactly match the SCDL pasted it the JIRA text but i

[jira] Issue Comment Edited: (TUSCANY-2084) Problems deserializing XML->SDO after using XMLType element calculated from Java to serialize SDO->XML onto

[ https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582302#action_12582302 ] scottkurz edited comment on TUSCANY-2084 at 3/26/08 7:51 AM: --

[jira] Commented: (TUSCANY-2084) Problems deserializing XML->SDO after using XMLType element calculated from Java to serialize SDO->XML onto

[ https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582302#action_12582302 ] Scott Kurz commented on TUSCANY-2084: - There's a similar issue for dynamic SDO. Inst

[jira] Updated: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?

[ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2113: Description: There's a problem with how the fault matching in DTI uses the private DTI.typesMatc

[jira] Updated: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?

[ https://issues.apache.org/jira/browse/TUSCANY-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2113: Description: There's a problem with how the fault matching in DTI uses the private DTI.typesMatc

[jira] Created: (TUSCANY-2113) Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames?

Problem with fault comparison in DataTransformationInterceptor; maybe we should compare elem QNames, not type QNames? - Key: TUSCANY-2113 URL: http

[jira] Commented: (TUSCANY-2033) java interface exposed as service, annoted with javax.xml.ws.RequestWrapper(...) is ignoring the namespace

[ https://issues.apache.org/jira/browse/TUSCANY-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579836#action_12579836 ] Scott Kurz commented on TUSCANY-2033: - I'm surprised we'd view Clemens' original exam

[jira] Created: (TUSCANY-2094) Would like to keep track of element name during fault/exception mapping at introspect time and invocation time so I can use FaultException matching helpfully

Would like to keep track of element name during fault/exception mapping at introspect time and invocation time so I can use FaultException matching helpfully ---

[jira] Updated: (TUSCANY-2094) Would like to keep track of element name during fault/exception mapping at introspect time and invocation time so I can use FaultException matching helpfully

[ https://issues.apache.org/jira/browse/TUSCANY-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2094: Attachment: JAXWSFaultExcMapper.patch > Would like to keep track of element name during fault/exc

[jira] Updated: (TUSCANY-2085) ConcurentModExc in DefaultDataBindingExtensionPoint

[ https://issues.apache.org/jira/browse/TUSCANY-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2085: Attachment: 2085.patch > ConcurentModExc in DefaultDataBindingExtensionPoint > -

[jira] Created: (TUSCANY-2085) ConcurentModExc in DefaultDataBindingExtensionPoint

ConcurentModExc in DefaultDataBindingExtensionPoint Key: TUSCANY-2085 URL: https://issues.apache.org/jira/browse/TUSCANY-2085 Project: Tuscany Issue Type: Bug Components: Java S

[jira] Created: (TUSCANY-2084) Problems deserializing XML->SDO after using XMLType element calculated from Java to serialize SDO->XML onto

Problems deserializing XML->SDO after using XMLType element calculated from Java to serialize SDO->XML onto Key: TUSCANY-2084 URL: https://issues.apache.

[jira] Updated: (TUSCANY-2084) Problems deserializing XML->SDO after using XMLType element calculated from Java to serialize SDO->XML onto

[ https://issues.apache.org/jira/browse/TUSCANY-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-2084: Component/s: Java SDO Implementation Java SCA Data Binding Runtime

[jira] Commented: (TUSCANY-1679) PBVInvoker always uses service-side classloader to deserialize ... also doesn't handle checked/business excs

[ https://issues.apache.org/jira/browse/TUSCANY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570742#action_12570742 ] Scott Kurz commented on TUSCANY-1679: - The implications of some other discussions we'

[jira] Updated: (TUSCANY-1679) PBVInvoker doesn't handle checked/business excs

[ https://issues.apache.org/jira/browse/TUSCANY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1679: Summary: PBVInvoker doesn't handle checked/business excs (was: PBVInvoker always uses service-si

[jira] Commented: (TUSCANY-2042) Dynamically generated WSDL not generating output message for void types

[ https://issues.apache.org/jira/browse/TUSCANY-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567848#action_12567848 ] Scott Kurz commented on TUSCANY-2042: - It is looking more like an Axis2 versioning is

[jira] Issue Comment Edited: (TUSCANY-2042) Dynamically generated WSDL not generating output message for void types

[ https://issues.apache.org/jira/browse/TUSCANY-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567709#action_12567709 ] scottkurz edited comment on TUSCANY-2042 at 2/11/08 9:16 AM: --

[jira] Commented: (TUSCANY-2042) Dynamically generated WSDL not generating output message for void types

[ https://issues.apache.org/jira/browse/TUSCANY-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567709#action_12567709 ] Scott Kurz commented on TUSCANY-2042: - I recreated this at the same time as stepping

[jira] Created: (TUSCANY-2010) Default binding URI for service from Composite impl component is incorrect

Default binding URI for service from Composite impl component is incorrect -- Key: TUSCANY-2010 URL: https://issues.apache.org/jira/browse/TUSCANY-2010 Project: Tuscany

[jira] Commented: (TUSCANY-1938) doc-lit-wrapped WSDLs with wrapper elems with non-substitution-group refs are incorrectly treated as non-wrapped

[ https://issues.apache.org/jira/browse/TUSCANY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559236#action_12559236 ] Scott Kurz commented on TUSCANY-1938: - It works now (operation is treated as 'wrapped

[jira] Updated: (TUSCANY-1938) doc-lit-wrapped WSDLs with wrapper elems with non-substitution-group refs are incorrectly treated as non-wrapped

[ https://issues.apache.org/jira/browse/TUSCANY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1938: Attachment: helloworld.wsdl > doc-lit-wrapped WSDLs with wrapper elems with non-substitution-grou

[jira] Created: (TUSCANY-1938) doc-lit-wrapped WSDLs with wrapper elems with non-substitution-group refs are incorrectly treated as non-wrapped

doc-lit-wrapped WSDLs with wrapper elems with non-substitution-group refs are incorrectly treated as non-wrapped Key: TUSCANY-1938 URL: https://issues

[jira] Created: (TUSCANY-1926) Problem w/ JDKInvocationHandler with dynamic reference with WSDLinterface

Problem w/ JDKInvocationHandler with dynamic reference with WSDLinterface - Key: TUSCANY-1926 URL: https://issues.apache.org/jira/browse/TUSCANY-1926 Project: Tuscany Is

[jira] Updated: (TUSCANY-1902) Input2InputTransformer doesn't handle null input going from SDO->AXIOM

[ https://issues.apache.org/jira/browse/TUSCANY-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1902: Patch Info: [Patch Available] > Input2InputTransformer doesn't handle null input going from SDO->

[jira] Updated: (TUSCANY-1902) Input2InputTransformer doesn't handle null input going from SDO->AXIOM

[ https://issues.apache.org/jira/browse/TUSCANY-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1902: Attachment: 1902.patch > Input2InputTransformer doesn't handle null input going from SDO->AXIOM >

[jira] Created: (TUSCANY-1902) Input2InputTransformer doesn't handle null input going from SDO->AXIOM

Input2InputTransformer doesn't handle null input going from SDO->AXIOM -- Key: TUSCANY-1902 URL: https://issues.apache.org/jira/browse/TUSCANY-1902 Project: Tuscany Issue Ty

[jira] Updated: (TUSCANY-1902) Input2InputTransformer doesn't handle null input going from SDO->AXIOM

[ https://issues.apache.org/jira/browse/TUSCANY-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1902: Fix Version/s: (was: Java-SCA-1.0.1) > Input2InputTransformer doesn't handle null input going

[jira] Created: (TUSCANY-1899) Java2WSDL (trivial) - do we have to assume method names start w/ a lowercase char?

Java2WSDL (trivial) - do we have to assume method names start w/ a lowercase char? -- Key: TUSCANY-1899 URL: https://issues.apache.org/jira/browse/TUSCANY-1899 Project: T

[jira] Updated: (TUSCANY-1681) DataObject2XMLStreamReader can't handle a null (or could this be an SDO bug??)

[ https://issues.apache.org/jira/browse/TUSCANY-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1681: Attachment: 1681.patch Well, let me push the issue a bit by at least submitting a patch to return

[jira] Updated: (TUSCANY-1206) DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style

[ https://issues.apache.org/jira/browse/TUSCANY-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1206: Attachment: 1206.a.patch This is a patch created against r558780. It is, for a few reasons, not

[jira] Created: (TUSCANY-1826) DataTransformationInteceptor should be spelled: DataTransformationInterceptor

DataTransformationInteceptor should be spelled: DataTransformationInterceptor --- Key: TUSCANY-1826 URL: https://issues.apache.org/jira/browse/TUSCANY-1826 Project: Tuscany

[jira] Updated: (TUSCANY-1818) XMLStreamSerializer - IllegalStateException caused by unnecessary XMLStreamWriter calls

[ https://issues.apache.org/jira/browse/TUSCANY-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1818: Attachment: 1818.patch > XMLStreamSerializer - IllegalStateException caused by unnecessary > XM

[jira] Created: (TUSCANY-1818) XMLStreamSerializer - IllegalStateException caused by unnecessary XMLStreamWriter calls

XMLStreamSerializer - IllegalStateException caused by unnecessary XMLStreamWriter calls Key: TUSCANY-1818 URL: https://issues.apache.org/jira/browse/TUSCANY-1818

[jira] Reopened: (TUSCANY-1142) Need to allow generation of wrapped Java intf from doc-lit-wrap WSDL with named complexType

[ https://issues.apache.org/jira/browse/TUSCANY-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz reopened TUSCANY-1142: - I haven't tested the very latest code but by inspection and trying a recent build, I'd say this is

[jira] Created: (TUSCANY-1682) DataBindingRuntimeWireProcessor bug in processing boundary condition of no-arg, no-returnType method

DataBindingRuntimeWireProcessor bug in processing boundary condition of no-arg, no-returnType method - Key: TUSCANY-1682 URL: https://issues.apache.org/jira/brows

[jira] Created: (TUSCANY-1681) DataObject2XMLStreamReader can't handle a null (or could this be an SDO bug??)

DataObject2XMLStreamReader can't handle a null (or could this be an SDO bug??) -- Key: TUSCANY-1681 URL: https://issues.apache.org/jira/browse/TUSCANY-1681 Project: Tuscany

[jira] Created: (TUSCANY-1680) Need a way to detect that PBR can be used when building reference-side binding

Need a way to detect that PBR can be used when building reference-side binding -- Key: TUSCANY-1680 URL: https://issues.apache.org/jira/browse/TUSCANY-1680 Project: Tuscany

[jira] Created: (TUSCANY-1679) PBVInvoker always uses service-side classloader to deserialize ... also doesn't handle checked/business excs

PBVInvoker always uses service-side classloader to deserialize ... also doesn't handle checked/business excs Key: TUSCANY-1679 URL: https://issues.apache.

[jira] Updated: (TUSCANY-1678) Would like to improve performance by not doing a PBVInvoker.copy in a couple cases where it's unnecessary

[ https://issues.apache.org/jira/browse/TUSCANY-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1678: Component/s: Java SCA Data Binding Runtime Affects Version/s: Java-SCA-1.0 > Would like

[jira] Created: (TUSCANY-1678) Would like to improve performance by not doing a PBVInvoker.copy in a couple cases where it's unnecessary

Would like to improve performance by not doing a PBVInvoker.copy in a couple cases where it's unnecessary - Key: TUSCANY-1678 URL: https://issues.apache.org/ji

[jira] Commented: (TUSCANY-544) WSDL2Java should support WSDLs with schema imports

[ https://issues.apache.org/jira/browse/TUSCANY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524150 ] Scott Kurz commented on TUSCANY-544: In my experience (admittedly not on the absolute latest version of the code

[jira] Commented: (TUSCANY-1473) Define component's service with interface.wsdl ,throws 'No matching operation' error.

[ https://issues.apache.org/jira/browse/TUSCANY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518747 ] Scott Kurz commented on TUSCANY-1473: - This problem looks similar to TUSCANY-1342 which I opened. I commented

[jira] Created: (TUSCANY-1426) Contribution service's Artifact resolving assumes only one WSDL file per Namespace, which disallows import of portType WSDL from endpoint WSDL

Contribution service's Artifact resolving assumes only one WSDL file per Namespace, which disallows import of portType WSDL from endpoint WSDL --

[jira] Commented: (TUSCANY-824) DataBinding: Is it a concern of Programming Model vs. Assembly?

[ https://issues.apache.org/jira/browse/TUSCANY-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510391 ] Scott Kurz commented on TUSCANY-824: I found a problem in this area when I run with my "promote DataBinding to

[jira] Created: (TUSCANY-1412) NPE in DataBindingRuntimeWireProcessor in null output boundary case (and null input?)

NPE in DataBindingRuntimeWireProcessor in null output boundary case (and null input?) - Key: TUSCANY-1412 URL: https://issues.apache.org/jira/browse/TUSCANY-1412 Proj

[jira] Commented: (TUSCANY-1342) Component-level not supported

[ https://issues.apache.org/jira/browse/TUSCANY-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509830 ] Scott Kurz commented on TUSCANY-1342: - Is this as simple as modifying method:boolean match(Operation, Metho

[jira] Updated: (TUSCANY-824) DataBinding: Is it a concern of Programming Model vs. Assembly?

[ https://issues.apache.org/jira/browse/TUSCANY-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-824: --- Attachment: skurz.824.v1.patch This patch attempts to solve two databinding-related problems, though

[jira] Created: (TUSCANY-1342) Component-level not supported

Component-level not supported -- Key: TUSCANY-1342 URL: https://issues.apache.org/jira/browse/TUSCANY-1342 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects

[jira] Commented: (TUSCANY-1327) Generate static SDO APIs from wsdl files with type definition from and

[ https://issues.apache.org/jira/browse/TUSCANY-1327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502022 ] Scott Kurz commented on TUSCANY-1327: - What authority (if any) does the Basic Profile 1.1 have here? BP 1.1

[jira] Commented: (TUSCANY-824) DataBinding: Is it a concern of Programming Model vs. Assembly?

[ https://issues.apache.org/jira/browse/TUSCANY-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501735 ] Scott Kurz commented on TUSCANY-824: This is a link to the ML discussion Raymond mentioned: http://www.mail-arc

[jira] Created: (TUSCANY-1206) DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style

DataBinding support for transform of Fault DataTypes should account for wrappered FaultBean in JAX-WS style --- Key: TUSCANY-1206 URL: https://issues.apache.or

[jira] Commented: (TUSCANY-394) NPE when running wsdl2java tool with "xsd:anyType" in the schema

[ https://issues.apache.org/jira/browse/TUSCANY-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487580 ] Scott Kurz commented on TUSCANY-394: To me it looks like this is no longer a problem. I'm not sure in what sen

[jira] Created: (TUSCANY-1165) Integration branch - Timing issue: incorrect dependency on order of Component loader and ImportSDOLoader within Composite loading

Integration branch - Timing issue: incorrect dependency on order of Component loader and ImportSDOLoader within Composite loading - Key: TUSCANY-1165

[jira] Commented: (TUSCANY-695) JavaComponentTypeLoader.load() returns PojoComponentType which isn't a ModelObject

[ https://issues.apache.org/jira/browse/TUSCANY-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477872 ] Scott Kurz commented on TUSCANY-695: Since I opened this.. I just checked and can see that the specific issue m

[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't clone operations

[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1146: Attachment: 1146.patch Same patch with ASF license..sorry > ServiceContract clone() doesn't clon

[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't clone operations

[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1146: Attachment: 1146.patch This is a patch on the integration-branch. (Should I have attached one to

[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't clone operations

[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1146: Summary: ServiceContract clone() doesn't clone operations (was: ServiceContract clone() doesn't

[jira] Updated: (TUSCANY-1146) ServiceContract clone() doesn't clone operation

[ https://issues.apache.org/jira/browse/TUSCANY-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1146: Summary: ServiceContract clone() doesn't clone operation (was: ServiceContract clone() doesn't c

[jira] Created: (TUSCANY-1146) ServiceContract clone() doesn't clone Operations()

ServiceContract clone() doesn't clone Operations() -- Key: TUSCANY-1146 URL: https://issues.apache.org/jira/browse/TUSCANY-1146 Project: Tuscany Issue Type: Bug Components: Java SCA C

[jira] Created: (TUSCANY-1142) Need to allow generation of wrapped Java intf from doc-lit-wrap WSDL with named complexType

Need to allow generation of wrapped Java intf from doc-lit-wrap WSDL with named complexType Key: TUSCANY-1142 URL: https://issues.apache.org/jira/browse/TUSCANY-1142

[jira] Commented: (TUSCANY-1137) WSDL2Java tool should be able to handle imports of other WSDL files into the original WSDL

[ https://issues.apache.org/jira/browse/TUSCANY-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475537 ] Scott Kurz commented on TUSCANY-1137: - So in the above example if Service.wsdl imports PortType.wsdl, we hit th

[jira] Updated: (TUSCANY-1137) WSDL2Java tool should be able to handle imports of other WSDL files into the original WSDL

[ https://issues.apache.org/jira/browse/TUSCANY-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1137: Attachment: Service.wsdl > WSDL2Java tool should be able to handle imports of other WSDL files in

[jira] Updated: (TUSCANY-1137) WSDL2Java tool should be able to handle imports of other WSDL files into the original WSDL

[ https://issues.apache.org/jira/browse/TUSCANY-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Kurz updated TUSCANY-1137: Attachment: PortType.wsdl > WSDL2Java tool should be able to handle imports of other WSDL files i

[jira] Created: (TUSCANY-1137) WSDL2Java tool should be able to handle imports of other WSDL files into the original WSDL

WSDL2Java tool should be able to handle imports of other WSDL files into the original WSDL -- Key: TUSCANY-1137 URL: https://issues.apache.org/jira/browse/TUSCANY-1137

[jira] Commented: (TUSCANY-544) WSDL2Java should support WSDLs with schema imports

[ https://issues.apache.org/jira/browse/TUSCANY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475520 ] Scott Kurz commented on TUSCANY-544: I think it would help to add some specific detail on what you want WSDL2Ja

[jira] Commented: (TUSCANY-983) Schema Definitions need to be unregistered from Registry

[ https://issues.apache.org/jira/browse/TUSCANY-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475330 ] Scott Kurz commented on TUSCANY-983: When Kapish and I noticed the overall lack of undeploy and the problematic

[jira] Created: (TUSCANY-1063) Improve diagnostics running XSD2JavaGenerator against bad schema

Improve diagnostics running XSD2JavaGenerator against bad schema Key: TUSCANY-1063 URL: https://issues.apache.org/jira/browse/TUSCANY-1063 Project: Tuscany Issue Type: Improvem

[jira] Commented: (TUSCANY-1019) WSDL2Java should offer option to generate Java signature with non-wrapper style mapping from doc-lit-wrapped WSDL

[ https://issues.apache.org/jira/browse/TUSCANY-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12463905 ] Scott Kurz commented on TUSCANY-1019: - Thanks for investigating. I'd assume you'd be able to use any compatib

[jira] Created: (TUSCANY-1034) Need to add support for business exceptions - at least in simple intra-Composite case to begin with

Need to add support for business exceptions - at least in simple intra-Composite case to begin with --- Key: TUSCANY-1034 URL: https://issues.apache.org/jira/browse/TU

[jira] Created: (TUSCANY-1019) WSDL2Java should offer option to generate Java signature with non-wrapper style mapping from doc-lit-wrapped WSDL

WSDL2Java should offer option to generate Java signature with non-wrapper style mapping from doc-lit-wrapped WSDL - Key: TUSCANY-1019 URL: http://issue

[jira] Updated: (TUSCANY-941) Zero Parm operation w/ SDO @DataType annotation fails over WS binding

[ http://issues.apache.org/jira/browse/TUSCANY-941?page=all ] Scott Kurz updated TUSCANY-941: --- Attachment: helloworld.wsdl I believe this is the correct way to do this..to keep the input message on the operation and to wrap an empty element:

[jira] Updated: (TUSCANY-947) JDKCallbackInvocationHandler should handle toString(), hashCode(), equals() specially

[ http://issues.apache.org/jira/browse/TUSCANY-947?page=all ] Scott Kurz updated TUSCANY-947: --- Attachment: 947.patch Jim, I don't know enough about EasyMock or the class I'm changing to copy over the Inbound handler's tests, so I just copied to outbound

[jira] Updated: (TUSCANY-947) JDKCallbackInvocationHandler should handle toString(), hashCode(), equals() specially

[ http://issues.apache.org/jira/browse/TUSCANY-947?page=all ] Scott Kurz updated TUSCANY-947: --- Attachment: 947.patch I can copy code from one place to the next ;) But if someone wants to do something better go ahead. > JDKCallbackInvocationHandler shou

[jira] Created: (TUSCANY-947) JDKCallbackInvocationHandler should handle toString(), hashCode(), equals() specially

JDKCallbackInvocationHandler should handle toString(), hashCode(), equals() specially - Key: TUSCANY-947 URL: http://issues.apache.org/jira/browse/TUSCANY-947 Project

[jira] Commented: (TUSCANY-686) InterfaceWSDLLoader creates WSDLServiceContract objs which return null on getInterfaceClass()

[ http://issues.apache.org/jira/browse/TUSCANY-686?page=comments#action_12452031 ] Scott Kurz commented on TUSCANY-686: I THINK THIS JIRA CAN BE CLOSED I believe the current reworking of the bindings' use of the ServiceContract and the Ja

[jira] Commented: (TUSCANY-942) Need to build proxy when using locateService on Composite reference w/

[ http://issues.apache.org/jira/browse/TUSCANY-942?page=comments#action_12451412 ] Scott Kurz commented on TUSCANY-942: DUPLICATE: Looks like Ant already opened this same issue as TUSCANY-862. > Need to build proxy when using locateServ

[jira] Created: (TUSCANY-942) Need to build proxy when using locateService on Composite reference w/

Need to build proxy when using locateService on Composite reference w/ --- Key: TUSCANY-942 URL: http://issues.apache.org/jira/browse/TUSCANY-942 Project: Tuscany

[jira] Commented: (TUSCANY-642) Composite references and services - model and runtime representations

[ http://issues.apache.org/jira/browse/TUSCANY-642?page=comments#action_12433608 ] Scott Kurz commented on TUSCANY-642: I'm having two problems w/ this last patch, RevisedInnerCompositeCallback.patch First, when I try to apply w/: > patch

[jira] Created: (TUSCANY-695) JavaComponentTypeLoader.load() returns PojoComponentType which isn't a ModelObject

JavaComponentTypeLoader.load() returns PojoComponentType which isn't a ModelObject -- Key: TUSCANY-695 URL: http://issues.apache.org/jira/browse/TUSCANY-695 Project: Tusc

[jira] Commented: (TUSCANY-686) InterfaceWSDLLoader creates WSDLServiceContract objs which return null on getInterfaceClass()

[ http://issues.apache.org/jira/browse/TUSCANY-686?page=comments#action_12432666 ] Scott Kurz commented on TUSCANY-686: A few points I'd like to add to the discussion here: First, 1) It could be that it's best to consider it to be the bind

[jira] Created: (TUSCANY-686) InterfaceWSDLLoader creates WSDLServiceContract objs which return null on getInterfaceClass()

InterfaceWSDLLoader creates WSDLServiceContract objs which return null on getInterfaceClass() - Key: TUSCANY-686 URL: http://issues.apache.org/jira/browse/TUSCANY-686

[jira] Updated: (TUSCANY-679) InterfaceWSDLLoader mismatch btw. @Constructor annot. and actual Constructor parms

[ http://issues.apache.org/jira/browse/TUSCANY-679?page=all ] Scott Kurz updated TUSCANY-679: --- Attachment: InterfaceWSDLLoader.ConstructorFix.patch Hopefully this is the right patch format (this is my first patch here) > InterfaceWSDLLoader mismatch btw.

[jira] Created: (TUSCANY-679) InterfaceWSDLLoader mismatch btw. @Constructor annot. and actual Constructor parms

InterfaceWSDLLoader mismatch btw. @Constructor annot. and actual Constructor parms --- Key: TUSCANY-679 URL: http://issues.apache.org/jira/browse/TUSCANY-679 Project: Tu

[jira] Created: (TUSCANY-662) Axis2 Binding's OperationClient needs to be reset to support repeated invocation

Axis2 Binding's OperationClient needs to be reset to support repeated invocation Key: TUSCANY-662 URL: http://issues.apache.org/jira/browse/TUSCANY-662 Project: Tuscany

[jira] Updated: (TUSCANY-232) It would be educational to provide a flavor of the HelloWorld WS / HWWS Client sample which used different names in different contexts where the name "HelloWorldService"

[ http://issues.apache.org/jira/browse/TUSCANY-232?page=all ] Scott Kurz updated TUSCANY-232: --- Attachment: JIRA-232.patch.zip OK... so I didn't refresh my page in 3 hours and missed Sebastien's comment. I attached the only thing left, which is just the

  1   2   >