Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #27960
| Newsgroups | comp.lang.java.programmer |
|---|---|
| Date | 2014-04-05 15:47 -0700 |
| References | <61n0k9911baggmm7g4anvqqine4ng58tlb@4ax.com> |
| Message-ID | <ec05c820-9f9d-467c-8d8f-79b22e2a2b66@googlegroups.com> (permalink) |
| Subject | Re: debugging Java Web Start |
| From | firstsql@gmail.com |
On Saturday, April 5, 2014 12:41:32 PM UTC-7, Roedy Green wrote: > The only way I have been able to debug Java Web Start JNLP apps is to > > strip out the Webstart code turning them into ordinary apps, debug, > > then put it back. Is there an easier way? I didn't have that problem because I wanted my app to run on Web Start and as a pure standalone app. I had my Web Start configuration set a -jnlp toggle to tell the app what to do. I also didn't want to sign my app. I used the Web Start classes that only asked for permission when you wanted to access the file system. I used Class.forName() to load my file system system code, driven by the -jnlp toggle. BTW, I love Class.forName(). With judicious coding, it can support all the dynamic loading you need without the nastiness of java.lang.reflect. However, I have an extra reason --- I usually want my code to run on JVMs that don't support java.lang.reflect. I call it "poor man's" reflection. Of course, this may be more than you want to do to get easier debugging. -- Lee Fesperman, FirstSQL Software (http://www.firstsql.com) ============================================================= * Pure Java implementation, runs on cellphones to mainframes * FirstSQL/J Object/Relational DBMS (http://www.firstsql.com)
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Find similar | Unroll thread
debugging Java Web Start Roedy Green <see_website@mindprod.com.invalid> - 2014-04-05 12:41 -0700 Re: debugging Java Web Start firstsql@gmail.com - 2014-04-05 15:47 -0700
csiph-web