[jboss-jira] [JBoss JIRA] Commented: (AS7-867) Dependency issue on OSGi bundle in AS7

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/AS7-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603627#comment-12603627 ] 

Gary Brown commented on AS7-867:
--------------------------------

Has this test been pushed to AS7 master, as could not find it: https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src/test/java/org/jboss/as/testsuite/integration/osgi?

So is the problem the fact that I have added ".jar" to my dependency? i.e. Dependencies: deployment.TestBundle
.jar

I tried removing the .jar and it still complains:

10:03:31,164 INFO  [org.jboss.as.server] (MSC service thread 1-3) Service status report
   New missing/unsatisfied dependencies:
      service module.spec.service."deployment.TestBundle".main (missing)

10:03:31,177 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment WS-Dependencies.war in 10ms
10:03:31,178 INFO  [org.jboss.as.server] (MSC service thread 1-4) Service status report
   Newly corrected services:
      service module.spec.service."deployment.TestBundle".main (no longer required)

Do I need to wait for CR1 before this will work? If so, any idea when it will be released?

Thanks in advance.

> Dependency issue on OSGi bundle in AS7
> --------------------------------------
>
>                 Key: AS7-867
>                 URL: https://issues.jboss.org/browse/AS7-867
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi
>         Environment: jbossas7-beta3
>            Reporter: Gary Brown
>            Assignee: Thomas Diesler
>         Attachments: TestBundle.jar, WS-Dependencies.war
>
>
> When I deploy the attached "TestBundle.jar" OSGi bundle (with activation set to eager in standalone.xml, to force it to activate),
>         <subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="eager">
> I get:
> 10:57:14,168 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "TestBundle.jar"
> 10:57:14,273 INFO  [org.jboss.as.osgi] (MSC service thread 1-3) Installing deployment: [TestBundle:1.0.0.201105171313,location=TestBundle.jar]
> 10:57:14,277 INFO  [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: TestBundle:1.0.0.201105171313
> 10:57:14,282 INFO  [stdout] (MSC service thread 1-3) Hello World!!
> 10:57:14,282 INFO  [stdout] (MSC service thread 1-3) CREATED TEST SERVICE
> 10:57:14,294 INFO  [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread 1-3) Bundle started: TestBundle:1.0.0.201105171313
> which is expected - i.e. the "Hello World!!" message is generated from the activator's start method, so indicates that the bundle has activated.
> However if I deploy a war that has a dependency on this module (WS-Dependencies.war), I get:
> 10:58:59,335 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "WS-Dependencies.war"
> 10:58:59,399 INFO  [org.jboss.as.server] (MSC service thread 1-2) Service status report
>    New missing/unsatisfied dependencies:
>       service module.spec.service."deployment.TestBundle.jar".main (missing)
> 10:58:59,417 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment WS-Dependencies.war in 14ms
> 10:58:59,417 INFO  [org.jboss.as.server] (MSC service thread 1-1) Service status report
>    Newly corrected services:
>       service module.spec.service."deployment.TestBundle.jar".main (no longer required)
> But if I do this same process with a TestBundle.jar that has no OSGi metadata (so just a plain jar), when I deploy the war I get:
> 11:08:19,704 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Starting deployment of "TestBundle.jar"
> 11:08:34,780 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "WS-Dependencies.war"
> 11:08:34,849 WARN  [org.jboss.wsf.stack.cxf.deployment.aspect.DescriptorDeploymentAspect] (MSC service thread 1-1) Spring not available, skipping check for user provided jbossws-cxf.xml / cxf.xml configuration files.
> 11:08:34,855 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-1) Add Service
>  id=HelloPortType
>  address=http://localhost:8080/WS-Dependencies/HelloPortType
>  implementor=test.HelloPortTypeImpl
>  invoker=org.jboss.wsf.stack.cxf.InvokerJSE
>  serviceName={http://test/}HelloPortType
>  portName={http://test/}HelloPortTypeImplPort
>  wsdlLocation=null
>  mtomEnabled=false
> 11:08:34,856 INFO  [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (MSC service thread 1-1) register: jboss.ws:context=WS-Dependencies,endpoint=HelloPortType
> 11:08:35,831 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-1) Creating Service {http://test/}HelloPortType from class test.HelloPortType
> 11:08:36,215 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-1) Setting the server's publish address to be http://localhost:8080/WS-Dependencies/HelloPortType
> 11:08:36,300 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-1) WSDL published to: file:/home/gbrown/NotBackedUp/testing/riftsaw/as7/jboss-7.0.0.Beta3/standalone/data/wsdl/WS-Dependencies.war/HelloPortType.wsdl
> 11:08:37,149 INFO  [org.jboss.web] (MSC service thread 1-3) registering web context: /WS-Dependencies
> First line shows the plain jar being deployed.
> This seems to indicate that the OSGi bundle is not in a fully activated state from the jboss modules perspective?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira