Return-Path: 
 <cxf-dev-return-675-apmail-incubator-cxf-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org
Received: (qmail 66441 invoked from network); 28 Sep 2006 09:03:45 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 28 Sep 2006 09:03:45 -0000
Received: (qmail 27640 invoked by uid 500); 28 Sep 2006 09:03:44 -0000
Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org
Received: (qmail 27601 invoked by uid 500); 28 Sep 2006 09:03:44 -0000
Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:cxf-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:cxf-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:cxf-dev@incubator.apache.org>
List-Id: <cxf-dev.incubator.apache.org>
Reply-To: cxf-dev@incubator.apache.org
Delivered-To: mailing list cxf-dev@incubator.apache.org
Received: (qmail 27590 invoked by uid 99); 28 Sep 2006 09:03:44 -0000
Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org)
 (140.211.166.84)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Sep 2006 02:03:44 -0700
X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=
Received: from [63.65.132.112] ([63.65.132.112:34695]
 helo=amereast-smg2.iona.com)
	by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP
	id 4D/CC-05478-DEF8B154 for <cxf-dev@incubator.apache.org>;
 Thu, 28 Sep 2006 02:03:42 -0700
Received: from amereast-ems2.IONAGLOBAL.COM ([10.65.6.84])
	by amereast-smg2.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
 k8S8v40k019141
	for <cxf-dev@incubator.apache.org>; Thu, 28 Sep 2006 04:57:14 -0400 (EDT)
Received: from [10.129.9.105] ([10.129.9.105]) by amereast-ems2.IONAGLOBAL.COM
 with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 28 Sep 2006 05:03:25 -0400
Message-ID: <451B8F75.90106@iona.com>
Date: Thu, 28 Sep 2006 17:01:41 +0800
From: Jiang Ning <ning.jiang@iona.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cxf-dev@incubator.apache.org
Subject: Re: How can I setup the configuration for management
References: <451A34A9.9050707@iona.com> <451A64B0.7060507@iona.com>
 <451B73D2.5000708@iona.com> <451B75CB.8050303@iona.com>
In-Reply-To: <451B75CB.8050303@iona.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Sep 2006 09:03:26.0311 (UTC)
 FILETIME=[F551F770:01C6E2DC]
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Andrea

Just a quick question about your latest commit which includes an 
management configuration.
   <bean id="org.apache.cxf.management.InstrumentationManager" 
abstract="true">
I checked abstract with the spring reference :

Is this bean "abstract", i.e. not meant to be instantiated itself but
rather just serving as parent for concrete child bean definitions. 



I can't tell which is the parent and which is child.

I got the example from spring reference CH3
<bean id="inheritedTestBeanWithoutClass" abstract="true">
    <property name="name" value="parent"/>
    <property name="age" value="1"/>
</bean>

<bean id="inheritsWithClass" class="org.springframework.beans.DerivedTestBean"
    parent="inheritedTestBeanWithoutClass" init-method="initialize">
  <property name="name" value="override"/>
  /<!-- age will inherit value of 1 from parent -->/
</bean> 

So org.apache.cxf.management.InstrumentationManager just the Templet bean. 
How can this bean value be set to InstrumentationManagerConfigBean?
What does the bean's id mean to InstrumentationManagerConfigBean which is really used in management?  


Thanks

Willem.



Andrea Smyth wrote:

> Jiang Ning wrote:
>
>> Hi Andrea,
>>
>> Thank you for your replay. Just one more question I want to ask,  
>> current  configuration Spring Beans provider getter ,setter method 
>> and can be set the value by Spring reading the configure xml, but If 
>> the Spring Beans values of complex types which are generated by JAXB 
>> not support this.
>
>
> Hi Willem,
>
> This is supported - see test case 
> org.apache.cxf.configuraton.spring.JaxbPropertyEditorTest in 
> cxf-common-utilities.
> It's just that these complex types, or rather property editors for 
> them,  have to be registered.
> I'll commit a fix soon.
>
> Cheers,
> Andrea.
>
>
>> eg. If I just want to enable the JMS In the configuration, how can I 
>> just write the configuration like this.
>>  <bean class="org.apache.cxf.management.InstrumentationConfigBean">
>>     <property name="instrumentationControl">
>>         <value>
>>               <bean 
>> class="org.apache.cxf.management.InstrumentationType"> 
>>                                            <property name 
>> ="jMXEnabled" value= "true"/>
>>               </bean>
>>         </value>
>>     </property>
>> </bean>
>>
>> Thanks,
>> Willem.
>>
>>
>> Andrea Smyth wrote:
>>
>>> Hi Willem,
>>>
>>> First I need to get the property editors for the non-standard types 
>>> registered - I have created JIRA CXF-123 for this.
>>> Second, you should update the contents of the value elements below 
>>> to conform to the new (simplified)  instrumentation.xsd schema.
>>> Will let you know when the CXF-123 is resolved.
>>>
>>> Andrea.
>>>
>>>
>>> Jiang Ning wrote:
>>>
>>>> Hi Adrea,
>>>> I had tried to use the new cxf configuration for  management. I 
>>>> can't make the xjc created class be set value by spring config xml.
>>>> Here is the Celtix style configuration to enable the JMX and setup 
>>>> the JMX Connetor's URL.
>>>> <bean class="org.apache.cxf.management.InstrumentationConfigBean">
>>>>      <property name="instrumentationControl">
>>>>          <value>
>>>>                <im:instrumentation>
>>>>                        
>>>> <im:InstrumentationEnabled>true</im:InstrumentationEnabled>
>>>>                        <im:JMXEnabled>true</im:JMXEnabled>
>>>>                </im:instrumentation>
>>>>          </value>
>>>>      </property>
>>>>      <property name="MBServer">
>>>>          <value>
>>>>             <im:MBServer>
>>>>                <im:JMXConnector>
>>>>                   <im:Threaded>true</im:Threaded>
>>>>                   <im:Daemon>false</im:Daemon>
>>>>                   
>>>> <im:JMXServiceURL>service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/server</im:JMXServiceURL> 
>>>>
>>>>                 </im:JMXConnector>
>>>>              </im:MBServer>
>>>>          </value>
>>>>      </property>
>>>>  </bean>
>>>> Can you get me the example how can these complex value type can be 
>>>> set with the new CXF configuration.
>>>>
>>>> Thanks,
>>>>
>>>> Willem.
>>>>
>>>>
>>>
>>>
>
>