cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akitoshi Yoshida (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5984) Provide a simple way start a decoupled servlet endpoint
Date Wed, 10 Sep 2014 09:11:28 GMT

     [ https://issues.apache.org/jira/browse/CXF-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Akitoshi Yoshida resolved CXF-5984.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.1.0
                   3.0.2

> Provide a simple way start a decoupled servlet endpoint
> -------------------------------------------------------
>
>                 Key: CXF-5984
>                 URL: https://issues.apache.org/jira/browse/CXF-5984
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 3.0.1
>            Reporter: Akitoshi Yoshida
>            Assignee: Akitoshi Yoshida
>             Fix For: 3.0.2, 3.1.0
>
>
> Typically, the endpoint address of a decoupled http endpoint is given as a full http
URL and the corresponding destination will be set up as a jetty destination. In some cases,
where the client is running in a container that has the CXFServlet, it is useful to start
a servlet destination using this servlet.
> We can provide this option by allowing the endpoint address to be given as a relative
path (as used in the servlet destination) and use another runtime property to create the full
http URL when setting the WS-A ReplyTo header.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message