Hi Josh
Sergey,
Thanks again for the detailed documentation you've provided in this thread.
I was able to easily convert from JAX-WS to JAX-RS, which (I think) will
make our lives even easier. Once we've got the ability to expose a single
service with both of these frontends, I'll make use of t
2009/6/24 Daniel Kulp :
> Any chance you could try with Jetty? Maybe Jetty does something different.
Sure, I'll need to install a few things on the server first -- I'll
set it up today hopefully and let you know what happens.
Andrew.
--
:: http://biotext.org.uk/ ::
On Thu June 25 2009 1:39:34 am liucong wrote:
> Hi, Dan,
>
> Thank you very much for your advice. By some experiments for the
> WSDL extension. I think it is right that this WSDL extension needs some
> changes to CXF wsdl processing. And the CXF wsdl processing will supoort
> the entension in
Unfortunately, circumstances conspire against me...
Our network guys said it would take a couple of days to open another
port to test this with Jetty, meanwhile the guy at the remote site who
wrote the client is leaving today, which I only just found out.
So I'll have to simulate it here in order
Hi Josh
I'd like to ask your opinion about providing JAXRS providers through this
pattern.
I'm not sure how CXF keeps track of these providers now, but I assume
there's a registry of some kind. Are the providers tied to specific jax-rs
resources, or are they "global"? If it's a global
On Thu, Jun 25, 2009 at 8:46 AM, Sergey Beryozkin wrote:
> Hi Josh
>
>
> I'd like to ask your opinion about providing JAXRS providers through this
>>> pattern.
>>>
>>
>
>>
>>>
> I'm not sure how CXF keeps track of these providers now, but I assume
>> there's a registry of some kind. Are the pr
Hi
Please see my comments with prefixed with S.B.
>>
>>>
> I'm not sure how CXF keeps track of these providers now, but I assume
>> there's a registry of some kind. Are the providers tied to specific
>> jax-rs
>> resources, or are they "global"? If it's a global registry, it should be
>> tri
