from:"Raymond Feng"

[
https://issues.apache.org/jira/browse/TUSCANY-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604572#action_12604572
]

Raymond Feng commented on TUSCANY-2383:
---

If the component is implemented in java, I think this is a grey area in the
spec. The spec says the configuration in the componentType should be compatible
with the result from the instrospection of implemention. Let's say your purpose
is to declare a property in the componentType file, then it has to be
associated to a field or setter in the java class. Is the field/setter required
to be protected or public? My understanding is that we can use the
componentType to provide a default value to a property, but not add a new
property if it doesn't exist in the impl class.

There are discussions on the ML about if we should use componentType to
redefine the service interface using interface.wsdl. I think these are in the
same area.

Cannot define component property with Component Type File
-

Key: TUSCANY-2383
URL: https://issues.apache.org/jira/browse/TUSCANY-2383
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Kevin Williams

Lines 450-451 of the Assembly spec:
The componentType element can contain Service elements, Reference elements
and Property elements.
I defined a test that inspects an injected property value. In the initial
version I defined the property using the @Property annotation. I then tried
replacing the annotation with an entry in a Component Type File without
success.
The test:
org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase.typeFile3
demonstrates this failure and is currently @Ignore(d)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (TUSCANY-2386) Databinding problem for array of javax.xml.transform.Source with binding.ws


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2386:
-

Assignee: Raymond Feng

 Databinding problem for array of javax.xml.transform.Source with binding.ws
 ---

 Key: TUSCANY-2386
 URL: https://issues.apache.org/jira/browse/TUSCANY-2386
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime, Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 I am getting a TransformationException with a service method that takes an 
 array of javax.xml.transform.Source objects.  See 
 StandardTypesDatabindingTestCase.testWSNewSourceArray() under 
 sca\itest\databindings\jaxb-bottom-up.  StackTrace is given below:
 org.apache.tuscany.sca.databinding.TransformationException: No path found for 
 the transformation: java:array-org.apache.axiom.om.OMElement
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:165)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:69)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:201)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:45)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:81)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:186)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:76)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
   at $Proxy21.getNewSourceArray(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.impl.StandardTypesLocalServiceClientImpl.getNewSourceArrayForward(StandardTypesLocalServiceClientImpl.java:147)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:111)
   at 
 org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
   at $Proxy20.getNewSourceArrayForward(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.StandardTypesDatabindingTestCase.performTestNewSourceArray(StandardTypesDatabindingTestCase.java:1300)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.StandardTypesDatabindingTestCase.testWSNewSourceArray(StandardTypesDatabindingTestCase.java:649)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
   at 
 org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
   at 
 org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
   at 
 org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
   at 
 org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
   at 
 org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
   at 
 org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
   at 
 org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
   at 
 org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run

[jira] Assigned: (TUSCANY-2385) Problem with Databinding for URI and UUID objects when using binding.ws


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2385:
-

Assignee: Raymond Feng

 Problem with Databinding for URI and UUID objects when using binding.ws
 ---

 Key: TUSCANY-2385
 URL: https://issues.apache.org/jira/browse/TUSCANY-2385
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime, Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 I am noticing that when I am invoking a service method that takes an object 
 as parameter over binding.ws,, the URI and UUID standard types that map to 
 xs:string XML data type are being presented to the service method as String 
 rather than their respective types.
 See StandardTypesDatabindingTestCase.testWSNewObject() under 
 sca\itest\databindings\jaxb-bottom-up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (TUSCANY-2387) Databinding problem for array of javax.xml.transform.Source with binding.sca and remotable service


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2387:
-

Assignee: Raymond Feng

 Databinding problem for array of javax.xml.transform.Source with binding.sca 
 and remotable service
 --

 Key: TUSCANY-2387
 URL: https://issues.apache.org/jira/browse/TUSCANY-2387
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime, Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 I am getting a MarshalException with a remotable service method that takes an 
 array of javax.xml.transform.Source objects invoked over binding.sca. See 
 StandardTypesDatabindingTestCase.testSCANewSourceArray() under 
 sca\itest\databindings\jaxb-bottom-up. StackTrace is given below: 
 java.lang.IllegalArgumentException: javax.xml.bind.MarshalException
  - with linked exception:
 [javax.xml.bind.JAXBException: class javax.xml.transform.dom.DOMSource nor 
 any of its super class is known to this context.]
   at 
 org.apache.tuscany.sca.databinding.jaxb.JAXBDataBinding.copy(JAXBDataBinding.java:117)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.copy(DefaultDataBindingExtensionPoint.java:172)
   at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copy(PassByValueInterceptor.java:241)
   at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copy(PassByValueInterceptor.java:160)
   at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:106)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
   at $Proxy21.getNewSourceArray(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.impl.StandardTypesLocalServiceClientImpl.getNewSourceArrayForward(StandardTypesLocalServiceClientImpl.java:147)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:111)
   at 
 org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
   at $Proxy20.getNewSourceArrayForward(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.StandardTypesDatabindingTestCase.performTestNewSourceArray(StandardTypesDatabindingTestCase.java:1300)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.StandardTypesDatabindingTestCase.testSCANewSourceArray(StandardTypesDatabindingTestCase.java:354)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
   at 
 org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
   at 
 org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
   at 
 org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
   at 
 org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
   at 
 org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
   at 
 org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
   at 
 org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
   at 
 org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38

[jira] Assigned: (TUSCANY-2366) QName with just a localPart not getting passed in arrays with binding.ws to invoke service


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2366:
-

Assignee: Raymond Feng

 QName with just a localPart not getting passed in arrays with binding.ws to 
 invoke service
 --

 Key: TUSCANY-2366
 URL: https://issues.apache.org/jira/browse/TUSCANY-2366
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 I have a service method that takes an array of QName and returns an array of 
 QName.  I am noticing that when I invoke the method using webservice binding, 
 the QName elements with just the localPart are not getting passed over the 
 wire.  To give an idea of what is happening, I have the following QName array:
 QName[] qnames = new QName[4];
 qnames[0] = new QName(localPart);
 qnames[1] = new QName(namespaceUri, localPart);
 qnames[2] = new QName(namespaceUri, localPart, prefix);
 qnames[3] = new QName(localPart2);
 When the method is invoked, it is receiving an array with only two elements 
 instead of four.  The first and last element that have only the localpart are 
 not getting passed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (TUSCANY-2385) Problem with Databinding for URI and UUID objects when using binding.ws


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng resolved TUSCANY-2385.
---

Resolution: Invalid

Both URI and UUID are mapped into xsd:string. So the URI and UUID values will 
be mashaled as xsd:string in the request. On the receiving side, the argument 
type is Object.class. As a result, the value is unmarshaled as a String. So 
it's a problem on the interface definition, we need to make the argument 
explicitly URI or UUID so that it can roundtrip across WS.

 Problem with Databinding for URI and UUID objects when using binding.ws
 ---

 Key: TUSCANY-2385
 URL: https://issues.apache.org/jira/browse/TUSCANY-2385
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime, Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 I am noticing that when I am invoking a service method that takes an object 
 as parameter over binding.ws,, the URI and UUID standard types that map to 
 xs:string XML data type are being presented to the service method as String 
 rather than their respective types.
 See StandardTypesDatabindingTestCase.testWSNewObject() under 
 sca\itest\databindings\jaxb-bottom-up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (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:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2388:
-

Assignee: Raymond Feng

 Data binding does not work when Java interface  implementation (where method 
 param is not String, primitive) exposed with a web services binding 
 --

 Key: TUSCANY-2388
 URL: https://issues.apache.org/jira/browse/TUSCANY-2388
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.1
 Environment: Windows XP; IBM J2RE 1.5.0 (Build 2.3)
Reporter: Peter Kemp
Assignee: Raymond Feng
 Attachments: testcase.zip


 1. Create a component with a java implementation, with a service defined by a 
 Java interface. 
 The parameter to the method is not a String, primitive or wrapper - rather, 
 it's a class containing a couple of Strings and an Integer.
 2. Expose the service with a webservice binding.  
 3. Deploy the composite (as a WAR or embedded).
 4. Retrieve the WSDL for the service (eg from 
 http://localhost:8080/SomeServices?wsdl).
 5. Generate a web service request from the WSDL.
 The runtime fails to map the web service request message to the 
 implementation class method parameters - it calls the correct method, but the 
 method parameter is null.
 The test works fine when the parameter is a String.
 Composite definition (some.composite):
 ---
 ?xml version=1.0 encoding=UTF-8?
 composite xmlns=http://www.osoa.org/xmlns/sca/1.0; 
 targetNamespace=http://test; xmlns:test=http://test; name=some
 service name=SomeServices promote=SomeServicesComponent
 binding.ws uri=http://localhost:8080/SomeServices/
 /service
 component name=SomeServicesComponent
 implementation.java class=service.SomeServiceImpl/
 service name=SomeService
 interface.java interface=service.SomeService /  
 /service
 /component
 /composite
 Service interface:
 ---
 /**
  * 
  */
 package service;
 import org.osoa.sca.annotations.Remotable;
 @Remotable
 public interface SomeService {
 
 public AnObject getUsingString(String stringParam);
 public AnObject getUsingMoreComplexObject(MoreComplexObject 
 moreComplexParam);
 
 }
 Implementation:
 --
 package service;
 import org.osoa.sca.annotations.Service;
 @Service(SomeService.class)
 public class SomeServiceImpl implements SomeService {
 public AnObject getUsingString(String stringParam) {
 System.out.println(Param value: + stringParam);
 return getAnObject(stringParam);
 }
 private AnObject getAnObject(String stringParam) {
 // TODO Auto-generated method stub
 return new AnObject(stringParam + 123, 123);
 }
 public AnObject getUsingMoreComplexObject(MoreComplexObject 
 moreComplexParam) {
 System.out.println(Param value: + 
 moreComplexParam.getStringParam());
 
 return getAnObject(moreComplexParam.getStringParam());
 }
 
 }
 MoreComplexObject.java
 ---
 /**
  * 
  */
 package service;
 import java.io.Serializable;
 public class MoreComplexObject implements Serializable{
 private static final long serialVersionUID = 43242314234123L;
 private String stringParam;
 private Integer intParam;
 private String stringParam2;
 public String getStringParam() {
 return stringParam;
 }
 public void setStringParam(String stringParam) {
 this.stringParam = stringParam;
 }
 public Integer getIntParam() {
 return intParam;
 }
 public void setIntParam(Integer intParam) {
 this.intParam = intParam;
 }
 public String getStringParam2() {
 return stringParam2;
 }
 public void setStringParam2(String stringParam2) {
 this.stringParam2 = stringParam2;
 }
 
 }
 AnObject.java
 -
 package service;
 public class AnObject {
 private String someRetValue;
 private Integer someOtherRetValue;
 
 public AnObject() {
 }
 public AnObject(String someRetValue, Integer someOtherRetValue) {
 this.someRetValue = someRetValue;
 this.someOtherRetValue = someOtherRetValue;
 }
 /**
  * @return the someOtherRetValue
  */
 public Integer getSomeOtherRetValue() {
 return someOtherRetValue;
 }
 /**
  * @param someOtherRetValue the someOtherRetValue to set
  */
 public void setSomeOtherRetValue(Integer someOtherRetValue) {
 this.someOtherRetValue = someOtherRetValue;
 }
 /**
  * @return

[jira] Resolved: (TUSCANY-2351) byte array passed by reference when using sca binding even though implementation does not have @AllowsPassByReference


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng resolved TUSCANY-2351.
---

Resolution: Fixed

Fixed under 667179

 byte array passed by reference when using sca binding even though 
 implementation does not have @AllowsPassByReference
 -

 Key: TUSCANY-2351
 URL: https://issues.apache.org/jira/browse/TUSCANY-2351
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 I have method (in a remotable interface)  that takes a byte array parameter 
 and returns a byte array.  When I invoke the method using SCA binding, I am 
 noticing that the parameter passed to the method is modified even though the 
 implementation is not annotated with @AllowsPassByReference.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (TUSCANY-2383) Cannot define component property with Component Type File

2008-06-12 Thread Raymond Feng


Hi,

It turned out this test case is not adding incompatible changes from the 
componentType file. We were checking if the field is public upon the 
injection of a property value. It was an interpretation of the Java AA:


1349 Properties may also be injected via public setter methods even when the 
@Property annotation is not
1350 present. However, the @Property annotation must be used in order to 
inject a property onto a non-public
1351 field. In the case where there is no @Property annotation, the name of 
the property is the same as the

1352 name of the field or setter.

See TUSCANY-2289 too.

I just fixed it by not checking if the field is public.

Thanks,
Raymond

--
From: Kevin Williams [EMAIL PROTECTED]
Sent: Thursday, June 12, 2008 10:38 AM
To: Raymond Feng (JIRA) tuscany-dev@ws.apache.org
Subject: Re: [jira] Commented: (TUSCANY-2383) Cannot define component 
property with Component Type File



I may not fully understand your comment but it seems inconsistent to
support the provision of component type information via a type file
for service and reference elements but not for property elements.

In the test I have only removed the @Property annotation from the java
implementation and replaced it with an element in the Component Type
File.

On Thu, Jun 12, 2008 at 10:52 AM, Raymond Feng (JIRA)
tuscany-dev@ws.apache.org wrote:


   [ 
https://issues.apache.org/jira/browse/TUSCANY-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604572#action_12604572 ]


Raymond Feng commented on TUSCANY-2383:
---

If the component is implemented in java, I think this is a grey area in 
the spec. The spec says the configuration in the componentType should be 
compatible with the result from the instrospection of implemention. Let's 
say your purpose is to declare a property in the componentType file, then 
it has to be associated to a field or setter in the java class. Is the 
field/setter required to be protected or public? My understanding is that 
we can use the componentType to provide a default value to a property, 
but not add a new property if it doesn't exist in the impl class.


There are discussions on the ML about if we should use componentType to 
redefine the service interface using interface.wsdl. I think these are in 
the same area.



Cannot define component property with Component Type File
-

Key: TUSCANY-2383
URL: https://issues.apache.org/jira/browse/TUSCANY-2383
Project: Tuscany
 Issue Type: Bug
 Components: Java SCA Core Runtime
   Affects Versions: Java-SCA-Next
   Reporter: Kevin Williams

Lines 450-451 of the Assembly spec:
The componentType element can contain Service elements, Reference 
elements and Property elements.
I defined a test that inspects an injected property value.  In the 
initial version I defined the property using the @Property annotation. 
I then tried replacing the annotation with an entry in a Component Type 
File without success.

The test:
org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase.typeFile3 
demonstrates this failure and is currently @Ignore(d)


--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Commented: (TUSCANY-2383) Cannot define component property with Component Type File

2008-06-12 Thread Raymond Feng


Hi,

I just make the protected field injectable. :-)

Thanks,
Raymond
--
From: Scott Kurz [EMAIL PROTECTED]
Sent: Thursday, June 12, 2008 1:08 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [jira] Commented: (TUSCANY-2383) Cannot define component 
property with Component Type File



Raymond,

Just curious: did you fix it in a way such that the .componentType 
property

definition matters or is the component property definition enough to have
the value injected?


On Thu, Jun 12, 2008 at 3:39 PM, Raymond Feng [EMAIL PROTECTED] wrote:


Hi,

It turned out this test case is not adding incompatible changes from the
componentType file. We were checking if the field is public upon the
injection of a property value. It was an interpretation of the Java AA:

1349 Properties may also be injected via public setter methods even when
the @Property annotation is not
1350 present. However, the @Property annotation must be used in order to
inject a property onto a non-public
1351 field. In the case where there is no @Property annotation, the name 
of

the property is the same as the
1352 name of the field or setter.

See TUSCANY-2289 too.

I just fixed it by not checking if the field is public.

Thanks,
Raymond

--
From: Kevin Williams [EMAIL PROTECTED]
Sent: Thursday, June 12, 2008 10:38 AM
To: Raymond Feng (JIRA) tuscany-dev@ws.apache.org
Subject: Re: [jira] Commented: (TUSCANY-2383) Cannot define component
property with Component Type File


 I may not fully understand your comment but it seems inconsistent to

support the provision of component type information via a type file
for service and reference elements but not for property elements.

In the test I have only removed the @Property annotation from the java
implementation and replaced it with an element in the Component Type
File.

On Thu, Jun 12, 2008 at 10:52 AM, Raymond Feng (JIRA)
tuscany-dev@ws.apache.org wrote:



  [
https://issues.apache.org/jira/browse/TUSCANY-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604572#action_12604572]

Raymond Feng commented on TUSCANY-2383:
---

If the component is implemented in java, I think this is a grey area in
the spec. The spec says the configuration in the componentType should 
be
compatible with the result from the instrospection of implemention. 
Let's
say your purpose is to declare a property in the componentType file, 
then it

has to be associated to a field or setter in the java class. Is the
field/setter required to be protected or public? My understanding is 
that we
can use the componentType to provide a default value to a property, but 
not

add a new property if it doesn't exist in the impl class.

There are discussions on the ML about if we should use componentType to
redefine the service interface using interface.wsdl. I think these are 
in

the same area.

 Cannot define component property with Component Type File

-

   Key: TUSCANY-2383
   URL: https://issues.apache.org/jira/browse/TUSCANY-2383
   Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
  Affects Versions: Java-SCA-Next
  Reporter: Kevin Williams

Lines 450-451 of the Assembly spec:
The componentType element can contain Service elements, Reference
elements and Property elements.
I defined a test that inspects an injected property value.  In the
initial version I defined the property using the @Property annotation. 
I
then tried replacing the annotation with an entry in a Component Type 
File

without success.
The test:
org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase.typeFile3
demonstrates this failure and is currently @Ignore(d)



--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: svn commit: r666556 - /incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java

2008-06-11 Thread Raymond Feng

I have all these test cases passed in my eclipse. I'm checking if I miss any 
changes in the commit.


Thanks,
Raymond

--
From: [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 12:56 AM
To: [EMAIL PROTECTED]
Subject: svn commit: r666556 - 
/incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java



Author: vamsic007
Date: Wed Jun 11 00:56:50 2008
New Revision: 666556

URL: http://svn.apache.org/viewvc?rev=666556view=rev
Log:
Marking the failing tests with @Ignore.

Modified:

incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java

Modified: 
incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java
URL: 
http://svn.apache.org/viewvc/incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java?rev=666556r1=666555r2=666556view=diff

==
---  
incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java 
(original)
+++ 
incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java 
Wed Jun 11 00:56:50 2008

@@ -25,6 +25,7 @@
import 
org.apache.tuscany.sca.itest.databindings.jaxb.impl.GenericsTransformer;

import org.junit.AfterClass;
import org.junit.BeforeClass;
+import org.junit.Ignore;
import org.junit.Test;

/**
@@ -81,7 +82,7 @@
 * Service method invoked is getTypeExtends.
 */
@Test
-// @Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)
+@Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)

public void testSCATypeExtends() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientSCAComponent);

performTestTypeExtends(serviceClient);
@@ -113,7 +114,7 @@
 * Service method invoked is getWildcardSuper.
 */
@Test
-// @Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)
+@Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)

public void testSCAWildcardSuper() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientSCAComponent);

