9:41 a.m.
Kevin Pollet [http://community.jboss.org/people/kevinpollet] created the discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/605472#605472
--------------------------------------------------------------
Thoughts?
Hi all,
I just want to give you my thinking and Mathieu's thinking about the use of the
OSGiService qualifier. First of all, we agree with you that it's possible to get rid
of the OSGiService qualifier (if a service is not found in CDI, it's possible to look
at the OSGi service registry).
I thought a lot about this and one interrogation comes to my mind. How differentiate the
case of a missing CDI binding and the case of a local implementation for a service? The
default behavior of CDI is to throw an exception specifying that there is no binding for
this injection target but in this case, a proxy waiting for an hypothetical OSGi service
will be injected (and obviously will fail at runtime). IMHO, doing this will break the
default CDI programming model. I mean that the user applicition will start without any
problem in our case but in the default CDI programming model an exception will be thrown.
We think that the user have to specify where he wants to use OSGi (so the user will knows
where to deal with OSGi dynamism).
On the other hand, as you say in your above comments, this feature has to be enabled by
the user. In this case he could be aware of this behavior, but we think it's too much
changes for the CDI programming model.
WDYT?
Kevin & Mathieu
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605472#605472]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
9:50 a.m.
Ales Justin [http://community.jboss.org/people/alesj] created the discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/605478#605478
--------------------------------------------------------------
WDYT?
Good question.
I agree with you on the "surprise" from a CDI user,
which expects its beans to be available at runtime, since validation "said" so.
What we could do is add a dependency on a OSGi bundle from a CDI deployment which uses
some bundle's service.
This should / would be transparently added via Weld/OSGi+AS integration,
which would then also unwind the CDI deployment if the required OSGi service would go
away.
(and could potentially re-wind it back, if the service came back)
This might again be an over-kill, but I don't see how else you can properly handle
this from CDI side.
Otoh, OSGi side could easily live with dynamic CDI beans, as this is what it already
does.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605478#605478]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:08 a.m.
David Bosschaert [http://community.jboss.org/people/bosschaert] created the discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/605575#605575
--------------------------------------------------------------
Kevin Pollet wrote:
WDYT?
The OSGi Blueprint Specification deals with a similar problem using something called
'the Grace Period' ( http://www.osgi.org/Download/Release4V42 OSGi 4.2 Enterprise
spec section 121.3.7). Essentially this is a period of time during which the system gives
all the components a chance to initialize and injection to happen. If after the grace
period has expired there are still missing dependencies, the deployment will fail. This
might also work for CDI.
Re Ales, suggestion of taking the CDI deployment away when a mandatory dependency goes
away. This is what OSGi Declarative Services (DS) do as well.
Essentially one of the main differences between Blueprint and DS is how they react to
changes in dependencies. Blueprint keeps the dependent component alive in the hope that a
replacement service will be made available at some point where DS takes the dependent away
and potentially instantiates a new one when a replacement service arrives. So the
Blueprint model has a dampening effect on the liveness of OSGi services whereas DS follows
it directly.
I think both have their uses and ideally this kind of behaviour would be configurable for
OSGi/CDI - but I guess it would be fine to pick either of the two as an initial model...
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605575#605575]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:32 a.m.
Mathieu ANCELIN [http://community.jboss.org/people/mathieu.ancelin] created the
discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/605588#605588
--------------------------------------------------------------
Actually, we followed a different approach for Weld-OSGi.
We don't think that it's mandatory to fail a deployment if some OSGi services are
not present (after all, OSGi is dynamic and everything is a matter of services that come
and go).
With Weld-OSGi it's possible to mark an OSGi service injection point as
'Required' to specify that we absolutely need an implementation of that particular
service to work. In this case, it's possible to declare callbacks (via CDI events)
that will be activated when all 'Required' dependencies will be present in OSGi
service registry or when there are missing dependencies. Then, it's possible to handle
cases of mandatory dependencies with these callbacks (start the application when the XYZ
service appears and shut it down when it goes off, etc ...)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605588#605588]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1 p.m.
New subject: [JBoss AS 7 Development] - Re: Weld-OSGi integration in AS7
Konstantin Pupkov [http://community.jboss.org/people/goodidea] created the discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/643429#643429
--------------------------------------------------------------
Just download AS7 CR1. Trying to make work CDI example from
bosschaert-coderthoughts-c8edd9c.zip
I have got error:
10:23:25,749 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) Starting
deployment of "osgi-cdi-demo-provider-bundle-1.0.0-SNAPSHOT.jar"
10:23:25,765 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread
1-7) Install bundle: osgi-cdi-demo-provider-bundle:1.0.0.SNAP
SHOT
10:23:25,780 INFO [stdout] (MSC service thread 1-7) *** osgi-cdi-demo-provider-bundle
started.
10:23:25,780 INFO [org.jboss.as.server] (HttpManagementService-threads - 5) JBAS018559:
Deployed "osgi-cdi-demo-provider-bundle-1.0.0-SNAPSHOT.jar"
10:23:25,796 INFO [org.jboss.osgi.framework.internal.HostBundleState] (MSC service thread
1-7) Bundle started: osgi-cdi-demo-provider-bundle:1.0.0.SN
APSHOT
10:25:22,000 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting
deployment of "osgi-cdi-demo-webapp.war"
10:25:22,062 INFO [org.jboss.weld] (MSC service thread 1-4) Processing CDI deployment:
osgi-cdi-demo-webapp.war
10:25:22,078 INFO [org.jboss.weld] (MSC service thread 1-3) Starting Services for CDI
deployment: osgi-cdi-demo-webapp.war
10:25:22,078 INFO [org.jboss.weld] (MSC service thread 1-7) Starting weld service
10:25:22,140 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed
to start service jboss.deployment.unit."osgi-cdi-demo-webapp
.war".WeldService: org.jboss.msc.service.StartException in service
jboss.deployment.unit."osgi-cdi-demo-webapp.war".WeldService:
org.jboss.weld.except
ions.DeploymentException: WELD-001408 Unsatisfied dependencies for type
[OSGiPropertyProvider] with qualifiers [@Default] at injection point [[field]
@Inject org.coderthoughts.demo.cdiosgi.web.CDIServlet.osgiPropertyProvider]
at org.jboss.as.weld.services.WeldService.start(WeldService.java:96)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
[jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied
dependencies for type [OSGiPropertyProvider] with qualifiers [@Defau
lt] at injection point [[field] @Inject
org.coderthoughts.demo.cdiosgi.web.CDIServlet.osgiPropertyProvider]
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:274)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:243)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:106)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:126)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:345)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:330)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
... 5 more
10:25:22,375 INFO [org.jboss.as.server] (HttpManagementService-threads - 6) JBAS015856:
Undeploy of deployment "osgi-cdi-demo-webapp.war" was rolled
back with failure message {"JBAS014671: Failed services" =>
{"jboss.deployment.unit.\"osgi-cdi-demo-webapp.war\".WeldService"
=> "org.jboss.msc.servic
e.StartException in service
jboss.deployment.unit.\"osgi-cdi-demo-webapp.war\".WeldService:
org.jboss.weld.exceptions.DeploymentException: WELD-001408
Unsatisfied dependencies for type [OSGiPropertyProvider] with qualifiers [@Default] at
injection point [[field] @Inject org.coderthoughts.demo.cdiosg
i.web.CDIServlet.osgiPropertyProvider]"}}
10:25:22,375 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped
deployment osgi-cdi-demo-webapp.war in 12ms
10:25:22,375 INFO [org.jboss.as.controller] (HttpManagementService-threads - 6)
JBAS014774: Service status report
JBAS014777: Services which failed to start: service
jboss.deployment.unit."osgi-cdi-demo-webapp.war".WeldService:
org.jboss.msc.service.StartEx
ception in service jboss.deployment.unit."osgi-cdi-demo-webapp.war".WeldService:
org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfie
d dependencies for type [OSGiPropertyProvider] with qualifiers [@Default] at injection
point [[field] @Inject org.coderthoughts.demo.cdiosgi.web.CDISe
rvlet.osgiPropertyProvider]
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/643429#643429]
Start a new discussion in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
1:53 a.m.
New subject: [JBoss AS 7 Development] - Re: Weld-OSGi integration in AS7
David Bosschaert [http://community.jboss.org/people/bosschaert] created the discussion
"Re: Weld-OSGi integration in AS7"
To view the discussion, visit: http://community.jboss.org/message/644251#644251
--------------------------------------------------------------
Hi Konstantin,
The Weld-OSGi integration is not yet part of AS7. Please check
https://issues.jboss.org/browse/JBOSGI-445 JBOSGI-445 to see the status.
Best regards,
David
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/644251#644251]
Start a new discussion in JBoss AS 7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4736
days inactive
4968
days old
jboss-dev-forums@lists.jboss.org
5 comments
5 participants
participants (5)
-
Ales Justin -
David Bosschaert
-
Kevin Pollet
-
Konstantin Pupkov
-
Mathieu ANCELIN