• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

What does proper browser embed JavaFX app deployment looks like?

 
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have tried to deploy JavaFX app intent to be embed to browser.

I have done steps bellow:

1. javapackager -createjar -outdir compiled -outfile myapp -appclass MyApp -srcdir bin
2. javapackager -deploy -outdir deployed -outfile outfile -width 400 -height 400 -name AppName -appclass MyApp -srcdir compiled

Then I've tried to run JNLP file created but I got exception below:



So I've tried to solve this problem by steps below:
1. I tried to signed jar file.
2. I tried to specify in JNPL file that this jar is the main one;

3. As I saw some solution I have change paramater appclass for javapacker to application.MyApp.
4. Than I tried steps 1–3 again.
5. And also in both cases I have tried mark jar as main before signing it.

The exception in every case is the same.

If I compile jar classic way – jarsigner myapp.jar *.class allLastingFiles – app is normally runnig. This jar also normally works if it is signed.


Whole JNLP looks like this:



I have tried Google but I am not sure what to search.
 
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't know if this will help, but I would strongly suggest that your main class should be in a package.
 
Petr Omáčka
Ranch Hand
Posts: 39
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
@Paul Clapham: I have definitely main class file included in jar file.
 
Paul Clapham
Marshal
Posts: 28193
95
Eclipse IDE Firefox Browser MySQL Database
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When I said it should be in a package, I meant that the first line in its source code should be

I know that classes in the unnamed package (such as yours appears to be) can't be imported by classes in a named package. That's a compile-time issue; I don't know if it's involved here but it's a possibility.
 
Petr Omáčka
Ranch Hand
Posts: 39
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Problem is solved. I have for uknown reason packaged in jar source file instead of binaries.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic