You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dan Diephouse (JIRA)" <ji...@apache.org> on 2006/09/25 23:17:50 UTC

[jira] Created: (CXF-116) Remove references to HTTPAddress/SOAPAddress/etc in EndpointInfo

Remove references to HTTPAddress/SOAPAddress/etc in EndpointInfo
----------------------------------------------------------------

                 Key: CXF-116
                 URL: http://issues.apache.org/jira/browse/CXF-116
             Project: CeltiXfire
          Issue Type: Improvement
            Reporter: Dan Diephouse
             Fix For: 2.0-M1


I don't think we should be referencing binding specific extensors in the EndpointInfo. I'd like us to come up with a more generic way to do things.

I think a good 80/20 solution might be to make the EndpointInfo.Address a url string and support having the binding set it. If the protocol isn't url based, it can always set extensors.

We also might want to consider tightening up the APIs with the transports at the same time. I'm not sure the Transports should take an EndpointInfo as we might want to use them outside of the service model. We could make an interface which EndpointInfo implements or tie together the EndpointReferenceType in some how too. 

-- 
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] Closed: (CXF-116) Remove references to HTTPAddress/SOAPAddress/etc in EndpointInfo

Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/CXF-116?page=all ]

Dan Diephouse closed CXF-116.
-----------------------------

    Resolution: Fixed

This is fixed now in SVN.

> Remove references to HTTPAddress/SOAPAddress/etc in EndpointInfo
> ----------------------------------------------------------------
>
>                 Key: CXF-116
>                 URL: http://issues.apache.org/jira/browse/CXF-116
>             Project: CeltiXfire
>          Issue Type: Improvement
>            Reporter: Dan Diephouse
>             Fix For: 2.0-M1
>
>
> I don't think we should be referencing binding specific extensors in the EndpointInfo. I'd like us to come up with a more generic way to do things.
> I think a good 80/20 solution might be to make the EndpointInfo.Address a url string and support having the binding set it. If the protocol isn't url based, it can always set extensors.
> We also might want to consider tightening up the APIs with the transports at the same time. I'm not sure the Transports should take an EndpointInfo as we might want to use them outside of the service model. We could make an interface which EndpointInfo implements or tie together the EndpointReferenceType in some how too. 

-- 
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