It seems there is a bug.
From the log, the components are initialized in the order they are
specified (which is good), but they are not started in the same order (which is bad). I have just fixed that in svn.
Cheers, Guillamue Nodet On 5/17/06, bgoetzmann <[EMAIL PROTECTED]> wrote:
Here the new log : 14:45:24,404 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=ManagementContext 14:45:24,893 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=EnvironmentContext 14:45:24,923 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Registry 14:45:24,953 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Broker 14:45:25,113 | INFO | JBIContainer | activateComponent 989 | Activating component for: [container=ServiceMix,name=#SubscriptionManager#] with service: null component: [EMAIL PROTECTED] 14:45:25,133 | INFO | ComponentMBeanImpl | init 184 | Initializing component: #SubscriptionManager# 14:45:25,343 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=InstallationService 14:45:25,433 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=DeploymentService 14:45:25,662 | INFO | DeploymentService | buildState 683 | Restoring service assemblies 14:45:25,662 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AutoDeploymentService 14:45:25,702 | DEBUG | AutoDeploymentService | readState 564 | State file doesn't exist: C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install.xml 14:45:25,782 | DEBUG | AutoDeploymentService | readState 564 | State file doesn't exist: C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy.xml 14:45:25,792 | DEBUG | ManagementContext | egisterSystemService 567 | Registering system service: org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AdminCommandsService 14:45:25,832 | INFO | JBIContainer | init 519 | ServiceMix JBI Container (http://servicemix.org/) name: ServiceMix running version: 3.0-SNAPSHOT 14:45:25,842 | INFO | JBIContainer | activateComponent 989 | Activating component for: [container=ServiceMix,name=jsr181] with service: null component: [EMAIL PROTECTED] 14:45:25,842 | INFO | ComponentMBeanImpl | init 184 | Initializing component: jsr181 14:45:25,902 | DEBUG | Jsr181SpringComponent | init 103 | Initializing component 14:45:25,912 | DEBUG | JBIContainer | etTransactionManager 635 | No transaction manager found from naming context: scheme java not recognized 14:45:26,651 | DEBUG | Jsr181SpringComponent | registerService 284 | 14:45:26,711 | DEBUG | Jsr181SpringComponent | init 110 | Component initialized 14:45:26,721 | INFO | JBIContainer | activateComponent 989 | Activating component for: [container=ServiceMix,name=ID:bgoetzmann-2691-1147869920468-0:0] with service: null component: [EMAIL PROTECTED] 14:45:26,721 | INFO | ComponentMBeanImpl | init 184 | Initializing component: ID:bgoetzmann-2691-1147869920468-0:0 14:45:26,731 | DEBUG | HttpSpringComponent | init 103 | Initializing component 14:45:27,101 | DEBUG | HttpSpringComponent | init 110 | Component initialized 14:45:27,111 | DEBUG | HttpSpringComponent | start 195 | Starting component 14:45:27,161 | INFO | log | info 216 | Logging to [EMAIL PROTECTED] via org.mortbay.log.Slf4jLog 14:45:27,410 | INFO | log | info 216 | Started SelectChannelConnector @ localhost:8194 14:45:27,660 | DEBUG | HttpSpringComponent | start 201 | Component started 14:45:27,720 | DEBUG | Jsr181SpringComponent | start 195 | Starting component 14:45:27,740 | DEBUG | ComponentContextImpl | activateEndpoint 133 | Component: jsr181 activated endpoint: {http://servicemix.org/test/}Hello : testService 14:45:27,740 | DEBUG | Jsr181SpringComponent | etServiceDescription 72 | Querying service description for ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService] 14:45:27,750 | DEBUG | EndpointRegistry | facesFromDescription 274 | Endpoint ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService] implements interface {http://servicemix.org/test/}HelloPortType 14:45:27,760 | DEBUG | Jsr181SpringComponent | injectContext 169 | Unable to inject ComponentContext: TestService.setContext(javax.jbi.component.ComponentContext) 14:45:27,760 | DEBUG | Jsr181SpringComponent | start 201 | Component started 14:45:27,770 | DEBUG | AutoDeploymentService | monitorDirectory 484 | Monitoring directory C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or modified archives 14:45:27,780 | DEBUG | AutoDeploymentService | monitorDirectory 484 | Monitoring directory C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified archives -- View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4429778 Sent from the ServiceMix - User forum at Nabble.com.
-- Cheers, Guillaume Nodet
