[ 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
