I've seen some examples that show how to set that up, but it seems like a pain. And, if it's a pain for me, it's going to be a pain for anyone who wants to use our proposed JNLP-based Preferences API.
At this point, I'm questioning the value of continuing to pursue the Preferences class: - JNLP seems like a pain to work with - We could base it on the file system, but that would required signed applets - We could try to come up with a server-based means of storing preferences, but that seems like a big rat hole I'm leaning towards bagging Preferences for now (at least, until Sun makes it easier to launch and debug JNLP-based applications). For now, I'd suggest that apps that need to manage user preferences can simply do it with custom code. JSONSerializer provides most of what you'd need to manipulate JSON-based preferences, anyways. This way, it's up to the app to decide where/how they should be stored. Thoughts? On Tuesday, April 14, 2009, at 05:24PM, "Christopher Brind" <[email protected]> wrote: >Doesn't look like it... see attached image. > >I don't know too much about developing with JNLP but are you able to create >a remote debug session? If so, you should be able to connect from the debug >perspective. You can add the JNLP APIs to your debug session's class/source >path. > >Cheers, >Chris > > >2009/4/14 Greg Brown <[email protected]> > >> Hi all, >> I'm running Eclipse 3.3 and it doesn't include a launch configuration for >> JNLP applications. Does Eclipse 3.4 have such a feature? Without it, >> debugging applications that use the JNLP APIs seems very difficult. >> Thanks, >> Greg >> >> >> >