performTestWildcardSuper(serviceClient);
@@ -124,7 +125,7 @@
 * Service method invoked is getWildcardExtends.
 */
@Test
-// @Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)
+@Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)

public void testSCAWildcardExtends() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientSCAComponent);

performTestWildcardExtends(serviceClient);
@@ -198,7 +199,7 @@
 * Service method invoked is getWildcardSuper.
 */
@Test
-// @Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)
+@Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)

public void testWSWildcardSuper() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientWSComponent);

performTestWildcardSuper(serviceClient);
@@ -209,7 +210,7 @@
 * Service method invoked is getWildcardExtends.
 */
@Test
-// @Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)
+@Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)

public void testWSWildcardExtends() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientWSComponent);

performTestWildcardExtends(serviceClient);

Re: svn commit: r666556 - /incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java

2008-06-11 Thread Raymond Feng


Yes, I missed one file. I'll add it in now.

Thanks,
Raymond

--
From: Raymond Feng [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 8:14 AM
To: tuscany-dev@ws.apache.org
Subject: Re: svn commit: r666556 - 
/incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java


I have all these test cases passed in my eclipse. I'm checking if I miss 
any changes in the commit.


Thanks,
Raymond

--
From: [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 12:56 AM
To: [EMAIL PROTECTED]
Subject: svn commit: r666556 - 
/incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java



Author: vamsic007
Date: Wed Jun 11 00:56:50 2008
New Revision: 666556

URL: http://svn.apache.org/viewvc?rev=666556view=rev
Log:
Marking the failing tests with @Ignore.

Modified:

incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java

Modified: 
incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java
URL: 
http://svn.apache.org/viewvc/incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java?rev=666556r1=666555r2=666556view=diff

==
---  
incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java 
(original)
+++ 
incubator/tuscany/java/sca/itest/databindings/jaxb-bottom-up/src/test/java/org/apache/tuscany/sca/itest/databindings/jaxb/GenericsDatabindingTestCase.java 
Wed Jun 11 00:56:50 2008

@@ -25,6 +25,7 @@
import 
org.apache.tuscany.sca.itest.databindings.jaxb.impl.GenericsTransformer;

import org.junit.AfterClass;
import org.junit.BeforeClass;
+import org.junit.Ignore;
import org.junit.Test;

/**
@@ -81,7 +82,7 @@
 * Service method invoked is getTypeExtends.
 */
@Test
-// @Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)
+@Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)

public void testSCATypeExtends() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientSCAComponent);

