[ http://issues.apache.org/jira/browse/AXIS2-1604?page=comments#action_12447771 ] Deepal Jayasinghe commented on AXIS2-1604: ------------------------------------------
Hi Michele; When I introduce the concept of service life cycle I specifically said that there is no any correlation between service life cycle class and business implementation class. One can have servicelifecycle class w.o having a business impl class , As far as Axis2 is concerned ServiceClass and ServiceLifeCycle class are two different things and those are totally independent. The whole idea of ServiceLifeCycle (SLC) class is to do the tasks related to AxisService not for Business class, of course SLC class can populate data and business impl class use them. In the same time SLC class has nothing to do with sessions and there will be only one instance of SLC class throughout t the lifetime of the system , but there will be multiple instance of business logic impl class (depending on the session scope). In your case its a special , where you have uses the same class for both Business impl class and SLC class , so how come Axis2 knows that , it assume those two as separate things and create two instances . Well we can write code to do so , but I like to keep them separate. Comments ...... > many service instances are created when application scope service implements > the ServiceLifeCycle interface > ----------------------------------------------------------------------------------------------------------- > > Key: AXIS2-1604 > URL: http://issues.apache.org/jira/browse/AXIS2-1604 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel > Environment: java 1.5, axis2 1.1 branch 30/10/06 > Reporter: Michele Mazzucco > Assigned To: Deepal Jayasinghe > Priority: Blocker > Attachments: 1604.zip, Jira1604.zip, services.xml > > > The service runs in application scope and implements the ServiceLifeCycle > interface, but it does not work as expected. As shown by the tomcat output > below, > different service instances are created (4), while only one should be > available, 2 at deployment time and then each time the web service is invoked! > Nov 3, 2006 6:29:24 PM org.apache.catalina.core.AprLifecycleListener > lifecycleEvent > INFO: The Apache Tomcat Native library which allows optimal performance in > production environments was not found on the java.library.path: > .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java > Nov 3, 2006 6:29:24 PM org.apache.coyote.http11.Http11BaseProtocol init > INFO: Initializing Coyote HTTP/1.1 on http-8080 > Nov 3, 2006 6:29:24 PM org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 2311 ms > Nov 3, 2006 6:29:24 PM org.apache.catalina.core.StandardService start > INFO: Starting service Catalina > Nov 3, 2006 6:29:24 PM org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/5.5.15 > Nov 3, 2006 6:29:24 PM org.apache.catalina.core.StandardHost start > INFO: XML validation disabled > Nov 3, 2006 6:29:26 PM org.apache.catalina.startup.HostConfig deployWAR > INFO: Deploying web application archive axis2.war > 2006-11-03 18:29:28,617 INFO org.apache.axis2.deployment.DeploymentEngine - > Deploying module : addressing-1.1 > 2006-11-03 18:29:28,643 INFO org.apache.axis2.deployment.DeploymentEngine - > Deploying module : managerInterceptor > 2006-11-03 18:29:28,658 INFO org.apache.axis2.deployment.DeploymentEngine - > Deploying module : soapmonitor-1.1 > 2006-11-03 18:29:29,075 INFO ncl.qosp.controller.RoutingService - Startup > time is: Fri Nov 03 18:29:29 GMT 2006 > 2006-11-03 18:29:29,075 INFO ncl.qosp.controller.RoutingService - -- > Constructor > 2006-11-03 18:29:29,169 INFO > ncl.qosp.controller.scheduler.weighted.queue.QueueSizeScheduler - Scheduler > component started > 2006-11-03 18:29:29,169 INFO ncl.qosp.controller.RoutingService - Scheduler > registered to the mbean server > 2006-11-03 18:29:30,921 INFO org.apache.axis2.deployment.DeploymentEngine - > Deploying Web service RoutingService.aar > 2006-11-03 18:29:30,956 INFO org.apache.axis2.deployment.DeploymentEngine - > Deploying Web service version.aar > 2006-11-03 18:29:30,974 INFO ncl.qosp.controller.RoutingService - -- > Constructor > Nov 3, 2006 6:29:32 PM org.apache.coyote.http11.Http11BaseProtocol start > INFO: Starting Coyote HTTP/1.1 on http-8080 > Nov 3, 2006 6:29:32 PM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > Nov 3, 2006 6:29:32 PM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/63 config=null > Nov 3, 2006 6:29:32 PM org.apache.catalina.storeconfig.StoreLoader load > INFO: Find registry server-registry.xml at classpath resource > Nov 3, 2006 6:29:32 PM org.apache.catalina.startup.Catalina start > INFO: Server startup in 8440 ms > 2006-11-03 18:34:51,090 INFO ncl.qosp.controller.RoutingService - -- > Constructor > 2006-11-03 18:41:00,315 INFO ncl.qosp.controller.RoutingService - -- > Constructor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
