[jira] [Commented] (TUSCANY-3882) Are there any changes in 1.x that we still need to apply to 2.x
[ https://issues.apache.org/jira/browse/TUSCANY-3882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13178861#comment-13178861 ] Simon Nash commented on TUSCANY-3882: - I've updated the list to add the changes for revision 1210165. Are there any changes in 1.x that we still need to apply to 2.x --- Key: TUSCANY-3882 URL: https://issues.apache.org/jira/browse/TUSCANY-3882 Project: Tuscany Issue Type: Improvement Affects Versions: Java-SCA-2.0-M5 Reporter: Simon Laws Fix For: Java-SCA-2.0 Attachments: edited-list-3.txt I don't know this to be true but I'm wondering if there are still changes in 1.x that we need in 2.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TUSCANY-3991) Build failure in binding-gdata-runtime
[ https://issues.apache.org/jira/browse/TUSCANY-3991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162425#comment-13162425 ] Simon Nash commented on TUSCANY-3991: - I have temporarily disabled the failing tests to allow the 1.x build to run. Committed under revision r1210154. Build failure in binding-gdata-runtime -- Key: TUSCANY-3991 URL: https://issues.apache.org/jira/browse/TUSCANY-3991 Project: Tuscany Issue Type: Bug Components: Java SCA Misc Binding Extensions Affects Versions: Java-SCA-1.x Reporter: Simon Nash The 1.x trunk build fails in binding-gdata-runtime with Unauthorized errors from the testClientPost and testClientDelete tests in GoogleBloggerServiceTestCase. See the stack traces below for details The failure is caused by an invalid username and password in the test case. I verified this by attempting to login to Blogger with this userid and password. The login was rejected. Here's the error log: Tests run: 6, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 4.717 sec FAILURE! testClientPost(org.apache.tuscany.sca.binding.gdata.GoogleBloggerServiceTestCase) Time elapsed: 0.208 sec ERROR! org.osoa.sca.ServiceRuntimeException: com.google.gdata.util.AuthenticationException: Unauthorized User does not have permission to create new post at org.apache.tuscany.sca.binding.gdata.provider.GdataBindingInvoker$PostInvoker.invoke(GdataBindingInvoker.java:172) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:55) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:349) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:193) at $Proxy11.post(Unknown Source) at org.apache.tuscany.sca.binding.gdata.CustomerClientImpl.clientPost(CustomerClientImpl.java:69) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:156) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:349) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:193) at $Proxy10.clientPost(Unknown Source) at org.apache.tuscany.sca.binding.gdata.GoogleBloggerServiceTestCase.testClientPost(GoogleBloggerServiceTestCase.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run(ParentRunner.java:220) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:138) at
[jira] [Commented] (TUSCANY-3984) Service references do not serialize according to SCA spec
[ https://issues.apache.org/jira/browse/TUSCANY-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13162435#comment-13162435 ] Simon Nash commented on TUSCANY-3984: - I've added code to CallableReferenceImpl and ComponentContextHelper in the 1.x trunk to support serializing and deserializing service references that use binding.ws, interface.wsdl and policySets. I've also added two new itests serialization-ws and serialization-ws-basicauth. The first of these new itests does the same as the helloworld-ws-service-secure/helloworld-ws-reference-secure sample using service references that have been serialized and deserialized. The second new itest does the same as the test case submitted with this JIRA, i.e., it verifies that service references that have been serialized and deserialized can be used with binding.ws, interface.wsdl, and an authentication policySet that implements HTTP basic authentication. Service references do not serialize according to SCA spec - Key: TUSCANY-3984 URL: https://issues.apache.org/jira/browse/TUSCANY-3984 Project: Tuscany Issue Type: Bug Components: SCA Java Runtime Affects Versions: Java-SCA-1.6 Environment: JDK 1.6 Reporter: Sebastian Millies Assignee: Simon Nash Attachments: helloworld-ws-reference-secure.zip, helloworld-ws-service-secure.zip After a service reference has been serialized and deserialized, it no longer supports calls using binding.ws. Indeed, service references can sometimes not even be deserialized. The attached test case produces a WSDL generation error during the deserialization stage (i. e. before making any service call) because no WSDL definition is found for the deserialized binding. I attach modified versions of two Tuscany samples. In helloworld-ws-service-secure I have modified the definitions.xml to use BasicAuthenticationPolicySet, as in my original setup with SAP. In helloworld-ws-reference-secure I have split the HelloWorldService interface into a part referring to the external web service, and a part containing additional methods that attempt the remote call while first serializing the embedded reference. I have deleted the test class just tested the Socket connection. You can try starting the service component with ant run and then manually starting (no build target) helloworld.HelloWorldClientTestCase in the client component. This test case contains two new tests, one with normal serialization, one with coding for explicit XML serialization. I have added some elements to the composite file and some annotations to the coding (both hopefully redundant) in order to get clearer about the code structure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
