You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Vijai Kalathur (Created) (JIRA)" <de...@tuscany.apache.org> on 2012/03/22 15:34:22 UTC

[jira] [Created] (TUSCANY-4033) Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen

Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen
----------------------------------------------------------------------------

                 Key: TUSCANY-4033
                 URL: https://issues.apache.org/jira/browse/TUSCANY-4033
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Assembly Model
    Affects Versions: Java-SCA-2.0
            Reporter: Vijai Kalathur


If I have a service interface which does not contain a no-arg default constructor and try to do a remote service invocation to that service, the invocation fails when the haveMatchingInterfaceContracts method in EndpointReferenceBinderImpl tries to generate a WSDL.  Since the interface does not contain a no-arg constructor, the wsdl  gen fails.  We might have to update something in this check

        if (endpointReferenceContract.getClass() != endpointContract.getClass() ||
            endpointReferenceContract.getNormalizedWSDLContract() != null ||
            endpointContract.getNormalizedWSDLContract() != null) {
            endpointReferenceContract = ((RuntimeEndpointReference)endpointReference).getGeneratedWSDLContract(endpointReferenceContract);
            endpointContract = ((RuntimeEndpoint)endpoint).getGeneratedWSDLContract(endpointContract);
        }

to not generate the wsdl in certain cases.

--
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-4033) Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen

Posted by "Simon Laws (Assigned) (JIRA)" <de...@tuscany.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws reassigned TUSCANY-4033:
-----------------------------------

    Assignee: Simon Laws
    
> Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen
> ----------------------------------------------------------------------------
>
>                 Key: TUSCANY-4033
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-4033
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model
>    Affects Versions: Java-SCA-2.0
>            Reporter: Vijai Kalathur
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> If I have a service interface which does not contain a no-arg default constructor and try to do a remote service invocation to that service, the invocation fails when the haveMatchingInterfaceContracts method in EndpointReferenceBinderImpl tries to generate a WSDL.  Since the interface does not contain a no-arg constructor, the wsdl  gen fails.  We might have to update something in this check
>         if (endpointReferenceContract.getClass() != endpointContract.getClass() ||
>             endpointReferenceContract.getNormalizedWSDLContract() != null ||
>             endpointContract.getNormalizedWSDLContract() != null) {
>             endpointReferenceContract = ((RuntimeEndpointReference)endpointReference).getGeneratedWSDLContract(endpointReferenceContract);
>             endpointContract = ((RuntimeEndpoint)endpoint).getGeneratedWSDLContract(endpointContract);
>         }
> to not generate the wsdl in certain cases.

--
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] [Closed] (TUSCANY-4033) Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen

Posted by "Simon Laws (Closed) (JIRA)" <de...@tuscany.apache.org>.
     [ https://issues.apache.org/jira/browse/TUSCANY-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws closed TUSCANY-4033.
-------------------------------

       Resolution: Fixed
    Fix Version/s: Java-SCA-2.0

Fix applied at revision: 1304327
                
> Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen
> ----------------------------------------------------------------------------
>
>                 Key: TUSCANY-4033
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-4033
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model
>    Affects Versions: Java-SCA-2.0
>            Reporter: Vijai Kalathur
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> If I have a service interface which does not contain a no-arg default constructor and try to do a remote service invocation to that service, the invocation fails when the haveMatchingInterfaceContracts method in EndpointReferenceBinderImpl tries to generate a WSDL.  Since the interface does not contain a no-arg constructor, the wsdl  gen fails.  We might have to update something in this check
>         if (endpointReferenceContract.getClass() != endpointContract.getClass() ||
>             endpointReferenceContract.getNormalizedWSDLContract() != null ||
>             endpointContract.getNormalizedWSDLContract() != null) {
>             endpointReferenceContract = ((RuntimeEndpointReference)endpointReference).getGeneratedWSDLContract(endpointReferenceContract);
>             endpointContract = ((RuntimeEndpoint)endpoint).getGeneratedWSDLContract(endpointContract);
>         }
> to not generate the wsdl in certain cases.

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