You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Lukasz Lichota <Lu...@sabre.com> on 2009/11/25 10:41:05 UTC
One endpoint handling multiple URL paths
hello folks,
I'd like to have one @WebServiceProvider endpoint but I'd like it to handle
all request coming to certain path "subfolders" that is e.g. /myservice/*.
So in other words when a client call /myservice/aaaa or /myservice/bbb the
same endpoint is invoked.
is there a way to do such thing?
regards
Lukasz
--
View this message in context: http://old.nabble.com/One-endpoint-handling-multiple-URL-paths-tp26509853p26509853.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: One endpoint handling multiple URL paths
Posted by Lukasz Lichota <Lu...@sabre.com>.
ah ok, indeed it works,
I knew about the servlet but it's almost alwasy mapped to '*', but I tried
and it worked,
the missing point was that I didn't know that when I have endpoint
/myservice/ then the request
to /myservice/something goes also to this endpoint and this actually what I
was asking for
thanks !
Sergey Beryozkin-2 wrote:
>
> Hi,
>
> So having a single CXFServlet with a "/myservice/*" uri pattern does not
> work ? That is, requests with URIs like
> "/myservice/foo" and "/myservice/bar" are not getting dispatched to your
> single provider endpoint ?
>
> Awhile back we worked on a project where JAXWS Provider endpoints were
> used and there were no problems with endpoints getting
> invoked (we had similar requirements regarding the dynamic dispatch).
> Can you provide some more details please ? How do you register your
> endpoint ?
>
> cheers, Sergey
>
>
>
--
View this message in context: http://old.nabble.com/One-endpoint-handling-multiple-URL-paths-tp26509853p26612765.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: One endpoint handling multiple URL paths
Posted by Sergey Beryozkin <sb...@progress.com>.
Hi,
So having a single CXFServlet with a "/myservice/*" uri pattern does not work ? That is, requests with URIs like
"/myservice/foo" and "/myservice/bar" are not getting dispatched to your single provider endpoint ?
Awhile back we worked on a project where JAXWS Provider endpoints were used and there were no problems with endpoints getting
invoked (we had similar requirements regarding the dynamic dispatch).
Can you provide some more details please ? How do you register your endpoint ?
cheers, Sergey
> Use case here is that the implementation should do some generic (custom)
> stuff like e.g. kind of dispatching. That's why the client need to be able
> to call certain endpoint (path) but because underlying implementation is the
> same I don't want to configure manually all endpoints to point to the
> implementing bean, the more that this requires manual configuration each
> time a new endpoint should be added.
>
> If handling '*' is possible than no code/configuration changes is needed to
> add another endpoint. The implementation can then determine the actual
> service that the client invoked based on the actual path that was used (plus
> payload if needed).
>
>
> vickatvuuch wrote:
>>
>> one way is to have a spring bean impl shared by two different jaxb and/or
>> jaxrs endpoints,
>> not sure though what is the use case here?
>>
>>
>
> --
> View this message in context: http://old.nabble.com/One-endpoint-handling-multiple-URL-paths-tp26509853p26525279.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
Re: One endpoint handling multiple URL paths
Posted by Lukasz Lichota <Lu...@sabre.com>.
Use case here is that the implementation should do some generic (custom)
stuff like e.g. kind of dispatching. That's why the client need to be able
to call certain endpoint (path) but because underlying implementation is the
same I don't want to configure manually all endpoints to point to the
implementing bean, the more that this requires manual configuration each
time a new endpoint should be added.
If handling '*' is possible than no code/configuration changes is needed to
add another endpoint. The implementation can then determine the actual
service that the client invoked based on the actual path that was used (plus
payload if needed).
vickatvuuch wrote:
>
> one way is to have a spring bean impl shared by two different jaxb and/or
> jaxrs endpoints,
> not sure though what is the use case here?
>
>
--
View this message in context: http://old.nabble.com/One-endpoint-handling-multiple-URL-paths-tp26509853p26525279.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: One endpoint handling multiple URL paths
Posted by vickatvuuch <vl...@gmail.com>.
one way is to have a spring bean impl shared by two different jaxb and/or
jaxrs endpoints,
not sure though what is the use case here?
Lukasz Lichota wrote:
>
> hello folks,
>
> I'd like to have one @WebServiceProvider endpoint but I'd like it to
> handle all request coming to certain path "subfolders" that is e.g.
> /myservice/*. So in other words when a client call /myservice/aaaa or
> /myservice/bbb the same endpoint is invoked.
>
> is there a way to do such thing?
>
> regards
> Lukasz
>
--
View this message in context: http://old.nabble.com/One-endpoint-handling-multiple-URL-paths-tp26509853p26520299.html
Sent from the cxf-user mailing list archive at Nabble.com.