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

2008-06-12 Thread Raymond Feng (JIRA)

[ 
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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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 
 

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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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)
   at 
 

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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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 the 

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

2008-06-12 Thread Raymond Feng (JIRA)

 [ 
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.



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

2008-06-10 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-10 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-10 Thread Raymond Feng (JIRA)

[ 
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.



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

2008-06-10 Thread Raymond Feng (JIRA)

[ 
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)
at 
 

[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

2008-06-06 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-06 Thread Raymond Feng (JIRA)

 [ 
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

2008-06-06 Thread Raymond Feng (JIRA)

[ 
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

2008-06-06 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2361.
---

Resolution: Fixed

Patch applied under r664103. Thanks,

 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] Resolved: (TUSCANY-2349) TransformationException when invoking a method with byte array paramter using webservice binding

2008-06-04 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2349.
---

Resolution: Fixed

The test case is now passed.

 TransformationException when invoking a method with byte array paramter using 
 webservice binding
 

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

 I have a service method that takes a byte array as parameter and returns a 
 byte array.  When I invoke the method using webservice binding, I am getting 
 a TransformationException: No path found for the transformation: 
 java:simpleType-java:array.
 The stacktrace is given below:
 org.apache.tuscany.sca.databinding.TransformationException: No path found for 
 the transformation: java:simpleType-java:array
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:163)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:67)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:152)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:1)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:79)
   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 $Proxy11.negateByteArray(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.impl.PrimitivesServiceClientImpl.negateByteArrayForward(PrimitivesServiceClientImpl.java:54)
   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:110)
   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 $Proxy10.negateByteArrayForward(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.PrimitivesDatabindingTestCase.performTestNegateByteArray(PrimitivesDatabindingTestCase.java:372)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.PrimitivesDatabindingTestCase.testWSNegateByteArray(PrimitivesDatabindingTestCase.java:236)
   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 
 

[jira] Assigned: (TUSCANY-2356) Databinding itests for Local service

2008-05-31 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2356:
-

Assignee: Raymond Feng

 Databinding itests for Local service
 

 Key: TUSCANY-2356
 URL: https://issues.apache.org/jira/browse/TUSCANY-2356
 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-2356.patch


 Databinding itests added by TUSCANY-2340 deal with only @Remotable service.  
 This JIRA is for itests for Local service.  See [1].
 [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-2356) Databinding itests for Local service

2008-05-31 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2356.
---

Resolution: Fixed

Patch applied under r662091. Thanks for the contribution!

 Databinding itests for Local service
 

 Key: TUSCANY-2356
 URL: https://issues.apache.org/jira/browse/TUSCANY-2356
 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-2356.patch


 Databinding itests added by TUSCANY-2340 deal with only @Remotable service.  
 This JIRA is for itests for Local service.  See [1].
 [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-2350) Databinding tests for primitive types and array of primitive types

2008-05-31 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2350.
---

Resolution: Fixed

Patch applied under r662091. Thanks for the contribution!

 Databinding tests for primitive types and array of primitive types
 --

 Key: TUSCANY-2350
 URL: https://issues.apache.org/jira/browse/TUSCANY-2350
 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-2350.patch


 Databinding tests for primitive types and array of primitive types

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



[jira] Assigned: (TUSCANY-2349) TransformationException when invoking a method with byte array paramter using webservice binding

2008-05-30 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2349:
-

Assignee: Raymond Feng

 TransformationException when invoking a method with byte array paramter using 
 webservice binding
 

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

 I have a service method that takes a byte array as parameter and returns a 
 byte array.  When I invoke the method using webservice binding, I am getting 
 a TransformationException: No path found for the transformation: 
 java:simpleType-java:array.
 The stacktrace is given below:
 org.apache.tuscany.sca.databinding.TransformationException: No path found for 
 the transformation: java:simpleType-java:array
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:163)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:67)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:152)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:1)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:79)
   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 $Proxy11.negateByteArray(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.impl.PrimitivesServiceClientImpl.negateByteArrayForward(PrimitivesServiceClientImpl.java:54)
   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:110)
   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 $Proxy10.negateByteArrayForward(Unknown Source)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.PrimitivesDatabindingTestCase.performTestNegateByteArray(PrimitivesDatabindingTestCase.java:372)
   at 
 org.apache.tuscany.sca.itest.databindings.jaxb.PrimitivesDatabindingTestCase.testWSNegateByteArray(PrimitivesDatabindingTestCase.java:236)
   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-2350) Databinding tests for primitive types and array of primitive types

2008-05-30 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2350:
-

Assignee: Raymond Feng

 Databinding tests for primitive types and array of primitive types
 --

 Key: TUSCANY-2350
 URL: https://issues.apache.org/jira/browse/TUSCANY-2350
 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-2350.patch


 Databinding tests for primitive types and array of primitive types

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



[jira] Resolved: (TUSCANY-2340) Databinding integration tests

2008-05-27 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2340.
---

Resolution: Fixed

Patch applied under r660648. Thanks Vamsi for the patch!

 Databinding integration tests
 -

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

 Attachments: TUSCANY-2340-new.patch, TUSCANY-2340.patch


 I have been trying out a few tests with databindings and am hitting some 
 TransformationExceptions.  I thought it is better I post the tests I am 
 creating to the JIRA so that others can take a look at these tests.

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



[jira] Commented: (TUSCANY-2339) Java 2 Security - Provide Tuscany Maven profile to run vtest and itest with Java 2 security enabled

2008-05-23 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2339:
---

Hi, Dan.

I suggest that we set a tuscany.policy property in the profile and activate the 
profile if the property is set:

profiles
  profile
idj2sec/id
activation
  property
nametuscany.policy/name
  /property
/activation
 properties

tuscany.policyfile:///${java.home}/lib/security/tuscany.policy/tuscany.policy
  /properties
  /profile
/profiles


 Java 2 Security - Provide Tuscany Maven profile to run vtest and itest with 
 Java 2 security enabled
 ---

 Key: TUSCANY-2339
 URL: https://issues.apache.org/jira/browse/TUSCANY-2339
 Project: Tuscany
  Issue Type: Improvement
  Components: Java SCA Core Runtime
 Environment: Maven profile should be operating system independent.
Reporter: Dan Becker
 Attachments: TUSCANY-2339.patch


 Provide Tuscany Maven profile to run vtest and itest with Java 2 security 
 enabled. This profile should specify a security profile for Tuscany, and 
 should run vtest and itests with Java 2 security enabled.
 Run the profile with
 mvn -P security.
 Suggested profile addition to Tuscany java/sca pom.xml
 profile
 idsecurity/id
 modules
 !-- moduledemos/module --
 moduleitest/module
 modulevtest/module
 /modules
 build
 plugins
 plugin
 groupIdorg.apache.maven.plugins/groupId
 artifactIdmaven-surefire-plugin/artifactId
 version2.3.1/version
 configuration
 includes
 include**/*TestCase.java/include
 /includes
 reportFormatbrief/reportFormat
 useFilefalse/useFile
 forkModeonce/forkMode
 !-- Place tuscany.policy in your Java home 
 security directory. Alternatively, hardcode the file location here. --
 argLine-Djava.security.manager 
 -Djava.security.policy=file:///${java.home}/lib/security/tuscany.policy 
 -Dpolicy.allowSystemProperty=true -Djava.security.debug=policy/argLine
 /configuration
 /plugin
 /plugins 
 /build
 /profile

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



[jira] Assigned: (TUSCANY-2290) Java 2 Security enablement for Tuscany sample (part 1)

2008-05-19 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2290:
-

Assignee: Raymond Feng

 Java 2 Security enablement for Tuscany sample (part 1)
 --

 Key: TUSCANY-2290
 URL: https://issues.apache.org/jira/browse/TUSCANY-2290
 Project: Tuscany
  Issue Type: Bug
Affects Versions: Java-SCA-1.2
 Environment: Windows, Java 1.5
Reporter: Dan Becker
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2290.3.patch


 Fix security issues that arise in Tuscany samples when Java 2 security is 
 turned on via 
 -java.security.manager  -Djava.security.policy=tuscany.policy 
 -Dpolicy.allowSystemProperty=true
 A typical exception might be for sample helloworld sdo ws 
 Problems trying to access System properties: 
 java.security.AccessControlException: access denied 
 (java.util.PropertyPermission java.specification.version read)
 java.lang.NoClassDefFoundError
   at 
 org.apache.tuscany.sca.databinding.sdo.SDODataBinding.introspect(SDODataBinding.java:61)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.introspect(DefaultDataBindingExtensionPoint.java:191)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:246)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:202)
   at 
 org.apache.tuscany.sca.core.databinding.processor.DataBindingJavaInterfaceProcessor.processInterface(DataBindingJavaInterfaceProcessor.java:116)
   at 
 org.apache.tuscany.sca.core.databinding.processor.DataBindingJavaInterfaceProcessor.visitInterface(DataBindingJavaInterfaceProcessor.java:58)
   at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:113)
   at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceFactoryImpl.createJavaInterface(JavaInterfaceFactoryImpl.java:48)
   at 
 org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor.createService(ServiceProcessor.java:159)
   at 
 org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor.visitClass(ServiceProcessor.java:90)
   at 
 org.apache.tuscany.sca.implementation.java.impl.JavaClassIntrospectorImpl.introspectClass(JavaClassIntrospectorImpl.java:72)
   at 
 org.apache.tuscany.sca.implementation.java.impl.JavaImplementationFactoryImpl.createJavaImplementation(JavaImplementationFactoryImpl.java:53)
   at 
 org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProcessor.resolve(JavaImplementationProcessor.java:152)
   at 
 org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProcessor.resolve(JavaImplementationProcessor.java:63)
 ...

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



[jira] Resolved: (TUSCANY-2290) Java 2 Security enablement for Tuscany sample (part 1)

2008-05-19 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2290.
---

Resolution: Fixed

Patch applied under r658007. Thanks Dan for the patch.

 Java 2 Security enablement for Tuscany sample (part 1)
 --

 Key: TUSCANY-2290
 URL: https://issues.apache.org/jira/browse/TUSCANY-2290
 Project: Tuscany
  Issue Type: Bug
Affects Versions: Java-SCA-1.2
 Environment: Windows, Java 1.5
Reporter: Dan Becker
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2290.3.patch


 Fix security issues that arise in Tuscany samples when Java 2 security is 
 turned on via 
 -java.security.manager  -Djava.security.policy=tuscany.policy 
 -Dpolicy.allowSystemProperty=true
 A typical exception might be for sample helloworld sdo ws 
 Problems trying to access System properties: 
 java.security.AccessControlException: access denied 
 (java.util.PropertyPermission java.specification.version read)
 java.lang.NoClassDefFoundError
   at 
 org.apache.tuscany.sca.databinding.sdo.SDODataBinding.introspect(SDODataBinding.java:61)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint$LazyDataBinding.introspect(DefaultDataBindingExtensionPoint.java:191)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:246)
   at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:202)
   at 
 org.apache.tuscany.sca.core.databinding.processor.DataBindingJavaInterfaceProcessor.processInterface(DataBindingJavaInterfaceProcessor.java:116)
   at 
 org.apache.tuscany.sca.core.databinding.processor.DataBindingJavaInterfaceProcessor.visitInterface(DataBindingJavaInterfaceProcessor.java:58)
   at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:113)
   at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceFactoryImpl.createJavaInterface(JavaInterfaceFactoryImpl.java:48)
   at 
 org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor.createService(ServiceProcessor.java:159)
   at 
 org.apache.tuscany.sca.implementation.java.introspect.impl.ServiceProcessor.visitClass(ServiceProcessor.java:90)
   at 
 org.apache.tuscany.sca.implementation.java.impl.JavaClassIntrospectorImpl.introspectClass(JavaClassIntrospectorImpl.java:72)
   at 
 org.apache.tuscany.sca.implementation.java.impl.JavaImplementationFactoryImpl.createJavaImplementation(JavaImplementationFactoryImpl.java:53)
   at 
 org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProcessor.resolve(JavaImplementationProcessor.java:152)
   at 
 org.apache.tuscany.sca.implementation.java.xml.JavaImplementationProcessor.resolve(JavaImplementationProcessor.java:63)
 ...

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



[jira] Resolved: (TUSCANY-2321) Databinding producing different DOM Objects depending on the transformation path in use

2008-05-15 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2321.
---

Resolution: Fixed

Fixed under r656747

 Databinding producing different DOM Objects depending on the transformation 
 path in use
 ---

 Key: TUSCANY-2321
 URL: https://issues.apache.org/jira/browse/TUSCANY-2321
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-Next
Reporter: Luciano Resende
Assignee: Raymond Feng

 When invoking a regular BPEL component, the databinding framework execute the 
 following transformation path (String-DOM) and produces a DOM Element as 
 result.
 When invoking a BPEL component exposed as web services (ws binding) the 
 databinding framework execute the following transformation path 
 (String-OMElement-DOM) and produces a DOM Document as result.
 This causes issues when the implementation is manipulating the expected DOM 
 arguments during invocation.
 It would be good if we could be consistent.

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



[jira] Assigned: (TUSCANY-2321) Databinding producing different DOM Objects depending on the transformation path in use

2008-05-15 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2321:
-

Assignee: Raymond Feng

 Databinding producing different DOM Objects depending on the transformation 
 path in use
 ---

 Key: TUSCANY-2321
 URL: https://issues.apache.org/jira/browse/TUSCANY-2321
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-Next
Reporter: Luciano Resende
Assignee: Raymond Feng

 When invoking a regular BPEL component, the databinding framework execute the 
 following transformation path (String-DOM) and produces a DOM Element as 
 result.
 When invoking a BPEL component exposed as web services (ws binding) the 
 databinding framework execute the following transformation path 
 (String-OMElement-DOM) and produces a DOM Document as result.
 This causes issues when the implementation is manipulating the expected DOM 
 arguments during invocation.
 It would be good if we could be consistent.

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



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

2008-05-09 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2084:
---

I tried the following XML with SDO 1.1 release and it seems to be working fine:

private static final String XML =
ns:return xmlns:ns=\http://services.move.ec3\; 
xmlns:ax21=\http://types.move.ec3/xsd\;  + 
xmlns:_typens_=\http://types.move.ec3/xsd\; 
xmlns:xsi=\http://www.w3.org/2001/XMLSchema-instance\; 
xsi:type=\_typens_:Comment\
+ 
ax21:bodyc/ax21:bodyax21:captionb/ax21:captionax21:entryId1/ax21:entryIdax21:ownera1/ax21:ownerax21:referencea1/ax21:referenceax21:tstamp2008-04-16T16:22:07.812Z/ax21:tstamp/ns:return;

I assume it has been fixed in SDO 1.1.

Thanks,
Raymond

 Problems deserializing XML-SDO after  using XMLType element calculated from 
 Java to serialize SDO-XML onto
 

 Key: TUSCANY-2084
 URL: https://issues.apache.org/jira/browse/TUSCANY-2084
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime, Java SDO Implementation
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
 Fix For: Java-SCA-Next


 Discussed in this thread:
 http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg28304.html
 Personally I worked around this by changing SDODatabinding.introspect() to do:
 dataType.setLogical(new XMLType(null, xmlType));
 //dataType.setLogical(new XMLType(elementName, xmlType));
 But Raymond suggested possibly fixing this in the SDO impl.   It would also 
 be possible to leave introspection the same
 but workaround this in the SDO transformers.
 Note that if you use the WS binding you typically won't see this, because the 
 presence of the WSDL intf on the XML side of things
 gives you a real element to serialize into, one that SDO can recognize during 
 deserialization.  You have to have a binding without a WSDL intf
 that you're transforming across.

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



[jira] Commented: (TUSCANY-2285) Make sca-api automatically build as an OSGi bundle

2008-05-02 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2285:
---

To respond on Rajini's comment, the problem we had with maven-bundle-plugin in 
sd-api happened with JDK 1.4.

 Make sca-api automatically build as an OSGi bundle
 --

 Key: TUSCANY-2285
 URL: https://issues.apache.org/jira/browse/TUSCANY-2285
 Project: Tuscany
  Issue Type: Improvement
  Components: Java SCA Core Runtime, Java SCA OSGi Integration
Affects Versions: Java-SCA-Next
 Environment: All
Reporter: Graham Charters
Priority: Minor
 Fix For: Java-SCA-Next

 Attachments: sca-api-bundle-2.patch, sca-api-bundle.patch

   Original Estimate: 0.5h
  Remaining Estimate: 0.5h

 Itest/osgi-tuscany creates an OSGi bundle for the sca-api module.  As a step 
 towards providing better support for OSGi, it has been suggested on the 
 dev-list that we simply make sca-api automatically build as an OSGi bundle.  
 This does not preclude it being used as a normal jar.
 I have a patch which I will attached shortly.

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



[jira] Commented: (TUSCANY-2285) Make sca-api automatically build as an OSGi bundle

2008-05-01 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2285:
---

We have experienced an issue with the maven-bundle-plugin if the packaging is 
set to bundle in the sdo-api module. See:
http://markmail.org/message/ihjubv4pmywac7nk?q=sebb+%5BVOTE%5D+SDO+1%2E1+rc3+releasepage=1refer=ihjubv4pmywac7nk

We ended up with a slight different usage of the plugin which is less invasive. 
Please see:

http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1.1/sdo-api/pom.xml

 Make sca-api automatically build as an OSGi bundle
 --

 Key: TUSCANY-2285
 URL: https://issues.apache.org/jira/browse/TUSCANY-2285
 Project: Tuscany
  Issue Type: Improvement
  Components: Java SCA Core Runtime, Java SCA OSGi Integration
Affects Versions: Java-SCA-Next
 Environment: All
Reporter: Graham Charters
Priority: Minor
 Fix For: Java-SCA-Next

 Attachments: sca-api-bundle.patch

   Original Estimate: 0.5h
  Remaining Estimate: 0.5h

 Itest/osgi-tuscany creates an OSGi bundle for the sca-api module.  As a step 
 towards providing better support for OSGi, it has been suggested on the 
 dev-list that we simply make sca-api automatically build as an OSGi bundle.  
 This does not preclude it being used as a normal jar.
 I have a patch which I will attached shortly.

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



[jira] Commented: (TUSCANY-2280) No data transformation for fault types

2008-04-30 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2280:
---

Is your interface a remotable interface? for example, a WSDL portType or a java 
interface with @Remotable annotation. 

Please also attach a test case (I assume you are trying it:-).

Thanks,
Raymond

 No data transformation for fault types
 --

 Key: TUSCANY-2280
 URL: https://issues.apache.org/jira/browse/TUSCANY-2280
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.1, Java-SCA-1.2
Reporter: Cezary Wisniewski
 Fix For: Java-SCA-1.1, Java-SCA-1.2


 DataTransformationInterceptor is not added to the InvocationChain when method 
 has no parameters and no return type e.g.
 void someMethod() throws MyException
 DataTransformationInterceptor should be added to the chain because the 
 exception has to be transformed. DataTransformationInterceptor is added to 
 the chain and exception is transformed when the method has at least one 
 parameter or return type e.g.
 MyStruct someMethod() throws MyExcpetions
 or
 void someMethod(MyStruct param) throws MyException
 The reason for such behavior is that DataBindingRuntimeWireProcessor only 
 takes care of parameters and return types and ignores fault types (see 
 DataBindingRuntimeWireProcessor.isTransformationRequired(Operation, Operation)

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



[jira] Assigned: (TUSCANY-2275) Problem when with Bean[] and null

2008-04-30 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2275:
-

Assignee: Raymond Feng

 Problem when with Bean[] and null
 -

 Key: TUSCANY-2275
 URL: https://issues.apache.org/jira/browse/TUSCANY-2275
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.2
 Environment: Tuscnay 1.2-RC4, WAS
Reporter: Nishant Joshi
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2

 Attachments: null problem.zip


 I have one service, in which i m passgin Bean[]... If i try to pass null 
 instead then it gives exception 
 -
 Exception in thread main org.osoa.sca.ServiceRuntimeException: Target fault 
 type cannot be resolved: null
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134)
   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 $Proxy6.processBean(Unknown Source)
   at com.client.Client.processBean(Client.java:22)
   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:109)
   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 
 org.apache.tuscany.sca.core.invocation.CglibProxyFactory$CglibMethodInterceptor.intercept(CglibProxyFactory.java:149)
   at com.client.Client$$EnhancerByCGLIB$$b5aedbbb.processBean(generated)
   at com.client.Client.main(Client.java:34)
 Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: Array 
 index out of range: 0
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
   ... 15 more
 Caused by: org.apache.axis2.AxisFault: Array index out of range: 0
   at 
 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
   at 
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:118)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:89)
   ... 16 more
 -
 please find the attached sample to reproduce it.
 please note that this error was on client side and can be generated using 
 attached sample...
 same works for servcie having  bean (not an array of bean)

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



[jira] Commented: (TUSCANY-2275) Problem when with Bean[] and null

2008-04-30 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2275:
---

Hi,

I debugged the issue and it turned out an interesting case. 

1) When the client side pass 'null' for the service.processBean() method, the 
body of soap message becomes:

ns1:processBean xmlns1=.../

It's the wrapper element with empty children.

2) On the receiving side, the empty data get converted into SimpleBean[0] which 
is an empty array of SimpleBean.

3) The user code in SimpleServiceImpl.java only tests if the simpleBean==null 
and it causes an ArrayOutofBoundException. Adding the test of 
simpleBean.length0 fixes the problem and the client runs successfuly.

I would resolve it as a user error. I'm not so sure if we should present the 
data as null or [0]. If you can find any spec covering this corner case, I 
would be happy to revisit it.

Thanks,
Raymond

 Problem when with Bean[] and null
 -

 Key: TUSCANY-2275
 URL: https://issues.apache.org/jira/browse/TUSCANY-2275
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.2
 Environment: Tuscnay 1.2-RC4, WAS
Reporter: Nishant Joshi
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2

 Attachments: null problem.zip


 I have one service, in which i m passgin Bean[]... If i try to pass null 
 instead then it gives exception 
 -
 Exception in thread main org.osoa.sca.ServiceRuntimeException: Target fault 
 type cannot be resolved: null
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134)
   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 $Proxy6.processBean(Unknown Source)
   at com.client.Client.processBean(Client.java:22)
   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:109)
   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 
 org.apache.tuscany.sca.core.invocation.CglibProxyFactory$CglibMethodInterceptor.intercept(CglibProxyFactory.java:149)
   at com.client.Client$$EnhancerByCGLIB$$b5aedbbb.processBean(generated)
   at com.client.Client.main(Client.java:34)
 Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: Array 
 index out of range: 0
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
   ... 15 more
 Caused by: org.apache.axis2.AxisFault: Array index out of range: 0
   at 
 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
   at 
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:118)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:89)
   ... 16 more
 -
 please find the attached sample to reproduce it.
 please note that this error was on client side and can be generated using 
 attached sample...
 same works for servcie having  bean (not an array of bean)

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



[jira] Resolved: (TUSCANY-2275) Problem when with Bean[] and null

2008-04-30 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2275.
---

Resolution: Won't Fix

Resolved as a user error.

 Problem when with Bean[] and null
 -

 Key: TUSCANY-2275
 URL: https://issues.apache.org/jira/browse/TUSCANY-2275
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.2
 Environment: Tuscnay 1.2-RC4, WAS
Reporter: Nishant Joshi
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2

 Attachments: null problem.zip


 I have one service, in which i m passgin Bean[]... If i try to pass null 
 instead then it gives exception 
 -
 Exception in thread main org.osoa.sca.ServiceRuntimeException: Target fault 
 type cannot be resolved: null
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134)
   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 $Proxy6.processBean(Unknown Source)
   at com.client.Client.processBean(Client.java:22)
   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:109)
   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 
 org.apache.tuscany.sca.core.invocation.CglibProxyFactory$CglibMethodInterceptor.intercept(CglibProxyFactory.java:149)
   at com.client.Client$$EnhancerByCGLIB$$b5aedbbb.processBean(generated)
   at com.client.Client.main(Client.java:34)
 Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: Array 
 index out of range: 0
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
   ... 15 more
 Caused by: org.apache.axis2.AxisFault: Array index out of range: 0
   at 
 org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
   at 
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:118)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:89)
   ... 16 more
 -
 please find the attached sample to reproduce it.
 please note that this error was on client side and can be generated using 
 attached sample...
 same works for servcie having  bean (not an array of bean)

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



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

2008-04-22 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2113.
---

Resolution: Fixed

Fixed under r650561

 Problem with fault comparison in DataTransformationInterceptor; maybe we 
 should compare elem QNames, not type QNames?
 -

 Key: TUSCANY-2113
 URL: https://issues.apache.org/jira/browse/TUSCANY-2113
 Project: Tuscany
  Issue Type: Bug
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 There's a problem with how the fault matching in DTI uses the private 
 DTI.typesMatch() method.
 I don't think it should be allowing a matching type name to return 'true', 
 i.e. indicate a successful match.
return matches(t1.getElementName(), t2.getElementName()) || 
 matches(t1.getTypeName(), t2.getTypeName());
 For one, I could have two distinct fault elems of the same type. 
 In addition, also note that, if you have a fault element with anonymous type, 
 the generated JAXB will look like:
 @XmlType(name = ..)
 so we will build up an XMLType with typeName equal to a namespace plus a null 
 name.One problem with this is that there is no way to distinguish between 
 two fault elems in the same NS, with anonymous types. 
 I haven't given this a huge amount of thought so I mention this in case 
 anyone thinks of other issues relating to some of the points I am making.

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



[jira] Assigned: (TUSCANY-2030) Java 2 security

2008-04-22 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2030:
-

Assignee: Raymond Feng

 Java 2 security
 ---

 Key: TUSCANY-2030
 URL: https://issues.apache.org/jira/browse/TUSCANY-2030
 Project: Tuscany
  Issue Type: New Feature
Affects Versions: Java-SCA-1.0.1
Reporter: Greg Dritschler
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2030.patch


 In environments where Java 2 security is enabled, an AccessControlException 
 may occur in Tuscany code even though it has privileges to perform the 
 action, because there is code on the call stack that does not have such 
 privileges.  doPrivileged calls must be used around such actions.
 Here is an example of a failure.  There are undoubtedly others.
 java.security.AccessControlException: Access denied 
 (java.lang.RuntimePermission getClassLoader)
   at 
 java.security.AccessController.checkPermission(AccessController.java:104)
   at java.lang.SecurityManager.checkPermission(SecurityManager.java:547)
   at 
 com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java:189)
   at java.lang.Class.getClassLoader(Class.java:234)
   at 
 org.apache.tuscany.sca.core.invocation.JDKProxyFactory.createProxy(JDKProxyFactory.java:64)
   at 
 org.apache.tuscany.sca.core.invocation.DefaultProxyFactoryExtensionPoint.createProxy(DefaultProxyFactoryExtensionPoint.java:105)
   at 
 org.apache.tuscany.sca.core.context.CallableReferenceImpl.getInstance(CallableReferenceImpl.java:154)
   at 
 org.apache.tuscany.sca.core.context.CallableReferenceImpl.getService(CallableReferenceImpl.java:162)
   at 
 org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.getService(EmbeddedSCADomain.java:138)
   at 
 com.ibm.ws.soa.sca.runtime.impl.SimpleCompositeContextImpl.locateService(SimpleCompositeContextImpl.java:86)
   at com.ibm._jsp._Calculator._jspService(_Calculator.java:96)

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



[jira] Resolved: (TUSCANY-2237) Java 2 Security - Enhancements to run Itest bucket

2008-04-22 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2237.
---

Resolution: Fixed

Patch applied under 650681. Thanks

 Java 2 Security - Enhancements to run Itest bucket
 --

 Key: TUSCANY-2237
 URL: https://issues.apache.org/jira/browse/TUSCANY-2237
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.1
 Environment: Java 1.5, Windows
Reporter: Dan Becker
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2237-2.patch


 Must add proper Java 2 security to allow all Itests to run and pass JUnit 
 testing. An example of a failing Itest occurs with 
 CallableReferenceRemoteTestcase with Java 2 security enables. Here is an 
 example AccessControlException:
 java.security.AccessControlException: access denied 
 (java.util.PropertyPermission java.io.tmpdir read)
   at java.security.AccessControlContext.checkPermission(Unknown Source)
   at java.security.AccessController.checkPermission(Unknown Source)
   at java.lang.SecurityManager.checkPermission(Unknown Source)
   at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
   at java.lang.System.getProperty(Unknown Source)
   at 
 org.apache.axis2.context.ConfigurationContext.cleanupTemp(ConfigurationContext.java:665)
   at 
 org.apache.axis2.context.ConfigurationContext.terminate(ConfigurationContext.java:653)
   at 
 org.apache.axis2.transport.http.AxisServlet.destroy(AxisServlet.java:449)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.destroy(Axis2ServiceServlet.java:236)
   at 
 org.apache.tuscany.sca.http.tomcat.ServletWrapper.destroyServlet(ServletWrapper.java:55)
   at 
 org.apache.tuscany.sca.http.tomcat.TomcatServer.removeServletMapping(TomcatServer.java:510)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.stop(Axis2ServiceProvider.java:308)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.stop(Axis2ServiceBindingProvider.java:98)
   at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:615)
   at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:513)
   at 
 org.apache.tuscany.sca.node.impl.SCADomainProxyImpl.destroy(SCADomainProxyImpl.java:500)
   at 
 org.apache.tuscany.sca.node.impl.SCANodeImpl.destroy(SCANodeImpl.java:441)
   at 
 org.apache.tuscany.sca.itest.callableref.CallableReferenceRemoteTestCase.destroy(CallableReferenceRemoteTestCase.java:97)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod(BeforeAndAfterRunner.java:74)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runAfters(BeforeAndAfterRunner.java:65)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:37)
   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)
 This is fixed by adding AccessController.doPrivileged blocks around the 
 sensitive call

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



[jira] Resolved: (TUSCANY-2030) Java 2 security

2008-04-22 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2030.
---

Resolution: Fixed

Patch applied under r650681. Thanks!

 Java 2 security
 ---

 Key: TUSCANY-2030
 URL: https://issues.apache.org/jira/browse/TUSCANY-2030
 Project: Tuscany
  Issue Type: New Feature
Affects Versions: Java-SCA-1.0.1
Reporter: Greg Dritschler
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2030.patch


 In environments where Java 2 security is enabled, an AccessControlException 
 may occur in Tuscany code even though it has privileges to perform the 
 action, because there is code on the call stack that does not have such 
 privileges.  doPrivileged calls must be used around such actions.
 Here is an example of a failure.  There are undoubtedly others.
 java.security.AccessControlException: Access denied 
 (java.lang.RuntimePermission getClassLoader)
   at 
 java.security.AccessController.checkPermission(AccessController.java:104)
   at java.lang.SecurityManager.checkPermission(SecurityManager.java:547)
   at 
 com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java:189)
   at java.lang.Class.getClassLoader(Class.java:234)
   at 
 org.apache.tuscany.sca.core.invocation.JDKProxyFactory.createProxy(JDKProxyFactory.java:64)
   at 
 org.apache.tuscany.sca.core.invocation.DefaultProxyFactoryExtensionPoint.createProxy(DefaultProxyFactoryExtensionPoint.java:105)
   at 
 org.apache.tuscany.sca.core.context.CallableReferenceImpl.getInstance(CallableReferenceImpl.java:154)
   at 
 org.apache.tuscany.sca.core.context.CallableReferenceImpl.getService(CallableReferenceImpl.java:162)
   at 
 org.apache.tuscany.sca.host.embedded.impl.EmbeddedSCADomain.getService(EmbeddedSCADomain.java:138)
   at 
 com.ibm.ws.soa.sca.runtime.impl.SimpleCompositeContextImpl.locateService(SimpleCompositeContextImpl.java:86)
   at com.ibm._jsp._Calculator._jspService(_Calculator.java:96)

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



[jira] Commented: (TUSCANY-2240) Creation of SDO object out of XML (read from an JMS message) is taking too long

2008-04-18 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2240:
---

Talking to Fuhwei offline and he pointed me to the code in 
org.apache.tuscany.sdo.util.DataObjectUtil.configureResourceSet(ResourceSet) 
which the set of SDOURIConverterImpl is commented out to allow the loading of 
XSD remotely. I think we could make a compromise here, in the 
SDOURIConverterImpl, we could check if the URI ends with .xsd or .wsdl, if yes, 
then allows the open stream, otherwise just throw an IOException so that the 
EMF layer will skip the loading.

Thanks,
Raymond

 Creation of SDO object out of XML (read from an JMS message) is taking too 
 long
 ---

 Key: TUSCANY-2240
 URL: https://issues.apache.org/jira/browse/TUSCANY-2240
 Project: Tuscany
  Issue Type: Bug
  Components: Java SDO Implementation
Affects Versions: Java-SDO-1.0, Java-SCA-1.1
 Environment: Windows XP Pro SP2, JDK 1.6_06, SCA 1.1, SDO 1.1
Reporter: Ph.Konradi

 After I've switched from JMS messages containing Objects to XML (migrated 
 from Tuscany 1.0.1 to 1.1) my application needs around 7 sec to call my 
 service.
 Before it reacted instantly. 
 I've debugged into to see where the problem is and saw that receiving of the 
 JMS message works still instantly but the processing takes pretty long. 
 Below in the stack trace one can see that a new http connection is opened 
 (???) and I guess that's responsible for the delay.
 Any explanation for this behaviour? What am I doing wrong?
 The service's method I'm calling has an argument of complex type.
 Thanks, 
 Philipp
 Daemon Thread [ActiveMQ Session Task] (Suspended) 
   PlainSocketImpl.socketConnect(InetAddress, int, int) line: not 
 available [native method]
   PlainSocketImpl.doConnect(InetAddress, int, int) line: 333  
   PlainSocketImpl.connectToAddress(InetAddress, int, int) line: 195   
   PlainSocketImpl.connect(SocketAddress, int) line: 182   
   Socket.connect(SocketAddress, int) line: 519
   Socket.connect(SocketAddress) line: 469 
   HttpClient(NetworkClient).doConnect(String, int) line: 157  
   HttpClient.openServer(String, int) line: 394
   HttpClient.openServer() line: 529   
   HttpClient.init(URL, Proxy, int) line: 233
   HttpClient.New(URL, Proxy, int, boolean) line: 306  
   HttpClient.New(URL, Proxy, int) line: 323   
   HttpURLConnection.getNewHttpClient(URL, Proxy, int) line: 788   
   HttpURLConnection.plainConnect() line: 729  
   HttpURLConnection.connect() line: 654   
   HttpURLConnection.getInputStream() line: 977
   URIConverterImpl.createURLInputStream(URI) line: 566
   URIConverterImpl.createInputStream(URI) line: 453   
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getPackageForURI(String)
  line: 2294
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getFactoryForPrefix(String)
  line: 2188 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createObjectByType(String,
  String, boolean) line: 1145 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createTopObject(String,
  String) line: 1247 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).processElement(String,
  String, String) line: 883   
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, 
 String, String) line: 866 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, 
 String, String, Attributes) line: 627 
   SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.startElement(String, 
 String, String, Attributes) line: 401 
   StAX2SAXAdapter.handleStartElement(XMLStreamReader, ContentHandler) 
 line: 162   
   StAX2SAXAdapter.parse(XMLStreamReader, ContentHandler) line: 111
   SDOXMLResourceImpl$SDOXMLLoadImpl$1.run() line: 472 
   AccessController.doPrivileged(PrivilegedExceptionActionT) line: not 
 available [native method] 
   SDOXMLResourceImpl$SDOXMLLoadImpl.load(XMLResource, XMLStreamReader, 
 Map) line: 470 
   SDOXMLResourceImpl.load(XMLStreamReader, Map) line: 598 
   XMLDocumentImpl.load(XMLStreamReader, Map) line: 248
   XMLStreamHelperImpl.loadDocument(XMLStreamReader, Map) line: 136
   XMLStreamHelperImpl.loadObject(XMLStreamReader, Map) line: 98   
   XMLStreamHelperImpl.loadObject(XMLStreamReader) line: 102   
   XMLStreamReader2DataObject.transform(XMLStreamReader, 
 TransformationContext) line: 49   
   XMLStreamReader2DataObject.transform(Object, TransformationContext) 
 line: 

[jira] Assigned: (TUSCANY-2240) Creation of SDO object out of XML (read from an JMS message) is taking too long

2008-04-18 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2240:
-

Assignee: Raymond Feng

 Creation of SDO object out of XML (read from an JMS message) is taking too 
 long
 ---

 Key: TUSCANY-2240
 URL: https://issues.apache.org/jira/browse/TUSCANY-2240
 Project: Tuscany
  Issue Type: Bug
  Components: Java SDO Implementation
Affects Versions: Java-SDO-1.0, Java-SCA-1.1
 Environment: Windows XP Pro SP2, JDK 1.6_06, SCA 1.1, SDO 1.1
Reporter: Ph.Konradi
Assignee: Raymond Feng

 After I've switched from JMS messages containing Objects to XML (migrated 
 from Tuscany 1.0.1 to 1.1) my application needs around 7 sec to call my 
 service.
 Before it reacted instantly. 
 I've debugged into to see where the problem is and saw that receiving of the 
 JMS message works still instantly but the processing takes pretty long. 
 Below in the stack trace one can see that a new http connection is opened 
 (???) and I guess that's responsible for the delay.
 Any explanation for this behaviour? What am I doing wrong?
 The service's method I'm calling has an argument of complex type.
 Thanks, 
 Philipp
 Daemon Thread [ActiveMQ Session Task] (Suspended) 
   PlainSocketImpl.socketConnect(InetAddress, int, int) line: not 
 available [native method]
   PlainSocketImpl.doConnect(InetAddress, int, int) line: 333  
   PlainSocketImpl.connectToAddress(InetAddress, int, int) line: 195   
   PlainSocketImpl.connect(SocketAddress, int) line: 182   
   Socket.connect(SocketAddress, int) line: 519
   Socket.connect(SocketAddress) line: 469 
   HttpClient(NetworkClient).doConnect(String, int) line: 157  
   HttpClient.openServer(String, int) line: 394
   HttpClient.openServer() line: 529   
   HttpClient.init(URL, Proxy, int) line: 233
   HttpClient.New(URL, Proxy, int, boolean) line: 306  
   HttpClient.New(URL, Proxy, int) line: 323   
   HttpURLConnection.getNewHttpClient(URL, Proxy, int) line: 788   
   HttpURLConnection.plainConnect() line: 729  
   HttpURLConnection.connect() line: 654   
   HttpURLConnection.getInputStream() line: 977
   URIConverterImpl.createURLInputStream(URI) line: 566
   URIConverterImpl.createInputStream(URI) line: 453   
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getPackageForURI(String)
  line: 2294
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getFactoryForPrefix(String)
  line: 2188 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createObjectByType(String,
  String, boolean) line: 1145 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createTopObject(String,
  String) line: 1247 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).processElement(String,
  String, String) line: 883   
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, 
 String, String) line: 866 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, 
 String, String, Attributes) line: 627 
   SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.startElement(String, 
 String, String, Attributes) line: 401 
   StAX2SAXAdapter.handleStartElement(XMLStreamReader, ContentHandler) 
 line: 162   
   StAX2SAXAdapter.parse(XMLStreamReader, ContentHandler) line: 111
   SDOXMLResourceImpl$SDOXMLLoadImpl$1.run() line: 472 
   AccessController.doPrivileged(PrivilegedExceptionActionT) line: not 
 available [native method] 
   SDOXMLResourceImpl$SDOXMLLoadImpl.load(XMLResource, XMLStreamReader, 
 Map) line: 470 
   SDOXMLResourceImpl.load(XMLStreamReader, Map) line: 598 
   XMLDocumentImpl.load(XMLStreamReader, Map) line: 248
   XMLStreamHelperImpl.loadDocument(XMLStreamReader, Map) line: 136
   XMLStreamHelperImpl.loadObject(XMLStreamReader, Map) line: 98   
   XMLStreamHelperImpl.loadObject(XMLStreamReader) line: 102   
   XMLStreamReader2DataObject.transform(XMLStreamReader, 
 TransformationContext) line: 49   
   XMLStreamReader2DataObject.transform(Object, TransformationContext) 
 line: 34
   DefaultTransformerExtensionPoint$LazyPullTransformer.transform(Object, 
 TransformationContext) line: 199 
   MediatorImpl.mediate(Object, DataType, DataType, MapString,Object) 
 line: 73   
   Input2InputTransformer.transform(Object[], TransformationContext) line: 
 179 
   Input2InputTransformer.transform(Object, TransformationContext) line: 
 43
   MediatorImpl.mediate(Object, DataType, DataType, MapString,Object) 
 line: 73   
 

[jira] Resolved: (TUSCANY-2240) Creation of SDO object out of XML (read from an JMS message) is taking too long

2008-04-18 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2240.
---

Resolution: Fixed

Fixed in trunk under r649628

 Creation of SDO object out of XML (read from an JMS message) is taking too 
 long
 ---

 Key: TUSCANY-2240
 URL: https://issues.apache.org/jira/browse/TUSCANY-2240
 Project: Tuscany
  Issue Type: Bug
  Components: Java SDO Implementation
Affects Versions: Java-SDO-1.0, Java-SCA-1.1
 Environment: Windows XP Pro SP2, JDK 1.6_06, SCA 1.1, SDO 1.1
Reporter: Ph.Konradi
Assignee: Raymond Feng

 After I've switched from JMS messages containing Objects to XML (migrated 
 from Tuscany 1.0.1 to 1.1) my application needs around 7 sec to call my 
 service.
 Before it reacted instantly. 
 I've debugged into to see where the problem is and saw that receiving of the 
 JMS message works still instantly but the processing takes pretty long. 
 Below in the stack trace one can see that a new http connection is opened 
 (???) and I guess that's responsible for the delay.
 Any explanation for this behaviour? What am I doing wrong?
 The service's method I'm calling has an argument of complex type.
 Thanks, 
 Philipp
 Daemon Thread [ActiveMQ Session Task] (Suspended) 
   PlainSocketImpl.socketConnect(InetAddress, int, int) line: not 
 available [native method]
   PlainSocketImpl.doConnect(InetAddress, int, int) line: 333  
   PlainSocketImpl.connectToAddress(InetAddress, int, int) line: 195   
   PlainSocketImpl.connect(SocketAddress, int) line: 182   
   Socket.connect(SocketAddress, int) line: 519
   Socket.connect(SocketAddress) line: 469 
   HttpClient(NetworkClient).doConnect(String, int) line: 157  
   HttpClient.openServer(String, int) line: 394
   HttpClient.openServer() line: 529   
   HttpClient.init(URL, Proxy, int) line: 233
   HttpClient.New(URL, Proxy, int, boolean) line: 306  
   HttpClient.New(URL, Proxy, int) line: 323   
   HttpURLConnection.getNewHttpClient(URL, Proxy, int) line: 788   
   HttpURLConnection.plainConnect() line: 729  
   HttpURLConnection.connect() line: 654   
   HttpURLConnection.getInputStream() line: 977
   URIConverterImpl.createURLInputStream(URI) line: 566
   URIConverterImpl.createInputStream(URI) line: 453   
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getPackageForURI(String)
  line: 2294
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getFactoryForPrefix(String)
  line: 2188 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createObjectByType(String,
  String, boolean) line: 1145 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createTopObject(String,
  String) line: 1247 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).processElement(String,
  String, String) line: 883   
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, 
 String, String) line: 866 
   
 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, 
 String, String, Attributes) line: 627 
   SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.startElement(String, 
 String, String, Attributes) line: 401 
   StAX2SAXAdapter.handleStartElement(XMLStreamReader, ContentHandler) 
 line: 162   
   StAX2SAXAdapter.parse(XMLStreamReader, ContentHandler) line: 111
   SDOXMLResourceImpl$SDOXMLLoadImpl$1.run() line: 472 
   AccessController.doPrivileged(PrivilegedExceptionActionT) line: not 
 available [native method] 
   SDOXMLResourceImpl$SDOXMLLoadImpl.load(XMLResource, XMLStreamReader, 
 Map) line: 470 
   SDOXMLResourceImpl.load(XMLStreamReader, Map) line: 598 
   XMLDocumentImpl.load(XMLStreamReader, Map) line: 248
   XMLStreamHelperImpl.loadDocument(XMLStreamReader, Map) line: 136
   XMLStreamHelperImpl.loadObject(XMLStreamReader, Map) line: 98   
   XMLStreamHelperImpl.loadObject(XMLStreamReader) line: 102   
   XMLStreamReader2DataObject.transform(XMLStreamReader, 
 TransformationContext) line: 49   
   XMLStreamReader2DataObject.transform(Object, TransformationContext) 
 line: 34
   DefaultTransformerExtensionPoint$LazyPullTransformer.transform(Object, 
 TransformationContext) line: 199 
   MediatorImpl.mediate(Object, DataType, DataType, MapString,Object) 
 line: 73   
   Input2InputTransformer.transform(Object[], TransformationContext) line: 
 179 
   Input2InputTransformer.transform(Object, TransformationContext) line: 
 43
   MediatorImpl.mediate(Object, DataType, DataType, 

[jira] Resolved: (TUSCANY-2069) Missing serialization in DirectedGraph

2008-04-17 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2069.
---

Resolution: Fixed

Fixed under r649158

 Missing serialization in DirectedGraph
 --

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


 I have a service with a web service binding that processes its input using an 
 SDO.  The service works fine with one client.  It also works fine if it is 
 driven once by one client and then driven by multiple clients.  But if it is 
 driven initially by multiple clients (2 is enough), various failures occur in 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.  It appears there is a 
 lack of synchronization in this class.
 Failure 1 - NPE
 java.lang.NullPointerException
   at 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph$Node.access$400(DirectedGraph.java:188)
   at 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:314)
   at 
 org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.processMessage(RuntimeExtensionManager.java:96)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeTuscanyInterceptor.invoke(RuntimeTuscanyInterceptor.java:154)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:852)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:119)
   at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
   at 
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:147)
   at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
 Failure 2 - timeout (code is probably looping)
 WTRN0124I: When the timeout occurred the thread with which the transaction 
 is, or was most recently, associated was Thread[WebContainer : 0,5,main]. The 
 stack trace of this thread when the timeout occurred was: 
   java.util.HashMap.findNonNullKeyEntry(Unknown Source)
   java.util.HashMap.putImpl(Unknown Source)
   java.util.HashMap.put(Unknown Source)
   
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:296)
   
 org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76)
   
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183)
   
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88)
   
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192)
   
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
   
 

[jira] Created: (TUSCANY-2236) Unknown attibute causes StackOverflowError in XMLHelper.load()

2008-04-16 Thread Raymond Feng (JIRA)
Unknown attibute causes StackOverflowError in XMLHelper.load()
--

 Key: TUSCANY-2236
 URL: https://issues.apache.org/jira/browse/TUSCANY-2236
 Project: Tuscany
  Issue Type: Bug
  Components: Java SDO Implementation
Affects Versions: Java-SDO-Next
Reporter: Raymond Feng


With this XSD:

xs:schema xmlns:ax21=http://types.move.ec3/xsd; 
attributeFormDefault=qualified elementFormDefault=qualified
targetNamespace=http://types.move.ec3/xsd; 
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xs:complexType name=Comment
xs:sequence
xs:element minOccurs=0 name=body nillable=true 
type=xs:string /
xs:element minOccurs=0 name=caption nillable=true 
type=xs:string /
xs:element minOccurs=0 name=entryId nillable=true 
type=xs:string /
xs:element minOccurs=0 name=owner nillable=true 
type=xs:string /
xs:element minOccurs=0 name=reference nillable=true 
type=xs:string /
xs:element minOccurs=0 name=tstamp nillable=true 
type=xs:dateTime /
/xs:sequence
/xs:complexType
/xs:schema

And this XML:
ns:return xmlns:ns=http://services.move.ec3; 
xmlns:ax21=http://types.move.ec3/xsd; 
xmlns:_typens_=http://types.move.ec3/xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
type=ec3.move.types.Comment 
xsi:type=_typens_:Commentax21:bodyc/ax21:bodyax21:captionb/ax21:captionax21:entryId1/ax21:entryIdax21:ownera1/ax21:ownerax21:referencea1/ax21:referenceax21:tstamp2008-04-16T16:22:07.812Z/ax21:tstamp/ns:return

And this test case:

public void testLoad() {
HelperContext context = SDOUtil.createHelperContext();
InputStream is = getClass().getResourceAsStream(/comment.xsd);
context.getXSDHelper().define(is, null);
try {
context.getXMLHelper().load(XML);
} catch (StackOverflowError e) {
// FIXME: This test case is failing at this point
e.printStackTrace();
}

}

at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)
at 
org.eclipse.emf.ecore.xmi.impl.XMLHandler.setAttribValue(XMLHandler.java:2466)
at 
org.eclipse.emf.ecore.xmi.impl.SAXXMLHandler.handleObjectAttribs(SAXXMLHandler.java:72)
at 
org.apache.tuscany.sdo.util.resource.SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.handleUnknownFeature(SDOXMLResourceImpl.java:366)

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


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



[jira] Assigned: (TUSCANY-2069) Missing serialization in DirectedGraph

2008-04-16 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2069:
-

Assignee: Raymond Feng

 Missing serialization in DirectedGraph
 --

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


 I have a service with a web service binding that processes its input using an 
 SDO.  The service works fine with one client.  It also works fine if it is 
 driven once by one client and then driven by multiple clients.  But if it is 
 driven initially by multiple clients (2 is enough), various failures occur in 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.  It appears there is a 
 lack of synchronization in this class.
 Failure 1 - NPE
 java.lang.NullPointerException
   at 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph$Node.access$400(DirectedGraph.java:188)
   at 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:314)
   at 
 org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.processMessage(RuntimeExtensionManager.java:96)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeTuscanyInterceptor.invoke(RuntimeTuscanyInterceptor.java:154)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:852)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:119)
   at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
   at 
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:147)
   at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
 Failure 2 - timeout (code is probably looping)
 WTRN0124I: When the timeout occurred the thread with which the transaction 
 is, or was most recently, associated was Thread[WebContainer : 0,5,main]. The 
 stack trace of this thread when the timeout occurred was: 
   java.util.HashMap.findNonNullKeyEntry(Unknown Source)
   java.util.HashMap.putImpl(Unknown Source)
   java.util.HashMap.put(Unknown Source)
   
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:296)
   
 org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76)
   
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183)
   
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88)
   
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192)
   
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
   
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211)
 

[jira] Resolved: (TUSCANY-2069) Missing serialization in DirectedGraph

2008-04-16 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2069.
---

Resolution: Fixed

I checked in a fix under 648763, please verify.

 Missing serialization in DirectedGraph
 --

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


 I have a service with a web service binding that processes its input using an 
 SDO.  The service works fine with one client.  It also works fine if it is 
 driven once by one client and then driven by multiple clients.  But if it is 
 driven initially by multiple clients (2 is enough), various failures occur in 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.  It appears there is a 
 lack of synchronization in this class.
 Failure 1 - NPE
 java.lang.NullPointerException
   at 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph$Node.access$400(DirectedGraph.java:188)
   at 
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:314)
   at 
 org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183)
   at 
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59)
   at 
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192)
   at 
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.invokeNextInterceptor(RuntimeExtensionManager.java:211)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeExtensionManager.processMessage(RuntimeExtensionManager.java:96)
   at 
 com.ibm.ws.soa.sca.runtime.impl.RuntimeTuscanyInterceptor.invoke(RuntimeTuscanyInterceptor.java:154)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:852)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:119)
   at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
   at 
 org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:147)
   at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
 Failure 2 - timeout (code is probably looping)
 WTRN0124I: When the timeout occurred the thread with which the transaction 
 is, or was most recently, associated was Thread[WebContainer : 0,5,main]. The 
 stack trace of this thread when the timeout occurred was: 
   java.util.HashMap.findNonNullKeyEntry(Unknown Source)
   java.util.HashMap.putImpl(Unknown Source)
   java.util.HashMap.put(Unknown Source)
   
 org.apache.tuscany.sca.databinding.impl.DirectedGraph.getShortestPath(DirectedGraph.java:296)
   
 org.apache.tuscany.sca.databinding.DefaultTransformerExtensionPoint.getTransformerChain(DefaultTransformerExtensionPoint.java:302)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:162)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:76)
   
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:183)
   
 org.apache.tuscany.sca.core.databinding.transformers.Input2InputTransformer.transform(Input2InputTransformer.java:59)
   
 org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:88)
   
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:192)
   
 org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:89)
   
 

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

2008-04-16 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2113:
-

Assignee: Raymond Feng

 Problem with fault comparison in DataTransformationInterceptor; maybe we 
 should compare elem QNames, not type QNames?
 -

 Key: TUSCANY-2113
 URL: https://issues.apache.org/jira/browse/TUSCANY-2113
 Project: Tuscany
  Issue Type: Bug
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 There's a problem with how the fault matching in DTI uses the private 
 DTI.typesMatch() method.
 I don't think it should be allowing a matching type name to return 'true', 
 i.e. indicate a successful match.
return matches(t1.getElementName(), t2.getElementName()) || 
 matches(t1.getTypeName(), t2.getTypeName());
 For one, I could have two distinct fault elems of the same type. 
 In addition, also note that, if you have a fault element with anonymous type, 
 the generated JAXB will look like:
 @XmlType(name = ..)
 so we will build up an XMLType with typeName equal to a namespace plus a null 
 name.One problem with this is that there is no way to distinguish between 
 two fault elems in the same NS, with anonymous types. 
 I haven't given this a huge amount of thought so I mention this in case 
 anyone thinks of other issues relating to some of the points I am making.

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


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



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

2008-04-16 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2113:
---

Hi, Scott.

Do you have a test case handy for this issue?

Thanks,
Raymond

 Problem with fault comparison in DataTransformationInterceptor; maybe we 
 should compare elem QNames, not type QNames?
 -

 Key: TUSCANY-2113
 URL: https://issues.apache.org/jira/browse/TUSCANY-2113
 Project: Tuscany
  Issue Type: Bug
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Assignee: Raymond Feng
 Fix For: Java-SCA-Next


 There's a problem with how the fault matching in DTI uses the private 
 DTI.typesMatch() method.
 I don't think it should be allowing a matching type name to return 'true', 
 i.e. indicate a successful match.
return matches(t1.getElementName(), t2.getElementName()) || 
 matches(t1.getTypeName(), t2.getTypeName());
 For one, I could have two distinct fault elems of the same type. 
 In addition, also note that, if you have a fault element with anonymous type, 
 the generated JAXB will look like:
 @XmlType(name = ..)
 so we will build up an XMLType with typeName equal to a namespace plus a null 
 name.One problem with this is that there is no way to distinguish between 
 two fault elems in the same NS, with anonymous types. 
 I haven't given this a huge amount of thought so I mention this in case 
 anyone thinks of other issues relating to some of the points I am making.

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


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



[jira] Assigned: (TUSCANY-2237) Java 2 Security - Enhancements to run Itest bucket

2008-04-16 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2237:
-

Assignee: Raymond Feng

 Java 2 Security - Enhancements to run Itest bucket
 --

 Key: TUSCANY-2237
 URL: https://issues.apache.org/jira/browse/TUSCANY-2237
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.1
 Environment: Java 1.5, Windows
Reporter: Dan Becker
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2237.patch


 Must add proper Java 2 security to allow all Itests to run and pass JUnit 
 testing. An example of a failing Itest occurs with 
 CallableReferenceRemoteTestcase with Java 2 security enables. Here is an 
 example AccessControlException:
 java.security.AccessControlException: access denied 
 (java.util.PropertyPermission java.io.tmpdir read)
   at java.security.AccessControlContext.checkPermission(Unknown Source)
   at java.security.AccessController.checkPermission(Unknown Source)
   at java.lang.SecurityManager.checkPermission(Unknown Source)
   at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
   at java.lang.System.getProperty(Unknown Source)
   at 
 org.apache.axis2.context.ConfigurationContext.cleanupTemp(ConfigurationContext.java:665)
   at 
 org.apache.axis2.context.ConfigurationContext.terminate(ConfigurationContext.java:653)
   at 
 org.apache.axis2.transport.http.AxisServlet.destroy(AxisServlet.java:449)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.destroy(Axis2ServiceServlet.java:236)
   at 
 org.apache.tuscany.sca.http.tomcat.ServletWrapper.destroyServlet(ServletWrapper.java:55)
   at 
 org.apache.tuscany.sca.http.tomcat.TomcatServer.removeServletMapping(TomcatServer.java:510)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.stop(Axis2ServiceProvider.java:308)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.stop(Axis2ServiceBindingProvider.java:98)
   at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:615)
   at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:513)
   at 
 org.apache.tuscany.sca.node.impl.SCADomainProxyImpl.destroy(SCADomainProxyImpl.java:500)
   at 
 org.apache.tuscany.sca.node.impl.SCANodeImpl.destroy(SCANodeImpl.java:441)
   at 
 org.apache.tuscany.sca.itest.callableref.CallableReferenceRemoteTestCase.destroy(CallableReferenceRemoteTestCase.java:97)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod(BeforeAndAfterRunner.java:74)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runAfters(BeforeAndAfterRunner.java:65)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:37)
   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)
 This is fixed by adding AccessController.doPrivileged blocks around the 
 sensitive call

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


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



[jira] Commented: (TUSCANY-2237) Java 2 Security - Enhancements to run Itest bucket

2008-04-16 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2237:
---

IMO, the following priviledged block is too wide. Can you find the offending 
module and move the doPrivileged() to that module only?

Index: 
modules/host-embedded/src/main/java/org/apache/tuscany/sca/host/embedded/impl/ReallySmallRuntime.java

-module.stop(registry);
+// Allow privileged access to stop MBeans. Requires 
MBeanPermission in security policy.
+AccessController.doPrivileged(new PrivilegedActionObject() {
+public Object run() {
+module.stop(registry);
+return null;
+}
+});


 Java 2 Security - Enhancements to run Itest bucket
 --

 Key: TUSCANY-2237
 URL: https://issues.apache.org/jira/browse/TUSCANY-2237
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.1
 Environment: Java 1.5, Windows
Reporter: Dan Becker
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-2237.patch


 Must add proper Java 2 security to allow all Itests to run and pass JUnit 
 testing. An example of a failing Itest occurs with 
 CallableReferenceRemoteTestcase with Java 2 security enables. Here is an 
 example AccessControlException:
 java.security.AccessControlException: access denied 
 (java.util.PropertyPermission java.io.tmpdir read)
   at java.security.AccessControlContext.checkPermission(Unknown Source)
   at java.security.AccessController.checkPermission(Unknown Source)
   at java.lang.SecurityManager.checkPermission(Unknown Source)
   at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
   at java.lang.System.getProperty(Unknown Source)
   at 
 org.apache.axis2.context.ConfigurationContext.cleanupTemp(ConfigurationContext.java:665)
   at 
 org.apache.axis2.context.ConfigurationContext.terminate(ConfigurationContext.java:653)
   at 
 org.apache.axis2.transport.http.AxisServlet.destroy(AxisServlet.java:449)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.destroy(Axis2ServiceServlet.java:236)
   at 
 org.apache.tuscany.sca.http.tomcat.ServletWrapper.destroyServlet(ServletWrapper.java:55)
   at 
 org.apache.tuscany.sca.http.tomcat.TomcatServer.removeServletMapping(TomcatServer.java:510)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.stop(Axis2ServiceProvider.java:308)
   at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.stop(Axis2ServiceBindingProvider.java:98)
   at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:615)
   at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:513)
   at 
 org.apache.tuscany.sca.node.impl.SCADomainProxyImpl.destroy(SCADomainProxyImpl.java:500)
   at 
 org.apache.tuscany.sca.node.impl.SCANodeImpl.destroy(SCANodeImpl.java:441)
   at 
 org.apache.tuscany.sca.itest.callableref.CallableReferenceRemoteTestCase.destroy(CallableReferenceRemoteTestCase.java:97)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
   at java.lang.reflect.Method.invoke(Unknown Source)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.invokeMethod(BeforeAndAfterRunner.java:74)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runAfters(BeforeAndAfterRunner.java:65)
   at 
 org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:37)
   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)
 This is fixed by adding AccessController.doPrivileged blocks around the 
 sensitive call

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



[jira] Assigned: (TUSCANY-2214) xml-bigbank demo relies on http://www.swanandmokashi.com which is not (currently) available

2008-04-14 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2214:
-

Assignee: Raymond Feng

 xml-bigbank demo relies on http://www.swanandmokashi.com  which is not 
 (currently) available
 

 Key: TUSCANY-2214
 URL: https://issues.apache.org/jira/browse/TUSCANY-2214
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK5
Reporter: Simon Laws
Assignee: Raymond Feng
Priority: Minor
 Fix For: Java-SCA-1.2


 demo/xml-bingbank fails with the error below because the web site the demo is 
 trying to contact is not (currently) available to me. It may be temporary or 
 may be permanent. At a minimum we should note in the README that this can 
 happen and that the demo will not work it this is the case. 
 ant run
 Buildfile: build.xml
 run:
  [java] 09-Apr-2008 13:06:11 
 org.apache.tuscany.sca.contribution.processor.E
 xtensibleStAXArtifactProcessor read
  [java] WARNING: Element 
 {http://tuscany.apache.org/xmlns/sca/1.0}binding.rs
 s cannot be processed. ([row,col {unknown-source}]: [34,13])
  [java] [Fatal Error] StockQuotes.asmx?WSDL:1:133: The element type 
 META m
 ust be terminated by the matching end-tag /META.
  [java] Exception in thread main org.osoa.sca.ServiceRuntimeException: 
 jav
 a.lang.RuntimeException: 
 org.apache.tuscany.sca.contribution.service.Contributio
 nReadException: javax.wsdl.WSDLException: WSDLException (at 
 /wsdl:definitions/ws
 dl:import): faultCode=PARSER_ERROR: Problem parsing 
 'http://www.swanandmokashi.c
 om/HomePage/WebServices/StockQuotes.asmx?WSDL'.: 
 org.xml.sax.SAXParseException:
 The element type META must be terminated by the matching end-tag /META.
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:264)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at bigbank.BigBankClient.main(BigBankClient.java:30)
  [java] Caused by: java.lang.RuntimeException: 
 org.apache.tuscany.sca.contri
 bution.service.ContributionReadException: javax.wsdl.WSDLException: 
 WSDLExceptio
 n (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing 
 'h
 ttp://www.swanandmokashi.com/HomePage/WebServices/StockQuotes.asmx?WSDL'.: 
 org.x
 ml.sax.SAXParseException: The element type META must be terminated by the 
 matc
 hing end-tag /META.
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.loadOnDemand(WSDLModelResolver.java:290)
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.aggregate(WSDLModelResolver.java:223)
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.resolveModel(WSDLModelResolver.java:256)
  [java] at 
 org.apache.tuscany.sca.contribution.resolver.ExtensibleModelR
 esolver.resolveModel(ExtensibleModelResolver.java:150)
  [java] at 
 org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
 sor.resolve(WebServiceBindingProcessor.java:269)
  [java] at 
 org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
 sor.resolve(WebServiceBindingProcessor.java:59)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.DefaultStAXArti
 factProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifac
 tProcessorExtensionPoint.java:252)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
 rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.res
 olveContracts(BaseAssemblyProcessor.java:362)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
 e(CompositeProcessor.java:822)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
 e(CompositeProcessor.java:80)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
 rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
 r.resolve(CompositeDocumentProcessor.java:138)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
 r.resolve(CompositeDocumentProcessor.java:53)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleURLAr
 tifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86)
  [java] at 
 org.apache.tuscany.sca.contribution.service.impl.Contribution
 ServiceImpl.processResolvePhase(ContributionServiceImpl.java:464)

[jira] Resolved: (TUSCANY-2214) xml-bigbank demo relies on http://www.swanandmokashi.com which is not (currently) available

2008-04-14 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2214.
---

Resolution: Fixed

Fixed under 647669  647670 in trunk.

 xml-bigbank demo relies on http://www.swanandmokashi.com  which is not 
 (currently) available
 

 Key: TUSCANY-2214
 URL: https://issues.apache.org/jira/browse/TUSCANY-2214
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK5
Reporter: Simon Laws
Assignee: Raymond Feng
Priority: Minor
 Fix For: Java-SCA-1.2


 demo/xml-bingbank fails with the error below because the web site the demo is 
 trying to contact is not (currently) available to me. It may be temporary or 
 may be permanent. At a minimum we should note in the README that this can 
 happen and that the demo will not work it this is the case. 
 ant run
 Buildfile: build.xml
 run:
  [java] 09-Apr-2008 13:06:11 
 org.apache.tuscany.sca.contribution.processor.E
 xtensibleStAXArtifactProcessor read
  [java] WARNING: Element 
 {http://tuscany.apache.org/xmlns/sca/1.0}binding.rs
 s cannot be processed. ([row,col {unknown-source}]: [34,13])
  [java] [Fatal Error] StockQuotes.asmx?WSDL:1:133: The element type 
 META m
 ust be terminated by the matching end-tag /META.
  [java] Exception in thread main org.osoa.sca.ServiceRuntimeException: 
 jav
 a.lang.RuntimeException: 
 org.apache.tuscany.sca.contribution.service.Contributio
 nReadException: javax.wsdl.WSDLException: WSDLException (at 
 /wsdl:definitions/ws
 dl:import): faultCode=PARSER_ERROR: Problem parsing 
 'http://www.swanandmokashi.c
 om/HomePage/WebServices/StockQuotes.asmx?WSDL'.: 
 org.xml.sax.SAXParseException:
 The element type META must be terminated by the matching end-tag /META.
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:264)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at bigbank.BigBankClient.main(BigBankClient.java:30)
  [java] Caused by: java.lang.RuntimeException: 
 org.apache.tuscany.sca.contri
 bution.service.ContributionReadException: javax.wsdl.WSDLException: 
 WSDLExceptio
 n (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing 
 'h
 ttp://www.swanandmokashi.com/HomePage/WebServices/StockQuotes.asmx?WSDL'.: 
 org.x
 ml.sax.SAXParseException: The element type META must be terminated by the 
 matc
 hing end-tag /META.
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.loadOnDemand(WSDLModelResolver.java:290)
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.aggregate(WSDLModelResolver.java:223)
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.resolveModel(WSDLModelResolver.java:256)
  [java] at 
 org.apache.tuscany.sca.contribution.resolver.ExtensibleModelR
 esolver.resolveModel(ExtensibleModelResolver.java:150)
  [java] at 
 org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
 sor.resolve(WebServiceBindingProcessor.java:269)
  [java] at 
 org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
 sor.resolve(WebServiceBindingProcessor.java:59)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.DefaultStAXArti
 factProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifac
 tProcessorExtensionPoint.java:252)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
 rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.res
 olveContracts(BaseAssemblyProcessor.java:362)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
 e(CompositeProcessor.java:822)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
 e(CompositeProcessor.java:80)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
 rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
 r.resolve(CompositeDocumentProcessor.java:138)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
 r.resolve(CompositeDocumentProcessor.java:53)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleURLAr
 tifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86)
  [java] at 
 org.apache.tuscany.sca.contribution.service.impl.Contribution
 

[jira] Commented: (TUSCANY-2220) WSDL representations of binding.ws generated incorrectly.

2008-04-13 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2220:
---

I checked in a fix into trunk for TUSCANY-2220 under r647623. It now uses the 
binding uri to popluate the generated port soap:address.

I'll let the Release Manager to decide if he wants to merge it into 1.2 branch. 


 WSDL representations of binding.ws generated incorrectly.
 -

 Key: TUSCANY-2220
 URL: https://issues.apache.org/jira/browse/TUSCANY-2220
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Embedded Runtime
Affects Versions: Java-SCA-1.2
 Environment: Websphere 6.1.0.14 on AIX, jdk150_10
 Jetty on Windows XP x86, jdk150_10
 Websphere on Windows XP x86, jdk150_10
 Tomcat on Windows XP x86. jdk150_10
Reporter: Dave Sowerby
 Fix For: Java-SCA-1.2


 WSDL representations of binding.ws generated incorrectly.
 I'm currently facing issues when attmepting to utilise the wsdl
 generated by a service exposed using binding.ws, when I use wsdl2java
 with this wsdl I get the following exception:
 IWAB0399E Error in generating Java from WSDL:  java.io.IOException:
 Emitter failure.  Cannot find endpoint address in port
 ServiceRequestPortType__SOAPHTTPPort in service
 ServiceRequestPortType__ServiceLocator
java.io.IOException: Emitter failure.  Cannot find endpoint
 address in port ServiceRequestPortType__SOAPHTTPPort in service
 ServiceRequestPortType__ServiceLocator
at 
 org.apache.axis.wsdl.toJava.JavaServiceImplWriter.writeFileBody(JavaServiceImplWriter.java:189)
at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127)
at 
 org.apache.axis.wsdl.toJava.JavaServiceWriter.generate(JavaServiceWriter.java:112)
at 
 org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421)
at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:476)
at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362)
at java.lang.Thread.run(Unknown Source)
 I've diffed a previously functioning wsdl against the currently (RC3a)
 generated wsdl file, the difference causing this problem appears to be
 the additional lines of:
  wsdl:service name=ServiceRequestPortType__Service
wsdl:port name=ServiceRequestPortType__SOAPHTTPPort
 binding=ns2:ServiceRequestPortType__SOAPBinding
/wsdl:port
  /wsdl:service
 Which without an address is causing wsdl2java to fail.

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


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



[jira] Assigned: (TUSCANY-2219) Patch support wsjar in host embedded

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2219:
-

Assignee: Raymond Feng

 Patch support wsjar in host embedded
 --

 Key: TUSCANY-2219
 URL: https://issues.apache.org/jira/browse/TUSCANY-2219
 Project: Tuscany
  Issue Type: Improvement
  Components: Java SCA Embedded Runtime
Affects Versions: Java-SCA-1.2
 Environment: Tuscany 1.2-incubating RC3b, WAS 6.1
Reporter: Nishant Joshi
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2


 When you need to call with SCADomain under structure like
 my_war.ear/my.war/WEB-INF/lib/some_jar_under_war.jar!/my.composite
 then your contributionArtifactURL will comes like wsjar:file:/C:/Program 
 Files/IBM/WebSphere/AppServer/profiles/bmw/installedApps/bmw/my_war.ear/my.war/WEB-INF/lib/some_jar_under_war.jar!/my.composite
  so... to resolve this issue somebody needs to apply patch in file 
 DefaultSCADomain.java and method is getContributionLocation the patch is 
 as below
  else if (jar.equals(protocol)) {
 // jar contribution
 String location = url.substring(4, url.lastIndexOf(!/));
 // workaround for evil url/uri from maven
 contributionURL = FileHelper.toFile(new 
 URL(location)).toURI().toURL();
 } else if (wsjar.equals(protocol)) {
 // wsjar contribution
 String location = url.substring(6, url.lastIndexOf(!/));
 // workaround for evil url/uri from maven
 contributionURL = FileHelper.toFile(new 
 URL(location)).toURI().toURL();
 
 } 

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


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



[jira] Resolved: (TUSCANY-2219) Patch support wsjar in host embedded

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2219.
---

Resolution: Fixed

Patch applied under r647238. Thank you for the contribution!

 Patch support wsjar in host embedded
 --

 Key: TUSCANY-2219
 URL: https://issues.apache.org/jira/browse/TUSCANY-2219
 Project: Tuscany
  Issue Type: Improvement
  Components: Java SCA Embedded Runtime
Affects Versions: Java-SCA-1.2
 Environment: Tuscany 1.2-incubating RC3b, WAS 6.1
Reporter: Nishant Joshi
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2


 When you need to call with SCADomain under structure like
 my_war.ear/my.war/WEB-INF/lib/some_jar_under_war.jar!/my.composite
 then your contributionArtifactURL will comes like wsjar:file:/C:/Program 
 Files/IBM/WebSphere/AppServer/profiles/bmw/installedApps/bmw/my_war.ear/my.war/WEB-INF/lib/some_jar_under_war.jar!/my.composite
  so... to resolve this issue somebody needs to apply patch in file 
 DefaultSCADomain.java and method is getContributionLocation the patch is 
 as below
  else if (jar.equals(protocol)) {
 // jar contribution
 String location = url.substring(4, url.lastIndexOf(!/));
 // workaround for evil url/uri from maven
 contributionURL = FileHelper.toFile(new 
 URL(location)).toURI().toURL();
 } else if (wsjar.equals(protocol)) {
 // wsjar contribution
 String location = url.substring(6, url.lastIndexOf(!/));
 // workaround for evil url/uri from maven
 contributionURL = FileHelper.toFile(new 
 URL(location)).toURI().toURL();
 
 } 

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


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



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

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2217:
-

Assignee: Raymond Feng

 Some null guards needed in MediatorImpl
 ---

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

 Attachments: 2217.patch


 I think we should add guards to MediatorImpl.mediate() so that:
 - We don't do the introspectType(source) if 'source' is null
 - We simply return 'source' if 'targetDataType' is null
 While, for some methods, we might put the burden on the caller to check, this 
 method is already one that can handle nulls for certain objs, and we want to 
 possibly allow transforming a null
 'source', so it seems better to make the mediate() method itself more robust.
 I'll attach a patch.

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


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



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

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2085:
-

Assignee: Raymond Feng

 ConcurentModExc in DefaultDataBindingExtensionPoint 
 

 Key: TUSCANY-2085
 URL: https://issues.apache.org/jira/browse/TUSCANY-2085
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Assignee: Raymond Feng
Priority: Minor
 Fix For: Java-SCA-Next

 Attachments: 2085.patch


 Get an exception like the following, 
 java.util.ConcurrentModificationException
 at java.util.AbstractList$SimpleListIterator.next(Unknown Source)at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:223)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSFaultExceptionMapper.introspectFaultDataType(JAXWSFaultExceptionMapper.java:214)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.introspectFaultTypes(JAXWSJavaInterfaceProcessor.java:178)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:90)
 at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:91)
 as this thread, A, is in a for-loop looping through 'databindings'
  public boolean introspectType(DataType dataType, Annotation[] annotations, 
 boolean isException) {
 loadDataBindings();
 for (DataBinding binding : databindings) {
 while another thread, B, is still in loadDataBindings() and is still adding 
 to the databindings ArrayList.
 I'm working around this by putting a lock around the whole body  of 
 loadDataBindings()
 private final byte[] loadingLock = new byte[0];
 ...
 private void loadDataBindings() {
 synchronized (loadingLock) {
 if (loadedDataBindings)
 return;
...
}
}
 Another option might be to change addDataBinding() to look at the 'bindings' 
 Map before adding to 'databindings'.   
 I'll attach a patch and leave it for a second opinion.  

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


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



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

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2085:
---

To achieve the same purpose as Scott proposed, I would just simply add 
synchronized for loadDataBindings() method. We just have to make it atomic. I 
don't expect new data bindings are added dynamically at this point. 

 ConcurentModExc in DefaultDataBindingExtensionPoint 
 

 Key: TUSCANY-2085
 URL: https://issues.apache.org/jira/browse/TUSCANY-2085
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Assignee: Raymond Feng
Priority: Minor
 Fix For: Java-SCA-Next

 Attachments: 2085.patch


 Get an exception like the following, 
 java.util.ConcurrentModificationException
 at java.util.AbstractList$SimpleListIterator.next(Unknown Source)at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:223)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSFaultExceptionMapper.introspectFaultDataType(JAXWSFaultExceptionMapper.java:214)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.introspectFaultTypes(JAXWSJavaInterfaceProcessor.java:178)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:90)
 at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:91)
 as this thread, A, is in a for-loop looping through 'databindings'
  public boolean introspectType(DataType dataType, Annotation[] annotations, 
 boolean isException) {
 loadDataBindings();
 for (DataBinding binding : databindings) {
 while another thread, B, is still in loadDataBindings() and is still adding 
 to the databindings ArrayList.
 I'm working around this by putting a lock around the whole body  of 
 loadDataBindings()
 private final byte[] loadingLock = new byte[0];
 ...
 private void loadDataBindings() {
 synchronized (loadingLock) {
 if (loadedDataBindings)
 return;
...
}
}
 Another option might be to change addDataBinding() to look at the 'bindings' 
 Map before adding to 'databindings'.   
 I'll attach a patch and leave it for a second opinion.  

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


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



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

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2085.
---

Resolution: Fixed

Fixed under rr647242. Thanks for the patch. 

 ConcurentModExc in DefaultDataBindingExtensionPoint 
 

 Key: TUSCANY-2085
 URL: https://issues.apache.org/jira/browse/TUSCANY-2085
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Data Binding Runtime
Affects Versions: Java-SCA-1.1
Reporter: Scott Kurz
Assignee: Raymond Feng
Priority: Minor
 Fix For: Java-SCA-Next

 Attachments: 2085.patch


 Get an exception like the following, 
 java.util.ConcurrentModificationException
 at java.util.AbstractList$SimpleListIterator.next(Unknown Source)at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensionPoint.introspectType(DefaultDataBindingExtensionPoint.java:223)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSFaultExceptionMapper.introspectFaultDataType(JAXWSFaultExceptionMapper.java:214)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.introspectFaultTypes(JAXWSJavaInterfaceProcessor.java:178)
 at 
 org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:90)
 at 
 org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl.introspectInterface(JavaInterfaceIntrospectorImpl.java:91)
 as this thread, A, is in a for-loop looping through 'databindings'
  public boolean introspectType(DataType dataType, Annotation[] annotations, 
 boolean isException) {
 loadDataBindings();
 for (DataBinding binding : databindings) {
 while another thread, B, is still in loadDataBindings() and is still adding 
 to the databindings ArrayList.
 I'm working around this by putting a lock around the whole body  of 
 loadDataBindings()
 private final byte[] loadingLock = new byte[0];
 ...
 private void loadDataBindings() {
 synchronized (loadingLock) {
 if (loadedDataBindings)
 return;
...
}
}
 Another option might be to change addDataBinding() to look at the 'bindings' 
 Map before adding to 'databindings'.   
 I'll attach a patch and leave it for a second opinion.  

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


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



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

2008-04-11 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2217.
---

Resolution: Fixed

Patch applied under r647246. Thanks for the patch.

 Some null guards needed in MediatorImpl
 ---

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

 Attachments: 2217.patch


 I think we should add guards to MediatorImpl.mediate() so that:
 - We don't do the introspectType(source) if 'source' is null
 - We simply return 'source' if 'targetDataType' is null
 While, for some methods, we might put the burden on the caller to check, this 
 method is already one that can handle nulls for certain objs, and we want to 
 possibly allow transforming a null
 'source', so it seems better to make the mediate() method itself more robust.
 I'll attach a patch.

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


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



[jira] Commented: (TUSCANY-2214) xml-bigbank demo relies on http://www.swanandmokashi.com which is not (currently) available

2008-04-10 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2214:
---

We could use http://www.webservicex.net/stockquote.asmx as an alternative. I'll 
try later on.

 xml-bigbank demo relies on http://www.swanandmokashi.com  which is not 
 (currently) available
 

 Key: TUSCANY-2214
 URL: https://issues.apache.org/jira/browse/TUSCANY-2214
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK5
Reporter: Simon Laws
Priority: Minor
 Fix For: Java-SCA-1.2


 demo/xml-bingbank fails with the error below because the web site the demo is 
 trying to contact is not (currently) available to me. It may be temporary or 
 may be permanent. At a minimum we should note in the README that this can 
 happen and that the demo will not work it this is the case. 
 ant run
 Buildfile: build.xml
 run:
  [java] 09-Apr-2008 13:06:11 
 org.apache.tuscany.sca.contribution.processor.E
 xtensibleStAXArtifactProcessor read
  [java] WARNING: Element 
 {http://tuscany.apache.org/xmlns/sca/1.0}binding.rs
 s cannot be processed. ([row,col {unknown-source}]: [34,13])
  [java] [Fatal Error] StockQuotes.asmx?WSDL:1:133: The element type 
 META m
 ust be terminated by the matching end-tag /META.
  [java] Exception in thread main org.osoa.sca.ServiceRuntimeException: 
 jav
 a.lang.RuntimeException: 
 org.apache.tuscany.sca.contribution.service.Contributio
 nReadException: javax.wsdl.WSDLException: WSDLException (at 
 /wsdl:definitions/ws
 dl:import): faultCode=PARSER_ERROR: Problem parsing 
 'http://www.swanandmokashi.c
 om/HomePage/WebServices/StockQuotes.asmx?WSDL'.: 
 org.xml.sax.SAXParseException:
 The element type META must be terminated by the matching end-tag /META.
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:264)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at bigbank.BigBankClient.main(BigBankClient.java:30)
  [java] Caused by: java.lang.RuntimeException: 
 org.apache.tuscany.sca.contri
 bution.service.ContributionReadException: javax.wsdl.WSDLException: 
 WSDLExceptio
 n (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing 
 'h
 ttp://www.swanandmokashi.com/HomePage/WebServices/StockQuotes.asmx?WSDL'.: 
 org.x
 ml.sax.SAXParseException: The element type META must be terminated by the 
 matc
 hing end-tag /META.
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.loadOnDemand(WSDLModelResolver.java:290)
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.aggregate(WSDLModelResolver.java:223)
  [java] at 
 org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
 r.resolveModel(WSDLModelResolver.java:256)
  [java] at 
 org.apache.tuscany.sca.contribution.resolver.ExtensibleModelR
 esolver.resolveModel(ExtensibleModelResolver.java:150)
  [java] at 
 org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
 sor.resolve(WebServiceBindingProcessor.java:269)
  [java] at 
 org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
 sor.resolve(WebServiceBindingProcessor.java:59)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.DefaultStAXArti
 factProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifac
 tProcessorExtensionPoint.java:252)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
 rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.res
 olveContracts(BaseAssemblyProcessor.java:362)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
 e(CompositeProcessor.java:822)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
 e(CompositeProcessor.java:80)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
 rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
 r.resolve(CompositeDocumentProcessor.java:138)
  [java] at 
 org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
 r.resolve(CompositeDocumentProcessor.java:53)
  [java] at 
 org.apache.tuscany.sca.contribution.processor.ExtensibleURLAr
 tifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86)
  [java] at 
 

[jira] Updated: (TUSCANY-1802) RMI Implementation Error Handling lost inner exception's detail information

2008-04-08 Thread Raymond Feng (JIRA)

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

Raymond Feng updated TUSCANY-1802:
--

Patch Info: [Patch Available]

 RMI Implementation Error Handling lost inner exception's detail information
 ---

 Key: TUSCANY-1802
 URL: https://issues.apache.org/jira/browse/TUSCANY-1802
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Java Implementation Extension
Reporter: Yang Sun
Assignee: Venkatakrishnan
 Fix For: Java-SCA-Next

 Attachments: 1802.patch


 Here is an email I sent to the tuscany user group. Raymond Feng confirms it 
 may be a potential bug. Please have a look.
 /--
 Hi,
 I am a new user of Tuscany and I am very excited with this great software. I 
 am trying to introduce it into my project and currently I am evaluate it with 
 every possible situations. 
 Currently, I met a small problem with the spring implementation. I am not 
 sure if I understand the background and configure the composites right. 
 Please correct me if I make anything wrong. 
 The problem I met is that I cannot get the detailed original exception when 
 the server-side throw any kinds of exceptions. After a rough looking at the 
 src code and debugging, I see the following code in SpringInvoker.java :
 ---
 private Object doInvoke(Object payload) throws SpringInvocationException {
 if (theMethod == null)
 setupMethod(); 
 if (badInvoker)
 throw new SpringInvocationException(Spring invoker incorrectly 
 configured);
 // Invoke the method on the Spring bean using the payload, returning 
 the results 
 try {
 Object ret;
 if (payload != null  !payload.getClass().isArray()) {
 ret = theMethod.invoke(bean, payload);
 } else {
 ret = theMethod.invoke(bean, (Object[])payload);
 }
 return ret;
 } catch (InvocationTargetException e) {
 throw new SpringInvocationException(e.getMessage());
 } catch (Exception e) { 
 throw new SpringInvocationException(e.getMessage());
 }
 } // end method doInvoke
  
 When the invoked method throw an exception (checked or unchecked), the 
 program flow will go to the InvocationTargetException exception handler. Then 
 the program only put the message of the original message to the wrapper 
 exception SpringInvocationException. The detailed information of the original 
 exception is missing. I am thinking it is here that will lost the detailed 
 information of the original exception detail. 
 The reason for me to bring this question is that if we cannot get the 
 detailed information of the original exception, how can we deal with the 
 application exceptions (such as NotEnoughMoneyException)? The only thing I 
 can get is the java.lang.reflect.InvocationTargetException wrapped in 
 java.rmi.UnexpectedException. And with those information, I cannot get the 
 right information to make the further decision in the program.
 I am not sure whether I got the right point or if I misunderstand anything. 
 Please give me some suggestions on this problem. 
 Best Regards,
 Yang Sun
 /

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


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



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

2008-04-08 Thread Raymond Feng (JIRA)

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

Raymond Feng updated TUSCANY-2109:
--

Patch Info: [Patch Available]

 Conflicts between component reference interface and promoted composite 
 reference interface are not detected 
 

 Key: TUSCANY-2109
 URL: https://issues.apache.org/jira/browse/TUSCANY-2109
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.1
 Environment: All
Reporter: Simon Nash
 Fix For: Java-SCA-Next

 Attachments: jira2109.patch, jira2109.zip


 See TUSCANY-2033 for the background to this problem.
 When a component reference defined with interface.java (either explicitly 
 or implicitly by introspection) is promoted to a composite reference defined 
 with interface.wsdl, and there is a namespace conflict between the 
 component reference's interface.java and the composite reference's 
 interface.wsdl. this conflict should be diagnosed as an error because it 
 violates the spec rule that an interface specified on a composite reference 
 must be a compatible superset of the interface of the promoted component 
 reference. In this case, the composite interface is incompatible with the 
 component reference because it has a different namespace.
 There is code in CompositeWireBuilderImpl.connectCompositeReferences() to 
 handle connections between composite references and promoted compoennt 
 references. The only interface processing performed in this method is to copy 
 the component reference's interface contract to the composite reference's 
 interface contract if the composite reference does not have an interface 
 contract. Code should be added here to check for conflicts between the 
 composite reference's interface and the component reference's interface if 
 both interfaces are specified.
 Similar code should be added to 
 CompositeWireBuilderImpl.connectCompositeServices() to check that the 
 composite service interface is a compatible subset of the component service 
 interface as required by the spec. 

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


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



[jira] Assigned: (TUSCANY-1876) @Reference(required=false) ignored

2008-04-07 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-1876:
-

Assignee: Raymond Feng

 @Reference(required=false) ignored
 --

 Key: TUSCANY-1876
 URL: https://issues.apache.org/jira/browse/TUSCANY-1876
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.0
 Environment: Ubuntu 7.10, Gutsy Gibbon
 Sun JDK version 1.5.0_13
Reporter: Olivier Abdoun
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: optionalreference.tar.gz


 When specifying @Reference(required=false) and providing no reference for the 
 component in the composite, a proxy is injected in the component and next 
 call to the component fails with:
 org.osoa.sca.ServiceUnavailableException: No service invoker is available for 
 reference foo (bindingURI=null operation=getFoo).
   at 
 org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:192)
   at 
 org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addBindingInterceptor(RuntimeWireImpl.java:214)
   at 
 org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:156)
   at 
 org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:97)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:190)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:124)
   at $Proxy6.getFoo(Unknown Source)
   at foo.Baz.getBar(Baz.java:20)
   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:105)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:233)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:130)
   at $Proxy5.getBar(Unknown Source)
   at 
 foo.OptionalReferenceTestCase.testOptionalReference(OptionalReferenceTestCase.java:13)
   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 junit.framework.TestCase.runTest(TestCase.java:154)
   at junit.framework.TestCase.runBare(TestCase.java:127)
   at junit.framework.TestResult$1.protect(TestResult.java:106)
   at junit.framework.TestResult.runProtected(TestResult.java:124)
   at junit.framework.TestResult.run(TestResult.java:109)
   at junit.framework.TestCase.run(TestCase.java:118)
   at junit.framework.TestSuite.runTest(TestSuite.java:208)
   at junit.framework.TestSuite.run(TestSuite.java:203)
   at 
 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
   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)

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


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



[jira] Resolved: (TUSCANY-1876) @Reference(required=false) ignored

2008-04-07 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-1876.
---

Resolution: Fixed

This has been fixed now. We now doesn't inject a proxy any more for this case. 
Please verify.

 @Reference(required=false) ignored
 --

 Key: TUSCANY-1876
 URL: https://issues.apache.org/jira/browse/TUSCANY-1876
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.0
 Environment: Ubuntu 7.10, Gutsy Gibbon
 Sun JDK version 1.5.0_13
Reporter: Olivier Abdoun
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: optionalreference.tar.gz


 When specifying @Reference(required=false) and providing no reference for the 
 component in the composite, a proxy is injected in the component and next 
 call to the component fails with:
 org.osoa.sca.ServiceUnavailableException: No service invoker is available for 
 reference foo (bindingURI=null operation=getFoo).
   at 
 org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.createInvoker(RuntimeSCAReferenceBindingProvider.java:192)
   at 
 org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.addBindingInterceptor(RuntimeWireImpl.java:214)
   at 
 org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.initInvocationChains(RuntimeWireImpl.java:156)
   at 
 org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.getInvocationChains(RuntimeWireImpl.java:97)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.getInvocationChain(JDKInvocationHandler.java:190)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:124)
   at $Proxy6.getFoo(Unknown Source)
   at foo.Baz.getBar(Baz.java:20)
   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:105)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:233)
   at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:130)
   at $Proxy5.getBar(Unknown Source)
   at 
 foo.OptionalReferenceTestCase.testOptionalReference(OptionalReferenceTestCase.java:13)
   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 junit.framework.TestCase.runTest(TestCase.java:154)
   at junit.framework.TestCase.runBare(TestCase.java:127)
   at junit.framework.TestResult$1.protect(TestResult.java:106)
   at junit.framework.TestResult.runProtected(TestResult.java:124)
   at junit.framework.TestResult.run(TestResult.java:109)
   at junit.framework.TestCase.run(TestCase.java:118)
   at junit.framework.TestSuite.runTest(TestSuite.java:208)
   at junit.framework.TestSuite.run(TestSuite.java:203)
   at 
 org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
   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)

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


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



[jira] Resolved: (TUSCANY-1791) binding-notification-* samples don't work

2008-04-06 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-1791.
---

Resolution: Fixed

Fixed under r645254 in trunk.

 binding-notification-* samples don't work
 -

 Key: TUSCANY-1791
 URL: https://issues.apache.org/jira/browse/TUSCANY-1791
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.0
 Environment: Windows XP
Reporter: Simon Nash
Assignee: Ignacio Silva-Lepe
 Fix For: Java-SCA-1.2


 I tried to run the binding-notification-* samples from the 1.0 rc3a binary 
 distro  by following the README instructions.  I always get a failure on the 
 second application that starts.  I tried various different combinations of 
 which application to start first and which to start second and the failure 
 was consistent.  For example, if I start the consumer first on port 8083 and 
 then the producer second on port 8084, I see the following exception from the 
 producer:
 H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating\samples\binding-notification-producerjava
  -Dnotification.httpPort=8084 -cp 
 target\sample-binding-notification-producer-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR%
  notification.producer.TrafficAdvisoryServer
 org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException: 
 org.apache.tuscany.sca.binding.notification.encoding.EncodingException: 
 com.ctc.wstx.
 exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: 
 [1,0]
 at 
 org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:610)
 at 
 org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:95)
 at 
 org.apache.tuscany.sca.binding.notification.util.IOUtils.sendHttpRequest(IOUtils.java:51)
 at 
 org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl.newProducer(NotificationTypeManagerImpl.java:150)
 at 
 org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.deployProducer(NotificationReferenceBindingProvider.java:170)
 at 
 org.apache.tuscany.sca.binding.notification.NotificationBindingProviderFactory.referenceProviderStarted(NotificationBindingProviderFactory.java:186)
 at 
 org.apache.tuscany.sca.binding.notification.NotificationReferenceBindingProvider.start(NotificationReferenceBindingProvider.java:159)
 at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:456)
 at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:186)
 at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:230)
 at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
 at 
 notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
 Caused by: 
 org.apache.tuscany.sca.binding.notification.encoding.EncodingException: 
 com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col 
 {unknown-source}]: [1,0]
 at 
 org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:65)
 at 
 org.apache.tuscany.sca.binding.notification.NotificationTypeManagerImpl$InputStreamDecoder.read(NotificationTypeManagerImpl.java:607)
 ... 11 more
 Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at 
 [row,col {unknown-source}]: [1,0]
 at 
 com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:661)
 at 
 com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134)
 at 
 com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040)
 at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
 at 
 org.apache.tuscany.sca.binding.notification.encoding.EncodingUtils.decodeFromStream(EncodingUtils.java:60)
 ... 12 more
 org.osoa.sca.ServiceRuntimeException: java.lang.RuntimeException: 
 java.lang.RuntimeException: 
 org.apache.tuscany.sca.binding.notification.util.IOUtils$IOUtilsException: 
 org.apache.tuscany.sca.binding.notification.encoding.EncodingException: 
 com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col 
 {unknown-source}]: [1,0]
 at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
 at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69)
 at 
 notification.producer.TrafficAdvisoryServer.main(TrafficAdvisoryServer.java:31)
 Caused by: java.lang.RuntimeException: java.lang.RuntimeException: 
 

[jira] Resolved: (TUSCANY-2196) passing Java bean using a JSON binding

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2196.
---

Resolution: Invalid

Hi,

I tried the test case, it works fine. You seems to be confused by the display 
of the result. As shown below, you need to extract the result data by accessing 
all the fields. p + result +/p will only give you [object Object]. With 
the change in the HTML, I can see the strEmail ...

function contentCallBack(result) {
var handlerNode = document.getElementById(ReturnedContent);
handlerNode.innerHTML = p + result.strEmail + 
/p ;
}

Thanks,
Raymond

 passing Java bean using a JSON binding
 --

 Key: TUSCANY-2196
 URL: https://issues.apache.org/jira/browse/TUSCANY-2196
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA JSON-RPC Binding Extension
Affects Versions: Java-SCA-1.1
 Environment: Windows xp2
Reporter: Ashwini Kumar J
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: employee-det.war

   Original Estimate: 24h
  Remaining Estimate: 24h

 The service is exposed over JSON binding and will return a  java bean as a 
 response but as per my knowledge the bean is not properly converted to json 
 object as shown in the smd below:
 {SMDVersion:.1,objectName:EmployeeBOService,serviceType:JSON-RPC,serviceURL:http://localhost:8080/employee-det/EmployeeJSONService,methods:[{name:fetchEmployeeData,parameters:[{name:param0,type:STRING}]}]}
 Response:
 [object Object]
 Console output is:
 Apr 4, 2008 11:23:07 AM com.metaparadigm.jsonrpc.BeanSerializer analyzeBean
 INFO: analyzing com.infosys.poc.employeedata.EmployeeData

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


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



[jira] Assigned: (TUSCANY-2196) passing Java bean using a JSON binding

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2196:
-

Assignee: Raymond Feng

 passing Java bean using a JSON binding
 --

 Key: TUSCANY-2196
 URL: https://issues.apache.org/jira/browse/TUSCANY-2196
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA JSON-RPC Binding Extension
Affects Versions: Java-SCA-1.1
 Environment: Windows xp2
Reporter: Ashwini Kumar J
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: employee-det.war

   Original Estimate: 24h
  Remaining Estimate: 24h

 The service is exposed over JSON binding and will return a  java bean as a 
 response but as per my knowledge the bean is not properly converted to json 
 object as shown in the smd below:
 {SMDVersion:.1,objectName:EmployeeBOService,serviceType:JSON-RPC,serviceURL:http://localhost:8080/employee-det/EmployeeJSONService,methods:[{name:fetchEmployeeData,parameters:[{name:param0,type:STRING}]}]}
 Response:
 [object Object]
 Console output is:
 Apr 4, 2008 11:23:07 AM com.metaparadigm.jsonrpc.BeanSerializer analyzeBean
 INFO: analyzing com.infosys.poc.employeedata.EmployeeData

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


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



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

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2193:
-

Assignee: Raymond Feng

 NPE when configuring WSDL interface on component ref when the component has a 
 Composite impl
 

 Key: TUSCANY-2193
 URL: https://issues.apache.org/jira/browse/TUSCANY-2193
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Reporter: Scott Kurz
Assignee: Raymond Feng
Priority: Minor

 I noticed this with a more complicated example.  
 To reproduce more simply maybe, go to the SVN dir:  sca/itest/recursive
 and modify BComposite.composite so it looks like:
 composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
 targetNamespace=http://sample;
 xmlns:sample=http://sample;
 name=BComposite

 component name=BComponent
 implementation.composite name=sample:CComposite/
 reference name=PromotedRefX
interface.wsdl interface=http://blah#wsdl.interface(Blah) /
 /reference

 Note that you can put any old WSDL in there.   You shouldn't get far enough 
 for it to even matter.  
 You'll hit errors like:
 java.lang.NullPointerException
   at 
 org.apache.tuscany.sca.interfacedef.impl.InterfaceContractMapperImpl.checkCompatibility(InterfaceContractMapperImpl.java:155)
   at 
 org.apache.tuscany.sca.interfacedef.impl.InterfaceContractMapperImpl.isCompatible(InterfaceContractMapperImpl.java:271)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.reconcileReferences(CompositeConfigurationBuilderImpl.java:527)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.configureComponents(CompositeConfigurationBuilderImpl.java:250)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.configureComponents(CompositeConfigurationBuilderImpl.java:85)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl.build(CompositeBuilderImpl.java:97)

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


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



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

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2193.
---

Resolution: Fixed

Fixed under r644824

 NPE when configuring WSDL interface on component ref when the component has a 
 Composite impl
 

 Key: TUSCANY-2193
 URL: https://issues.apache.org/jira/browse/TUSCANY-2193
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Reporter: Scott Kurz
Assignee: Raymond Feng
Priority: Minor

 I noticed this with a more complicated example.  
 To reproduce more simply maybe, go to the SVN dir:  sca/itest/recursive
 and modify BComposite.composite so it looks like:
 composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
 targetNamespace=http://sample;
 xmlns:sample=http://sample;
 name=BComposite

 component name=BComponent
 implementation.composite name=sample:CComposite/
 reference name=PromotedRefX
interface.wsdl interface=http://blah#wsdl.interface(Blah) /
 /reference

 Note that you can put any old WSDL in there.   You shouldn't get far enough 
 for it to even matter.  
 You'll hit errors like:
 java.lang.NullPointerException
   at 
 org.apache.tuscany.sca.interfacedef.impl.InterfaceContractMapperImpl.checkCompatibility(InterfaceContractMapperImpl.java:155)
   at 
 org.apache.tuscany.sca.interfacedef.impl.InterfaceContractMapperImpl.isCompatible(InterfaceContractMapperImpl.java:271)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.reconcileReferences(CompositeConfigurationBuilderImpl.java:527)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.configureComponents(CompositeConfigurationBuilderImpl.java:250)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.configureComponents(CompositeConfigurationBuilderImpl.java:85)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl.build(CompositeBuilderImpl.java:97)

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


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



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

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2189:
---

I'm getting the NPE as the implemention invoker is in the invocation chain:

Caused by: java.lang.NullPointerException
at 
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78)
at 
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:110)
... 29 more

 Problems building the wire for a service implemented by Composite
 -

 Key: TUSCANY-2189
 URL: https://issues.apache.org/jira/browse/TUSCANY-2189
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Reporter: Scott Kurz
 Fix For: Java-SCA-Next

 Attachments: test.2189.jar


 Take something like this:
 composite name=OuterComposite
 component name=OuterCalculatorComponent
   service name=OuterCalculatorService
 binding.ws wsdlElement=/
   /service
   implementation.composite name=calc:InnerComposite/
 /component
 /composite
 composite name=InnerComposite
 service name=OuterCalculatorService 
 promote=CalculatorComponent/CalculatorService/
 component name=CalculatorComponent
 service name=CalculatorService/
 implementation.java class=calculator.CalculatorServiceImpl/
 /component
 /composite
 --
 I'm noticing that the wireTarget that ends up getting built for the wire from 
 the OuterCalculatorService service-side WS binding into the impl has a 
 wireTarget
 with a Composite impl. This causes a problem when 
 RuntimeWireImpl.initInvocationChains()  calls addImplementationInterceptor(); 
 we need a non-composite impl (Java impl) at this point to set up the 
 interceptor on the chain.
 Might it be appropriate to do something like what's done in 
 CompositeWireBuilderImpl.connectComponentReferences(), where we drill down 
 recursively to unwrap the Composite impl services?
 I looked at the 'recursive' itest and didn't see anything besides 
 binding.sca... so maybe we don't think we've gotten to this yet.
 In the cases it does work, with binding.sca, we must somehow be connected to 
 the inner-layer wire from the component in the nested Composite.

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


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



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

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2189:
-

Assignee: Raymond Feng

 Problems building the wire for a service implemented by Composite
 -

 Key: TUSCANY-2189
 URL: https://issues.apache.org/jira/browse/TUSCANY-2189
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Reporter: Scott Kurz
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: test.2189.jar


 Take something like this:
 composite name=OuterComposite
 component name=OuterCalculatorComponent
   service name=OuterCalculatorService
 binding.ws wsdlElement=/
   /service
   implementation.composite name=calc:InnerComposite/
 /component
 /composite
 composite name=InnerComposite
 service name=OuterCalculatorService 
 promote=CalculatorComponent/CalculatorService/
 component name=CalculatorComponent
 service name=CalculatorService/
 implementation.java class=calculator.CalculatorServiceImpl/
 /component
 /composite
 --
 I'm noticing that the wireTarget that ends up getting built for the wire from 
 the OuterCalculatorService service-side WS binding into the impl has a 
 wireTarget
 with a Composite impl. This causes a problem when 
 RuntimeWireImpl.initInvocationChains()  calls addImplementationInterceptor(); 
 we need a non-composite impl (Java impl) at this point to set up the 
 interceptor on the chain.
 Might it be appropriate to do something like what's done in 
 CompositeWireBuilderImpl.connectComponentReferences(), where we drill down 
 recursively to unwrap the Composite impl services?
 I looked at the 'recursive' itest and didn't see anything besides 
 binding.sca... so maybe we don't think we've gotten to this yet.
 In the cases it does work, with binding.sca, we must somehow be connected to 
 the inner-layer wire from the component in the nested Composite.

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


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



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

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2189.
---

Resolution: Fixed

Fixed under r644934.

 Problems building the wire for a service implemented by Composite
 -

 Key: TUSCANY-2189
 URL: https://issues.apache.org/jira/browse/TUSCANY-2189
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Reporter: Scott Kurz
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: test.2189.jar


 Take something like this:
 composite name=OuterComposite
 component name=OuterCalculatorComponent
   service name=OuterCalculatorService
 binding.ws wsdlElement=/
   /service
   implementation.composite name=calc:InnerComposite/
 /component
 /composite
 composite name=InnerComposite
 service name=OuterCalculatorService 
 promote=CalculatorComponent/CalculatorService/
 component name=CalculatorComponent
 service name=CalculatorService/
 implementation.java class=calculator.CalculatorServiceImpl/
 /component
 /composite
 --
 I'm noticing that the wireTarget that ends up getting built for the wire from 
 the OuterCalculatorService service-side WS binding into the impl has a 
 wireTarget
 with a Composite impl. This causes a problem when 
 RuntimeWireImpl.initInvocationChains()  calls addImplementationInterceptor(); 
 we need a non-composite impl (Java impl) at this point to set up the 
 interceptor on the chain.
 Might it be appropriate to do something like what's done in 
 CompositeWireBuilderImpl.connectComponentReferences(), where we drill down 
 recursively to unwrap the Composite impl services?
 I looked at the 'recursive' itest and didn't see anything besides 
 binding.sca... so maybe we don't think we've gotten to this yet.
 In the cases it does work, with binding.sca, we must somehow be connected to 
 the inner-layer wire from the component in the nested Composite.

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


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



[jira] Resolved: (TUSCANY-2186) @OneWay over binding.ws arguments not being serialized properly

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2186.
---

Resolution: Fixed

Fixed under r644935. Thanks.

 @OneWay over binding.ws arguments not being serialized properly
 ---

 Key: TUSCANY-2186
 URL: https://issues.apache.org/jira/browse/TUSCANY-2186
 Project: Tuscany
  Issue Type: Bug
Reporter: Lou Amodeo
Assignee: Raymond Feng

 I am finding that @Oneway operations over binding.ws are not having method 
 arguments marshalled properly apparently due to a change in  the sequence of 
 interceptors. Previously the NonBlockingInterceptor was being added after the 
 DataTransformationInterceptor.  The data transformation needs to occur prior
 to the thread switch to the non-blocking interceptor to allow Axiom to 
 marshall  the message payload before the thread switch.  
 In the Tuscany revision level  I have R634808 the 
 DataBindingRuntimeWireProcessor does this:
 chain.addInterceptor(0, interceptor);
 In the past the index of 0 would have put the databinding interceptor at the 
 front of the interceptor chain, ahead of the NonBlockingInterceptor (which 
 has already been added at this point).  However in this Tuscany revision the 
 index is ignored and instead a new phase-based ordering mechanism is used.  
 The above call to addInterceptor obviously wasn't changed yet at this level 
 to replace the index with a phase.  It has been changed in the trunk and now 
 looks like this:
 String phase =
 (wire.getSource().getContract() instanceof ComponentReference) ? 
 Phase.REFERENCE_INTERFACE
 : Phase.SERVICE_INTERFACE;
 chain.addInterceptor(phase, interceptor);
 RuntimeWireImpl is doing this to add the NonBlockingInterceptor:
 chain.addInterceptor(Phase.SERVICE_BINDING, new 
 NonBlockingInterceptor(workScheduler));
 Here are the relevant phase definitions in PhaseManager:
 private final static String[] SYSTEM_SERVICE_PHASES =
 {Phase.SERVICE_BINDING, Phase.SERVICE_POLICY, 
 Phase.SERVICE_INTERFACE, Phase.SERVICE};
 I assume this is an ordered list, so this means the NonBlockingInterceptor 
 (phase SERVICE_BINDING) is before the DataBindingInterceptor (phase 
 SERVICE_INTERFACE), which is still opposite of what we want to solve this 
 problem.   
 Thanks for your help! 
  

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


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



[jira] Commented: (TUSCANY-2204) helloworld-ws-sdo fails with exception, using 1.2, RC3 candidate

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2204:
---

Confirmed here. It works.

 helloworld-ws-sdo fails with exception, using 1.2, RC3 candidate
 

 Key: TUSCANY-2204
 URL: https://issues.apache.org/jira/browse/TUSCANY-2204
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
Reporter: haleh mahbod
Priority: Critical
 Fix For: Java-SCA-1.2


 ant run results in 
 C:\tuscany\sca\tuscany-sca-1.2-incubating\samples\helloworld-ws-sdoant run
 Buildfile: build.xml
 run:
  [java] Injected helloWorldService
  [java] Called getGreetings
  [java] Exception in thread main java.lang.IllegalArgumentException: 
 Pass-
 by-value is not supported for the given object
  [java] at 
 org.apache.tuscany.sca.databinding.javabeans.JavaBeansDataBin
 ding.copy(JavaBeansDataBinding.java:102)
  [java] at 
 org.apache.tuscany.sca.databinding.DefaultDataBindingExtensio
 nPoint$LazyDataBinding.copy(DefaultDataBindingExtensionPoint.java:171)
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.copy(PassByValueInterceptor.java:235)
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.copyFault(PassByValueInterceptor.java:130)
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.invoke(PassByValueInterceptor.java:115)
  [java] at 
 org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.inv
 oke(SCABindingInvoker.java:61)
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.invoke(PassByValueInterceptor.java:108)
  [java] at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.i
 nvoke(JDKInvocationHandler.java:286)
  [java] at 
 org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.i
 nvoke(JDKInvocationHandler.java:154)
  [java] at $Proxy5.getGreetings(Unknown Source)
  [java] at helloworld.HelloWorldClient.main(HelloWorldClient.java:39)
  [java] Caused by: java.io.NotSerializableException: 
 org.apache.axiom.om.imp
 l.llom.OMElementImpl
  [java] at 
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.ja
 va:1081)
  [java] at 
 java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStr
 eam.java:1375)
  [java] at 
 java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream
 .java:1347)
  [java] at 
 java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputSt
 ream.java:1290)
  [java] at 
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.ja
 va:1079)
  [java] at 
 java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStr
 eam.java:1375)
  [java] at 
 java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStr
 eam.java:391)
  [java] at java.lang.Throwable.writeObject(Throwable.java:649)
  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  [java] at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
 sorImpl.java:39)
  [java] at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
 hodAccessorImpl.java:25)
  [java] at java.lang.reflect.Method.invoke(Method.java:585)
  [java] at 
 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass
 .java:917)
  [java] at 
 java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream
 .java:1339)
  [java] at 
 java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputSt
 ream.java:1290)
  [java] at 
 java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.ja
 va:1079)
  [java] at 
 java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStr
 eam.java:1375)
  [java] at 
 java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStr
 eam.java:391)
  [java] at java.lang.Throwable.writeObject(Throwable.java:649)
  [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  [java] at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
 sorImpl.java:39)
  [java] at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
 hodAccessorImpl.java:25)
  [java] at java.lang.reflect.Method.invoke(Method.java:585)
  [java] at 
 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass
 .java:917)
  [java] at 
 java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream
 .java:1339)
  [java] at 
 java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputSt
 ream.java:1290)
  [java] at 
 

[jira] Commented: (TUSCANY-2200) Sample calculator-webapp fails in WAS 6.1

2008-04-04 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2200:
---

I'm the guy who I added the FIXME :-). But I don't tthink the problem reported 
by this JIRA is caused by such a usage. The XPathFactory APIs have been part of 
the JDK since 1.5. I just tested it with SUN JDK 1.5.x, 1.6.x and IBM JDK 
1.5.x. The method is successful in all of three JDKs without additional jars on 
the classpath.

The XPath javadoc also says:

public static final XPathFactory newInstance()Get a new XPathFactory instance 
using the default object model, DEFAULT_OBJECT_MODEL_URI, the W3C DOM.

This method is functionally equivalent to:

   newInstance(DEFAULT_OBJECT_MODEL_URI)
 Since the implementation for the W3C DOM is always available, this method will 
never fail.

Returns:
Instance of an XPathFactory.


 Sample calculator-webapp fails in WAS 6.1
 -

 Key: TUSCANY-2200
 URL: https://issues.apache.org/jira/browse/TUSCANY-2200
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
Reporter: Luciano Resende
 Fix For: Java-SCA-1.2


 Exception = org.osoa.sca.ServiceRuntimeException
 Source = com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.init
 probeid = 111
 Stack Dump = org.osoa.sca.ServiceRuntimeException: 
 java.lang.reflect.InvocationTargetException
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82)
   at 
 org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:216)
   at 
 org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50)
   at 
 com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.init(FilterInstanceWrapper.java:142)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager._loadFilter(WebAppFilterManager.java:465)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter(WebAppFilterManager.java:379)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterInstanceWrapper(WebAppFilterManager.java:238)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterChain(WebAppFilterManager.java:296)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:721)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:673)
   at 
 com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:688)
   at 
 com.ibm.ws.wswebcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:101)
   at 
 com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.invokeFilters(DefaultExtensionProcessor.java:758)
   at 
 com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:471)
   at 
 com.ibm.ws.wswebcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:113)
   at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3276)
   at 
 com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:267)
   at 
 com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:811)
   at 
 com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455)
   at 
 com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113)
   at 
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454)
   at 
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383)
   at 
 com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:263)
   at 
 com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
   at 
 com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
   at 
 com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
   at 
 com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
   at 
 com.ibm.io.async.AsyncChannelFuture$1.run(AsyncChannelFuture.java:205)
   at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)
 Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
   at 
 

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

2008-04-03 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2193:
---

I see the same problem when I look into TUSCANY-2189.

 NPE when configuring WSDL interface on component ref when the component has a 
 Composite impl
 

 Key: TUSCANY-2193
 URL: https://issues.apache.org/jira/browse/TUSCANY-2193
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Core Runtime
Reporter: Scott Kurz
Priority: Minor

 I noticed this with a more complicated example.  
 To reproduce more simply maybe, go to the SVN dir:  sca/itest/recursive
 and modify BComposite.composite so it looks like:
 composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
 targetNamespace=http://sample;
 xmlns:sample=http://sample;
 name=BComposite

 component name=BComponent
 implementation.composite name=sample:CComposite/
 reference name=PromotedRefX
interface.wsdl interface=http://blah#wsdl.interface(Blah) /
 /reference

 Note that you can put any old WSDL in there.   You shouldn't get far enough 
 for it to even matter.  
 You'll hit errors like:
 java.lang.NullPointerException
   at 
 org.apache.tuscany.sca.interfacedef.impl.InterfaceContractMapperImpl.checkCompatibility(InterfaceContractMapperImpl.java:155)
   at 
 org.apache.tuscany.sca.interfacedef.impl.InterfaceContractMapperImpl.isCompatible(InterfaceContractMapperImpl.java:271)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.reconcileReferences(CompositeConfigurationBuilderImpl.java:527)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.configureComponents(CompositeConfigurationBuilderImpl.java:250)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeConfigurationBuilderImpl.configureComponents(CompositeConfigurationBuilderImpl.java:85)
   at 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl.build(CompositeBuilderImpl.java:97)

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


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



[jira] Assigned: (TUSCANY-2186) @OneWay over binding.ws arguments not being serialized properly

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2186:
-

Assignee: Raymond Feng

 @OneWay over binding.ws arguments not being serialized properly
 ---

 Key: TUSCANY-2186
 URL: https://issues.apache.org/jira/browse/TUSCANY-2186
 Project: Tuscany
  Issue Type: Bug
Reporter: Lou Amodeo
Assignee: Raymond Feng

 I am finding that @Oneway operations over binding.ws are not having method 
 arguments marshalled properly apparently due to a change in  the sequence of 
 interceptors. Previously the NonBlockingInterceptor was being added after the 
 DataTransformationInterceptor.  The data transformation needs to occur prior
 to the thread switch to the non-blocking interceptor to allow Axiom to 
 marshall  the message payload before the thread switch.  
 In the Tuscany revision level  I have R634808 the 
 DataBindingRuntimeWireProcessor does this:
 chain.addInterceptor(0, interceptor);
 In the past the index of 0 would have put the databinding interceptor at the 
 front of the interceptor chain, ahead of the NonBlockingInterceptor (which 
 has already been added at this point).  However in this Tuscany revision the 
 index is ignored and instead a new phase-based ordering mechanism is used.  
 The above call to addInterceptor obviously wasn't changed yet at this level 
 to replace the index with a phase.  It has been changed in the trunk and now 
 looks like this:
 String phase =
 (wire.getSource().getContract() instanceof ComponentReference) ? 
 Phase.REFERENCE_INTERFACE
 : Phase.SERVICE_INTERFACE;
 chain.addInterceptor(phase, interceptor);
 RuntimeWireImpl is doing this to add the NonBlockingInterceptor:
 chain.addInterceptor(Phase.SERVICE_BINDING, new 
 NonBlockingInterceptor(workScheduler));
 Here are the relevant phase definitions in PhaseManager:
 private final static String[] SYSTEM_SERVICE_PHASES =
 {Phase.SERVICE_BINDING, Phase.SERVICE_POLICY, 
 Phase.SERVICE_INTERFACE, Phase.SERVICE};
 I assume this is an ordered list, so this means the NonBlockingInterceptor 
 (phase SERVICE_BINDING) is before the DataBindingInterceptor (phase 
 SERVICE_INTERFACE), which is still opposite of what we want to solve this 
 problem.   
 Thanks for your help! 
  

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


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



[jira] Commented: (TUSCANY-1451) Fix the algorithm to determine references for an unannotated java class

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-1451:
---

My understanding is that @Service cannot be applied to interfaces. 

 Fix the algorithm to determine references for an unannotated java class
 ---

 Key: TUSCANY-1451
 URL: https://issues.apache.org/jira/browse/TUSCANY-1451
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Java Implementation Extension
Affects Versions: Java-SCA-Next
Reporter: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-1451-testcase.patch, TUSCANY-1451.patch


 http://www.osoa.org/display/Main/Errata+for+Java+Component+Implementation+V1.00
 4. Fix and clarify algorithm for determining references of an unannotated 
 POJO (section 1.2.7)
 Replace the algorithm on lines 369-377 with the following:
 1) If the Java type is an interface annotated with @Remotable, then it's a
 reference.
 2) Otherwise, if the Java type is an array whose element type is an
 interface annotated with @Remotable, then it's a reference.
 3) Otherwise, if the Java type is a java.util.Collection or a 
 sub-interface
 or sub-class of it, if the parameterized type of the collection is an
 interface annotated with @Remotable, then it's a reference.
 4) Otherwise it's a property.

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


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



[jira] Assigned: (TUSCANY-1451) Fix the algorithm to determine references for an unannotated java class

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-1451:
-

Assignee: Raymond Feng

 Fix the algorithm to determine references for an unannotated java class
 ---

 Key: TUSCANY-1451
 URL: https://issues.apache.org/jira/browse/TUSCANY-1451
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Java Implementation Extension
Affects Versions: Java-SCA-Next
Reporter: Raymond Feng
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-1451-testcase.patch, TUSCANY-1451.patch


 http://www.osoa.org/display/Main/Errata+for+Java+Component+Implementation+V1.00
 4. Fix and clarify algorithm for determining references of an unannotated 
 POJO (section 1.2.7)
 Replace the algorithm on lines 369-377 with the following:
 1) If the Java type is an interface annotated with @Remotable, then it's a
 reference.
 2) Otherwise, if the Java type is an array whose element type is an
 interface annotated with @Remotable, then it's a reference.
 3) Otherwise, if the Java type is a java.util.Collection or a 
 sub-interface
 or sub-class of it, if the parameterized type of the collection is an
 interface annotated with @Remotable, then it's a reference.
 4) Otherwise it's a property.

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


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



[jira] Resolved: (TUSCANY-1451) Fix the algorithm to determine references for an unannotated java class

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-1451.
---

Resolution: Fixed

Patch applied under r644031. Thanks,

 Fix the algorithm to determine references for an unannotated java class
 ---

 Key: TUSCANY-1451
 URL: https://issues.apache.org/jira/browse/TUSCANY-1451
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Java Implementation Extension
Affects Versions: Java-SCA-Next
Reporter: Raymond Feng
Assignee: Raymond Feng
 Fix For: Java-SCA-Next

 Attachments: TUSCANY-1451-testcase.patch, TUSCANY-1451.patch


 http://www.osoa.org/display/Main/Errata+for+Java+Component+Implementation+V1.00
 4. Fix and clarify algorithm for determining references of an unannotated 
 POJO (section 1.2.7)
 Replace the algorithm on lines 369-377 with the following:
 1) If the Java type is an interface annotated with @Remotable, then it's a
 reference.
 2) Otherwise, if the Java type is an array whose element type is an
 interface annotated with @Remotable, then it's a reference.
 3) Otherwise, if the Java type is a java.util.Collection or a 
 sub-interface
 or sub-class of it, if the parameterized type of the collection is an
 interface annotated with @Remotable, then it's a reference.
 4) Otherwise it's a property.

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


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



[jira] Assigned: (TUSCANY-2187) Surefire fails because of java.endorsed.dirs setting

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2187:
-

Assignee: Raymond Feng

 Surefire fails because of java.endorsed.dirs setting
 

 Key: TUSCANY-2187
 URL: https://issues.apache.org/jira/browse/TUSCANY-2187
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
 Environment: Windows XP with Java home C:\Program 
 Files\Java\jdk1.5.0_10
 Maven version: 2.0.8
Reporter: Andreas Veithen
Assignee: Raymond Feng
Priority: Minor

 In revision 642377, the following setting was added to the Surefire plugin 
 configuration in sdo/pom.xml:
 argLine-Djava.endorsed.dirs=${java.endorsed.dirs}/argLine
 On systems where the path to the Java directory contains spaces (as is 
 usually the case on most Windows systems), execution of the tests (e.g. in 
 sdo/impl) fails with the following kind of error:
 java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_10\jre\lib\endorsed
 I tried to add quotes to the argument, but I couldn't figure out how to make 
 Maven understand that the value of argLine is a single argument.

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


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



[jira] Commented: (TUSCANY-2187) Surefire fails because of java.endorsed.dirs setting

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2187:
---

It seems that SUN JDK 5.x has the java.endorsed.dirs system property set by the 
jdk. On Wondows, the path contains spaces but surefire plugin cannot handle it 
correctly. 

The property is used to pass endorsed dirs to enable the workaround for SUN JDK 
1.4.x as reported in TUSCANY-1925. I'll fix it with the following:

argLine-Djava.endorsed.dirs=${endorsed.dirs}/argLine

Now you need to use the commands below to work around TUSCANY-1925:

set MAVEN_OPTS=-Dendorsed.dirs=directory to host xercesImpl-2.8.1.jar and 
xml-apis-1.3.03.jar


 Surefire fails because of java.endorsed.dirs setting
 

 Key: TUSCANY-2187
 URL: https://issues.apache.org/jira/browse/TUSCANY-2187
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
 Environment: Windows XP with Java home C:\Program 
 Files\Java\jdk1.5.0_10
 Maven version: 2.0.8
Reporter: Andreas Veithen
Assignee: Raymond Feng
Priority: Minor

 In revision 642377, the following setting was added to the Surefire plugin 
 configuration in sdo/pom.xml:
 argLine-Djava.endorsed.dirs=${java.endorsed.dirs}/argLine
 On systems where the path to the Java directory contains spaces (as is 
 usually the case on most Windows systems), execution of the tests (e.g. in 
 sdo/impl) fails with the following kind of error:
 java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_10\jre\lib\endorsed
 I tried to add quotes to the argument, but I couldn't figure out how to make 
 Maven understand that the value of argLine is a single argument.

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


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



[jira] Updated: (TUSCANY-2187) Surefire fails because of java.endorsed.dirs setting

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng updated TUSCANY-2187:
--

Priority: Critical  (was: Minor)

 Surefire fails because of java.endorsed.dirs setting
 

 Key: TUSCANY-2187
 URL: https://issues.apache.org/jira/browse/TUSCANY-2187
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
 Environment: Windows XP with Java home C:\Program 
 Files\Java\jdk1.5.0_10
 Maven version: 2.0.8
Reporter: Andreas Veithen
Assignee: Raymond Feng
Priority: Critical

 In revision 642377, the following setting was added to the Surefire plugin 
 configuration in sdo/pom.xml:
 argLine-Djava.endorsed.dirs=${java.endorsed.dirs}/argLine
 On systems where the path to the Java directory contains spaces (as is 
 usually the case on most Windows systems), execution of the tests (e.g. in 
 sdo/impl) fails with the following kind of error:
 java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_10\jre\lib\endorsed
 I tried to add quotes to the argument, but I couldn't figure out how to make 
 Maven understand that the value of argLine is a single argument.

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


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



[jira] Commented: (TUSCANY-1925) Cannot build or run with Sun's 1.4.2 JDK

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-1925:
---

You can now run the build for SUN JDK 1.4.x as follows:

set MAVEN_OPTS=-Dendorsed.dirs=directory to host xercesImpl-2.8.1.jar and 
xml-apis-1.3.03.jar 
mvn clean install 


 Cannot build or run with Sun's 1.4.2 JDK
 

 Key: TUSCANY-1925
 URL: https://issues.apache.org/jira/browse/TUSCANY-1925
 Project: Tuscany
  Issue Type: Bug
  Components: Java SDO Implementation
Affects Versions: Java-SDO-Next
 Environment: WinXP, Sun's 1.4.2 JDK
Reporter: Chris Mildebrandt

 Hello,
 When I extract the latest SDO and attempt to build it with the Sun JDK 
 1.4.2_15, I get the following error in the test cases:
 Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.01 sec  
 FAILURE!
 Running org.apache.tuscany.sdo.test.XSDHelperTestCase
 java.lang.NullPointerException
 at 
 org.apache.crimson.tree.ElementNode2.getAttributeNodeNS(ElementNode2.java:432)
 at 
 org.apache.crimson.tree.ElementNode2.hasAttributeNS(ElementNode2.java:388)
 at 
 org.apache.tuscany.sdo.helper.SDOXSDEcoreBuilder.getEcoreAttribute(SDOXSDEcoreBuilder.java:432)
 at 
 org.eclipse.xsd.ecore.XSDEcoreBuilder.getEcoreAttribute(XSDEcoreBuilder.java:2758)
 at 
 org.apache.tuscany.sdo.helper.BaseSDOXSDEcoreBuilder.getEStructuralFeature(BaseSDOXSDEcoreBuilder.java:1621)
 at 
 org.apache.tuscany.sdo.helper.BaseSDOXSDEcoreBuilder.generate(BaseSDOXSDEcoreBuilder.java:1674)
 at 
 org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelperImpl.java:246)
 at 
 org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelperImpl.java:224)
 at 
 org.apache.tuscany.sdo.test.XSDHelperTestCase.testDefineWithLocation(XSDHelperTestCase.java:60)
 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:324)
 at junit.framework.TestCase.runTest(TestCase.java:154)
 at junit.framework.TestCase.runBare(TestCase.java:127)
 at junit.framework.TestResult$1.protect(TestResult.java:106)
 at junit.framework.TestResult.runProtected(TestResult.java:124)
 at junit.framework.TestResult.run(TestResult.java:109)
 at junit.framework.TestCase.run(TestCase.java:118)
 at junit.framework.TestSuite.runTest(TestSuite.java:208)
 at junit.framework.TestSuite.run(TestSuite.java:203)
 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:324)
 at 
 org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
 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:324)
 at 
 org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290)
 at 
 org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818)
 I get similar errors when running with Sun's 1.4.2 JDK with already built SDO 
 jars. I don't get this error with the IBM 1.4.2 JRE. 
 Let me know if you need any additional information. Thanks,
 -Chris

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


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



[jira] Resolved: (TUSCANY-2187) Surefire fails because of java.endorsed.dirs setting

2008-04-02 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2187.
---

Resolution: Fixed

Fixed under r644071 (1.1)  644069 (trunk)

 Surefire fails because of java.endorsed.dirs setting
 

 Key: TUSCANY-2187
 URL: https://issues.apache.org/jira/browse/TUSCANY-2187
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
 Environment: Windows XP with Java home C:\Program 
 Files\Java\jdk1.5.0_10
 Maven version: 2.0.8
Reporter: Andreas Veithen
Assignee: Raymond Feng
Priority: Critical

 In revision 642377, the following setting was added to the Surefire plugin 
 configuration in sdo/pom.xml:
 argLine-Djava.endorsed.dirs=${java.endorsed.dirs}/argLine
 On systems where the path to the Java directory contains spaces (as is 
 usually the case on most Windows systems), execution of the tests (e.g. in 
 sdo/impl) fails with the following kind of error:
 java.lang.NoClassDefFoundError: Files\Java\jdk1/5/0_10\jre\lib\endorsed
 I tried to add quotes to the argument, but I couldn't figure out how to make 
 Maven understand that the value of argLine is a single argument.

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


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



[jira] Assigned: (TUSCANY-2150) samples/helloworld-ws-servicereference-jms

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2150:
-

Assignee: Raymond Feng

 samples/helloworld-ws-servicereference-jms
 ---

 Key: TUSCANY-2150
 URL: https://issues.apache.org/jira/browse/TUSCANY-2150
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK 5
Reporter: Simon Laws
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2


 Running  helloworld-ws-service-jms gives rise to...
 C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\samples\hellowo
 rld-ws-service-jmsant run
 Buildfile: build.xml
 run:
  [java] 27-Mar-2008 10:57:15 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2Se
 rviceProvider start
  [java] INFO: Axis2 JMS 
 URL=jms:/queue.sample?transport.jms.ConnectionFactor
 yJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq
 .jndi.ActiveMQInitialContextFactoryjava.naming.provider.url=tcp://localhost:616
 19
  [java] Exception in thread main org.osoa.sca.ServiceRuntimeException: 
 org
 .apache.axis2.transport.jms.AxisJMSException: Error connecting to JMS 
 connection
  factory : QueueConnectionFactory
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:264)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at helloworld.HelloWorldServer.main(HelloWorldServer.java:33)
  [java] Caused by: org.apache.axis2.transport.jms.AxisJMSException: Error 
 co
 nnecting to JMS connection factory : QueueConnectionFactory
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.handleException(JM
 SListener.java:420)
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.initializeConnecti
 onFactories(JMSListener.java:256)
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.init(JMSListener.j
 ava:109)
  [java] at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.
 start(Axis2ServiceProvider.java:285)
  [java] at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingPr
 ovider.start(Axis2ServiceBindingProvider.java:94)
  [java] at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.s
 tart(CompositeActivatorImpl.java:520)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in
 it(DefaultSCADomain.java:226)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.i
 nit(DefaultSCADomain.java:109)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:230)
  [java] ... 2 more
  [java] Caused by: javax.naming.NoInitialContextException: Cannot 
 instantiat
 e class: org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root 
 exception
 is java.lang.ClassNotFoundException: 
 org.apache.activemq.jndi.ActiveMQInitialCon
 textFactory]
  [java] at 
 javax.naming.spi.NamingManager.getInitialContext(NamingManage
 r.java:669)
  [java] at 
 javax.naming.InitialContext.getDefaultInitCtx(InitialContext.
 java:259)
  [java] at javax.naming.InitialContext.init(InitialContext.java:235)
  [java] at javax.naming.InitialContext.init(InitialContext.java:209)
  [java] at 
 org.apache.axis2.transport.jms.JMSConnectionFactory.createIni
 tialContext(JMSConnectionFactory.java:189)
  [java] at 
 org.apache.axis2.transport.jms.JMSConnectionFactory.connect(J
 MSConnectionFactory.java:170)
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.initializeConnecti
 onFactories(JMSListener.java:253)
  [java] ... 9 more
  [java] Caused by: java.lang.ClassNotFoundException: 
 org.apache.activemq.jnd
 i.ActiveMQInitialContextFactory
  [java] at java.lang.Class.forName(Class.java:163)
  [java] at 
 com.sun.naming.internal.VersionHelper12.loadClass(VersionHelp
 er12.java:57)
  [java] at 
 javax.naming.spi.NamingManager.getInitialContext(NamingManage
 r.java:666)
  [java] ... 15 more
  [java] Java Result: 1

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


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



[jira] Resolved: (TUSCANY-2150) samples/helloworld-ws-servicereference-jms

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2150.
---

Resolution: Fixed

Fixed under r643083 (1.2 branch) and r643081 (trunk)

 samples/helloworld-ws-servicereference-jms
 ---

 Key: TUSCANY-2150
 URL: https://issues.apache.org/jira/browse/TUSCANY-2150
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK 5
Reporter: Simon Laws
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2


 Running  helloworld-ws-service-jms gives rise to...
 C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\samples\hellowo
 rld-ws-service-jmsant run
 Buildfile: build.xml
 run:
  [java] 27-Mar-2008 10:57:15 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2Se
 rviceProvider start
  [java] INFO: Axis2 JMS 
 URL=jms:/queue.sample?transport.jms.ConnectionFactor
 yJNDIName=QueueConnectionFactoryjava.naming.factory.initial=org.apache.activemq
 .jndi.ActiveMQInitialContextFactoryjava.naming.provider.url=tcp://localhost:616
 19
  [java] Exception in thread main org.osoa.sca.ServiceRuntimeException: 
 org
 .apache.axis2.transport.jms.AxisJMSException: Error connecting to JMS 
 connection
  factory : QueueConnectionFactory
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:264)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at helloworld.HelloWorldServer.main(HelloWorldServer.java:33)
  [java] Caused by: org.apache.axis2.transport.jms.AxisJMSException: Error 
 co
 nnecting to JMS connection factory : QueueConnectionFactory
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.handleException(JM
 SListener.java:420)
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.initializeConnecti
 onFactories(JMSListener.java:256)
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.init(JMSListener.j
 ava:109)
  [java] at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.
 start(Axis2ServiceProvider.java:285)
  [java] at 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingPr
 ovider.start(Axis2ServiceBindingProvider.java:94)
  [java] at 
 org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.s
 tart(CompositeActivatorImpl.java:520)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in
 it(DefaultSCADomain.java:226)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.i
 nit(DefaultSCADomain.java:109)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:230)
  [java] ... 2 more
  [java] Caused by: javax.naming.NoInitialContextException: Cannot 
 instantiat
 e class: org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root 
 exception
 is java.lang.ClassNotFoundException: 
 org.apache.activemq.jndi.ActiveMQInitialCon
 textFactory]
  [java] at 
 javax.naming.spi.NamingManager.getInitialContext(NamingManage
 r.java:669)
  [java] at 
 javax.naming.InitialContext.getDefaultInitCtx(InitialContext.
 java:259)
  [java] at javax.naming.InitialContext.init(InitialContext.java:235)
  [java] at javax.naming.InitialContext.init(InitialContext.java:209)
  [java] at 
 org.apache.axis2.transport.jms.JMSConnectionFactory.createIni
 tialContext(JMSConnectionFactory.java:189)
  [java] at 
 org.apache.axis2.transport.jms.JMSConnectionFactory.connect(J
 MSConnectionFactory.java:170)
  [java] at 
 org.apache.axis2.transport.jms.JMSListener.initializeConnecti
 onFactories(JMSListener.java:253)
  [java] ... 9 more
  [java] Caused by: java.lang.ClassNotFoundException: 
 org.apache.activemq.jnd
 i.ActiveMQInitialContextFactory
  [java] at java.lang.Class.forName(Class.java:163)
  [java] at 
 com.sun.naming.internal.VersionHelper12.loadClass(VersionHelp
 er12.java:57)
  [java] at 
 javax.naming.spi.NamingManager.getInitialContext(NamingManage
 r.java:666)
  [java] ... 15 more
  [java] Java Result: 1

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


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



[jira] Assigned: (TUSCANY-2146) Array index out of range in binding-notification sample

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2146:
-

Assignee: Raymond Feng

 Array index out of range in binding-notification sample
 ---

 Key: TUSCANY-2146
 URL: https://issues.apache.org/jira/browse/TUSCANY-2146
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK5
Reporter: Simon Laws
Assignee: Raymond Feng
Priority: Critical
 Fix For: Java-SCA-1.2


 To reproduce run up
 binding-notification-broker
 binding-notification-producer 
 binding-notification-consumer
 As per the associate README
 Enter some message into the broker, e.g ABC and hit enter. I see the 
 following exception
 Then
   [java] java.lang.ArrayIndexOutOfBoundsException: Array index out of range:
 1
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.copy(PassByValueInterceptor.java:155)
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.invoke(PassByValueInterceptor.java:106)
  [java] at 
 org.apache.tuscany.sca.binding.notification.NotificationServi
 ceBindingProvider.invoke(NotificationServiceBindingProvider.java:263)
  [java] at 
 org.apache.tuscany.sca.binding.notification.NotificationServi
 ceBindingProvider.handle(NotificationServiceBindingProvider.java:244)
  [java] at 
 org.apache.tuscany.sca.binding.notification.util.Notification
 Servlet.doPost(NotificationServlet.java:76)
  [java] at 
 javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
  [java] at 
 javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
  [java] at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.
 java:487)
  [java] at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandle
 r.java:362)
  [java] at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandle
 r.java:181)
  [java] at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandle
 r.java:726)
  [java] at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrappe
 r.java:139)
  [java] at org.mortbay.jetty.Server.handle(Server.java:324)
  [java] at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection
 .java:505)
  [java] at 
 org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpC
 onnection.java:842)
  [java] at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
  [java] at 
 org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:2
 11)
  [java] at 
 org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:3
 80)
  [java] at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEnd
 Point.java:395)
  [java] at 
 org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.ja
 va:61)
  [java] at 
 org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$Decora
 tingWork.run(ThreadPoolWorkManager.java:214)
  [java] at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread
 PoolExecutor.java:665)
  [java] at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
 Executor.java:690)
  [java] at java.lang.Thread.run(Thread.java:801)

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


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



[jira] Resolved: (TUSCANY-2146) Array index out of range in binding-notification sample

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2146.
---

Resolution: Fixed

Fixed under r643103 (1.2) and r643102 (trunk)

 Array index out of range in binding-notification sample
 ---

 Key: TUSCANY-2146
 URL: https://issues.apache.org/jira/browse/TUSCANY-2146
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK5
Reporter: Simon Laws
Assignee: Raymond Feng
Priority: Critical
 Fix For: Java-SCA-1.2


 To reproduce run up
 binding-notification-broker
 binding-notification-producer 
 binding-notification-consumer
 As per the associate README
 Enter some message into the broker, e.g ABC and hit enter. I see the 
 following exception
 Then
   [java] java.lang.ArrayIndexOutOfBoundsException: Array index out of range:
 1
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.copy(PassByValueInterceptor.java:155)
  [java] at 
 org.apache.tuscany.sca.core.databinding.wire.PassByValueInter
 ceptor.invoke(PassByValueInterceptor.java:106)
  [java] at 
 org.apache.tuscany.sca.binding.notification.NotificationServi
 ceBindingProvider.invoke(NotificationServiceBindingProvider.java:263)
  [java] at 
 org.apache.tuscany.sca.binding.notification.NotificationServi
 ceBindingProvider.handle(NotificationServiceBindingProvider.java:244)
  [java] at 
 org.apache.tuscany.sca.binding.notification.util.Notification
 Servlet.doPost(NotificationServlet.java:76)
  [java] at 
 javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
  [java] at 
 javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
  [java] at 
 org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.
 java:487)
  [java] at 
 org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandle
 r.java:362)
  [java] at 
 org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandle
 r.java:181)
  [java] at 
 org.mortbay.jetty.handler.ContextHandler.handle(ContextHandle
 r.java:726)
  [java] at 
 org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrappe
 r.java:139)
  [java] at org.mortbay.jetty.Server.handle(Server.java:324)
  [java] at 
 org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection
 .java:505)
  [java] at 
 org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpC
 onnection.java:842)
  [java] at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648)
  [java] at 
 org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:2
 11)
  [java] at 
 org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:3
 80)
  [java] at 
 org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEnd
 Point.java:395)
  [java] at 
 org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.ja
 va:61)
  [java] at 
 org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$Decora
 tingWork.run(ThreadPoolWorkManager.java:214)
  [java] at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread
 PoolExecutor.java:665)
  [java] at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
 Executor.java:690)
  [java] at java.lang.Thread.run(Thread.java:801)

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


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



[jira] Assigned: (TUSCANY-2168) Incorrect level of commons-httpclient in distribution

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2168:
-

Assignee: Raymond Feng

 Incorrect level of commons-httpclient in distribution
 -

 Key: TUSCANY-2168
 URL: https://issues.apache.org/jira/browse/TUSCANY-2168
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
Affects Versions: Java-SCA-1.2
Reporter: Jean-Sebastien Delfino
Assignee: Raymond Feng
Priority: Critical
 Fix For: Java-SCA-1.2


 When I build the distribution I get commons-httpclient-2.0.1 in the distro 
 lib. The bindings that use that the httpclient require 
 commons-httpclient-3.0.1 and fail with various exceptions like ClassNotFound 
 and NoSuchMethod.

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


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



[jira] Resolved: (TUSCANY-2168) Incorrect level of commons-httpclient in distribution

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng resolved TUSCANY-2168.
---

Resolution: Fixed

Fixed under r643144 in 1.2 branch.

 Incorrect level of commons-httpclient in distribution
 -

 Key: TUSCANY-2168
 URL: https://issues.apache.org/jira/browse/TUSCANY-2168
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
Affects Versions: Java-SCA-1.2
Reporter: Jean-Sebastien Delfino
Assignee: Raymond Feng
Priority: Critical
 Fix For: Java-SCA-1.2


 When I build the distribution I get commons-httpclient-2.0.1 in the distro 
 lib. The bindings that use that the httpclient require 
 commons-httpclient-3.0.1 and fail with various exceptions like ClassNotFound 
 and NoSuchMethod.

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


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



[jira] Commented: (TUSCANY-2169) Saxon download does not work when you are not using the default Maven local repository directory

2008-03-31 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2169:
---

The donwload ant task is a workaround as the saxon 9.0.0.2 artifacts are not 
uploaded in the public repos. Now we created a tuscany maven repo at 
http://svn.apache.org/repos/asf/incubator/tuscany/maven. We can declare it in 
the pom.xml and remove the tuscany-saxon module as well as the download scripts.

 Saxon download does not work when you are not using the default Maven local 
 repository directory
 

 Key: TUSCANY-2169
 URL: https://issues.apache.org/jira/browse/TUSCANY-2169
 Project: Tuscany
  Issue Type: Bug
  Components: Build System
 Environment: SVN trunk revision 642924
 Linux
Reporter: Mark Combellack
Assignee: Mark Combellack
Priority: Minor
 Fix For: Java-SCA-Next


 By default, Maven uses the directory home/.m2/repository (where home is 
 your home directory) for it's local repository.
 Maven also supports using a user specified local repository directory using 
 the -Dmaven.repo.local=/some/other/directory on the Maven command line.
 The Saxon module will download the required release of Saxon and copy it into 
 the Maven local repository. However, this does not work if you are using a 
 custom local Maven repository directory.

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


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



[jira] Commented: (TUSCANY-2154) demos/alert-aggregator-webapp still uses package ant target and startup failure

2008-03-28 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2154:
---

The java.lang.NoClassDefFoundError: javax.wsdl.extensions.ExtensionSerializer 
issue should be fixed under TUSCANY-2156.

 demos/alert-aggregator-webapp still uses package ant target and startup 
 failure
 ---

 Key: TUSCANY-2154
 URL: https://issues.apache.org/jira/browse/TUSCANY-2154
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK5, Tomcat 6.0.13
Reporter: Simon Laws
Priority: Minor
 Fix For: Java-SCA-1.2


 Firstly this demo still relies on the package ant target. We should replace 
 this with compile which all other samples  demos use
 Secondly, on start up, the webapp fails and reports the following in the 
 tomcat log (this looks to be the same problem as 
 https://issues.apache.org/jira/browse/TUSCANY-2151)
 SEVERE: Exception starting filter tuscany
 org.osoa.sca.ServiceRuntimeException: 
 java.lang.reflect.InvocationTargetException
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82)
   at 
 org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:215)
   at 
 org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50)
   at 
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at 
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
   at 
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108)
   at 
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4340)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
   at 
 org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
   at 
 org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
   at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
   at 
 org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
   at 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
   at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
   at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
   at 
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
   at 
 org.apache.catalina.core.StandardService.start(StandardService.java:516)
   at 
 org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
   at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:615)
   at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
   at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
 Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:521)
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:246)
   ... 30 more
 Caused by: java.lang.NoClassDefFoundError: 
 javax.wsdl.extensions.ExtensionSerializer
   at java.lang.J9VMInternals.verifyImpl(Native Method)
   at java.lang.J9VMInternals.verify(J9VMInternals.java:66)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:127)
   at java.lang.Class.forNameImpl(Native Method)
   at java.lang.Class.forName(Class.java:163)
   at 
 

[jira] Commented: (TUSCANY-2156) demos/xml-bigbank run failure

2008-03-27 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2156:
---

It seems that wstx-asl.jar is missing from the classpath.

 demos/xml-bigbank run failure
 -

 Key: TUSCANY-2156
 URL: https://issues.apache.org/jira/browse/TUSCANY-2156
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK 5
Reporter: Simon Laws
 Fix For: Java-SCA-1.2


 running demos/xml-bigbank give rise to 
 C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\demos\xml-bigba
 nkant run
 Buildfile: build.xml
 run:
  [java] Exception in thread main 
 javax.xml.stream.FactoryConfigurationErro
 r: Provider com.bea.xml.stream.MXParserFactory not found
  [java] at 
 javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java
 :72)
  [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176)
  [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
  [java] at 
 javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.
 java:136)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntimeB
 uilder.createContributionService(ReallySmallRuntimeBuilder.java:176)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.
 start(ReallySmallRuntime.java:139)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in
 it(DefaultSCADomain.java:118)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.i
 nit(DefaultSCADomain.java:109)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:230)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at bigbank.BigBankClient.main(BigBankClient.java:30)
  [java] Java Result: 1

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


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



[jira] Commented: (TUSCANY-2144) Error while Invoking Service

2008-03-27 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2144:
---

Hi,

Can you please tell me how to reproduce your problem? 

I tried the following steps and get the service binding working:

1) Bootstrap the RunTime.composite (I cut the ComposerImpl.java to simply 
returns the input string)
2) Remove the requires=integrity from the composite file (I got NPE as I test 
from web service explorer in Eclipse and I cannot set the security header)
3) Start the web service explorer from the eai.wsdl and point to 
http://localhost:8080/ComposerService;
4) Invoke the WS with string 123 and I get the correct response.

Thanks,
Raymond

  Error while Invoking Service
 -

 Key: TUSCANY-2144
 URL: https://issues.apache.org/jira/browse/TUSCANY-2144
 Project: Tuscany
  Issue Type: Test
  Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-1.1
 Environment: Eclipse 3.1 , tomcat 5.5 , tuscany 1.1 , java 5
Reporter: Sandeep Raman
Priority: Critical
 Attachments: main.zip

   Original Estimate: 0.03h
  Remaining Estimate: 0.03h

 I have a service running accepting a string as input , it has 
 
 implementation in a java class. When i invoke the wsdl with a SOAP message
 
 i get error as following, what may be the reason for this:
 
   
 
 Mar 25, 2008 9:50:43 AM   
 
 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1   
 
 problem   
 
 WARNING: Duplicate service name: ComposerComponent/Composer   
 
 Mar 25, 2008 9:50:56 AM org.apache.tuscany.sca.http.jetty.JettyServer 
 
 addServletMapping 
 
 INFO: Added Servlet mapping:  
 
 http://01hw113905:8080/LOSComposite/LOSComposerService
 
 Mar 25, 2008 9:55:40 AM   
 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver  
 
 invokeBusinessLogic   
 
 SEVERE: java.lang.ClassCastException: java.lang.String
 
 org.osoa.sca.ServiceRuntimeException: java.lang.ClassCastException:   
 
 java.lang.String  
 
at 
 
 org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke( 
 
 RuntimeWireInvoker.java:122)  
 
at 
 
 org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke( 
 
 RuntimeWireInvoker.java:88)   
 
at 
 
 org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke( 
 
 RuntimeWireInvoker.java:82)   
 
at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(
 
 RuntimeWireImpl.java:126) 
 
at 
 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(
 
 Axis2ServiceProvider.java:589)
 
at 
 
 org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBus
 Axis2ServiceInOutSyncMessageReceiver.java:59) 
 
at 
 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(
   
 AbstractInOutSyncMessageReceiver.java:42) 
 
at org.apache.axis2.receivers.AbstractMessageReceiver.receive( 
 
 AbstractMessageReceiver.java:96)  
 
at 

[jira] Commented: (TUSCANY-2156) demos/xml-bigbank run failure

2008-03-27 Thread Raymond Feng (JIRA)

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

Raymond Feng commented on TUSCANY-2156:
---

It references wstx-asl-3.2.0.jar (which is not in the lib folder) instead of 
wstx-asl-3.2.1.jar (in the lib).

 demos/xml-bigbank run failure
 -

 Key: TUSCANY-2156
 URL: https://issues.apache.org/jira/browse/TUSCANY-2156
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK 5
Reporter: Simon Laws
 Fix For: Java-SCA-1.2


 running demos/xml-bigbank give rise to 
 C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\demos\xml-bigba
 nkant run
 Buildfile: build.xml
 run:
  [java] Exception in thread main 
 javax.xml.stream.FactoryConfigurationErro
 r: Provider com.bea.xml.stream.MXParserFactory not found
  [java] at 
 javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java
 :72)
  [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176)
  [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
  [java] at 
 javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.
 java:136)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntimeB
 uilder.createContributionService(ReallySmallRuntimeBuilder.java:176)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.
 start(ReallySmallRuntime.java:139)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in
 it(DefaultSCADomain.java:118)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.i
 nit(DefaultSCADomain.java:109)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:230)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at bigbank.BigBankClient.main(BigBankClient.java:30)
  [java] Java Result: 1

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


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



[jira] Assigned: (TUSCANY-2156) demos/xml-bigbank run failure

2008-03-27 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2156:
-

Assignee: Raymond Feng

 demos/xml-bigbank run failure
 -

 Key: TUSCANY-2156
 URL: https://issues.apache.org/jira/browse/TUSCANY-2156
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK 5
Reporter: Simon Laws
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2


 running demos/xml-bigbank give rise to 
 C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\demos\xml-bigba
 nkant run
 Buildfile: build.xml
 run:
  [java] Exception in thread main 
 javax.xml.stream.FactoryConfigurationErro
 r: Provider com.bea.xml.stream.MXParserFactory not found
  [java] at 
 javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java
 :72)
  [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176)
  [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
  [java] at 
 javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.
 java:136)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntimeB
 uilder.createContributionService(ReallySmallRuntimeBuilder.java:176)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.
 start(ReallySmallRuntime.java:139)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in
 it(DefaultSCADomain.java:118)
  [java] at 
 org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.i
 nit(DefaultSCADomain.java:109)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
 nce(SCADomain.java:230)
  [java] at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
 ADomain.java:69)
  [java] at bigbank.BigBankClient.main(BigBankClient.java:30)
  [java] Java Result: 1

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


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



[jira] Assigned: (TUSCANY-2151) samples/helloworld-ws-sdo-webapp

2008-03-27 Thread Raymond Feng (JIRA)

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

Raymond Feng reassigned TUSCANY-2151:
-

Assignee: Raymond Feng

 samples/helloworld-ws-sdo-webapp
 

 Key: TUSCANY-2151
 URL: https://issues.apache.org/jira/browse/TUSCANY-2151
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
 Environment: WinXP SP2, IBM JDK 5, Tomcat 6.0.13
Reporter: Simon Laws
Assignee: Raymond Feng
 Fix For: Java-SCA-1.2


 helloworld-ws-sdo-webapp fails to start up in Tomcat giving the following 
 message in the Tomcat log
 SEVERE: Exception starting filter tuscany
 org.osoa.sca.ServiceRuntimeException: 
 java.lang.reflect.InvocationTargetException
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264)
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82)
   at 
 org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:215)
   at 
 org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50)
   at 
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
   at 
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397)
   at 
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:108)
   at 
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4340)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
   at 
 org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
   at 
 org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
   at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206)
   at 
 org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
   at 
 org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
   at 
 org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
   at 
 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
   at 
 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
   at 
 org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
   at java.lang.Thread.run(Thread.java:801)
 Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
   at 
 sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
   at 
 sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:521)
   at 
 org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:246)
   ... 22 more
 Caused by: java.lang.NoClassDefFoundError: 
 javax.wsdl.extensions.ExtensionSerializer
   at java.lang.J9VMInternals.verifyImpl(Native Method)
   at java.lang.J9VMInternals.verify(J9VMInternals.java:66)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:127)
   at java.lang.Class.forNameImpl(Native Method)
   at java.lang.Class.forName(Class.java:163)
   at 
 org.apache.tuscany.sca.extensibility.ServiceDeclaration.loadClass(ServiceDeclaration.java:63)
   at 
 org.apache.tuscany.sca.contribution.resolver.DefaultModelResolverExtensionPoint.getResolver(DefaultModelResolverExtensionPoint.java:65)
   at 
 org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.getModelResolverInstance(ExtensibleModelResolver.java:107)
   at 
 org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.addModel(ExtensibleModelResolver.java:130)
   at 
 org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processReadPhase(ContributionServiceImpl.java:407)
   at 
 org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:339)
   at 
 org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:161)
   at 
 

  1   2   3   4   5   6   7   >