[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Gavin King]

  User: gavin   
  Date: 07/02/22 17:09:21

  Modified:    doc/reference/en/modules  spring.xml
  Log:
  minor
  
  Revision  Changes    Path
  1.8       +4 -2      jboss-seam/doc/reference/en/modules/spring.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: spring.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/spring.xml,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -b -r1.7 -r1.8
  --- spring.xml	22 Feb 2007 22:07:49 -0000	1.7
  +++ spring.xml	22 Feb 2007 22:09:21 -0000	1.8
  @@ -188,12 +188,14 @@
           <para> Seam-scoped Spring beans defined this way can be injected into other Spring beans without the use of
               <literal>&lt;seam:instance/&gt;</literal>. However, care must be taken to ensure scope impedance is 
               maintained. The normal approach used in Spring is to specify <literal>&lt;aop:scoped-proxy/&gt;</literal> 
  -            in the bean definition. However, Seam-scoped Spring beans are <emphasis>not</emphasis> compatible with
  +            in the bean definition. But Seam-scoped Spring beans are <emphasis>not</emphasis> compatible with
               <literal>&lt;aop:scoped-proxy/&gt;</literal>. So if you need to inject a Seam-scoped Spring bean
               into a singleton, <literal>&lt;seam:instance/&gt;</literal> must be used: </para>
               
           <programlisting><![CDATA[<bean id="someSpringBean" class="SomeSpringBeanClass" scope="seam.CONVERSATION"/>
           
  +...
  +
   <bean id="someSingleton">
       <property name="someSeamScopedSpringBean">
           <seam:instance name="someSpringBean" proxy="true"/>