You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Sebastian Millies (Created) (JIRA)" <de...@tuscany.apache.org> on 2011/11/23 23:58:40 UTC
[jira] [Created] (TUSCANY-3984) Service refernces do not serialize
according to SCA spec
Service refernces 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
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
[jira] [Updated] (TUSCANY-3984) Service references do not serialize
according to SCA spec
Posted by "Sebastian Millies (Updated) (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Millies updated TUSCANY-3984:
---------------------------------------
Summary: Service references do not serialize according to SCA spec (was: Service refernces do not serialize according to SCA spec)
> 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
> 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
[jira] [Commented] (TUSCANY-3984) Service references do not
serialize according to SCA spec
Posted by "Simon Nash (Commented) (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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
[jira] [Updated] (TUSCANY-3984) Service refernces do not serialize
according to SCA spec
Posted by "Sebastian Millies (Updated) (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Millies updated TUSCANY-3984:
---------------------------------------
Attachment: helloworld-ws-service-secure.zip
helloworld-ws-reference-secure.zip
Test case
> Service refernces 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
> 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
[jira] [Assigned] (TUSCANY-3984) Service references do not
serialize according to SCA spec
Posted by "Simon Nash (Assigned) (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Nash reassigned TUSCANY-3984:
-----------------------------------
Assignee: Simon Nash
> 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