performTestTypeExtends(serviceClient);
@@ -113,7 +114,7 @@
 * Service method invoked is getWildcardSuper.
 */
@Test
-// @Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)
+@Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)

public void testSCAWildcardSuper() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientSCAComponent);

performTestWildcardSuper(serviceClient);
@@ -124,7 +125,7 @@
 * Service method invoked is getWildcardExtends.
 */
@Test
-// @Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)
+@Ignore(java.lang.IllegalArgumentException: 
javax.xml.bind.MarshalException)

public void testSCAWildcardExtends() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientSCAComponent);

performTestWildcardExtends(serviceClient);
@@ -198,7 +199,7 @@
 * Service method invoked is getWildcardSuper.
 */
@Test
-// @Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)
+@Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)

public void testWSWildcardSuper() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientWSComponent);

performTestWildcardSuper(serviceClient);
@@ -209,7 +210,7 @@
 * Service method invoked is getWildcardExtends.
 */
@Test
-// @Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)
+@Ignore(org.osoa.sca.ServiceRuntimeException: 
org.apache.axis2.AxisFault)

public void testWSWildcardExtends() throws Exception {
GenericsServiceClient serviceClient = 
domain.getService(GenericsServiceClient.class, 
GenericsServiceClientWSComponent);

performTestWildcardExtends(serviceClient);

Re: Databinding test for javax.xml.transform.Source problem

2008-06-11 Thread Raymond Feng

If I run the test case alone without others in the same class, then it 
passes. I think there is some interference from other test cases. 
Especially, the Source, Image are both map to the same XSD type.


We need to dig out what's conflicting.

Thanks,
Raymond
--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 6:01 AM
To: tuscany-dev@ws.apache.org
Subject: Databinding test for javax.xml.transform.Source problem


I have updated the tests to get the content out of Source objects and
compare the contents. I have the following StreamSource as input:

new StreamSource(new StringReader(aA/a)).

The content I am from this source is as follows:
?xml version=1.0 encoding=UTF-8?
aA/a

I have a service method that returns a copy of the source that is passed 
to

it.  The source that is returned when the service method is invoked over
binding.ws is giveing the following content:
?xml version=1.0 encoding=UTF-8?
return xmlns=http://jaxb.databindings.itest.sca.tuscany.apache.org/
A/return

Notice the namespace and the change in the root tag.  Any suggestions on
changing the test?

Good practice for disabling/ignoring failing test cases

2008-06-11 Thread Raymond Feng


Hi,

I see Vamsi uses the following strategy to disable failing unit test cases.

@Test
@Ignore(TUSCANY-) // Ignore the test case due to JIRA TUSCANY-
public void testMySrtuff() {
}

I think it's a very good practice we should follow to maintain a clean build 
while keep track of the ignored failing test cases with JIRAs.


Thanks,
Raymond

Re: Unable to download the artifact from any repository

2008-06-11 Thread Raymond Feng


Hi,

We should have the following maven repo declared in the pom.xml:

   repository
   idapache.snapshots/id
   nameApache Snapshot Repository/name
   urlhttp://people.apache.org/repo/m2-snapshot-repository/url
   releases
   enabledfalse/enabled
   /releases
   snapshots
   enabledtrue/enabled
   /snapshots
   /repository

But I cannot find it anywhere in the pom.xml under the java/sca tree. Is it 
a bug? If we build from sca folder, then it works fine. What about 
building modules/... from an empty local maven repo?


Thanks,
Raymond

--
From: Oscar Castaneda [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 11:29 AM
To: tuscany-dev@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: Unable to download the artifact from any repository

Thanks ant. I tried it but unfortunately I'm getting the same problem. 
I'll

continue looking at it, any suggestions are welcome.


On Wed, Jun 11, 2008 at 8:21 PM, ant elder [EMAIL PROTECTED] wrote:


There's a Maven settings.xml we have for Tuscany the might help you at:
https://svn.apache.org/repos/asf/incubator/tuscany/java/etc/settings.xml

  ...ant

On Wed, Jun 11, 2008 at 7:13 PM, Oscar Castaneda 
[EMAIL PROTECTED] wrote:

 
  It doesn't look right that the first of those URLs is pointing at my
 apache
  space - 
  http://people.apache.org/~antelderhttp://people.apache.org/%7Eantelder

http://people.apache.org/%7Eantelder
 http://people.apache.org/%7Eantelder
  .


 Thanks alot ant, you're right! I changed settings.xml following an old
 email
 thread. I deleted the file and executed mvn and its now complaining 
 about

 not being able to resolve artifacts (and that's solvable my manually
 installing them I think).

 However, I was only testing this because of the problems I was
experiencing
 when building revision 643746. Any ideas here? Maybe modifying the
 settings.xml to get the required files from somewhere else?

 Here's the trace:

 $ mvn clean install -Dtest=no
 [INFO] Scanning for projects...
 [INFO]
 
 [ERROR] FATAL ERROR
 [INFO]
 
 [INFO] Failed to resolve artifact.

 GroupId: org.apache.tuscany.sca
 ArtifactId: tuscany-sca
 Version: 2.0-incubating-SNAPSHOT

 Reason: Unable to download the artifact from any repository

   org.apache.tuscany.sca:tuscany-sca:pom:2.0-incubating-SNAPSHOT

 from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


 [INFO]
 
 [INFO] Trace
 org.apache.maven.reactor.MavenExecutionException: Cannot find parent:
 org.apache.tuscany.sca:tuscany-sca for project:
 null:tuscany-modules:pom:null
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at


sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at


sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at 
 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Caused by: org.apache.maven.project.ProjectBuildingException: Cannot 
 find

 parent: org.apache.tuscany.sca:tuscany-sca for project:
 null:tuscany-modules:pom:null
at


org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1264)
at


org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:749)
at


org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:479)
at


org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364)
... 11 more
 Caused by: org.apache.maven.project.ProjectBuildingException: POM
 'org.apache.tuscany.sca:tuscany-sca' not found in repository: Unable to
 download the artifact from any repository

   org.apache.tuscany.sca:tuscany-sca:pom:2.0-incubating-SNAPSHOT

 from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

at

Test failure: CallBackSetCallbackConvTestCase

2008-06-11 Thread Raymond Feng


Hi, Simon Nash.

I'm seeing the following failure after I refreshed from r666738 (your fix 
for TUSCANY-2312).


Thanks,
Raymond

---
T E S T S
---
Running org.apache.tuscany.sca.test.CallBackSetCallbackConvTestCase
CallBackSetCallbackConvServiceImpl message received: Knock Knock
Entering CallBackSetCallbackObjectCallback callBackMessage: Who's There
Entering callback increment: This should do it
CallBackSetCallbackConvServiceImpl response sent
CallBackSetCallbackConvServiceImpl message received: Knock Knock
java.lang.reflect.UndeclaredThrowableException
   at $Proxy12.callBackMessage(Unknown Source)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvServiceImpl.knockKnock(CallBackSetCallbackConvServiceImpl.java:43)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:128)
   at 
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)

   at $Proxy11.knockKnock(Unknown Source)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvClientImpl.test8(CallBackSetCallbackConvClientImpl.java:108)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvClientImpl.run(CallBackSetCallbackConvClientImpl.java:59)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:128)
   at 
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
   at 
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
   at 
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)

   at $Proxy10.run(Unknown Source)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvTestCase.testCallBackSetCallback(CallBackSetCallbackConvTestCase.java:31)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at junit.framework.TestCase.runTest(TestCase.java:168)
   at junit.framework.TestCase.runBare(TestCase.java:134)
   at junit.framework.TestResult$1.protect(TestResult.java:110)
   at junit.framework.TestResult.runProtected(TestResult.java:128)
   at junit.framework.TestResult.run(TestResult.java:113)
   at junit.framework.TestCase.run(TestCase.java:124)
   at junit.framework.TestSuite.runTest(TestSuite.java:232)
   at junit.framework.TestSuite.run(TestSuite.java:227)
   at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
   at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
   at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
   at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)

   at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:308)
   at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:879)
Caused by: java.lang.NoSuchMethodException:

Re: Test failure: CallBackSetCallbackConvTestCase

2008-06-11 Thread Raymond Feng


There are some mismatching in the exceptions. I fixed it under r666812.

Thanks,
Raymond
--
From: Raymond Feng [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 11:54 AM
To: tuscany-dev@ws.apache.org
Subject: Test failure: CallBackSetCallbackConvTestCase


Hi, Simon Nash.

I'm seeing the following failure after I refreshed from r666738 (your fix 
for TUSCANY-2312).


Thanks,
Raymond

---
T E S T S
---
Running org.apache.tuscany.sca.test.CallBackSetCallbackConvTestCase
CallBackSetCallbackConvServiceImpl message received: Knock Knock
Entering CallBackSetCallbackObjectCallback callBackMessage: Who's There
Entering callback increment: This should do it
CallBackSetCallbackConvServiceImpl response sent
CallBackSetCallbackConvServiceImpl message received: Knock Knock
java.lang.reflect.UndeclaredThrowableException
   at $Proxy12.callBackMessage(Unknown Source)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvServiceImpl.knockKnock(CallBackSetCallbackConvServiceImpl.java:43)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:128)
   at 
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)

   at $Proxy11.knockKnock(Unknown Source)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvClientImpl.test8(CallBackSetCallbackConvClientImpl.java:108)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvClientImpl.run(CallBackSetCallbackConvClientImpl.java:59)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:128)
   at 
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
   at 
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
   at 
org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
   at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)

   at $Proxy10.run(Unknown Source)
   at 
