Hi Alexander, Kevin and Arun
JBS : https://bugs.openjdk.java.net/browse/JDK-8139114
Webrev : http://cr.openjdk.java.net/~ghb/8139114/webrev.00/
RC and Solution updated in JIRA.
Thanks,
Guru
This way only the app will be accessible by other components through the
service registry. The app itself can not have any @reference because it it
is javafx itself that instantiates the app object and not the osgi
declarative services framework (which also takes care of injecting your
I make sure that the application is basically only the primary stage,
therefore it only needs to publish itself. All other UI and business
logic is done by other bundles.
Op 20-02-16 om 15:50 schreef Stephen Winnall:
I have been trying a similar approach. I’m using declarative services
and I
I have been trying a similar approach. I’m using declarative services and I
have some @References to other services in the Application, but I haven’t
managed to get these instantiated. Do you have an approach for that? I suppose
I can just write some code and instantiate them manually…
Steve
That is why the bundle activator creates a bundle-singleton of itself,
that way the app can access the OSGi world. In my case to register
itself as a service.
@Override
public void start(Stage primaryStage) throws Exception {
primaryStage.show();
Hi Maurice
I have done something similar, but it has the following drawback in my view:
the class launched (Udoo15App in your case) does not run under OSGi control, so
it has no access to OSGi bundles or services, nor is it accessible by them. If
you don’t need that, you're OK. But I need that
For my OSGi based JavaFX solution on the Udoo Quad (ARM based Linux) I
created a service that publishes the application in the context.The
application does as little as possible. It sets up the primary stage as
fullscreen and puts a stackpane in it. Initially the stackpane displays
a 'boot
