jclouds-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Garcia Ibañez <Carlos.Gar...@EMEA.NEC.COM>
Subject RE: [jClouds Abiquo] - Issue when deploying to jBoss
Date Wed, 08 Jan 2014 11:53:07 GMT
1.       Thank you, Ignasi. I've opened an issue (JCLOUDS-421<https://issues.apache.org/jira/browse/JCLOUDS-421>)
as you suggest, though I'm not sure if the description is correct :)
But as it gets solved, is there any workaround I can implement on my side in the meantime?

From: Ignasi Barrera [mailto:ignasi.barrera@gmail.com]
Sent: miércoles, 08 de enero de 2014 12:19
To: Carlos Garcia Ibañez
Cc: user@jclouds.apache.org
Subject: Re: [jClouds Abiquo] - Issue when deploying to jBoss

This is something that hs already been fixed in the Abiquo dependencies. The wink-common was
included just for commodity, but we've removed the dependency in the last version of the api-model-transport.
Using it requires some changes in the Abiquo provider and I've still had no time to make them.
Could you please file a JIRA issue for this?

On 8 January 2014 11:11, Carlos Garcia Ibañez <Carlos.Garcia@emea.nec.com<mailto:Carlos.Garcia@emea.nec.com>>
Good morning everyone!
I'm facing an issue when deploying an application which uses the jClouds/Abiquo libraries
(my project depends on org.apache.jclouds.labs:abiquo:1.7.0), and I hope some of you have
found and solved this problem.
When I started developing my project I noticed that the RESTEasy services provided by jBoss
conflicted with the Wink libraries used by jClouds/Abiquo and the server failed to deploy
the application. Right then, I decided to disable the REST extensions provided by jBoss by
commenting out some lines in the standalone.xml configuration file of the server, like this:

<!-- extension module="org.jboss.as.jaxrs"/ -->

<!-- subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/ -->
Everything worked ok until I needed to re-enable these extensions to allow a new module to
use them. And then , the deployment problem reappeared:

10:35:33,193 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing
weld deployment IaasGateway-ear-1.0.0-SNAPSHOT.ear
10:35:33,421 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed
to start service jboss.deployment.unit."IaasGateway-ear-1.0.0-SNAPSHOT.ear".POST_MODULE: org.jboss.msc.service.StartException
in service jboss.deployment.unit."IaasGateway-ear-1.0.0-SNAPSHOT.ear".POST_MODULE: JBAS018733:
Failed to process phase POST_MODULE of deployment "IaasGateway-ear-1.0.0-SNAPSHOT.ear"
       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
       at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
       at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011232: Only
one JAX-RS Application Class allowed.  org.apache.wink.common.internal.application.SimpleWinkApplication
org.apache.wink.common.WinkApplication org.apache.wink.common.internal.model.ModelUtils$1
       at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.scan(JaxrsScanningProcessor.java:206)
       at org.jboss.as.jaxrs.deployment.JaxrsScanningProcessor.deploy(JaxrsScanningProcessor.java:100)
       at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120)
       ... 5 more
I've tried excluding the Wink dependencies from my project to be able to deploy it, but then
the application fails when some of the Wink classes is referenced since they cannot be found.
Any idea will be welcome; thank you so much in advance!


Click here<https://www.mailcontrol.com/sr/9w8HFfNc2Q!GX2PQPOmvUndZP90azNGYgBKfmPEqRY!ijnPsCxTfFTi37crpSUmD6!d5cSRWK9U94h7CChK4GQ==>
to report this email as spam.

View raw message