[Springframework-cvs] spring/docs/reference/src jmx.xml,1.40,1.41

[Juergen H. <jho...@us...>]

Update of /cvsroot/springframework/spring/docs/reference/src
In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv6171/docs/reference/src

Modified Files:
	jmx.xml 
Log Message:
added warning on JMX annotations with JDK proxies

Index: jmx.xml
===================================================================
RCS file: /cvsroot/springframework/spring/docs/reference/src/jmx.xml,v
retrieving revision 1.40
retrieving revision 1.41
diff -C2 -d -r1.40 -r1.41
*** jmx.xml	21 Jul 2008 13:36:52 -0000	1.40
--- jmx.xml	20 Oct 2008 20:52:20 -0000	1.41
***************
*** 643,651 ****
  
        <para>As you can see little has changed, other than the basic syntax of
!       the metadata definitions. Behind the scenes this approach is a little
!       slower at startup because the JDK 5.0 annotations are converted into the
!       classes used by Commons Attributes. However, this is only a one-off cost
!       and JDK 5.0 annotations give you the added (and valuable) benefit of
!       compile-time checking.</para>
  
        <programlisting><![CDATA[<beans>
--- 643,647 ----
  
        <para>As you can see little has changed, other than the basic syntax of
!       the metadata definitions.</para>
  
        <programlisting><![CDATA[<beans>
***************
*** 961,965 ****
  
      <section id="jmx-interface-java">
!       <title>Defining Management interfaces using Java interfaces</title>
  
        <para>In addition to the
--- 957,961 ----
  
      <section id="jmx-interface-java">
!       <title>Defining management interfaces using Java interfaces</title>
  
        <para>In addition to the
***************
*** 1244,1247 ****
--- 1240,1252 ----
        <programlisting><![CDATA[<context:mbean-export server="myMBeanServer" default-domain="myDomain"/>]]></programlisting>.
  
+       <note>
+         <para>Do not use interface-based AOP proxies in combination with autodetection of
+         JMX annotations in your bean classes. Interface-based proxies 'hide' the target class,
+         which also hides the JMX managed resource annotations. Hence, use target-class proxies
+         in that case: through setting the 'proxy-target-class' flag on <literal>&lt;aop:config/&gt;</literal>,
+         <literal>&lt;tx:annotation-driven/&gt;</literal>, etc. Otherwise, your JMX beans
+         might be silently ignored at startup...</para>
+       </note>
+ 
      </section>
    </section>