This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Html and jnlp files generated from FX project with fxml files fails to run | ||
---|---|---|---|
Product: | javafx | Reporter: | Stepan Zebra <stezeb> |
Component: | Deployment | Assignee: | Petr Somol <psomol> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | dstrupl, mmirilovic |
Priority: | P1 | ||
Version: | 7.1 | ||
Hardware: | PC | ||
OS: | Windows 7 x64 | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Stepan Zebra
2011-09-24 20:56:00 UTC
in daily (non-beta) build this is not reproducible. Note that I tested this after the changes done by changeset http://hg.netbeans.org/jet-main/rev/714e74976915 while the bugreport was based on build without the changeset. Tried to create New FX FXML Application, followed by Run. This correctly build and run the FXML application. Tried the same with the FXML-Login sample and it works. Note that the changeset also changed the behavior of New File -> FXML Template. After a request FXML SceneBuilder team we removed from the template the generation of main file. 714e74976915 transplanted to e8a442ddf09c in beta (In reply to comment #1) > in daily (non-beta) build this is not reproducible. > Note that I tested this after the changes done by changeset > > http://hg.netbeans.org/jet-main/rev/714e74976915 > > while the bugreport was based on build without the changeset. > > Tried to create New FX FXML Application, followed by Run. This correctly build > and run the FXML application. Tried the same with the FXML-Login sample and it > works. > > Note that the changeset also changed the behavior of New File -> FXML Template. > After a request FXML SceneBuilder team we removed from the template the > generation of main file. Actually, I noticed this problem for the first time during verification of this fix in a build I made from trunk myself. Anton confirmed same problem on his machine. Does this worksforyou even if you try the beta build? I think it's not related to this fix. If you won't get the error in beta, then it might be caused by my environment. I will wait until today's daily build (will include this fix) is finished, and then re-check in that, to eliminate the possibility that it was caused by my environment. works for me in beta by now. More specific description of current functionality: Applications created as New FXML Application using New Project wizard run correctly in all three deployment modes (standalone, webstart, embedded in html) if signing is on. If signing is off, then the application runs correctly standalone, but an attempt to run it as WebStart does nothing and run In Browser reports an error in the application's area within the html. (In reply to comment #5) > More specific description of current functionality: > Applications created as New FXML Application using New Project wizard > run correctly in all three deployment modes (standalone, webstart, embedded in > html) if signing is on. If signing is off, then the application runs correctly > standalone, but an attempt to run it as WebStart does nothing and run In > Browser reports an error in the application's area within the html. Verified. The application works after signing. This is already integrated since September and does not need any further action. Changing Target milestone back to 7.1. |