Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » e(fx)clipse » Hybrid jars(Hybrid jars fail to run)
Hybrid jars [message #1233862] Mon, 20 January 2014 17:29 Go to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
Hey,

i have a project that has swing + javafx in it. exporting a regular jar obviously doesn't work,
so I build a jar like in the first tutorial.

the jar is created and the build is successful, however i cannot run it :

(running with java -jar)

Exception in Application constructor
2014-01-20 18:44:54.536 java[43988:2707] [JRSAppKitAWT markAppIsDaemon]: Process manager already initialized: can't fully enable headless mode.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.javafx.main.Main.launchApp(Main.java:698)
at com.javafx.main.Main.main(Main.java:871)
Caused by: java.lang.RuntimeException: Unable to construct Application instance: class application.Dstrux
at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:393)
at com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:47)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:115)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:276)
... 3 more
Caused by: java.awt.HeadlessException
at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:207)
at java.awt.MenuComponent.<init>(MenuComponent.java:159)
at java.awt.MenuItem.<init>(MenuItem.java:214)
at java.awt.MenuItem.<init>(MenuItem.java:198)
at java.awt.CheckboxMenuItem.<init>(CheckboxMenuItem.java:139)
at java.awt.CheckboxMenuItem.<init>(CheckboxMenuItem.java:122)
at application.Dstrux.<init>(Unknown Source)
... 8 more
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.javafx.main.Main$2.run(Main.java:948)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:241)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
Caused by: java.awt.HeadlessException
at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:207)
at java.awt.Window.<init>(Window.java:535)
at java.awt.Frame.<init>(Frame.java:420)
at java.awt.Frame.<init>(Frame.java:385)
at javax.swing.SwingUtilities$SharedOwnerFrame.<init>(SwingUtilities.java:1759)
at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1834)
at javax.swing.JOptionPane.getRootFrame(JOptionPane.java:1697)
at javax.swing.JOptionPane.showOptionDialog(JOptionPane.java:863)
at javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:667)
at javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:638)


Also, it weight only 300k, the regular jar was 14m, does that make sense?

Thanks
Lior
Re: Hybrid jars [message #1234085 is a reply to message #1233862] Tue, 21 January 2014 07:52 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
Hi,

First of all I think you need to export with "Toolkit Type" == swing.
Still this does not explain why you only get such a small jar size. Are
you repackaging libs when doing the ordinary export?

Tom

On 20.01.14 20:37, Lior Giller wrote:
> Hey,
> i have a project that has swing + javafx in it. exporting a regular jar
> obviously doesn't work,
> so I build a jar like in the first tutorial.
> the jar is created and the build is successful, however i cannot run it :
>
> (running with java -jar)
>
> Exception in Application constructor
> 2014-01-20 18:44:54.536 java[43988:2707] [JRSAppKitAWT markAppIsDaemon]:
> Process manager already initialized: can't fully enable headless mode.
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.javafx.main.Main.launchApp(Main.java:698)
> at com.javafx.main.Main.main(Main.java:871)
> Caused by: java.lang.RuntimeException: Unable to construct Application
> instance: class application.Dstrux
> at
> com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:393)
>
> at
> com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:47)
> at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:115)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at
> com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:276)
>
> ... 3 more
> Caused by: java.awt.HeadlessException
> at
> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:207)
> at java.awt.MenuComponent.<init>(MenuComponent.java:159)
> at java.awt.MenuItem.<init>(MenuItem.java:214)
> at java.awt.MenuItem.<init>(MenuItem.java:198)
> at java.awt.CheckboxMenuItem.<init>(CheckboxMenuItem.java:139)
> at java.awt.CheckboxMenuItem.<init>(CheckboxMenuItem.java:122)
> at application.Dstrux.<init>(Unknown Source)
> ... 8 more
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.javafx.main.Main$2.run(Main.java:948)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:241)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
> at java.awt.EventQueue.access$200(EventQueue.java:103)
> at java.awt.EventQueue$3.run(EventQueue.java:694)
> at java.awt.EventQueue$3.run(EventQueue.java:692)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
>
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
> at
> java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
>
> at
> java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
>
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
>
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
> Caused by: java.awt.HeadlessException
> at
> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:207)
> at java.awt.Window.<init>(Window.java:535)
> at java.awt.Frame.<init>(Frame.java:420)
> at java.awt.Frame.<init>(Frame.java:385)
> at
> javax.swing.SwingUtilities$SharedOwnerFrame.<init>(SwingUtilities.java:1759)
>
> at
> javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1834)
> at javax.swing.JOptionPane.getRootFrame(JOptionPane.java:1697)
> at javax.swing.JOptionPane.showOptionDialog(JOptionPane.java:863)
> at javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:667)
> at javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:638)
>
>
> Also, it weight only 300k, the regular jar was 14m, does that make sense?
>
> Thanks Lior
Re: Hybrid jars [message #1234094 is a reply to message #1234085] Tue, 21 January 2014 08:18 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
Hey Tom,


Thank you for the reply,

first i have changed the "Toolkit Type" == swing. it did not helped. the jar is still 300k, and i still get the
Process manager already initialized: can't fully enable headless mode.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

for you second question, I'm not repackaging libs, I am exporting all the java sources and resources, than compress the jar.

exception when running. from Jar, when running from the e(fx)clipse all is still ok.
i wrote a new project just so i can find the issue since my project is very large,
i rewrote just the basics, something like a simple javafx project with a system tray app.
again, works well on the e(fx)clipse, but not as jar (except I don't get an error, the jar just doesn't do anything).


As I said before, my app is really big, and working well from the eclipse, so there must be something i'm doing wrong while packaging right?

I would hate to re do this whole thing just cause i cant get a proper jar Sad

ill appreciate any idea at this moment!!!

Thanks!
Re: Hybrid jars [message #1234098 is a reply to message #1234094] Tue, 21 January 2014 08:31 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
Also, it might be nothing, but i tried every possible thing other than that,
When i'm running from e(fx)clipse, this is the icon i get the blue and red java icon
But wen running as Jar, the icon is that black coffee with pan icon..

I know its stupid but maybe java versioning also cause some issues?

Lior
Re: Hybrid jars [message #1234102 is a reply to message #1234094] Tue, 21 January 2014 08:38 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
Hi,

IIRC the export is not packaging the libraries directly into the JAR but
adds a MANIFEST.MF-Entry pointing to them, not?

I'd need something to test to see what's broken. In the end all our
build is doing is to write the build.xml and execute it. You can take a
look at the build.xml and fix things manually?

Tom

On 21.01.14 09:18, Lior Giller wrote:
> Hey Tom,
>
>
> Thank you for the reply,
>
> first i have changed the "Toolkit Type" == swing. it did not helped. the
> jar is still 300k, and i still get the Process manager already
> initialized: can't fully enable headless mode.
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> for you second question, I'm not repackaging libs, I am exporting all
> the java sources and resources, than compress the jar.
> exception when running. from Jar, when running from the e(fx)clipse all
> is still ok.
> i wrote a new project just so i can find the issue since my project is
> very large, i rewrote just the basics, something like a simple javafx
> project with a system tray app. again, works well on the e(fx)clipse,
> but not as jar (except I don't get an error, the jar just doesn't do
> anything).
>
>
> As I said before, my app is really big, and working well from the
> eclipse, so there must be something i'm doing wrong while packaging right?
> I would hate to re do this whole thing just cause i cant get a proper
> jar :(
> ill appreciate any idea at this moment!!!
>
> Thanks!
Re: Hybrid jars [message #1234115 is a reply to message #1234102] Tue, 21 January 2014 09:07 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
Correct, its create the manifest, which is also what happens when I use the ant build.

I can attach my test app, it might help?
I'll be happy to manually fix things on my build.xml but i'm afraid I currently don't know what to change (as you noticed i'm new in all of this) any ideas?


Re: Hybrid jars [message #1234120 is a reply to message #1234115] Tue, 21 January 2014 09:25 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
File a bug and attach the test application project.

Tom

On 21.01.14 10:07, Lior Giller wrote:
> Correct, its create the manifest, which is also what happens when I use
> the ant build.
>
> I can attach my test app, it might help? I'll be happy to manually fix
> things on my build.xml but i'm afraid I currently don't know what to
> change (as you noticed i'm new in all of this) any ideas?
>
>
Re: Hybrid jars [message #1234126 is a reply to message #1234120] Tue, 21 January 2014 09:45 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
I will thank you very much!!
how long does it take to process a bug?

Thank you!!
Re: Hybrid jars [message #1234129 is a reply to message #1234126] Tue, 21 January 2014 09:49 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
Well this depends on when I have time and how pressing the issue is.

Unfortunately - for you - we are in RC-Mode and while I understand that
this is a pressing issue for you I don't think I can squeeze it into 0.9.0.

Tom

On 21.01.14 10:45, Lior Giller wrote:
> I will thank you very much!!
> how long does it take to process a bug?
>
> Thank you!!
Re: Hybrid jars [message #1234173 is a reply to message #1234129] Tue, 21 January 2014 11:54 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
I have some progress which might help understand the issue better.
i realised (and maybe it was obvious but i missed it( that fro running from e(fx)clipse, i use "main" method., but if i want my jar to work, i need to use "start" method.
i manages to get my simple system tray app working by copying my "main" code into the start, but from eclipse its stopped cause i have to have main.

thats why i fail running as javafx jars, as it searches for the start method.
also, on my mac, when i'm running from main all is ok, but same code running from start i get different result for
if (!SystemTray.isSupported()) {
System.out.println("SystemTray is not supported");
return;

running from eclipse- its supported, running from jar its not.

Does that make any sense to you?

Lior
Re: Hybrid jars [message #1234191 is a reply to message #1234173] Tue, 21 January 2014 12:41 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
If you look at the MANIFEST.MF generated? Does it hold the special
JavaFX-Launcher as the main-class?

If I remember correct JavaFX-Launcher does not call main but directly
bootstraps the application class and calls the start method.

What makes me wonder a bit because you said you have a Swing application!

Tom

On 21.01.14 12:54, Lior Giller wrote:
> I have some progress which might help understand the issue better.
> i realised (and maybe it was obvious but i missed it( that fro running
> from e(fx)clipse, i use "main" method., but if i want my jar to work, i
> need to use "start" method. i manages to get my simple system tray app
> working by copying my "main" code into the start, but from eclipse its
> stopped cause i have to have main.
> thats why i fail running as javafx jars, as it searches for the start
> method. also, on my mac, when i'm running from main all is ok, but same
> code running from start i get different result for if
> (!SystemTray.isSupported()) {
> System.out.println("SystemTray is not supported");
> return;
>
> running from eclipse- its supported, running from jar its not.
>
> Does that make any sense to you?
>
> Lior
Re: Hybrid jars [message #1234202 is a reply to message #1234191] Tue, 21 January 2014 12:59 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
My app is swing, thats why it wroked from eclipse beacuse its run from the main method.
however building by build.builfx causes the jar to run from start- which then makes my system tray app not supported from javafx.

maybe i made one big mess. i have a regular java project, with references to javafx, and uses javafx as run later.
should i have created the jar with regular export, or the build,buildfx?
Re: Hybrid jars [message #1234206 is a reply to message #1234202] Tue, 21 January 2014 13:00 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
So you are using JXPanel to embed FX into your application?

Tom

On 21.01.14 13:59, Lior Giller wrote:
> My app is swing, thats why it wroked from eclipse beacuse its run from
> the main method.
> however building by build.builfx causes the jar to run from start- which
> then makes my system tray app not supported from javafx.
>
> maybe i made one big mess. i have a regular java project, with
> references to javafx, and uses javafx as run later.
> should i have created the jar with regular export, or the build,buildfx?
>
Re: Hybrid jars [message #1234209 is a reply to message #1234206] Tue, 21 January 2014 13:06 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
yes!
Re: Hybrid jars [message #1234219 is a reply to message #1234209] Tue, 21 January 2014 13:39 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
So there can't be a start-method then because you are NOT subclassing
Application!

Tom

On 21.01.14 14:06, Lior Giller wrote:
> yes!
Re: Hybrid jars [message #1234222 is a reply to message #1234219] Tue, 21 January 2014 13:43 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
I guess your problem is that you created an artificial class which
subclasses application because our browse button only displays
subclasses of application?

I fear that we need relax this restriction, but you can enter your main
class manually!

Tom

On 21.01.14 14:39, Tom Schindl wrote:
> So there can't be a start-method then because you are NOT subclassing
> Application!
>
> Tom
>
> On 21.01.14 14:06, Lior Giller wrote:
>> yes!
>
Re: Hybrid jars [message #1234240 is a reply to message #1234222] Tue, 21 January 2014 14:19 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
but once I add the javafx libary than the project demands to implement a start class, so i implement it and leave it empty.
So my question is basically:

1. should i still create the jar with the build.buildfx and toolkit swing? or regular export?
2. how can I manually get it to run via the main and not start?
3. or how can i not have start at all?

Thank you!!
Re: Hybrid jars [message #1234243 is a reply to message #1234240] Tue, 21 January 2014 14:29 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
No you don't need any Application subclass! JFXPanel will bootstrap
JavaFX when needed.

1. Yes you have to do that on Java7 because you need to bootstrapping
code inserted

2. The class you provide as the main class has to be your original main
one which DOES NOT subclass Application

3. Once more you don't need to have an Application because JFXPanel
does the bootstraping internally

Tom

On 21.01.14 15:19, Lior Giller wrote:
> but once I add the javafx libary than the project demands to implement a
> start class, so i implement it and leave it empty. So my question is
> basically:
>
> 1. should i still create the jar with the build.buildfx and toolkit
> swing? or regular export? 2. how can I manually get it to run via the
> main and not start?
> 3. or how can i not have start at all?
>
> Thank you!!
Re: Hybrid jars [message #1234250 is a reply to message #1234243] Tue, 21 January 2014 14:44 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
First of all thank you for all the help! I really appreciate it.
I removed the "extend application" from my class, and the implementation of the start method.run the build.buildfx with the swing toolkit.
now the jar runs and i can see my system tray app which is a great progress.
HOWEVER, nothing on the system tray works. again, its still working OK on the e(fx)clips...i have no idea why..
Re: Hybrid jars [message #1234260 is a reply to message #1234250] Tue, 21 January 2014 15:06 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5434
Registered: July 2009
Senior Member
So the system tray uses JavaFX? Do you get any exceptions when you run
this guy on the console?

Tom

On 21.01.14 15:44, Lior Giller wrote:
> First of all thank you for all the help! I really appreciate it. I
> removed the "extend application" from my class, and the implementation
> of the start method.run the build.buildfx with the swing toolkit. now
> the jar runs and i can see my system tray app which is a great progress.
> HOWEVER, nothing on the system tray works. again, its still working OK
> on the e(fx)clips...i have no idea why..
Re: Hybrid jars [message #1234262 is a reply to message #1234260] Tue, 21 January 2014 15:13 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
No i dont get any exception,
but seems like most of the code's not working, usually the app reads from disk to see if the user logged in, (the info is there so it suppose to be looged in)
but from jar it already goes to disconnected mode, and the "login" button open an empty JFrame.
the quit button works. thats it.

on debug from eclipse its working ok.. im trying to understand whats the different in those modes that will cause the jar to run but not function.
Re: Hybrid jars [message #1234265 is a reply to message #1234262] Tue, 21 January 2014 15:24 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
and btw my jar is still 315kb only..
Re: Hybrid jars [message #1234284 is a reply to message #1234265] Tue, 21 January 2014 16:05 Go to previous messageGo to next message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
im pretty sure that it cannot find any images and icons for the frame, thats why the jframe is empty
Re: Hybrid jars [message #1234296 is a reply to message #1234284] Tue, 21 January 2014 16:26 Go to previous message
Lior Giller is currently offline Lior Giller
Messages: 14
Registered: January 2014
Junior Member
All is fixed!!!! Thank you very much!!
Previous Topic:Can't install e(fx)clipse to Eclipse Kepler
Next Topic:IEventBroker.subscribe to UIEvents.UILifeCycle.APP_STARTUP_COMPLETE does not work
Goto Forum:
  


Current Time: Thu Oct 30 16:00:38 GMT 2014

Powered by FUDForum. Page generated in 0.02599 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software