org.apache.tuscany.sca.test.CallBackSetCallbackConvTestCase.testCallBackSetCallback(CallBackSetCallbackConvTestCase.java:31)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

   at java.lang.reflect.Method.invoke(Method.java:597)
   at junit.framework.TestCase.runTest(TestCase.java:168)
   at junit.framework.TestCase.runBare(TestCase.java:134)
   at junit.framework.TestResult$1.protect(TestResult.java:110)
   at junit.framework.TestResult.runProtected(TestResult.java:128)
   at junit.framework.TestResult.run(TestResult.java:113)
   at junit.framework.TestCase.run(TestCase.java:124)
   at junit.framework.TestSuite.runTest(TestSuite.java:232)
   at junit.framework.TestSuite.run(TestSuite.java:227)
   at 
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35)
   at 
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
   at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138)
   at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:125)

   at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25

Test failure: org.apache.tuscany.sca.vtest.javaapi.apis.callablereference.CallableReferenceTestCase.testGetConversation()

2008-06-11 Thread Raymond Feng

Hi,

Do any of you see this failure too?

Thanks,
Raymond

org.apache.tuscany.sca.vtest.javaapi.apis.callablereference.CallableReferenceTestCase.testGetConversation()

java.lang.AssertionError: 
 at org.junit.Assert.fail(Assert.java:69)
 at org.junit.Assert.assertTrue(Assert.java:32)
 at org.junit.Assert.assertNull(Assert.java:256)
 at org.junit.Assert.assertNull(Assert.java:265)
 at 
org.apache.tuscany.sca.vtest.javaapi.apis.callablereference.impl.BComponentImpl.testNullConversation(BComponentImpl.java:67)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:133)
 at 
org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
 at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
 at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
 at $Proxy14.testNullConversation(Unknown Source)
 at 
org.apache.tuscany.sca.vtest.javaapi.apis.callablereference.CallableReferenceTestCase.testGetConversation(CallableReferenceTestCase.java:103)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
 at 
org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
 at 
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
 at 
org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
 at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
 at 
org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
 at 
org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
 at 
org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
 at 
org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
 at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
 at 
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38)
 at 
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
 at 
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)

Re: GSoC Project - CORBA Support for Apache Tuscany

2008-06-11 Thread Raymond Feng


Hi, Wojtek.

Please see my comments inline.

Thanks,
Raymond
--
From: Wojtek Janiszewski [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 11:55 AM
To: tuscany-dev@ws.apache.org
Subject: Re: GSoC Project - CORBA Support for Apache Tuscany


Hi,
I understand you mean to look at generated classes to determine
Java/CORBA mapping. I followed case A, using existing IDL file:
http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/binding-corba/src/test/resources/general_tests.idl
and focused on interface TestObject. Generated classes are in:
http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/binding-corba/src/test/java/org/apache/tuscany/sca/binding/corba/testing/generated/

Example 1.
Java interface for TestObject implements TestObjectOperations,
org.omg.CORBA.Object, org.omg.CORBA.portable.IDLEntity. This means that
user should define this interface using CORBA API types. This is what
you mean?


To access an existing CORBA service with general_tests.idl, I should be able 
to use TestObject interface generated from the IDL in my SCA reference 
with binding.corba. The CORBA reference binding invoker should be able to 
marshal/marshal the data from the interface.


Another case is that Java2IDL compliant java interface (for example, the 
remote interfaces for EJB). We already have support in the binding.ejb 
module.




Example 2.
Operation:
SomeStruct setStruct(inout SomeStruct arg)
for interface TestObject uses SomeStructHolder (for passing INOUT 
argument) which implements
org.omg.CORBA.portable.Streamable. SomeStructHolder contains SomeStruct as 
a structure representation. Again, SomeStruct uses CORBA API interface - 
it implements org.omg.CORBA.portable.IDLEntity. In this case SomeStruct 
was meant to be INOUT argument, so it uses

SomeStructHolder. If SomeStruct would be declared as OUT, then again
SomeStructHolder would be used, but little different application logic
would be used - argument wouldn't be sent, but only retrieved after
operation invocation (this remaining logic is generated in stubs
and skeletons - so it's outside generated interface). This means, that
user using holders  the same way as in the generated style cannot tell
to the binding reference whether the modifier is INOUT or OUT.
This is one example of some real constraints which blocks using Java
interface hierarchy the same way as generated from idlj compiler.



OK. My understanding is that the generated java interface doesn't catch all 
the information from the IDL because some of them are in the generated 
stubs/skeletons. We probably need to decide what's the best default here. 
For example, for the Holder type, we will default to INOUT.


Another perspective is that for SCA remotable interfaces, the data exchange 
semantics is pass-by-value. In the case that @AllowsPassByReference is used, 
it only means the data is safe to pass by reference and it does NOT mandate 
pass-by-reference. So we can perfectly argue that the binding.corba doesn't 
support the INOUT and OUT arguments.



Thanks,
Wojtek

Raymond Feng wrote:

Hi,

There are two specifications in these areas.

1) Java2IDL: http://www.omg.org/docs/formal/08-01-14.pdf
2) IDL2Java: http://www.omg.org/docs/formal/08-01-11.pdf

Let's try to use a few scenarios to help us understand what rules should 
be applied.


Case A: There is an existing CORBA service (Java or C++) with IDL. Now we 
want to consume it using SCA.


Here is what I would do:
a) Run idl2java to generate a java interface (ignoring other stubs and 
skeletons) from the IDL.
b) Declare a SCA reference with binding.corba and set the interface to 
the one generated from a)
c) The Tuscany corba invoker should be able to create a request stream 
for input args and parse the response to get the return value.


The corba invoker needs to find the corba operation name from the java 
method and know how to marshal/unmarshal the parameters/return value.


Case B: We have a SCA component and we want to expose it as a CORBA 
service.


The corba service binding listener will have to unpack/pack data from the 
ServerRequest. Let's assume the component service interface is defined in 
java, then we need to follow the Java2IDL spec so that we handle the java 
parameters/return value following the CORBA IDL rules.


Ideally, the exposed CORBA service would behave as it has an IDL 
generated from rmic -idl java_interface.


Thanks,
Raymond

[snip]


Hi,
I recently submitted some code, which helps invoking remote objects. 
Mechanism for invoking remote CORBA objects is determining operation 
arguments types by Java types and I'm not sure that Java to CORBA 
mapping model I proposed is OK.


There is quite nice description of Java to CORBA mapping under [1]. It 
shows how idlj compiler creates Java structure basing on idl file and I 
believe we shouldn't precisely follow those rules and try to make them 
as simple as possible. Am I right?


1. Structures

Re: GSoC Project - CORBA Support for Apache Tuscany

2008-06-11 Thread Raymond Feng

To map CORBA exceptions (object id) to java exceptions, we can follow the 
logic in org.apache.tuscany.sca.binding.ejb.util.EJBHandler.java:


} catch (ApplicationException ex) {
   in = (InputStream)ex.getInputStream();
   try {
   org.apache.tuscany.sca.binding.ejb.corba.Java2IDLUtil.throwException(methodInfo.getMethod(), 
in);

   return null;
   } catch (Throwable e) {
   throw new RemoteException(e.getMessage(), e);
   }
   } catch (RemarshalException ex) {
   return invokeRemoteCORBACall(stub, methodName, args);
   } finally {
   stub._releaseReply(in);
   }
   } catch (SystemException ex) {
   throw Util.mapSystemException(ex);
   }

Please note 
org.apache.tuscany.sca.binding.ejb.corba.Java2IDLUtil.throwException maps 
the object id to a declared java exception.


Thanks,
Raymond
--
From: Wojtek Janiszewski [EMAIL PROTECTED]
Sent: Sunday, June 08, 2008 6:50 PM
To: tuscany-dev@ws.apache.org
Subject: Re: GSoC Project - CORBA Support for Apache Tuscany


Hi,
I've gathered all current/past issues regarding project on wiki page: 
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/CORBA+reference+binding+features%2C+bugs%2C+issues

Comments are always welcome.

Thanks,
Wojtek

Wojtek Janiszewski wrote:

Wojtek Janiszewski wrote:

Simon Nash wrote:

One comment inline.

  Simon
6. If CORBA objects operation argument is object reference, then 
user should provide object which was previously obtained from 
binding or other CORBA object. User cannot use users-side object as 
an argument.




Yes. Let's don't worry object reference too much at this point. We 
are in the SOA world instead of distributed object :-).



This is OK if we are exposing a SCA service via CORBA.  If we are using
SCA to invoke existing CORBA services that expect object references
to be passed, we will need to come up with an approach for handling 
them.


I'd suggest that we start first with exposing SCA services via CORBA
as this seems to be the simplest and most useful form of integration.


Unfortunately I started earlier with reference bindings - even submitted 
a patch today.


My thoughts for object references are that after obtaining some remote 
reference, it will be enhanced by cglib and connected to users declared 
interface. By enhancing I mean interception of methods invocations and 
adding dynamic CORBA invocations. Such enhanced object could be 
recognizable by dynamic invocation mechanism, and it could be passed 
while invoking operations on remote objects.


In this solution we would have two types of CORBA objects - ones that 
were intentionally declared, and ones that were obtained from roots, and 
which are transparent. It's maybe kind of out of control by Tuscany 
runtime, but is there any other way to obtain and use CORBA references 
which are not registered in name services?


Thanks,
Wojtek



Hi,
I recently submitted some code, which helps invoking remote objects. 
Mechanism for invoking remote CORBA objects is determining operation 
arguments types by Java types and I'm not sure that Java to CORBA mapping 
model I proposed is OK.


There is quite nice description of Java to CORBA mapping under [1]. It 
shows how idlj compiler creates Java structure basing on idl file and I 
believe we shouldn't precisely follow those rules and try to make them as 
simple as possible. Am I right?


1. Structures
I proposed that CORBA structures will be Java classes, with public fields 
and no get/set methods. So every class field is member for CORBA 
structure. Or maybe we should map JavaBean classes to CORBA structures?


2. Sequences and arrays
Sequences and arrays can be mapped to Java by arrays or lists. 
Unfortunately both CORBA types behaves bit different, additionally CORBA 
arrays have fixed length so there should be possibility to distinguish 
those types somehow. For now on I cannot find any other solution, but 
annotating arrays with it's target length. Any opinions?


3. Arguments with inout/out modifiers
In CORBA, operation argument value can be changed. As we know Java 
supports passing arguments by values only, so update on argument is not 
possible. Such was solved in Java by wrapping arguments in holder 
classes, ie:


public class IntHolder {
public int value;
}

