You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "ant elder (JIRA)" <de...@tuscany.apache.org> on 2008/08/07 11:17:44 UTC
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12620565#action_12620565 ]
ant elder commented on TUSCANY-2513:
------------------------------------
Doing this make sense to me.
But something that bothers me with the patch is that it creates a hard dependency on the @WebService annotation class so the jsr181-api jar will need to be on the classpath always whether or not the @WebService annotation is being used. That said Tuscany already has a hard dependency on the jsr181-api jar as it gets dragged in by core-databinding so maybe I shouldn't be worrying, however I've been slowing fixing up all these types of issues to make dependency's optional where possible so Tuscany can run with a minimal set of dependency jars. There is also a user raised JIRA related to this - TUSCANY-2514.
> 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
> Priority: Minor
> 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.
Re: [jira] Commented: (TUSCANY-2513) Java intfs with @WebService should be treated like @Remotable intfs wrt calculation of services implemented by a Java implementation
Posted by Raymond Feng <en...@gmail.com>.
I can accept it for @WebService. What about other technology-specific
remotable interfaces such as RMI Remote or EJB Remote? It's probably better
to have the SCA spec well specify the case .
Thanks,
Raymond
From: Scott Kurz
Sent: Friday, August 15, 2008 1:25 PM
To: dev@tuscany.apache.org
Subject: Re: [jira] Commented: (TUSCANY-2513) Java intfs with @WebService
should be treated like @Remotable intfs wrt calculation of services
implemented by a Java implementation
Raymond,
Just noticing that the OSOA Java anno/api spec already includes in the
errata:
http://osoa.org/display/Main/Errata+for+Java+Annotations+and+APIs+V1.00
the statement that...
" section 1.9 of the Java API specification .... should be replaced with the
following:
The SCA Client and Implementation Model for Java applies the WSDL to Java
and Java to WSDL mapping rules as defined by the JAX-WS specification [4]
for generating remotable Java interfaces from WSDL portTypes and vice versa.
For the purposes of the Java-to-WSDL mapping algorithm, the interface is
treated as if it had a @WebService annotation on the class, even if it
doesn't, and the org.osoa.OneWay annotation should be treated as a synonym
for javax.jws.OneWay. For the WSDL-to-Java, the generated @WebService
annotation should imply that the interface is @Remotable.
For the mapping from Java types to XML schema types SCA supports both the
SDO 2.1 [2] mapping and the JAXB [3] mapping. Having a choice of binding
technologies is allowed, as noted in the first paragraph of section 5 of the
JSR 181 (version 2) specification, which is referenced by the JAX-WS
specification."
I can accept that this clarifies the situation well enough, although it
would only help to add clarification to the Java C&I spec as well.
What do you think?
Scott
On Thu, Aug 7, 2008 at 1:01 PM, Raymond Feng <en...@gmail.com> wrote:
Can we take this issue to the SCA spec first?
Thanks,
Raymond
--------------------------------------------------
From: "ant elder (JIRA)" <de...@tuscany.apache.org>
Sent: Thursday, August 07, 2008 2:17 AM
To: <de...@tuscany.apache.org>
Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12620565#action_12620565 ]
ant elder commented on TUSCANY-2513:
------------------------------------
Doing this make sense to me.
But something that bothers me with the patch is that it creates a hard
dependency on the @WebService annotation class so the jsr181-api jar will
need to be on the classpath always whether or not the @WebService annotation
is being used. That said Tuscany already has a hard dependency on the
jsr181-api jar as it gets dragged in by core-databinding so maybe I
shouldn't be worrying, however I've been slowing fixing up all these types
of issues to make dependency's optional where possible so Tuscany can run
with a minimal set of dependency jars. There is also a user raised JIRA
related to this - TUSCANY-2514.
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
Priority: Minor
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.
Re: [jira] Commented: (TUSCANY-2513) Java intfs with @WebService should be treated like @Remotable intfs wrt calculation of services implemented by a Java implementation
Posted by Scott Kurz <sc...@gmail.com>.
Raymond,
Just noticing that the OSOA Java anno/api spec already includes in the
errata:
*http://osoa.org/display/Main/Errata+for+Java+Annotations+and+APIs+V1.00*
the statement that...
" section 1.9 of the Java API specification .... should be replaced with the
following:
The SCA Client and Implementation Model for Java applies the WSDL to Java
and Java to WSDL mapping rules as defined by the JAX-WS specification [4]
for generating remotable Java interfaces from WSDL portTypes and vice versa.
For the purposes of the Java-to-WSDL mapping algorithm, the interface is
treated as if it had a @WebService annotation on the class, even if it
doesn't, and the org.osoa.OneWay annotation should be treated as a synonym
for javax.jws.OneWay. For the WSDL-to-Java, the generated @WebService
annotation should imply that the interface is @Remotable.
For the mapping from Java types to XML schema types SCA supports both the
SDO 2.1 [2] mapping and the JAXB [3] mapping. Having a choice of binding
technologies is allowed, as noted in the first paragraph of section 5 of the
JSR 181 (version 2) specification, which is referenced by the JAX-WS
specification."
I can accept that this clarifies the situation well enough, although it
would only help to add clarification to the Java C&I spec as well.
What do you think?
Scott
On Thu, Aug 7, 2008 at 1:01 PM, Raymond Feng <en...@gmail.com> wrote:
> Can we take this issue to the SCA spec first?
>
> Thanks,
> Raymond
>
> --------------------------------------------------
> From: "ant elder (JIRA)" <de...@tuscany.apache.org>
> Sent: Thursday, August 07, 2008 2:17 AM
> To: <de...@tuscany.apache.org>
> Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12620565#action_12620565]
>>
>> ant elder commented on TUSCANY-2513:
>> ------------------------------------
>>
>> Doing this make sense to me.
>>
>> But something that bothers me with the patch is that it creates a hard
>> dependency on the @WebService annotation class so the jsr181-api jar will
>> need to be on the classpath always whether or not the @WebService annotation
>> is being used. That said Tuscany already has a hard dependency on the
>> jsr181-api jar as it gets dragged in by core-databinding so maybe I
>> shouldn't be worrying, however I've been slowing fixing up all these types
>> of issues to make dependency's optional where possible so Tuscany can run
>> with a minimal set of dependency jars. There is also a user raised JIRA
>> related to this - TUSCANY-2514.
>>
>>
>>
>>
>>
>> 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
>>> Priority: Minor
>>> 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.
>>
>>
Re: [jira] Commented: (TUSCANY-2513) Java intfs with @WebService should be treated like @Remotable intfs wrt calculation of services implemented by a Java implementation
Posted by Raymond Feng <en...@gmail.com>.
Can we take this issue to the SCA spec first?
Thanks,
Raymond
--------------------------------------------------
From: "ant elder (JIRA)" <de...@tuscany.apache.org>
Sent: Thursday, August 07, 2008 2:17 AM
To: <de...@tuscany.apache.org>
Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12620565#action_12620565 ]
>
> ant elder commented on TUSCANY-2513:
> ------------------------------------
>
> Doing this make sense to me.
>
> But something that bothers me with the patch is that it creates a hard
> dependency on the @WebService annotation class so the jsr181-api jar will
> need to be on the classpath always whether or not the @WebService
> annotation is being used. That said Tuscany already has a hard dependency
> on the jsr181-api jar as it gets dragged in by core-databinding so maybe I
> shouldn't be worrying, however I've been slowing fixing up all these types
> of issues to make dependency's optional where possible so Tuscany can run
> with a minimal set of dependency jars. There is also a user raised JIRA
> related to this - TUSCANY-2514.
>
>
>
>
>
>> 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
>> Priority: Minor
>> 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.
>