axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-540) A default TransportInProtocol
Date Sat, 01 Apr 2006 14:38:28 GMT
    [ 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


Mime
View raw message