This means if user wants to get his argument updated he needs to create 
argument in holder class, which could be tough (maybe there are low-level 
techniques which allows to manipulate such arguments?).


I know I should provide some method to recognize if users class is holder 
for inout/out argument:

a. annotation
b. by implementing interface, ie:

public interface Holder {
void setValue(Object value);
Object getValue();
}

Or maybe there is some other solution? Which one should I choose?

I'll appreciate any comments.

Re: Good practice for disabling/ignoring failing test cases

2008-06-11 Thread Raymond Feng

I think weekly report makes sense. When we try to cut a release, we would 
like to see the reports too.

Thanks,
Raymond
--
From: Luciano Resende [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 2:49 PM
To: tuscany-dev@ws.apache.org
Subject: Re: Good practice for disabling/ignoring failing test cases

+1 for using this pattern to disable/ignore tests that are failing.

How about also running the script in an automated fashion and sending
an e-mail to the list with the results ? What would be a good interval
for running the script ?

On Wed, Jun 11, 2008 at 1:03 PM, Kevin Williams [EMAIL PROTECTED] 
wrote:

The vtest contributors get credit for this pattern! :-)  We also have
a Ruby script that scans the test source and, among other things,
lists ignored tests and the associated blocking Jiras.

On Wed, Jun 11, 2008 at 11:49 AM, Simon Laws [EMAIL PROTECTED] 
wrote:
On Wed, Jun 11, 2008 at 6:43 PM, Vamsavardhana Reddy 
[EMAIL PROTECTED]

wrote:

Thanks Raymond for pointing this out.  We never used this strategy in
Geronimo (infact, I have never put any JIRA number in any of the source
files other that Release Notes may be).  I have come across this in 
Tuscany
source code and have been following it consistently from then on. 
Should

give credit to who ever started this in Tuscany :)

++Vamsi

On Wed, Jun 11, 2008 at 11:02 PM, Raymond Feng [EMAIL PROTECTED]
wrote:

 Hi,

 I see Vamsi uses the following strategy to disable failing unit test
cases.

 @Test
 @Ignore(TUSCANY-) // Ignore the test case due to JIRA 
 TUSCANY-

 public void testMySrtuff() {
 }

 I think it's a very good practice we should follow to maintain a 
 clean

 build while keep track of the ignored failing test cases with JIRAs.

 Thanks,
 Raymond

+1 good idea

Simon

--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

Re: Tracking Tuscany extensions, was: Distribution zips and what they contain, was: SCA runtimes

2008-06-11 Thread Raymond Feng


Hi,

There are a few patterns we use to determine if a maven module is required. 
Let's take the contribution stuff as an example.


1) contribution contains the interfaces for the contribution model and 
default implementation classes, SPIs and extension points
2) contribution-xml deals with the reading/writing the xml document for the 
sca-contribution.xml
3) contribution-java, contribution-namspace, contribution-resource deal with 
a specific perspective of the contribution, for example, namespace, java, 
resource
4) contribution-osgi, contribution-groovy support specific packaging schemes 
of the SCA contributions.


Please note there is a tree-like dependency graph. I don't think it makes 
sense to merge the siblings into one module. Since an ancestor (for example 
contribution) are shared by mulitple children (-xml, -osgi, etc), it also 
not desirable to merge the common ancestor with other modules.


For databinding related modules, we have a similar strcuture:
1) databinding: The base model, SPIs and transformers for various XML 
technologies
2) databinding-jaxb, databinding-sdo, databinding-axiom, ... The individual 
databinding technologies
3) core-databinding: A set of hook code that leverage the databinding 
framework in the invocation chains (data transformation interceptors)


We can use 1 as the data transformation utility in binding/implementation or 
even 3rd party code without 3. We can also pick one or more modules from 2.


What I'm trying to point out is that our maven module structure reflects the 
nature of the feature units and dependencies fairly well. IMO, each module 
maps well into an OSGi bundle. IMHO, both the maven module and OSGi bundle 
follow the same principles and the results should be consistent.


Thanks,
Raymond

--
From: Simon Nash [EMAIL PROTECTED]
Sent: Wednesday, June 11, 2008 12:33 PM
To: tuscany-dev@ws.apache.org
Subject: Re: Tracking Tuscany extensions, was: Distribution zips and what 
they contain, was: SCA runtimes



Comments inline.

  Simon

Rajini Sivaram wrote:

On 6/10/08, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:

ant elder wrote:


On Tue, Jun 10, 2008 at 5:37 PM, Jean-Sebastien Delfino 
[EMAIL PROTECTED] wrote:

Simon Nash wrote:

ant elder wrote:

On Tue, Jun 10, 2008 at 3:02 AM, Jean-Sebastien Delfino 

[EMAIL PROTECTED] wrote:

Jean-Sebastien Delfino wrote:
I'd like to discuss the following: What distro Zips are we 
building

and
what do they contain?

I think we could improve our distro scheme to provide:
- smaller packages
- easier for people to find what they need

I was thinking about the following binary distro zips:

- tuscany-core.zip - The base that everybody needs.
 core assembly model and runtime
 Java APIs, Java components

- tuscany-web.zip - For WS and Web developers
 WS binding, Web 2.0 bindings, Scripting components, Widget
components

- tuscany-jee.zip - For JEE app integration
 EJB, RMI and JMS bindings, Spring components

- tuscany-process.zip - For process development
 BPEL and XQuery components

- tuscany-all.zip - all of the above

Note that I'm not trying to tackle release cycles and the 
potential

for
releasing the above zips independently in this discussion and I'm

assuming

that we release all of the above together.

I'm also assuming that the relevant samples are included in each 
zip.


 This email was from 1/22/08, generated a lot of discussion for 
about

3


weeks, lots of opinions, no conclusion, no commits :)


No commits as we haven't found much consensus yet.

 I still think the same as what I had posted then, plus additional
ideas:

- Use OSGi exports/imports to export clean SPIs, hide internals, 
and


refine

the contents of the distros and their dependencies.
Disclaimer - Please don't get me wrong I'm not saying that one 
distro

==

one

OSGi bundle, as I've already said several times on the list that the
big-OSGi-bundle approach didn't make sense to me :) I just think 
that

declaring and enforcing clean dependencies using OSGi will help us
refine
the contents of each distro.

 The term enforcing seems to suggest that there might be an OSGi


dependency for the Tuscany runtime.  I don't know if this was

intended.  I think the right approach is to have a Tuscany+OSGi
runtime (as we are building in itest\osgi-tuscany) which would
actually do enforcement, and a non-OSGi Tuscany runtime in which
the exports/imports are present in the jars but not enforced.

Huh, Yes sure, we'd enforce OSGi rules when running in an OSGi

environment...


What would be the granularity of these OSGi bundles?  If the bundles

are the current maven modules, I think we will find a number of
classes that need to be exported even though these classes are not
considered part of the SPI or API that the module provides.
To resolve this I see the following options:
 a) Export more than we really believe is correct.  This
  leaves us in the current unsatisfactory position of exposing

Re: Databinding tests for array of java.net.URI

2008-06-10 Thread Raymond Feng

I think it's a problem in the test case. The resolve() cannot work with 
http://abc (which abc is treated as a host name). I changed it to 
http://abc/, then it works well.


You can simply create a test case using URIs only without Tuscany in the 
picture.


Thanks,
Raymond
--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 2:20 AM
To: tuscany-dev@ws.apache.org
Subject: Databinding tests for array of java.net.URI


I am using the following URI's in my test:
   URI[] uris = new URI[3];
   uris[0] = URI.create(a/b/c);
   uris[1] = URI.create(http://abc;);
   uris[2] = URI.create(ftp://a/b;);

The return value from the service method is inputUri.resolve(uri).

One service method takes an uri as input and returns the changed uri as
given above.  Another method takes an array of uri as input and returns an
array of uri where each element in the returned array contains an uri 
which

is changed as given above.  The remotable service invoked over binding.sca
is able to provide expected return value for uris[1] with the method that
takes URI as argument.  But, with the method that takes URI array as
argument, the return value for uris[1] is not as expected.

In the failing case the input uri has (authority = abc, host = abc, 
path
= ) , expected uri has (authority = abc, host = abc, path = uri) 
and

the uri returned from the service method has (authority=abcuri, host =
abcuri, path = ).  I have verified through the debugger that the array
being returned by the service method has the second element as expected.
But, once the array is returned to the caller after data transformations,
the element is changed.  There definitely is a problem with the data
transformation.

Re: Databinding tests for array of java.net.URI

2008-06-10 Thread Raymond Feng


Hi,

Here is a simple test case to prove my point:

public class URITestCase {
   @Test
   public void testURI() {
   URI uri = URI.create(http://abc;);
   URI uri1 = uri.resolve(uri);
   URI uri2 = URI.create(http://abcxyz;);
   Assert.assertEquals(uri1, uri2);
   }
}

The Assert will fail, even though the uri1.toString() equals to 
uri2.toString().


Thanks,
Raymond

--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 8:26 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Databinding tests for array of java.net.URI


Hi Raymond,

Whether or not resolve() works with http://abc, I have a URI created as
URI.create(http://abc;).resolve(xyz) and java does not complain about
this URI object .  The current problem can be restated that this URI 
object

can not be passed in an array of URI objects back and forth between client
and service component in case of a remotable service.  The URI object can 
be

passed between the client and service components properly when the service
method takes an URI as argument.

++Vamsi

On Tue, Jun 10, 2008 at 8:33 PM, Raymond Feng [EMAIL PROTECTED] wrote:


I think it's a problem in the test case. The resolve() cannot work with
http://abc (which abc is treated as a host name). I changed it to
http://abc/, then it works well.

You can simply create a test case using URIs only without Tuscany in the
picture.

Thanks,
Raymond
--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 2:20 AM
To: tuscany-dev@ws.apache.org
Subject: Databinding tests for array of java.net.URI


 I am using the following URI's in my test:

  URI[] uris = new URI[3];
  uris[0] = URI.create(a/b/c);
  uris[1] = URI.create(http://abc;);
  uris[2] = URI.create(ftp://a/b;);

The return value from the service method is inputUri.resolve(uri).

One service method takes an uri as input and returns the changed uri as
given above.  Another method takes an array of uri as input and returns 
an

array of uri where each element in the returned array contains an uri
which
is changed as given above.  The remotable service invoked over 
binding.sca
is able to provide expected return value for uris[1] with the method 
that

takes URI as argument.  But, with the method that takes URI array as
argument, the return value for uris[1] is not as expected.

In the failing case the input uri has (authority = abc, host = abc,
path
= ) , expected uri has (authority = abc, host = abc, path = uri)
and
the uri returned from the service method has (authority=abcuri, host =
abcuri, path = ).  I have verified through the debugger that the 
array

being returned by the service method has the second element as expected.
But, once the array is returned to the caller after data 
transformations,

the element is changed.  There definitely is a problem with the data
transformation.

[jira] Resolved: (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
 ]

Raymond Feng resolved TUSCANY-2377.
---

Resolution: Fixed

Test case patch applied and the problem is fixed. 

 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
Reporter: Scott Kurz
Assignee: Raymond Feng
 Attachments: 2377.itest.example.diff, 2377.itest.example.diff


 I'm having trouble reading a complex property from a file pointed to via the 
 property @file attr. 
 I'm using a JAXB to hold the prop value in my Java impl, but in looking at 
 this briefly in the debugger I think the problem might be in the DOM object 
 before it is ever transformed into a JAXB (in my case).
 I think the problem is in the code:
 public class JavaPropertyValueObjectFactory
 public ObjectFactory createValueFactory(Property property, Object 
 propertyValue, Class javaType) {
 ... 
 } else {
 if (isSimpleType) {
   
 } else {
 ListNode nodes = getComplexPropertyValues(doc);
 Object value = null;
 if (!nodes.isEmpty()) {
 value = nodes.get(0);
 }
 return new ObjectFactoryImpl(property, value, isSimpleType, 
 javaType);
 }
 I'm not skilled with DOM... but I think this code is expecting a wrapper 
 around the real property value, which is why we do a 
 nodes.get(0) to get the first child.   
 I think this wrapper must be there in the case that the property value is set 
 inline in the SCDL or via a Composite property definition, but I think 
 there's a wrapper missing in the case that we use @file, in which case we get 
 a raw document.
 I'll attach a patch of an existing itest adding a couple tests to to show an 
 example.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (TUSCANY-2229) Got WARNING if @Context is used to annotate a setter method


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2229:
-

Assignee: Raymond Feng

 Got WARNING if @Context is used to annotate a setter method
 ---

 Key: TUSCANY-2229
 URL: https://issues.apache.org/jira/browse/TUSCANY-2229
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Gilbert Kwan
Assignee: Raymond Feng
Priority: Minor
 Fix For: Java-SCA-Next


 I got following warnings when @Context is used to annotate a setter method:
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/requestContext
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/componentContext
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/requestContext
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/componentContext
 Implementation Class:
 =
 public RequestContext requestContext;
 public ComponentContext componentContext;
 @Context
 public void setComponentContext(ComponentContext componentContext) {
this.componentContext = componentContext;
 }
 @Context
 public void setRequestContext(RequestContext requestContext) {
this.requestContext = requestContext;
 }
 Composite:
 =
 composite xmlns=http://www.osoa.org/xmlns/sca/1.0; 
targetNamespace=http://java-api-tests;
name=AB-Composite
component name=BComponent
implementation.java
 class=org.apache.tuscany.sca.vtest.javaapi.impl.BServiceImpl/
/component
 /composite
 If @Context is used to annotate a class field, there is no warning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TUSCANY-2229) Got WARNING if @Context is used to annotate a setter method


[ 
https://issues.apache.org/jira/browse/TUSCANY-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603932#action_12603932
 ] 

Raymond Feng commented on TUSCANY-2229:
---

Hi,

This is a result of declaring the two context fields as public. Tuscany takes 
them as properties. If you change them into private, then no warning is issued. 
I'll try to see if I can remove them from property list.

Thanks,
Raymond

 Got WARNING if @Context is used to annotate a setter method
 ---

 Key: TUSCANY-2229
 URL: https://issues.apache.org/jira/browse/TUSCANY-2229
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Gilbert Kwan
Priority: Minor
 Fix For: Java-SCA-Next


 I got following warnings when @Context is used to annotate a setter method:
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/requestContext
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/componentContext
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/requestContext
 Apr 15, 2008 11:45:18 AM
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1
 problem
 WARNING: No type specified on component property: BComponent/componentContext
 Implementation Class:
 =
 public RequestContext requestContext;
 public ComponentContext componentContext;
 @Context
 public void setComponentContext(ComponentContext componentContext) {
this.componentContext = componentContext;
 }
 @Context
 public void setRequestContext(RequestContext requestContext) {
this.requestContext = requestContext;
 }
 Composite:
 =
 composite xmlns=http://www.osoa.org/xmlns/sca/1.0; 
targetNamespace=http://java-api-tests;
name=AB-Composite
component name=BComponent
implementation.java
 class=org.apache.tuscany.sca.vtest.javaapi.impl.BServiceImpl/
/component
 /composite
 If @Context is used to annotate a class field, there is no warning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Tracking Tuscany extensions, was: Distribution zips and what they contain, was: SCA runtimes

2008-06-10 Thread Raymond Feng


Hi,

Please see my comments inline.

Thanks,
Raymond

[snip]
Good requirement, but I don't think that the current manifest + 
tuscany-all JAR solution is a good one (for example it mixes APIs and 
internals in the same JAR, doesn't work well with IDEs, works only for one 
big distro, requires different settings in J2SE and webapps)




IMHO, the all-in-one package pretty much defeats our modularity. For 
example, all module activators will be called even the extension won't be 
used at all. Two extension cannot have different versions of a 3rd party 
jar.



Here's what I'd like to see as a user:

- a short list of API JARs that I can add to my dev compile/build path

- a single small launcher or bootstrap JAR that takes care of 
bootstrapping the Tuscany runtime




This is similar to JEE launchClient. If I can invoke the Launcher directly 
in java, I would be happy.


- the launcher should detect the presence of installed extensions in a 
particular Tuscany installation


+1.


- as a user / app developer I should not have to know the list of JARs 
from all these extensions.


Do we expect the launcher to be smart enough to pick the right set of 
extensions based on the SCA assembly?




That's what I've been trying to do with the Node launcher and the library 
provided by the Tuscany Eclipse plugin. More work is required to get that 
vision in place (as the current launcher is still pretty rudimentary and 
only scans an installation directory for JARs).


There's a good extension registry mechanism in Eclipse Equinox [1]. It 
would allow us to rely on a robust mechanism for detecting installed 
extensions, tracking what they provide in an extension registry [2], and 
use a more user friendly syntax for registering extensions using 
plugin.xml files. If we start to integrate more with OSGi I think we 
should just use it (maybe in combination with what we currently have with 
META-INF/services for the cases where we don't use OSGi).




We can have a SPI so that different mechanism of extension discovery can be 
plugged in. I would prefer to see both OSGi and META-INF/services based 
approaches available.



[1] http://www.eclipse.org/equinox/
[2] http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.equinox.registry/

-- Sebastien

[jira] Commented: (TUSCANY-2331) Got expection where the wsdl defines an operation without input


[ 
https://issues.apache.org/jira/browse/TUSCANY-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603975#action_12603975
 ] 

Raymond Feng commented on TUSCANY-2331:
---

I got a diferent exception. It looks like that Axis2 treats the getName 
operation as an out-only MEP (in-only for client side) and assumes the 
invocation is initiated from the server side. It doesn't expect that we try to 
create a client.

java.lang.UnsupportedOperationException: The message exchange pattern (MEP) 
http://www.w3.org/ns/wsdl/in-only has not implemented the createClient method.
at 
org.apache.axis2.description.AxisOperation.createClient(AxisOperation.java:487)
at 
org.apache.axis2.client.ServiceClient.createClient(ServiceClient.java:646)
at 
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.createOperationClient(Axis2BindingInvoker.java:172)
at 
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:116)
at 
org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:94)
at 
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
at 
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
at $Proxy11.getName(Unknown Source)
at 
helloworld.HelloWorldServiceComponent.getName(HelloWorldServiceComponent.java:37)


 Got expection where the wsdl defines an operation without input
 ---

 Key: TUSCANY-2331
 URL: https://issues.apache.org/jira/browse/TUSCANY-2331
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Gilbert Kwan
 Attachments: BService.wsdl


 Got following exception in running where the wsdl defines an operation 
 without input parameter.
 java.lang.IllegalArgumentException: Pass-by-value is not supported for the 
 given object
at 
 org.apache.tuscany.sca.databinding.javabeans.JavaBeansDataBinding.copy(JavaBeansDataBinding.java:102)
at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.copy(DefaultDataBindingExtensionPoint.java:171)
at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copy(PassByValueInterceptor.java:235)
at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.copyFault(PassByValueInterceptor.java:130)
at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:115)
at 
 org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61)
at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108)
at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:286)
at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
at $Proxy7.getB1Name(Unknown Source)
at 
 org.apache.tuscany.sca.vtest.wsbinding.nowsdl.NoWsdlTestCase.testNoWsdl(NoWsdlTestCase.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at 
 org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99)
at 
 org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81)
at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at 
 org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75)
at 
 org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45)
at 
 org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.java:75)
at 
 org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:36)
at 
 org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42)
at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34)
at 
 org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52)
at 
 org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38

Re: Databinding tests for array of java.net.URI

2008-06-10 Thread Raymond Feng


What I pointed out is the following:

