You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by bgoetzmann <bg...@sophia.symag.com> on 2006/05/16 12:31:47 UTC
Getting WSDL from a JSR181 POJO Service
Hello,
I try a simple test with ServiceMix to expose a POJO as a web service, using
the following servicemix.xml file :
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:sm="http://servicemix.apache.org/config/1.0"
xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"
xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:test="http://servicemix.org/test/">
<!-- Le conteneur JBI -->
<sm:container id="jbi">
<sm:activationSpecs>
<sm:activationSpec service="test:Hello"
endpoint="testService">
<sm:component>
<jsr181:component>
<jsr181:endpoints>
<jsr181:endpoint
pojoClass="TestService" annotations="none"/>
</jsr181:endpoints>
</jsr181:component>
</sm:component>
</sm:activationSpec>
<sm:activationSpec>
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint
service="test:Hello" endpoint="testService" role="consumer"
defaultOperation="echo" locationURI="http://localhost:8194/Service/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out" soap="true"/>
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:container>
</beans>
My goal is to get the WSDL document corresponding to my POJO exposed as a
web service.
With a JMX Console I see two JMX beans with Type=Endpoint :
- One with Name =
{http___DefaultNamespace}TestServiceTestServiceJBIPort,SubType=Internal
- The other with Name =
{http___servicemix.org_test_}HellotestService,SubType=External
Each of these JMX beans has a getWSDL() operation
A call on this operation for the first beans returns (it seems) a WSDL
document, but for the second, only :
<?xml version="1.0" encoding="UTF-8"?>
I would expect that this call return a valid WSDL document including the URL
for binding (http://localhost:8194/Service/).
Why doest it not the case ?
An other test I make was to try to get the WSDL document using this URL
http://localhost:8194/Service?xml but I get the following error :
"Error 405 : GET not supported"
Is a way to get the WSDL document with an HTTP GET ?
--
View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4406444
Sent from the ServiceMix - User forum at Nabble.com.
Re: Getting WSDL from a JSR181 POJO Service
Posted by Guillaume Nodet <gn...@gmail.com>.
It should, but you have to build from sources, as we have problems
with our nightly snapshots due to maven 2 bugs :(
I'm creating a test case to be sure it works.
Cheers,
Guillaume Nodet
On 5/17/06, bgoetzmann <bg...@sophia.symag.com> wrote:
>
> Guillaume,
> Do you mean that this bug is corrected in the last version of ServiceMix ?
>
> Thank you.
> --
> View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4431589
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: Getting WSDL from a JSR181 POJO Service
Posted by bgoetzmann <bg...@sophia.symag.com>.
Guillaume,
Do you mean that this bug is corrected in the last version of ServiceMix ?
Thank you.
--
View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4431589
Sent from the ServiceMix - User forum at Nabble.com.
Re: Getting WSDL from a JSR181 POJO Service
Posted by Guillaume Nodet <gn...@gmail.com>.
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 <bg...@sophia.symag.com> 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: org.apache.servicemix.jbi.nmr.SubscriptionManager@f1916f
> 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:
> org.apache.servicemix.jsr181.Jsr181SpringComponent@195dd5b
> 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:
> org.apache.servicemix.http.HttpSpringComponent@8aeed0
> 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 org.slf4j.impl.JCLLoggerAdapter@987197 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
Re: Getting WSDL from a JSR181 POJO Service
Posted by bgoetzmann <bg...@sophia.symag.com>.
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: org.apache.servicemix.jbi.nmr.SubscriptionManager@f1916f
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:
org.apache.servicemix.jsr181.Jsr181SpringComponent@195dd5b
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:
org.apache.servicemix.http.HttpSpringComponent@8aeed0
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 org.slf4j.impl.JCLLoggerAdapter@987197 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.
Re: Getting WSDL from a JSR181 POJO Service
Posted by Guillaume Nodet <gn...@gmail.com>.
Could you change the log configuration pattern to something like
%d{ABSOLUTE} | %-5p | %-30.30c{1} | %-20.20M %4L | %m%n
and put name on components
<sm:actionvationSpec id="jsr181"
It should be much more readable.
Cheers,
Guillaume Nodet
On 5/17/06, bgoetzmann <bg...@sophia.symag.com> wrote:
>
> Guillaume,
> I'm some difficulty to determine which component is activated before the
> other. Here the log :
>
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=ManagementContext
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=EnvironmentContext
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Registry
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Broker
> INFO - JBIContainer.activateComponent(989) | Activating component for:
> [container=ServiceMix,name=#SubscriptionManager#] with service: null
> component: org.apache.servicemix.jbi.nmr.SubscriptionManager@2b7db1
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> #SubscriptionManager#
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=InstallationService
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=DeploymentService
> INFO - DeploymentService.buildState(683) | Restoring service assemblies
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AutoDeploymentService
> DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install.xml
> DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy.xml
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AdminCommandsService
> INFO - JBIContainer.init(519) | ServiceMix JBI Container
> (http://servicemix.org/) name: ServiceMix running version: 3.0-SNAPSHOT
> INFO - JBIContainer.activateComponent(989) | Activating component for:
> [container=ServiceMix,name=ID:bgoetzmann-1785-1147860901579-0:0] with
> service: null component:
> org.apache.servicemix.jsr181.Jsr181SpringComponent@18330bf
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> ID:bgoetzmann-1785-1147860901579-0:0
> DEBUG - BaseLifeCycle.init(103) | Initializing component
> DEBUG - JBIContainer.getTransactionManager(635) | No transaction manager
> found from naming context: scheme java not recognized
> DEBUG - Jsr181Endpoint.registerService(284) |
> DEBUG - BaseLifeCycle.init(110) | Component initialized
> INFO - JBIContainer.activateComponent(989) | Activating component for:
> [container=ServiceMix,name=ID:bgoetzmann-1785-1147860901579-0:1] with
> service: null component:
> org.apache.servicemix.http.HttpSpringComponent@1706da8
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> ID:bgoetzmann-1785-1147860901579-0:1
> DEBUG - BaseLifeCycle.init(103) | Initializing component
> DEBUG - BaseLifeCycle.init(110) | Component initialized
> DEBUG - BaseLifeCycle.start(195) | Starting component
>
> DEBUG - ComponentContextImpl.activateEndpoint(133) | Component:
> ID:bgoetzmann-1785-1147860901579-0:0 activated endpoint:
> {http://servicemix.org/test/}Hello : testService
>
> DEBUG - BaseComponent.getServiceDescription(72) | Querying service
> description for
> ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
> DEBUG - EndpointRegistry.retrieveInterfacesFromDescription(274) | Endpoint
> ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
> implements interface {http://servicemix.org/test/}HelloPortType
> DEBUG - Jsr181Endpoint.injectContext(169) | Unable to inject
> ComponentContext:
> TestService.setContext(javax.jbi.component.ComponentContext)
> DEBUG - BaseLifeCycle.start(201) | Component started
> DEBUG - BaseLifeCycle.start(195) | Starting component
> INFO - JCLLoggerAdapter.info(216) | Logging to
> org.slf4j.impl.JCLLoggerAdapter@c3e82b via org.mortbay.log.Slf4jLog
> DEBUG - BaseComponent.getServiceDescription(72) | Querying service
> description for
> ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
> INFO - JCLLoggerAdapter.info(216) | Started SelectChannelConnector @
> localhost:8194
> DEBUG - BaseLifeCycle.start(201) | Component started
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=ManagementContext
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=EnvironmentContext
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Registry
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Broker
> INFO - JBIContainer.activateComponent(989) | Activating component for:
> [container=ServiceMix,name=#SubscriptionManager#] with service: null
> component: org.apache.servicemix.jbi.nmr.SubscriptionManager@1d6747b
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> #SubscriptionManager#
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=InstallationService
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=DeploymentService
> INFO - DeploymentService.buildState(683) | Restoring service assemblies
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AutoDeploymentService
> DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install.xml
> DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy.xml
> DEBUG - ManagementContext.registerSystemService(567) | Registering system
> service:
> org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AdminCommandsService
> INFO - JBIContainer.init(519) | ServiceMix JBI Container
> (http://servicemix.org/) name: ServiceMix running version: 3.0-SNAPSHOT
> INFO - JBIContainer.activateComponent(989) | Activating component for:
> [container=ServiceMix,name=ID:bgoetzmann-1795-1147861165895-0:0] with
> service: null component:
> org.apache.servicemix.jsr181.Jsr181SpringComponent@2798e7
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> ID:bgoetzmann-1795-1147861165895-0:0
> DEBUG - BaseLifeCycle.init(103) | Initializing component
> DEBUG - JBIContainer.getTransactionManager(635) | No transaction manager
> found from naming context: scheme java not recognized
> DEBUG - Jsr181Endpoint.registerService(284) |
> DEBUG - BaseLifeCycle.init(110) | Component initialized
> INFO - JBIContainer.activateComponent(989) | Activating component for:
> [container=ServiceMix,name=ID:bgoetzmann-1795-1147861165895-0:1] with
> service: null component:
> org.apache.servicemix.http.HttpSpringComponent@33b121
> INFO - ComponentMBeanImpl.init(184) | Initializing component:
> ID:bgoetzmann-1795-1147861165895-0:1
> DEBUG - BaseLifeCycle.init(103) | Initializing component
> DEBUG - BaseLifeCycle.init(110) | Component initialized
> DEBUG - BaseLifeCycle.start(195) | Starting component
> INFO - JCLLoggerAdapter.info(216) | Logging to
> org.slf4j.impl.JCLLoggerAdapter@1a6a1a7 via org.mortbay.log.Slf4jLog
> INFO - JCLLoggerAdapter.info(216) | Started SelectChannelConnector @
> localhost:8194
> DEBUG - BaseLifeCycle.start(201) | Component started
> DEBUG - BaseLifeCycle.start(195) | Starting component
>
> DEBUG - ComponentContextImpl.activateEndpoint(133) | Component:
> ID:bgoetzmann-1795-1147861165895-0:0 activated endpoint:
> {http://servicemix.org/test/}Hello : testService
>
> DEBUG - BaseComponent.getServiceDescription(72) | Querying service
> description for
> ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
> DEBUG - EndpointRegistry.retrieveInterfacesFromDescription(274) | Endpoint
> ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
> implements interface {http://servicemix.org/test/}HelloPortType
> DEBUG - Jsr181Endpoint.injectContext(169) | Unable to inject
> ComponentContext:
> TestService.setContext(javax.jbi.component.ComponentContext)
> DEBUG - BaseLifeCycle.start(201) | Component started
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
> archives
> DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
> C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
> modified archives
>
> --
> View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4428070
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: Getting WSDL from a JSR181 POJO Service
Posted by bgoetzmann <bg...@sophia.symag.com>.
Guillaume,
I'm some difficulty to determine which component is activated before the
other. Here the log :
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=ManagementContext
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=EnvironmentContext
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Registry
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Broker
INFO - JBIContainer.activateComponent(989) | Activating component for:
[container=ServiceMix,name=#SubscriptionManager#] with service: null
component: org.apache.servicemix.jbi.nmr.SubscriptionManager@2b7db1
INFO - ComponentMBeanImpl.init(184) | Initializing component:
#SubscriptionManager#
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=InstallationService
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=DeploymentService
INFO - DeploymentService.buildState(683) | Restoring service assemblies
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AutoDeploymentService
DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install.xml
DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy.xml
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AdminCommandsService
INFO - JBIContainer.init(519) | ServiceMix JBI Container
(http://servicemix.org/) name: ServiceMix running version: 3.0-SNAPSHOT
INFO - JBIContainer.activateComponent(989) | Activating component for:
[container=ServiceMix,name=ID:bgoetzmann-1785-1147860901579-0:0] with
service: null component:
org.apache.servicemix.jsr181.Jsr181SpringComponent@18330bf
INFO - ComponentMBeanImpl.init(184) | Initializing component:
ID:bgoetzmann-1785-1147860901579-0:0
DEBUG - BaseLifeCycle.init(103) | Initializing component
DEBUG - JBIContainer.getTransactionManager(635) | No transaction manager
found from naming context: scheme java not recognized
DEBUG - Jsr181Endpoint.registerService(284) |
DEBUG - BaseLifeCycle.init(110) | Component initialized
INFO - JBIContainer.activateComponent(989) | Activating component for:
[container=ServiceMix,name=ID:bgoetzmann-1785-1147860901579-0:1] with
service: null component:
org.apache.servicemix.http.HttpSpringComponent@1706da8
INFO - ComponentMBeanImpl.init(184) | Initializing component:
ID:bgoetzmann-1785-1147860901579-0:1
DEBUG - BaseLifeCycle.init(103) | Initializing component
DEBUG - BaseLifeCycle.init(110) | Component initialized
DEBUG - BaseLifeCycle.start(195) | Starting component
DEBUG - ComponentContextImpl.activateEndpoint(133) | Component:
ID:bgoetzmann-1785-1147860901579-0:0 activated endpoint:
{http://servicemix.org/test/}Hello : testService
DEBUG - BaseComponent.getServiceDescription(72) | Querying service
description for
ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
DEBUG - EndpointRegistry.retrieveInterfacesFromDescription(274) | Endpoint
ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
implements interface {http://servicemix.org/test/}HelloPortType
DEBUG - Jsr181Endpoint.injectContext(169) | Unable to inject
ComponentContext:
TestService.setContext(javax.jbi.component.ComponentContext)
DEBUG - BaseLifeCycle.start(201) | Component started
DEBUG - BaseLifeCycle.start(195) | Starting component
INFO - JCLLoggerAdapter.info(216) | Logging to
org.slf4j.impl.JCLLoggerAdapter@c3e82b via org.mortbay.log.Slf4jLog
DEBUG - BaseComponent.getServiceDescription(72) | Querying service
description for
ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
INFO - JCLLoggerAdapter.info(216) | Started SelectChannelConnector @
localhost:8194
DEBUG - BaseLifeCycle.start(201) | Component started
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=ManagementContext
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=EnvironmentContext
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Registry
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=Broker
INFO - JBIContainer.activateComponent(989) | Activating component for:
[container=ServiceMix,name=#SubscriptionManager#] with service: null
component: org.apache.servicemix.jbi.nmr.SubscriptionManager@1d6747b
INFO - ComponentMBeanImpl.init(184) | Initializing component:
#SubscriptionManager#
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=InstallationService
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=DeploymentService
INFO - DeploymentService.buildState(683) | Restoring service assemblies
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AutoDeploymentService
DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install.xml
DEBUG - AutoDeploymentService.readState(564) | State file doesn't exist:
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy.xml
DEBUG - ManagementContext.registerSystemService(567) | Registering system
service:
org.apache.servicemix:ContainerName=ServiceMix,Type=SystemService,Name=AdminCommandsService
INFO - JBIContainer.init(519) | ServiceMix JBI Container
(http://servicemix.org/) name: ServiceMix running version: 3.0-SNAPSHOT
INFO - JBIContainer.activateComponent(989) | Activating component for:
[container=ServiceMix,name=ID:bgoetzmann-1795-1147861165895-0:0] with
service: null component:
org.apache.servicemix.jsr181.Jsr181SpringComponent@2798e7
INFO - ComponentMBeanImpl.init(184) | Initializing component:
ID:bgoetzmann-1795-1147861165895-0:0
DEBUG - BaseLifeCycle.init(103) | Initializing component
DEBUG - JBIContainer.getTransactionManager(635) | No transaction manager
found from naming context: scheme java not recognized
DEBUG - Jsr181Endpoint.registerService(284) |
DEBUG - BaseLifeCycle.init(110) | Component initialized
INFO - JBIContainer.activateComponent(989) | Activating component for:
[container=ServiceMix,name=ID:bgoetzmann-1795-1147861165895-0:1] with
service: null component:
org.apache.servicemix.http.HttpSpringComponent@33b121
INFO - ComponentMBeanImpl.init(184) | Initializing component:
ID:bgoetzmann-1795-1147861165895-0:1
DEBUG - BaseLifeCycle.init(103) | Initializing component
DEBUG - BaseLifeCycle.init(110) | Component initialized
DEBUG - BaseLifeCycle.start(195) | Starting component
INFO - JCLLoggerAdapter.info(216) | Logging to
org.slf4j.impl.JCLLoggerAdapter@1a6a1a7 via org.mortbay.log.Slf4jLog
INFO - JCLLoggerAdapter.info(216) | Started SelectChannelConnector @
localhost:8194
DEBUG - BaseLifeCycle.start(201) | Component started
DEBUG - BaseLifeCycle.start(195) | Starting component
DEBUG - ComponentContextImpl.activateEndpoint(133) | Component:
ID:bgoetzmann-1795-1147861165895-0:0 activated endpoint:
{http://servicemix.org/test/}Hello : testService
DEBUG - BaseComponent.getServiceDescription(72) | Querying service
description for
ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
DEBUG - EndpointRegistry.retrieveInterfacesFromDescription(274) | Endpoint
ServiceEndpoint[service={http://servicemix.org/test/}Hello,endpoint=testService]
implements interface {http://servicemix.org/test/}HelloPortType
DEBUG - Jsr181Endpoint.injectContext(169) | Unable to inject
ComponentContext:
TestService.setContext(javax.jbi.component.ComponentContext)
DEBUG - BaseLifeCycle.start(201) | Component started
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\deploy for new or modified
archives
DEBUG - AutoDeploymentService.monitorDirectory(484) | Monitoring directory
C:\OE\ServiceMix\Hello ServiceMix\jsr-181\rootDir\install for new or
modified archives
--
View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4428070
Sent from the ServiceMix - User forum at Nabble.com.
Re: Getting WSDL from a JSR181 POJO Service
Posted by Guillaume Nodet <gn...@gmail.com>.
On 5/17/06, bgoetzmann <bg...@sophia.symag.com> wrote:
>
> Hello,
> It is the first case. One time I can get the WSDL document by the JMX
> Console (with MC4J youc can do a copy/paste).
This is a lifecycle problem. The JBI spec defines service units and
service assemblies so that you can have a better control of lifecycle.
The problem is that lightweight components do not really use service
assemblies and service units and therefore their lifecycle is much
more simple (which is not very good in this case).
Given the order of the components however, the jsr181 component should
be activated before the http one, and thus the endpoint should exists
and the wsdl description available.
Could you check the log to see if this is the case ?
Put org.apache.servicemix.jbi.framework.ComponentContextImpl logger to
DEBUG and you should see messages:
"Component: xxx activated endpoint: yyy : zzz"
> What do you mean by "send the wsdl generated by the jsr181 component" ?
I was just saying to post the wsdl to the mailing list to see if there
is any problem with it.
Cheers,
Guillaume Nodet
>
> Thank you a lot for your constant help.
> --
> View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4426603
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: Getting WSDL from a JSR181 POJO Service
Posted by bgoetzmann <bg...@sophia.symag.com>.
Hello,
It is the first case. One time I can get the WSDL document by the JMX
Console (with MC4J youc can do a copy/paste).
What do you mean by "send the wsdl generated by the jsr181 component" ?
Thank you a lot for your constant help.
--
View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4426603
Sent from the ServiceMix - User forum at Nabble.com.
Re: Getting WSDL from a JSR181 POJO Service
Posted by Guillaume Nodet <gn...@gmail.com>.
It may happen because:
* the target jbi endpoint is not yet activated when the http
components tries to create the wsdl (you can use the jmx console to
stop / start the http component, which should recreate the wsdl)
* the target endpoint is not found (this means that when you send a
message, it will fail)
* the wsdl port is not found: if the target wsdl defines a service,
it should be the same than the jbi target service / endpoint.
If none of this solution works, send the wsdl generated by the jsr181
component .
Cheers,
Guillaume Nodet
On 5/16/06, bgoetzmann <bg...@sophia.symag.com> wrote:
>
> Thank you Guillaume,
>
> Having do so with the following servicemix.xml modified, I've the same
> incorrect behavior.
> And when I use the URL http://localhost:8194/Service/?.wsdl from a browser,
> I get
> the message "No wsdl is available for this service" and the URL is changed
> to http://localhost:8194/Service/main.wsdl.
>
> Have you any idea ?
>
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns:sm="http://servicemix.apache.org/config/1.0"
> xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"
> xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:test="http://servicemix.org/test/">
> <!-- Le conteneur JBI -->
> <sm:container id="jbi">
> <!-- property name="useMBeanServer" value="true"/>
> <property name="createMBeanServer" value="true"/>
> <property name="dumpStats" value="true"/>
> <property name="statsInterval" value="10"/ -->
> <sm:activationSpecs>
>
> <sm:activationSpec>
> <sm:component>
> <jsr181:component>
> <jsr181:endpoints>
> <jsr181:endpoint pojoClass="TestService" annotations="none"
> service="test:Hello" endpoint="testService"/>
> </jsr181:endpoints>
> </jsr181:component>
> </sm:component>
> </sm:activationSpec>
>
> <sm:activationSpec>
> <sm:component>
> <http:component>
> <http:endpoints>
> <http:endpoint service="test:Hello" endpoint="testService"
> role="consumer" defaultOperation="echo"
> locationURI="http://localhost:8194/Service/"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out" soap="true"/>
> </http:endpoints>
> </http:component>
> </sm:component>
> </sm:activationSpec>
>
> </sm:activationSpecs>
> </sm:container>
> </beans>
>
> --
> View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4408097
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
Re: Getting WSDL from a JSR181 POJO Service
Posted by bgoetzmann <bg...@sophia.symag.com>.
Thank you Guillaume,
Having do so with the following servicemix.xml modified, I've the same
incorrect behavior.
And when I use the URL http://localhost:8194/Service/?.wsdl from a browser,
I get
the message "No wsdl is available for this service" and the URL is changed
to http://localhost:8194/Service/main.wsdl.
Have you any idea ?
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:sm="http://servicemix.apache.org/config/1.0"
xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"
xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:test="http://servicemix.org/test/">
<!-- Le conteneur JBI -->
<sm:container id="jbi">
<!-- property name="useMBeanServer" value="true"/>
<property name="createMBeanServer" value="true"/>
<property name="dumpStats" value="true"/>
<property name="statsInterval" value="10"/ -->
<sm:activationSpecs>
<sm:activationSpec>
<sm:component>
<jsr181:component>
<jsr181:endpoints>
<jsr181:endpoint pojoClass="TestService" annotations="none"
service="test:Hello" endpoint="testService"/>
</jsr181:endpoints>
</jsr181:component>
</sm:component>
</sm:activationSpec>
<sm:activationSpec>
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint service="test:Hello" endpoint="testService"
role="consumer" defaultOperation="echo"
locationURI="http://localhost:8194/Service/"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out" soap="true"/>
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:container>
</beans>
--
View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4408097
Sent from the ServiceMix - User forum at Nabble.com.
Re: Getting WSDL from a JSR181 POJO Service
Posted by Guillaume Nodet <gn...@gmail.com>.
When using standard JBI components like servicemix-jsr181,
servicemix-http ... you can not use the sm:activationSpec to specify
the service / endpoint name. You should put then on the endpoint
definition.
Having done so, you should be able to view the WSDL from the jmx
console, and then browse the http://localhost:8194/Service/?wsdl to
retrieve it.
Cheers,
Guillaume Nodet
On 5/16/06, bgoetzmann <bg...@sophia.symag.com> wrote:
>
> Hello,
> I try a simple test with ServiceMix to expose a POJO as a web service, using
> the following servicemix.xml file :
>
> <?xml version="1.0" encoding="UTF-8"?>
> <beans xmlns:sm="http://servicemix.apache.org/config/1.0"
> xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0"
> xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:test="http://servicemix.org/test/">
> <!-- Le conteneur JBI -->
> <sm:container id="jbi">
> <sm:activationSpecs>
>
> <sm:activationSpec service="test:Hello"
> endpoint="testService">
> <sm:component>
> <jsr181:component>
> <jsr181:endpoints>
> <jsr181:endpoint
> pojoClass="TestService" annotations="none"/>
> </jsr181:endpoints>
> </jsr181:component>
> </sm:component>
> </sm:activationSpec>
>
> <sm:activationSpec>
> <sm:component>
> <http:component>
> <http:endpoints>
> <http:endpoint
> service="test:Hello" endpoint="testService" role="consumer"
> defaultOperation="echo" locationURI="http://localhost:8194/Service/"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out" soap="true"/>
> </http:endpoints>
> </http:component>
> </sm:component>
> </sm:activationSpec>
>
> </sm:activationSpecs>
> </sm:container>
> </beans>
>
> My goal is to get the WSDL document corresponding to my POJO exposed as a
> web service.
> With a JMX Console I see two JMX beans with Type=Endpoint :
> - One with Name =
> {http___DefaultNamespace}TestServiceTestServiceJBIPort,SubType=Internal
> - The other with Name =
> {http___servicemix.org_test_}HellotestService,SubType=External
>
> Each of these JMX beans has a getWSDL() operation
>
> A call on this operation for the first beans returns (it seems) a WSDL
> document, but for the second, only :
>
> <?xml version="1.0" encoding="UTF-8"?>
>
>
> I would expect that this call return a valid WSDL document including the URL
> for binding (http://localhost:8194/Service/).
>
> Why doest it not the case ?
>
> An other test I make was to try to get the WSDL document using this URL
> http://localhost:8194/Service?xml but I get the following error :
>
> "Error 405 : GET not supported"
>
> Is a way to get the WSDL document with an HTTP GET ?
> --
> View this message in context: http://www.nabble.com/Getting-WSDL-from-a-JSR181-POJO-Service-t1626322.html#a4406444
> Sent from the ServiceMix - User forum at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet