You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Vamsavardhana Reddy (JIRA)" <de...@tuscany.apache.org> on 2008/08/26 13:11:44 UTC

[jira] Reopened: (TUSCANY-2513) Java intfs with @WebService should be treated like @Remotable intfs wrt calculation of services implemented by a Java implementation

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

Vamsavardhana Reddy reopened TUSCANY-2513:
------------------------------------------


The commit resulted in build problems.  See [1]

Should org.apache.tuscany.sca.interfacedef.java.impl.JavaInterfaceIntrospectorImpl also be modified to take care of the @WebService annotation?

[1] http://www.mail-archive.com/dev@tuscany.apache.org/msg01968.html

> Java intfs with @WebService should be treated like @Remotable intfs wrt calculation of services implemented by a Java implementation
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2513
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2513
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SCA Java Implementation Extension
>            Reporter: Scott Kurz
>            Assignee: Raymond Feng
>            Priority: Minor
>             Fix For: Java-SCA-Next
>
>         Attachments: 2513.patch
>
>
> Since we're generally treating a Java intf marked with @WebService as remotable, I think it would be more consistent to treat them in the same way as Java intfs marked with @Remotable in calculating the services implemented by a Java implementation.
> That is, if a Java impl without an @Service annotation implements a Java intf marked with @WebService, I think this we should calculate that this impl implements a service typed by this Java intf (with @WebService).
> This is addressed by Java CI Sec. 1.2.1.3, though the wording doesn't make clear my suggestion is the right interpretation.
> I'll put a patch out here and see if anyone objects or maybe has other ideas as to where a similar type of issue might still be present.
> Thanks,
> Scott

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