URI.createURI(http//abc).resolve(uri) (toString()==http://abcuri;) 
creates a non-equal instance of URI.createURI(http://abcuri;). By the 
javadoc of URI, this is violating the rules:


http://java.sun.com/j2se/1.4.2/docs/api/java/net/URI.html
Identities
For any URI u, it is always the case that
new URI(u.toString()).equals(u) .

In the test case you have, the expected is 
URI.createURI(http//abc).resolve(uri). On the server side, the impl 
method produce URI.createURI(http//abc).resolve(uri) and it get 
serialized as http://abcuri; (URI.toString()) in the XML doc. On the client 
side, the URI is unmarshalled as URI.createURI(http://abcuri;). That's why 
two instances are not equal.


Thanks,
Raymond
--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 10:47 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Databinding tests for array of java.net.URI


Raymond,

The comment junit.framework.AssertionFailedError: 
expected:http://abcuri
but was:http://abcuri I had in @Ignore in the testcase code may have 
lead

to some confusion.  I agree that uri1.equals(uri2) is not same as
uri1.toString().equals(uri2.toString()).  The issue I am trying to bring 
up,

which I guess I am unsuccessful so far, is that if I have a service method
that takes a URI and returns the same URI back, and if I invoke that
remotable service with uri1 as parameter, the value that is returned 
(say

uri3) equals uri1 (i.e. uri1.equals(uri3) is true).  If I have another
service method that takes a URI[] and returns back the same URI[] and I
invoke this method with an URI array that contains just one element uri1,
then the URI that is returned is not equal to uri1.

uri1 is creating problems when it passed to the service method as an array
element.  So, it has to be a data transformation problem.

++Vamsi

On Tue, Jun 10, 2008 at 9:23 PM, Raymond Feng [EMAIL PROTECTED] wrote:


Hi,

Here is a simple test case to prove my point:

public class URITestCase {
  @Test
  public void testURI() {
  URI uri = URI.create(http://abc;);
  URI uri1 = uri.resolve(uri);
  URI uri2 = URI.create(http://abcxyz;);
  Assert.assertEquals(uri1, uri2);
  }
}

The Assert will fail, even though the uri1.toString() equals to
uri2.toString().

Thanks,
Raymond

--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 8:26 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Databinding tests for array of java.net.URI


 Hi Raymond,


Whether or not resolve() works with http://abc, I have a URI created as
URI.create(http://abc;).resolve(xyz) and java does not complain about
this URI object .  The current problem can be restated that this URI
object
can not be passed in an array of URI objects back and forth between 
client
and service component in case of a remotable service.  The URI object 
can

be
passed between the client and service components properly when the 
service

method takes an URI as argument.

++Vamsi

On Tue, Jun 10, 2008 at 8:33 PM, Raymond Feng [EMAIL PROTECTED]
wrote:

 I think it's a problem in the test case. The resolve() cannot work with

http://abc (which abc is treated as a host name). I changed it to
http://abc/, then it works well.

You can simply create a test case using URIs only without Tuscany in 
the

picture.

Thanks,
Raymond
--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Tuesday, June 10, 2008 2:20 AM
To: tuscany-dev@ws.apache.org
Subject: Databinding tests for array of java.net.URI


 I am using the following URI's in my test:


 URI[] uris = new URI[3];
 uris[0] = URI.create(a/b/c);
 uris[1] = URI.create(http://abc;);
 uris[2] = URI.create(ftp://a/b;);

The return value from the service method is inputUri.resolve(uri).

One service method takes an uri as input and returns the changed uri 
as
given above.  Another method takes an array of uri as input and 
returns

an
array of uri where each element in the returned array contains an uri
which
is changed as given above.  The remotable service invoked over
binding.sca
is able to provide expected return value for uris[1] with the method
that
takes URI as argument.  But, with the method that takes URI array as
argument, the return value for uris[1] is not as expected.

In the failing case the input uri has (authority = abc, host = 
abc,

path
= ) , expected uri has (authority = abc, host = abc, path = 
uri)

and
the uri returned from the service method has (authority=abcuri, host 
=

abcuri, path = ).  I have verified through the debugger that the
array
being returned by the service method has the second element as 
expected.

But, once the array is returned to the caller after data
transformations,
the element is changed.  There definitely is a problem with the data
transformation.

Re: GSoC Project - CORBA Support for Apache Tuscany

2008-06-10 Thread Raymond Feng


Hi,

There are two specifications in these areas.

1) Java2IDL: http://www.omg.org/docs/formal/08-01-14.pdf
2) IDL2Java: http://www.omg.org/docs/formal/08-01-11.pdf

Let's try to use a few scenarios to help us understand what rules should be 
applied.


Case A: There is an existing CORBA service (Java or C++) with IDL. Now we 
want to consume it using SCA.


Here is what I would do:
a) Run idl2java to generate a java interface (ignoring other stubs and 
skeletons) from the IDL.
b) Declare a SCA reference with binding.corba and set the interface to the 
one generated from a)
c) The Tuscany corba invoker should be able to create a request stream for 
input args and parse the response to get the return value.


The corba invoker needs to find the corba operation name from the java 
method and know how to marshal/unmarshal the parameters/return value.


Case B: We have a SCA component and we want to expose it as a CORBA service.

The corba service binding listener will have to unpack/pack data from the 
ServerRequest. Let's assume the component service interface is defined in 
java, then we need to follow the Java2IDL spec so that we handle the java 
parameters/return value following the CORBA IDL rules.


Ideally, the exposed CORBA service would behave as it has an IDL generated 
from rmic -idl java_interface.


Thanks,
Raymond

[snip]


Hi,
I recently submitted some code, which helps invoking remote objects. 
Mechanism for invoking remote CORBA objects is determining operation 
arguments types by Java types and I'm not sure that Java to CORBA mapping 
model I proposed is OK.


There is quite nice description of Java to CORBA mapping under [1]. It 
shows how idlj compiler creates Java structure basing on idl file and I 
believe we shouldn't precisely follow those rules and try to make them as 
simple as possible. Am I right?


1. Structures
I proposed that CORBA structures will be Java classes, with public fields 
and no get/set methods. So every class field is member for CORBA 
structure. Or maybe we should map JavaBean classes to CORBA structures?


2. Sequences and arrays
Sequences and arrays can be mapped to Java by arrays or lists. 
Unfortunately both CORBA types behaves bit different, additionally CORBA 
arrays have fixed length so there should be possibility to distinguish 
those types somehow. For now on I cannot find any other solution, but 
annotating arrays with it's target length. Any opinions?


3. Arguments with inout/out modifiers
In CORBA, operation argument value can be changed. As we know Java 
supports passing arguments by values only, so update on argument is not 
possible. Such was solved in Java by wrapping arguments in holder classes, 
ie:


public class IntHolder {
public int value;
}

This means if user wants to get his argument updated he needs to create 
argument in holder class, which could be tough (maybe there are low-level 
techniques which allows to manipulate such arguments?).


I know I should provide some method to recognize if users class is holder 
for inout/out argument:

a. annotation
b. by implementing interface, ie:

public interface Holder {
void setValue(Object value);
Object getValue();
}

Or maybe there is some other solution? Which one should I choose?

I'll appreciate any comments. Just ask if you need more details.

[1] - http://members.tripod.com/gsraj/corba/chapter/

Thanks,
Wojtek

Re: Tuscany support for Axis 1.4

2008-06-09 Thread Raymond Feng

+1 to move up. We can also start to take advantage of the latest versions of 
XmlSchema and AXIOM.

Thanks,
Raymond
--
From: ant elder [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 2:17 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Tuscany support for Axis 1.4

On Wed, May 14, 2008 at 1:12 PM, Lou Amodeo [EMAIL PROTECTED] wrote:

Is there a plan for Tuscany to support Axis2 1.4?

Axis2 1.4 and the associated wss4j and rampart releases for 1.4 are  all 
out

and available in the Maven repositories now. I've still a couple of issues
to resolve to get everything in the build working with 1.4 but hope to 
have

those fixed in the next day or 2 so would like to move up to 1.4 then

  ...ant

Re: [PROPOSAL] Disable unused domain modules

2008-06-09 Thread Raymond Feng

+1 to delete them to avoid further confusions.

Thanks,
Raymond

--
From: ant elder [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 2:04 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [PROPOSAL] Disable unused domain modules

On Mon, Jun 9, 2008 at 9:56 AM, Simon Laws [EMAIL PROTECTED]
wrote:

Hi All

Now that the new domain manager app is starting to settle down a bit I'd
like to disable the unused domain modules from the main build. They 
are...

modules/domain
modules/domain-api
modules/domain-xml
modules/node
modules/node-api
modules/node-xml

I have removed these from most of the places they were previously
referenced
with the exception of a couple of samples/itests. I propose that we break
these final dependencies and remove these modules from the main build and
from the distribution builds. The module themselves can remain in place 
for

a little while longer until we are happy the builds are stable and then I
think we can move them out to sandbox/old.

These modules are now replaced by a range of domain and node features
spread
across various modules. These are the ones I am aware of:

modules/domain-manager - represents the configured domain and provides a
web
interface to users
modules/endpoint - a plug point for late reference resolution (we don't
actually support late reference resolution yet in our runtimes.The domain
assumes that wires are known and static)
modules/implementation-node - the model that represents a configured node
in
the domain. Used to provide default binding configuration and relate
composites to nodes
modules/implementation-node-runtime
modules/implementation-node-xml
modules/node2-api - the new node implementation that reads its
configuration
from the command line or directly from the domain-manager
modules/node2-impl
modules/node2-launcher
modules/node2-launcher-webbapp
modules/runtime
modules/runtime-tomcat - deep integration with tomcat that allows 
composite

application wars to be deployed which don't contain Tuscany jars (under
development)
modules/workspace - the code behind the domain-manager contribution
processing.
modules/workspace-impl
modules/workspace-xml

Regards

Simon

+1 to removing the old modules.

I'd prefer they are deleted from the modules folder than left there just 
not

part of the build. They'll always be there in SVN history if they are ever
needed again for something.

  ...ant

Re: [NOTICE] Scott Kurz voted as Tuscany committer

2008-06-09 Thread Raymond Feng

Congratulations, Scott. 

Thanks,
Raymond

--
From: ant elder [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 12:48 AM
To: tuscany-dev tuscany-dev@ws.apache.org
Subject: [NOTICE] Scott Kurz voted as Tuscany committer

The Tuscany PMC has voted for Scott Kurz to become a Tuscany committer.

Welcome Scott!

  ...ant

Re: Why the QName of service be changed?

2008-06-09 Thread Raymond Feng

The trailing / is following the JAXWS java package to XML namespace mapping 
rule.


Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 9:06 AM
To: tuscany-dev@ws.apache.org
Subject: Why the QName of service be changed?


When I used 659139 build, my service qname was
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org}BService
When I used recent build 665707, my service qname was changed to
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BServiceService

Why?

Gilbert

Re: Why the QName of service be changed?

2008-06-09 Thread Raymond Feng


Hi,

I was probably confused. When you say service,  do you mean SCA service or 
the service element in the generated WSDL? My answer was for the later case.


Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 9:37 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Why the QName of service be changed?


Are you talking about the WS Binding Spec v1.0 line 273?
Base System URI for HTTP / Component Name / Service Name

If yes, 
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BServiceService

still did not fit
If no, would you point me where the spec defines it?

Thanks
Gilbert


On Mon, Jun 9, 2008 at 12:23 PM, Raymond Feng [EMAIL PROTECTED] wrote:
The trailing / is following the JAXWS java package to XML namespace 
mapping

rule.

Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 9:06 AM
To: tuscany-dev@ws.apache.org
Subject: Why the QName of service be changed?


When I used 659139 build, my service qname was
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org}BService
When I used recent build 665707, my service qname was changed to

{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BServiceService

Why?

Gilbert

Re: Why the QName of service be changed?

2008-06-09 Thread Raymond Feng

OK. I don't think the service QName in the generated WSDL has anything to do 
with the SCA service name. The WSDL service name is probably derived from 
the java interface package name and class name (@interface of 
interface.java).


BTW, why do you care the WSDL service qname? Are you trying to find the 
correct service for the WS client?


Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 10:10 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Why the QName of service be changed?


I defined following in my composite

component name=BComponent
   implementation.java
class=org.apache.tuscany.sca.vtest.wsbinding.nowsdl.soapversion.impl.BServiceImpl/
   service name=BService
   interface.java
interface=org.apache.tuscany.sca.vtest.wsbinding.nowsdl.soapversion.BService/
   binding.ws/
   /service
/component

I used WSDLReader to read the generated WSDL, such as
Definition wsdl = wsdlReader.readWSDL(uri + ?wsdl);

then got the services by wsdl.getServices(). For each service, I got
qname by s.getQName().

It was returned
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BServiceService

For old build, I got
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BService

Which is the proper qname?

Hope the information may help to understand my question.

Thanks
Gilbert





On Mon, Jun 9, 2008 at 1:01 PM, Raymond Feng [EMAIL PROTECTED] wrote:

Hi,

I was probably confused. When you say service,  do you mean SCA service 
or
the service element in the generated WSDL? My answer was for the later 
case.


Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 9:37 AM
To: tuscany-dev@ws.apache.org
Subject: Re: Why the QName of service be changed?


Are you talking about the WS Binding Spec v1.0 line 273?
   Base System URI for HTTP / Component Name / Service Name

If yes,
{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BServiceService
still did not fit
If no, would you point me where the spec defines it?

Thanks
Gilbert


On Mon, Jun 9, 2008 at 12:23 PM, Raymond Feng [EMAIL PROTECTED] 
wrote:


The trailing / is following the JAXWS java package to XML namespace
mapping
rule.

Thanks,
Raymond
--
From: Gilbert Kwan [EMAIL PROTECTED]
Sent: Monday, June 09, 2008 9:06 AM
To: tuscany-dev@ws.apache.org
Subject: Why the QName of service be changed?


When I used 659139 build, my service qname was

{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org}BService
When I used recent build 665707, my service qname was changed to


{http://soapversion.nowsdl.wsbinding.vtest.sca.tuscany.apache.org/}BServiceService

Why?

Gilbert

Re: Build error in sca\itest\properties

2008-06-08 Thread Raymond Feng

I fixed it under r664614. When I applied the patch, I forgot to adjust the 
dependencies as the Eclipse compiled it.


Thanks,
Raymond

--
From: Vamsavardhana Reddy [EMAIL PROTECTED]
Sent: Sunday, June 08, 2008 1:47 AM
To: tuscany-dev@ws.apache.org
Subject: Build error in sca\itest\properties


I am seeing a compilation failure in sca\itest\properties.  Is anyone else
hitting this error?  Command output given below.

[INFO] Scanning for projects...
[INFO]

[INFO] Building Apache Tuscany SCA Properties Integration Tests
[INFO]task-segment: [clean, install]
[INFO]

[INFO] [clean:clean]
[INFO] Deleting directory D:\T\java\sca\itest\properties\target
[INFO] [tuscany-sdo:generate {execution: generate-customer-sdo}]
[INFO] Generating SDO interfaces from
D:\T\java\sca\itest\properties\src\main\resources\customer.xsd

 Generating code
 Generating packages
 Generating package SdoPackageImpl
 Generating Java interface com.example.customer.sdo.SdoFactory
 Generating /TargetProject/com/example/customer/sdo/SdoFactory.java
 Generating Java class com.example.customer.sdo.impl.SdoFactoryImpl
 Generating

/TargetProject/com/example/customer/sdo/impl/SdoFactoryImpl.java

 Generating Customer
 Generating Java interface com.example.customer.sdo.Customer
 Generating /TargetProject/com/example/customer/sdo/Customer.java
 Generating Java class com.example.customer.sdo.impl.CustomerImpl
 Generating

/TargetProject/com/example/customer/sdo/impl/CustomerImpl.java
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 26 source files to
D:\T\java\sca\itest\properties\target\classes
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Compilation failure

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[29,22]
package javax.xml.bind does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[30,33]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[31,33]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[31,33]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[32,33]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[33,33]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[34,33]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[74,11]
cannot find symbol
symbol  : class JAXBElement
location: class test.jaxb.props.ObjectFactory

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[49,1]
cannot find symbol
symbol: class XmlRegistry
@XmlRegistry

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[57,1]
cannot find symbol
symbol: class XmlAccessorType
@XmlAccessorType(XmlAccessType.FIELD)

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[58,1]
cannot find symbol
symbol: class XmlType
@XmlType(name = ReturnCodeProperties, namespace = 
http://test.sca.jaxb/rcprops;, propOrder = {

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[73,5]
cannot find symbol
symbol  : class XmlElementDecl
location: class test.jaxb.props.ObjectFactory

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[64,5]
cannot find symbol
symbol  : class XmlElement
location: class test.jaxb.props.ReturnCodeProperties

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ReturnCodeProperties.java:[66,5]
cannot find symbol
symbol  : class XmlElement
location: class test.jaxb.props.ReturnCodeProperties

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\package-info.java:[26,26]
package javax.xml.bind.annotation does not exist

D:\T\java\sca\itest\properties\src\main\java\test\jaxb\props\ObjectFactory.java:[75,19]
cannot find symbol
symbol  : class JAXBElement
location: class test.jaxb.props.ObjectFactory


[INFO]

[INFO] For more information, run Maven with the -e switch
[INFO]

[INFO] Total time: 6 seconds
[INFO] Finished at: Sun Jun 08 14:15:34 IST 2008
[INFO] Final

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

2008-06-07 Thread Raymond Feng (JIRA)


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2377:
-

Assignee: Raymond Feng

 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
Reporter: Scott Kurz
Assignee: Raymond Feng
 Attachments: 2377.itest.example.diff, 2377.itest.example.diff


 I'm having trouble reading a complex property from a file pointed to via the 
 property @file attr. 
 I'm using a JAXB to hold the prop value in my Java impl, but in looking at 
 this briefly in the debugger I think the problem might be in the DOM object 
 before it is ever transformed into a JAXB (in my case).
 I think the problem is in the code:
 public class JavaPropertyValueObjectFactory
 public ObjectFactory createValueFactory(Property property, Object 
 propertyValue, Class javaType) {
 ... 
 } else {
 if (isSimpleType) {
   
 } else {
 ListNode nodes = getComplexPropertyValues(doc);
 Object value = null;
 if (!nodes.isEmpty()) {
 value = nodes.get(0);
 }
 return new ObjectFactoryImpl(property, value, isSimpleType, 
 javaType);
 }
 I'm not skilled with DOM... but I think this code is expecting a wrapper 
 around the real property value, which is why we do a 
 nodes.get(0) to get the first child.   
 I think this wrapper must be there in the case that the property value is set 
 inline in the SCDL or via a Composite property definition, but I think 
 there's a wrapper missing in the case that we use @file, in which case we get 
 a raw document.
 I'll attach a patch of an existing itest adding a couple tests to to show an 
 example.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (TUSCANY-2371) Databinding tests for StandardTypes, array of StandardTypes


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2371:
-

Assignee: Raymond Feng  (was: Vamsavardhana Reddy)

 Databinding tests for StandardTypes, array of StandardTypes
 ---

 Key: TUSCANY-2371
 URL: https://issues.apache.org/jira/browse/TUSCANY-2371
 Project: Tuscany
  Issue Type: Test
  Components: Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2371.patch


 Databinding itests for StandardTypes and array of StandardTypes.  Local and 
 remotable service.  See [1].
 JAXB Spec v2.1 - Sec 8.5.2Java Standard Classes:
 java.lang.String
 java.math.BigInteger
 java.math.BigDecimal
 java.util.Calendar
 java.util.Date
 javax.xml.namespace.QName
 java.net.URI
 javax.xml.datatype.XMLGregorianCalendar
 javax.xml.datatype.Duration
 java.lang.Object
 java.awt.Image
 javax.activation.DataHandler
 javax.xml.transform.Source
 java.util.UUID
 [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Databinding+Scope

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (TUSCANY-2361) Databinding tests for primitives and primitive arrays - local service, pass-by-value tests


 [ 
https://issues.apache.org/jira/browse/TUSCANY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raymond Feng reassigned TUSCANY-2361:
-

Assignee: Raymond Feng

 Databinding tests for primitives and primitive arrays - local service, 
 pass-by-value tests
 --

 Key: TUSCANY-2361
 URL: https://issues.apache.org/jira/browse/TUSCANY-2361
 Project: Tuscany
  Issue Type: Test
  Components: Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2361.patch


 TUSCANY-2350 added databinding tests for primitives and primitive arrays 
 using a remotable service.  The same tests need to be done for a local 
 service too (see [1]).  Also, the pass-by-value semantics does not seem to be 
 working for byte array.  It is a good idea to add tests for pass-by-value for 
 byte array and arrays of other primitive types.
 [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Databinding+Scope

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TUSCANY-2371) Databinding tests for StandardTypes, array of StandardTypes


[ 
https://issues.apache.org/jira/browse/TUSCANY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12603160#action_12603160
 ] 

Raymond Feng commented on TUSCANY-2371:
---

I applied the 1st patch and fixed a bunch of the issues.

 Databinding tests for StandardTypes, array of StandardTypes
 ---

 Key: TUSCANY-2371
 URL: https://issues.apache.org/jira/browse/TUSCANY-2371
 Project: Tuscany
  Issue Type: Test
  Components: Java SCA Integration Tests
Affects Versions: Java-SCA-Next
Reporter: Vamsavardhana Reddy
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2371.patch


 Databinding itests for StandardTypes and array of StandardTypes.  Local and 
 remotable service.  See [1].
 JAXB Spec v2.1 - Sec 8.5.2Java Standard Classes:
 java.lang.String
 java.math.BigInteger
 java.math.BigDecimal
 java.util.Calendar
 java.util.Date
 javax.xml.namespace.QName
 java.net.URI
 javax.xml.datatype.XMLGregorianCalendar
 javax.xml.datatype.Duration
 java.lang.Object
 java.awt.Image
 javax.activation.DataHandler
 javax.xml.transform.Source
 java.util.UUID
 [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Databinding+Scope

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (TUSCANY-2361) Databinding tests for primitives and primitive arrays - local service, pass-by-value tests