On 8/7/07 12:15 PM, "Daniel Kulp" <[EMAIL PROTECTED]> wrote:

Do you have a target release date for 2.0.1?

Regards,
Randy Burgess
Web Applications Developer
Nuvox Communications


> 
> Adding features to the bus wasn't added until after 2.0.    It should be
> in 2.0.1 if you want to test those release candidates:
> 
> http://people.apache.org/~dkulp/stage_cxf/2.0.1-incubator_take2/dist/
> 
> 
> Dan
> 
> On Tuesday 07 August 2007 12:07, Trenaman, Adrian wrote:
>> Hi all,
>> 
>> I was playing around with the logging feature in CXF 2.0, whereby you
>> can turn on logging with a really quick entry into the cxf.xml file,
>> ala:
>> 
>> <beans xmlns="http://www.springframework.org/schema/beans";
>>       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>       xmlns:cxf="http://cxf.apache.org/core";
>>       xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>> http://cxf.apache.org/core http://cxf.apache.org/schemas/core.xsd";>
>> 
>>   <cxf:bus>
>>    <cxf:features>
>>     <cxf:logging />
>>    </cxf:features>
>>   </cxf:bus>
>> 
>> </beans>
>> 
>> ... however, I'm finding that I get an error when I try and run: "The
>> matching wildcard is strict, but no declaration can be found for
>> element 'cxf:bus'." This seems similar to an issue uncovered by
>> Richard Shaw some time ago; his problem was I think with the HTTP
>> configuration. Any ideas on how to get around this?
>> 
>> To reproduce, simply copy the attached cxf.xml file over the one in
>> the samples/hello_world directory, and run the demo.
>> 
>> Thanks,
>> Ade.
>> 
>> ----------------------------
>> IONA Technologies PLC (registered in Ireland)
>> Registered Number: 171387
>> Registered Address: The IONA Building, Shelbourne Road, Dublin 4,
>> Ireland





This email and any attachments ("Message") may contain legally privileged 
and/or confidential information.  If you are not the addressee, or if this 
Message has been addressed to you in error, you are not authorized to read, 
copy, or distribute it, and we ask that you please delete it (including all 
copies) and notify the sender by return email.  Delivery of this Message to any 
person other than the intended recipient(s) shall not be deemed a waiver of 
confidentiality and/or a privilege.

Reply via email to