You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jervis Liu (JIRA)" <tu...@ws.apache.org> on 2006/08/17 05:42:13 UTC

[jira] Created: (TUSCANY-638) Support new binding elements and

Support new binding elements <binding.axis> and <binding.celtix>
----------------------------------------------------------------

                 Key: TUSCANY-638
                 URL: http://issues.apache.org/jira/browse/TUSCANY-638
             Project: Tuscany
          Issue Type: New Feature
          Components: Java SCA Axis Binding, Java SCA Celtix Binding
            Reporter: Jervis Liu


When spec binding <binding.ws> is used, we can assume that users do not care and should not care which Web Service binding implementation is used as all implementations should conform to the spec. It is up to the implementation of LoaderRegistry to determine which implementation of <binding.ws> to load using its own way. In this case, there is no guarantee to users that which binding implementation is getting used in Tuscany. If users do wish to use a specific binding implementation for some reasons, they need to do so by using a non-spec binding element , such as  <binding.axis> and <binding.celtix>, which are extended from binding element.  <binding.celtix> is product type binding that supports various bindings/protocols, such as soap/http and JMS. Users need Celtix specific knowledge in order to know how to configure which binding/protocol is being used. 



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Updated: (TUSCANY-638) Support new binding elements and

Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-638?page=all ]

ant elder updated TUSCANY-638:
------------------------------

    Component/s:     (was: Java SCA Axis Binding)

Removed JIRA from the axis binding component for now as we'll likely not have a binding.axis in the near future 

> Support new binding elements <binding.axis> and <binding.celtix>
> ----------------------------------------------------------------
>
>                 Key: TUSCANY-638
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-638
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SCA Celtix Binding
>    Affects Versions: Java-Mx
>            Reporter: Jervis Liu
>             Fix For: Java-Mx
>
>
> When spec binding <binding.ws> is used, we can assume that users do not care and should not care which Web Service binding implementation is used as all implementations should conform to the spec. It is up to the implementation of LoaderRegistry to determine which implementation of <binding.ws> to load using its own way. In this case, there is no guarantee to users that which binding implementation is getting used in Tuscany. If users do wish to use a specific binding implementation for some reasons, they need to do so by using a non-spec binding element , such as  <binding.axis> and <binding.celtix>, which are extended from binding element.  <binding.celtix> is product type binding that supports various bindings/protocols, such as soap/http and JMS. Users need Celtix specific knowledge in order to know how to configure which binding/protocol is being used. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Commented: (TUSCANY-638) Support new binding elements and

Posted by "Jervis Liu (JIRA)" <tu...@ws.apache.org>.
    [ http://issues.apache.org/jira/browse/TUSCANY-638?page=comments#action_12428565 ] 
            
Jervis Liu commented on TUSCANY-638:
------------------------------------

As far as the schema is concerned, I think it should be pretty much same to binding.ws. but it migh allow some custom properties to allow advanced configurations in the binding. For example, <binding.celtix> can have a property called "config-location" to specify the location of Celtix configuration file if the default location can not be used.


> Support new binding elements <binding.axis> and <binding.celtix>
> ----------------------------------------------------------------
>
>                 Key: TUSCANY-638
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-638
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SCA Axis Binding, Java SCA Celtix Binding
>            Reporter: Jervis Liu
>
> When spec binding <binding.ws> is used, we can assume that users do not care and should not care which Web Service binding implementation is used as all implementations should conform to the spec. It is up to the implementation of LoaderRegistry to determine which implementation of <binding.ws> to load using its own way. In this case, there is no guarantee to users that which binding implementation is getting used in Tuscany. If users do wish to use a specific binding implementation for some reasons, they need to do so by using a non-spec binding element , such as  <binding.axis> and <binding.celtix>, which are extended from binding element.  <binding.celtix> is product type binding that supports various bindings/protocols, such as soap/http and JMS. Users need Celtix specific knowledge in order to know how to configure which binding/protocol is being used. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Updated: (TUSCANY-638) Support new binding elements and

Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-638?page=all ]

ant elder updated TUSCANY-638:
------------------------------

        Fix Version/s: Java-Mx
    Affects Version/s: Java-Mx

> Support new binding elements <binding.axis> and <binding.celtix>
> ----------------------------------------------------------------
>
>                 Key: TUSCANY-638
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-638
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SCA Axis Binding, Java SCA Celtix Binding
>    Affects Versions: Java-Mx
>            Reporter: Jervis Liu
>             Fix For: Java-Mx
>
>
> When spec binding <binding.ws> is used, we can assume that users do not care and should not care which Web Service binding implementation is used as all implementations should conform to the spec. It is up to the implementation of LoaderRegistry to determine which implementation of <binding.ws> to load using its own way. In this case, there is no guarantee to users that which binding implementation is getting used in Tuscany. If users do wish to use a specific binding implementation for some reasons, they need to do so by using a non-spec binding element , such as  <binding.axis> and <binding.celtix>, which are extended from binding element.  <binding.celtix> is product type binding that supports various bindings/protocols, such as soap/http and JMS. Users need Celtix specific knowledge in order to know how to configure which binding/protocol is being used. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org


[jira] Commented: (TUSCANY-638) Support new binding elements and

Posted by "Jervis Liu (JIRA)" <tu...@ws.apache.org>.
    [ http://issues.apache.org/jira/browse/TUSCANY-638?page=comments#action_12428579 ] 
            
Jervis Liu commented on TUSCANY-638:
------------------------------------

I think another thing we could do for the binding.ws thing is have an option on the loader that says whether it should register for the technology default
(02:20:23) jboynes: so the Axis binding would always register to handle binding.axis
(02:20:36) jboynes: but could be configured to handle binding.ws or not
(02:20:52) jervisliu: yep
(02:21:09) jboynes: this is set with a property on it's composite to allow an admin to choose the default if both happen to be installed
(02:21:28) jboynes: and then the user "knows" - at least, if they talk to their admin :-)
(02:22:00) jervisliu: yes, this way actually we can load an bin‌ding implementation explicitly
(02:22:26) jboynes: and we give control to the admin and the developer
(02:23:22) jervisliu: but then how about both celtix and axis say they r default for binding.ws?
(02:23:43) jervisliu: is this considered a user configuration error? ;-)
(02:23:49) jboynes: then the policy is set by the LoaderRegistry - first, last or error
(02:24:51) jboynes: and an extension should always do it's own + the tech default
(02:25:01) jervisliu: wel, the first or last doesnt make much sense anyway. u never knows which binding get loads first on different os and platform
(02:25:34) jboynes: well you want one :-)
(02:25:49) jboynes: and "first" is really "first succeeds , others are ignored"
(02:26:09) jboynes: vs "first suceed, all others get an error"
(02:26:19) jervisliu: but anyway, its much clear to me now.
(02:26:41) jboynes: there's also the case where the celtix binding is deployed twice ;-)

> Support new binding elements <binding.axis> and <binding.celtix>
> ----------------------------------------------------------------
>
>                 Key: TUSCANY-638
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-638
>             Project: Tuscany
>          Issue Type: New Feature
>          Components: Java SCA Axis Binding, Java SCA Celtix Binding
>            Reporter: Jervis Liu
>
> When spec binding <binding.ws> is used, we can assume that users do not care and should not care which Web Service binding implementation is used as all implementations should conform to the spec. It is up to the implementation of LoaderRegistry to determine which implementation of <binding.ws> to load using its own way. In this case, there is no guarantee to users that which binding implementation is getting used in Tuscany. If users do wish to use a specific binding implementation for some reasons, they need to do so by using a non-spec binding element , such as  <binding.axis> and <binding.celtix>, which are extended from binding element.  <binding.celtix> is product type binding that supports various bindings/protocols, such as soap/http and JMS. Users need Celtix specific knowledge in order to know how to configure which binding/protocol is being used. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org