[jira] Resolved: (TUSCANY-336) After comonent is stopped, can still locateService

["Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/TUSCANY-336?page=all ]
     
Jean-Sebastien Delfino resolved TUSCANY-336:
--------------------------------------------

    Resolution: Fixed
     Assign To: Jim Marino

This looks very similar to another issue that Jim fixed last week. Could you please verify that this is now fixed on the latest code? Thanks!

> After comonent is stopped, can still locateService
> --------------------------------------------------
>
>          Key: TUSCANY-336
>          URL: http://issues.apache.org/jira/browse/TUSCANY-336
>      Project: Tuscany
>         Type: Bug

>  Environment: Win2000
>     Reporter: Yang Lei
>     Assignee: Jim Marino

>
> I was using the following code to stop a context ( component)
> public void stopModule(String name) {
> 		System.out.println("action stop module");
> 		Context context = getContext(name);
> 		display(context);
> 		if (context!=null)
> 		{
> 			if (context.getLifecycleState() == context.STOPPED)
> 				System.out.println("The module has already stopped.");
> 			else
> 			{
> 				System.out.println("Stopping module...");
> 				context.stop();
> 				
> 			}
> 		}else
> 		{
> 			System.out.println("The module is not available...");
> 		}
> 		
> 		display(context);
> 	}
> I can still locate the service after the context (component) is stopped:
> my service starting
> The next holiday is: Mon May 29 00:00:00 EDT 2006
> ...Stop MyService in Client1
> action stop module
> Context [MyServiceComponent] in state [RUNNING]
> Stopping module...
> Context [MyServiceComponent] in state [STOPPED]
> The next holiday is: Mon May 29 00:00:00 EDT 2006

-- 
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