We used 4.3.0-fuse-01-00 so that explains it.
Of course it's not a camel problem now that I actually read the jira properly..
/Bjorn



On Sat, Oct 16, 2010 at 6:22 AM, Willem Jiang <[email protected]> wrote:
> Did you update the CXF version to pick up the osgi transport fix.
>
> 2010/10/16, Freeman Fang <[email protected]>:
>> Hi,
>> Next SMX4.3 release I mentioned here is Apache SMX 4.3.
>>
>> Also, this is a cxf issue not camel issue, so camel 2.4 absolutely not
>> have the fix :-)
>> I don't think the fuse esb 4.3 you use has this fix.
>> Could you tell me exactly the fuse esb version?
>>
>> I test it with the latest 4.3.0-fuse-02-00, it already pick up the fix.
>> Also I test with 4.3.0-fuse-01-00, which doesn't pick up the fix.
>> So what I can suggest is play with the latest 4.3.0-fuse-02-00
>> Freeman
>> On 2010-10-15, at 下午11:28, Björn Bength wrote:
>>
>>> Thanks freeman,
>>>
>>> However, we use fuse usb 4.3 which uses a variant of camel 2.4 and
>>> still see this issue although
>>> the ticket states its fixed in camel 2.3 as late as aug 26 2010.
>>> which is really confusing.
>>>
>>> Regards
>>> bjorn
>>>
>>>
>>> On Fri, Oct 15, 2010 at 4:04 PM, Freeman Fang
>>> <[email protected]> wrote:
>>>> Hi,
>>>>
>>>> Yeah, I can reproduce the problem on SMX 4.2.
>>>> I believe both of you encounter a cxf http-osgi transport issue
>>>> which is
>>>> tracked by CXF-2947[1] and already get fixed.
>>>>
>>>> Next SMX4.3 release will pick up this fix.
>>>>
>>>> I can verify this fix on SMX4.3 snapshot kit I build locally.
>>>> [1]https://issues.apache.org/jira/browse/CXF-2947
>>>>
>>>> Freeman
>>>> On 2010-10-15, at 下午6:46, Björn Bength wrote:
>>>>
>>>>> This behaviour is not specific to cxfrs but also any cxf endpoint.
>>>>> We have noticed that the service (in the soap case) still appear to
>>>>> work ok, but we can no longer access the wsdl by appending ?wsdl.
>>>>> /Bjorn
>>>>>
>>>>>
>>>>> On Fri, Oct 15, 2010 at 11:02 AM, Auke <[email protected]> wrote:
>>>>>>
>>>>>> I have some issues with bundles that make use of the cxfrs
>>>>>> component. I
>>>>>> can
>>>>>> reproduce with the given example as well:
>>>>>>
>>>>>> 1. install examples-cxf-jaxrs feature
>>>>>>
>>>>>> 2. Go to  http://localhost:8181/cxf/crm/customerservice/customers/123
>>>>>> http://localhost:8181/cxf/crm/customerservice/customers/123  and
>>>>>> see the
>>>>>> correct result.
>>>>>>
>>>>>> 3. update the corresponding 'Apache ServiceMix Example :: CXF JAX-
>>>>>> RS
>>>>>> OSGI'
>>>>>> bundle.
>>>>>>
>>>>>> 4. Go to  http://localhost:8181/cxf/crm/customerservice/customers/123
>>>>>> http://localhost:8181/cxf/crm/customerservice/customers/123  and
>>>>>> see a
>>>>>> 404.
>>>>>>
>>>>>> Incidentally if you look at the  http://localhost:8181/cxf/
>>>>>> http://localhost:8181/cxf/  response in both cases it changes from:
>>>>>>
>>>>>> Endpoint address: http://localhost:8181/cxf/crm
>>>>>> WADL : http://localhost:8181/cxf/crm?_wadl&type=xml
>>>>>>
>>>>>> into
>>>>>>
>>>>>> Endpoint address: /crm
>>>>>> WADL : /crm?_wadl&type=xml
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> --
>>>>>> View this message in context:
>>>>>> http://servicemix.396122.n5.nabble.com/REST-service-stops-working-when-updating-bundle-with-cxfrs-bean-route-tp3213372p3213372.html
>>>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>>>
>>>>
>>>>
>>>> --
>>>> Freeman Fang
>>>>
>>>> ------------------------
>>>> blog: http://freemanfang.blogspot.com
>>>> twitter: http://twitter.com/freemanfang
>>>> Open Source SOA: http://fusesource.com
>>>> Apache Servicemix:http://servicemix.apache.org
>>>> Apache Cxf: http://cxf.apache.org
>>>> Apache Karaf: http://karaf.apache.org
>>>> Apache Felix: http://felix.apache.org
>>>>
>>>>
>>
>>
>> --
>> Freeman Fang
>>
>> ------------------------
>> blog: http://freemanfang.blogspot.com
>> twitter: http://twitter.com/freemanfang
>> Open Source SOA: http://fusesource.com
>> Apache Servicemix:http://servicemix.apache.org
>> Apache Cxf: http://cxf.apache.org
>> Apache Karaf: http://karaf.apache.org
>> Apache Felix: http://felix.apache.org
>>
>>
>
> --
> 从我的移动设备发送
>

Reply via email to