Thanks for catching that , will retest. I'm amazed it was working for me as I just incorrectly documented it . That's not the behavior I would have expected given the history.
Robert On 10/9/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Robert, Slight change needed! Please see http://marc.theaimsgroup.com/?l=axis-dev&m=115946726421521&w=2 the parameter name is ServiceTCCL and the value is composite. -- dims On 10/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: robertlazarski > Date: Mon Oct 9 13:09:38 2006 > New Revision: 454484 > > URL: http://svn.apache.org/viewvc?view=rev&rev=454484 > Log: > still have two copies? > > Modified: > webservices/axis2/branches/java/1_1/xdocs/spring.html > > Modified: webservices/axis2/branches/java/1_1/xdocs/spring.html > URL: http://svn.apache.org/viewvc/webservices/axis2/branches/java/1_1/xdocs/spring.html?view=diff&rev=454484&r1=454483&r2=454484 > ============================================================================== > --- webservices/axis2/branches/java/1_1/xdocs/spring.html (original) > +++ webservices/axis2/branches/java/1_1/xdocs/spring.html Mon Oct 9 13:09:38 2006 > @@ -35,7 +35,7 @@ > <h2>Introduction</h2> > > <p>The idea behind Axis2 and Spring integration is that Axis2 simply needs to > -have Spring supply in one of its pre-loaded beans to the Axis2 Message > +have Spring supply one of its pre-loaded beans to the Axis2 Message > Receiver defined in the AAR services.xml . While Axis2 typically uses > reflection to instantiate the ServiceClass defined in the services.xml that > the Message Receiver will use, alternatively one can define a > @@ -412,7 +412,7 @@ > }</pre> > </source> > <p>Here's the services.xml that now includes SpringInit and the > - needed load-on-startup parameter. There is also the forceTCCL parameter which is needed > + needed load-on-startup parameter. There is also the composite parameter which is needed > when loading Spring in the AAR - see the <a href="#263">Known issues running Spring inside the AAR</a> > area. </p> > <source><pre><serviceGroup> > @@ -421,7 +421,7 @@ > This is a spring sample Web Service with two operations. > </description> > <parameter name="ServiceClass" locked="false">spring.SpringInit</parameter> > - <parameter name="forceTCCL" locked="false">true</parameter> > + <parameter name="composite" locked="false">true</parameter> > <parameter name="load-on-startup" locked="false">true</parameter> > <operation name="springInit"> > <messageReceiver class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/> > @@ -445,8 +445,8 @@ > </li> > </ul> > <p>The Axis2 classloader strategy by default does not permit Spring to run inside the AAR. To allow > - Spring to run inside the AAR, the forceTCCL parameter is used in the services.xml as shown in the example > - above. The behavior of forceTCCL was the default in the developement cycle in between 1.0 and 1.1, but > + Spring to run inside the AAR, the 'composite' parameter is used in the services.xml as shown in the example > + above. The behavior of 'composite' was the default in the developement cycle in between 1.0 and 1.1, but > it resulted in the JIRA issue AXIS2-1214 - essentially problems with getting an initContext.lookup() > handle inside the AAR. Spring users typically have little desire to use initContext.lookup() however, > as they get their Datasources via org.springframework.jdbc.datasource.DriverManagerDataSource in an > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
