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.

Bug 76067 - an app started via JNLP doesn't maintain its state between runs
Summary: an app started via JNLP doesn't maintain its state between runs
Status: RESOLVED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 5.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-08 11:25 UTC by hefest
Modified: 2006-11-03 19:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hefest 2006-05-08 11:25:33 UTC
My test concluded of the following:
1. run the app via .jnlp from the IDE
2. copy .../dist/jnlp/* to my ~/public_html
3. run the app from localhost/~me/jnlp/local/master.jnlp
4. arrange a couple of TCs
5. close app
6. run the app from the same location
7. verify TC arrangement

I've done this experiment a number of times now and I've never seen it
work as I expected it to work: when the app starts, all the TCs are in their
default locations instead of where I left them.
Comment 1 Jaroslav Tulach 2006-08-09 15:55:22 UTC
Do you know that the master.jnlp after step "3" contains reference to files on 
your local disk and as such you are very likely not running against the HTTP 
server at all?

Anyway I know that the configuration of components is lost, I'll keep 
investigating.
Comment 2 Jaroslav Tulach 2006-08-10 04:43:46 UTC
/shared/data/ccvs/repository/core/startup/src/org/netbeans/core/startup/NbRepository.java,v  
<--  NbRepository.java
new revision: 1.5; previous revision: 1.4
done
Checking in src/org/netbeans/core/startup/CLIOptions.java;
/shared/data/ccvs/repository/core/startup/src/org/netbeans/core/startup/CLIOptions.java,v  
<--  CLIOptions.java
new revision: 1.12; previous revision: 1.11
done
RCS 
file: /shared/data/ccvs/repository/core/startup/test/unit/src/org/netbeans/core/startup/NbRepositoryTest.java,v
done
Checking in test/unit/src/org/netbeans/core/startup/NbRepositoryTest.java;
/shared/data/ccvs/repository/core/startup/test/unit/src/org/netbeans/core/startup/NbRepositoryTest.java,v  
<--  NbRepositoryTest.java
initial revision: 1.1
Comment 3 hefest 2006-08-10 11:01:31 UTC
I did some JNLP testing on other machines, running over apache...but most of the
time I probably ran from the local disk, as you said. Still, the more important
problem was handling change: can't wait to try out update 2. When is it due?
Comment 4 Jaroslav Tulach 2006-08-10 12:54:56 UTC
No plans right now, it costs a lot to do new update and still there are not 
that much new features. If you need the fix, try to pickup the apisupport from 
trunk.
Comment 5 hefest 2006-10-31 23:24:08 UTC
Great news! When is u1 due to be released?
Comment 6 Jesse Glick 2006-10-31 23:35:13 UTC
No concrete plans for 5.5u1 just yet.
Comment 7 hefest 2006-10-31 23:38:47 UTC
Never mind. If the functionality becomes urgently needed, I'll see if I can
build the platform from source.
Thanks