I spent most of the day yesterday googling to find out if there is a way to
build a JavaFX desktop application based upon Felix. So far I've not found
anything that advises how to do this or if it is even possible at this
stage of development.
Can anybody point me to an article that explains how,
Hi Chuck,
maybe this Project is an interesting starting Point for you:
http://www.drombler.org
Kind regards,
Thomas
Am 09.07.2017 18:17 schrieb "Chuck Davis" :
> I spent most of the day yesterday googling to find out if there is a way to
> build a JavaFX desktop application based upon Felix. S
Thanks Thomas. I guess there must be a way. I wish he would have just
explained how to use JavaFX with Felix rather than develop a whole third
party development environment.
On Sun, Jul 9, 2017 at 9:19 AM, Thomas Driessen
wrote:
> Hi Chuck,
>
> maybe this Project is an interesting starting
Hi Chuck,
It's an old post but could be what you're looking for
http://paulonjava.blogspot.nl/2014/11/making-javafx-better-with-osgi.html?m=1
Regards,
Bram
Op 9 jul. 2017 19:05 schreef "Chuck Davis" :
> Thanks Thomas. I guess there must be a way. I wish he would have just
> explained how to
Thanks Bram. I actually read that yesterday but unfortunately it's Eclipse
related and that ties me to Equinox. So far I haven't found anything to
like about Eclipse and I want true OSGi compatibility -- not tied to a
specific IDE or OSGi implementation. At least the Eclipse people are
wrestling
Hi Chuck,
Using Eclipse as an IDE does not tie you into using Equinox for your runtime.
I don’t know much about JavaFX but what is the actual problem you are
experiencing with it? Isn’t it just a library like any other?
Neil
> On 9 Jul 2017, at 18:18, Chuck Davis wrote:
>
> Thanks Bram. I a
Hi Chuck,
Had another look as I would've been supirised if Paul was using Equinox ;)
but I don't see anything related to that, and the sample on that's on
GitHub runs on Felix [1]
So Eclipse (with Bndtools) is only used as IDE and as Niel already
mentioned that doesn't force you to use Equinox
vafx-osgi<https://github.com/edvin/javafx-osgi>
github.com
javafx-osgi - JavaFX 8.0 OSGi bundle to support JavaFX in an OSGi container
Hope it helps,
Renato
De: Neil Bartlett
Enviado: segunda-feira, 10 de julho de 2017 03:24
Para: users@felix.apache.org
A
osgi<https://github.com/edvin/javafx-osgi>
> github.com
> javafx-osgi - JavaFX 8.0 OSGi bundle to support JavaFX in an OSGi container
>
>
>
>
>
> Hope it helps,
>
>
> Renato
>
>
>
> De: Neil Bartlett
> Enviado
Hi Neil:
I'm just beginning my investigation of OSGi because I want to do things
that it sounds like OSGi was designed to do and I'm too lazy to reinvent
the wheel if it already exists. I develop desktop business applications
and my development style is already quite modular in concept but I want
Hi Chuck,
I read through Paul’s article and it still looks very relevant and well written.
You don’t really want to use bnd directly. It’s a low-level tool… it would be
like using javac and the jar tool directly from the command line, rather than
via a build system. Does anybody still do that??
On Sunday 09 July 2017 15:50:51 Chuck Davis wrote:
> Hi Neil:
Hi Chuck,
> I'm just beginning my investigation of OSGi because I want to do things
> that it sounds like OSGi was designed to do and I'm too lazy to reinvent
> the wheel if it already exists. I develop desktop business applications
>
ngine.
JP
-Message d'origine-
De : Chuck Davis [mailto:cjgun...@gmail.com]
Envoyé : dimanche 9 juillet 2017 18:17
À : users@felix.apache.org
Objet : Re: Felix and JavaFX
I spent most of the day yesterday googling to find out if there is a way to
build a JavaFX desktop application b
quot; in order to start JavaFX engine.
>
> JP
>
> -Message d'origine-
> De : Chuck Davis [mailto:cjgun...@gmail.com]
> Envoyé : dimanche 9 juillet 2017 18:17
> À : users@felix.apache.org
> Objet : Re: Felix and JavaFX
>
> I spent most of the day yesterda
e : Chuck Davis [mailto:cjgun...@gmail.com]
Envoyé : lundi 17 juillet 2017 18:41
À : users@felix.apache.org
Objet : Re: Felix and JavaFX
JP, are you doing the same thing Paul outlines in his article? If you've taken
a different approach can you share it for the benefit of all of us following
this thre
e is a way to build a JavaFX desktop
> application based upon Felix..."
>
> Well, which problem are you experiencing with JavaFX?
>
> JP
>
> -Message d'origine-
> De : Chuck Davis [mailto:cjgun...@gmail.com]
> Envoyé : lundi 17 juillet 2017 18:41
> À : u
e the link to Paul's article?
Regards,
JP
-Message d'origine-
De : Chuck Davis [mailto:cjgun...@gmail.com]
Envoyé : jeudi 20 juillet 2017 05:32
À : users@felix.apache.org
Objet : Re: Felix and JavaFX
All the ones Paul's article delineates.
On Tue, Jul 18, 2017 at 8:12
Hi Chuck,
I realise that this is a response to an old message of yours but I have a
GitHub project that may be of interest to you that brings OSGi to JavaFx.
https://github.com/jtkb/osgifx
It aims to be simpler than Drombler and is agnostic to the OSGi implementation.
It is still a work in pro
Hi Kerry:
Thanks for the note. Old indeed. I don't remember anything I learned
from that project (though I did keep the modules). I did get it to work
by including the module somebody mentioned. It seems so easy, looking
at that module, I can't understand why Felix doesn't do the export fo
That's pretty easy to answer.
Felix by default exports all standard Java SE packages. JavaFX is not part
of Java SE, it is an extension that is only available on a subset of Java
implementations.
Neil
On 12 Dec 2017 2:56 pm, "Chuck Davis" wrote:
> Hi Kerry:
>
> Thanks for the note. Old indeed
Additionally, the JavaFX exports should now be available on java9 ootb
(assuming the modules are on the module path). As Neil correctly
points out, the reason they are not on older version is exactly that -
we don't know if they are there or not. With java9, we can detect that
(and we do starting
Karl, thanks for that information.
On 12/12/2017 08:31 AM, Karl Pauls wrote:
Additionally, the JavaFX exports should now be available on java9 ootb
(assuming the modules are on the module path). As Neil correctly
points out, the reason they are not on older version is exactly that -
we don't
Hi Chuck,
No problem, I wasn't aware of the issues you were having i.e. felix not
exporting the javafx packages by default. In Karaf they are exported by default
but obviously not everyone wants all the functionality provided by Karaf.
You've given me the idea to include some integration tests
I think you are refering to this one
http://paulonjava.blogspot.de/2014/11/making-javafx-better-with-osgi.html
regards
Marc
Von:CLEMENT Jean-Philippe
An: "users@felix.apache.org" ,
Datum: 20.07.2017 10:26
Betreff: RE: Felix and JavaFX
Sorry, I didn't find
}
@Override
public void start(final Stage stage) throws InterruptedException {
stage.hide();
sync.put(this);
}
}
JP
-Message d'origine-
De : marc.schle...@sdv-it.de [mailto:marc.schle...@sdv-it.de]
Envoyé : jeudi 20 juillet 2017 13:50
À : users@fel
JP:
Thanks for the additional information. I've seen some indication that the
Felix team are considering how to handle the JavaFX issues as well.
Perhaps it is time to investigate Karaf further -- but it adds a lot of
additional capabilities that a client doesn't actually need if I understand
cor
ublic void start(final Stage stage) throws InterruptedException {
>stage.hide();
>sync.put(this);
> }
> }
>
> JP
>
>
> -Message d'origine-
> De : marc.schle...@sdv-it.de [mailto:marc.schle...@sdv-it.de]
> Envoyé : jeudi 20 juillet 2017 13
dget
persistentStageService.getStage().show();
} catch (UnacceptableConfiguration | MissingHandlerException
| ConfigurationException | InvalidSyntaxException ex) {
Logger.getLogger(getClass().getName()).log(Level.SEVERE,
null, ex);
}
}
})
I've mentioned this before, so forgive the repeat:
http://blog.muddyhorse.com/2009/02/maven-osgi-spring-javafx-ant/
Basically, we put most of the javafx stuff into a bundle, and used it
that way. Then we had to do some magic to be able to load CustomNodes
because of stylesheet issues.
Pat.
--
Thanks for the prompt answer! Sorry I missed your earlier comment...
I've looked at your example and repeated it using Ant and bnd. Maybe I
should learn maven instead.
Anyway, the bndwrap task nicely wraps the javaFX classpath that is
used for the build as a single bundle although it throws
Well, don't try to tackle too many things at once... you'll need a
firm understanding of OSGi and JavaFX separately from one another in
order to be really effective. Maven-vs-ant shouldn't matter too much
at this point, though it does seem like the maven-bundle-plugin (which
uses BND) has been get
Thanks for the advise.
I also took the conservative approach in wrapping the SDK. Only the
jars javafxc, javafxrt, Scenario and javafxgui are wrapped in one jar.
Do you bundle them as well as one or as separate? That was not clear
from the maven code, given my limited knowledge of maven. The
What are the import-package headers for your javafx application,
bundle 3? It will have to include all the packages you use. BND can
successfully analyze the compile JFX classes to help create this
automatically, but if you are naming the import-packages manually it
won't.
Pat.
--
Defy mediocr
Here are the import headers:
Import-Package
com.sun.javafx.functions
com.sun.javafx.runtime
com.sun.javafx.runtime.annotation
com.sun.javafx.runtime.location
com.sun.javafx.runtime.sequence
framework.datamodel
javafx.geometry
javafx.scene
javafx.scene.effect
javafx.scene.input
> These are automatically created by bnd, as are the SDK headers. The export
> headers of the sdk look a bit different. BND does not explicitly mention
> these packages, but wraps them in a 'uses:=' statement. Could this be the
> problem?
If I understand it correctly the uses:= clauses are there t
Packages listed in "uses" directives for export packages are exposed in
some way by those exported packages (e.g., a method return value or
method parameter types). If you see a package listed in "uses" then it
will either be imported by your bundle or exported by it. The framework
uses this in
Thanks for the explanation of the uses:= clause. It still does not
work. I get the same errors as reported last week and I don't know
what I do wrong. I also tried to bundle each jar in the SDK
separately, but that didn't work either. I am open to all creative
solutions.
If used the follo
37 matches
Mail list logo
