You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "rnell (JIRA)" <ji...@apache.org> on 2006/04/01 00:01:37 UTC
[jira] Created: (AXIS2-540) A default TransportInProtocol
A default TransportInProtocol
-----------------------------
Key: AXIS2-540
URL: http://issues.apache.org/jira/browse/AXIS2-540
Project: Apache Axis 2.0 (Axis2)
Type: New Feature
Components: client-api
Reporter: rnell
Priority: Minor
it would be nice if:
1) options.setTo(targetEPR);
2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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
[jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by "Michel.Drescher (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-540?page=comments#action_12372763 ]
Michel.Drescher commented on AXIS2-540:
---------------------------------------
Hi all,
I strongly advise against this - it would break WS-Addressing compatibility (and more).
WS-Addressing gives abstract, transport-agnostic message properties. THe important point here is that the transport protocol is NOT defined in any WSA construct, it is rather defined n the WebService's WSDL in the binding secion!
> A default TransportInProtocol
> -----------------------------
>
> Key: AXIS2-540
> URL: http://issues.apache.org/jira/browse/AXIS2-540
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: client-api
> Reporter: rnell
> Priority: Minor
>
> it would be nice if:
> 1) options.setTo(targetEPR);
> 2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
> if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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
[jira] Resolved: (AXIS2-540) A default TransportInProtocol
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-540?page=all ]
Davanum Srinivas resolved AXIS2-540:
------------------------------------
Resolution: Won't Fix
marking as wont fix.
-- dims
> A default TransportInProtocol
> -----------------------------
>
> Key: AXIS2-540
> URL: http://issues.apache.org/jira/browse/AXIS2-540
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: client-api
> Reporter: rnell
> Priority: Minor
>
> it would be nice if:
> 1) options.setTo(targetEPR);
> 2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
> if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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
Re: [jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by Michel Drescher <Mi...@uk.fujitsu.com>.
Hi Sanjiva,
On 2 Apr 2006, at 8:38, Sanjiva Weerawarana wrote:
> On Sun, 2006-04-02 at 08:31 +0100, Michel.Drescher (JIRA) wrote:
>> [ http://issues.apache.org/jira/browse/AXIS2-540?
>> page=comments#action_12372822 ]
>>
>> Michel.Drescher commented on AXIS2-540:
>> ---------------------------------------
>>
>> Still, the address property of the EPR is NOT determining the
>> transport
>> protocol, whether WSDL is involved or not. THis is just the wrong
>> way
>> to do it, even if I would program against the API.
>
> I guess I don't understand ... in *most* cases, the address
> property of
> the EPR *does* determine the protocol and the physical address as
> well.
> In some cases (like having an explicit proxy of some sort) it
> doesn't -
> and we have a property that can be set to indicate that address.
The fact that an EPR is by about 99% a URL does not mean you can
extract its scheme, see that it is "http" and just go along with this.
The EPR's address property is a URI, and as such, just a string with
a defined formatting. This string, however, is just an identifier
with no additional sematics (as opposed to a URL, which incorporates
a scheme/transport id, authority, etc.) An example for such
identifying strings are XML namespaces, which are in overwhelming
majority URLs (because they offer intrinsic uniqueness).
But still, they are just identifier, nothing more.
As an example, WSRF uses WS-Addressing to identify the resource to
which to send the messages. It explicitly does *not* mention any
transport layer, as WSRF is itself transport agnostic. This way, WSRF
allows you to model your Web Service(s) so that you either offer one
Web Service per Resource, or one Web Service for all your resources.
Does this make it clearer, what I mean?
Cheers,
Michel
Re: [jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Sun, 2006-04-02 at 08:31 +0100, Michel.Drescher (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/AXIS2-540?page=comments#action_12372822 ]
>
> Michel.Drescher commented on AXIS2-540:
> ---------------------------------------
>
> Still, the address property of the EPR is NOT determining the transport
> protocol, whether WSDL is involved or not. THis is just the wrong way
> to do it, even if I would program against the API.
I guess I don't understand ... in *most* cases, the address property of
the EPR *does* determine the protocol and the physical address as well.
In some cases (like having an explicit proxy of some sort) it doesn't -
and we have a property that can be set to indicate that address.
Sanjiva.
[jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by "Michel.Drescher (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-540?page=comments#action_12372822 ]
Michel.Drescher commented on AXIS2-540:
---------------------------------------
Still, the address property of the EPR is NOT determining the transport protocol, whether WSDL is involved or not. THis is just the wrong way to do it, even if I would program against the API.
> A default TransportInProtocol
> -----------------------------
>
> Key: AXIS2-540
> URL: http://issues.apache.org/jira/browse/AXIS2-540
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: client-api
> Reporter: rnell
> Priority: Minor
>
> it would be nice if:
> 1) options.setTo(targetEPR);
> 2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
> if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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
[jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by "Sanjiva Weerawarana (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-540?page=comments#action_12372780 ]
Sanjiva Weerawarana commented on AXIS2-540:
-------------------------------------------
Absolutely right - but all this is doing is a DII scenario where the user is programming against the API and setting the target EPR. There's absolutely no WSDL involved and no breakage of WS-Addressing; am I missing something??
Going back to the original report, I don't think we require (2) at all .. IMO its a mistake on the user's part. Can the reporter please respond to Dims' comment?
> A default TransportInProtocol
> -----------------------------
>
> Key: AXIS2-540
> URL: http://issues.apache.org/jira/browse/AXIS2-540
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: client-api
> Reporter: rnell
> Priority: Minor
>
> it would be nice if:
> 1) options.setTo(targetEPR);
> 2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
> if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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
[jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-540?page=comments#action_12372833 ]
Eran Chinthaka commented on AXIS2-540:
--------------------------------------
Can we please have this discussion in the mailing list. Answering to some exact points is bit difficult here :(.
> A default TransportInProtocol
> -----------------------------
>
> Key: AXIS2-540
> URL: http://issues.apache.org/jira/browse/AXIS2-540
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: client-api
> Reporter: rnell
> Priority: Minor
>
> it would be nice if:
> 1) options.setTo(targetEPR);
> 2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
> if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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
[jira] Commented: (AXIS2-540) A default TransportInProtocol
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-540?page=comments#action_12372755 ]
Davanum Srinivas commented on AXIS2-540:
----------------------------------------
does the client fail of the setTransportInProtocol is not set? can u please try removing it and post any stack traces?
thanks,
dims
> A default TransportInProtocol
> -----------------------------
>
> Key: AXIS2-540
> URL: http://issues.apache.org/jira/browse/AXIS2-540
> Project: Apache Axis 2.0 (Axis2)
> Type: New Feature
> Components: client-api
> Reporter: rnell
> Priority: Minor
>
> it would be nice if:
> 1) options.setTo(targetEPR);
> 2) options.setTransportInProtocol( new URL( targetEPR.getAddress() ).getProtocol() );
> if line (2) was the default and didn't need to be set. Interestingly, there doesn't seem to be a reply tranport in the WSDL, so the default protocol would likely be the same as the targetEPR.
--
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