Open GoogleCodeExporter opened 9 years ago
Re-installing did not fix issue.
Original comment by paul.r...@nsolve.com
on 5 Aug 2013 at 8:43
Delete .rest-client directory in your home. This directory holds the history.
Original comment by subwiz
on 5 Aug 2013 at 10:57
Hurrah now it runs again :-)
Original comment by paul.r...@nsolve.com
on 7 Aug 2013 at 8:41
I restored the urls.list file and started again and it worked - so probably
some other issue than the historic urls
Original comment by paul.r...@nsolve.com
on 7 Aug 2013 at 8:43
I am having the same issue. I deleted rest client history folder. Is there
anything else I need to delete? I am using vmware view client to connect to my
VPI. Also rest client 3.1 is working fine. 3.2 was working before yesterday.
Original comment by krunal77...@gmail.com
on 21 Aug 2013 at 2:23
We store all configuration and history in .rest-client dir inside the home
directory. RESTClient depends on no other data.
Original comment by subwiz
on 23 Aug 2013 at 11:23
I understand that I need to delete.rest-client dir inside the home directory.
But Since I am using VPI, can't access the directory. Is there any way around
this? Can we have ability to choose same folder for the directory as the place
where we save the executable rest client jar file? I can run rest client 3.2
on my personal pc and see that every time It creates the .rest-client folder in
the directory same spot. Can we change this?
Original comment by krunal77...@gmail.com
on 23 Aug 2013 at 7:20
We don't have the option to change the .rest-client directory.
I can write a command line tool to delete .rest-client directory in your home
dir. Will that be useful for you?
Original comment by subwiz
on 24 Aug 2013 at 4:58
If you can provide that would be great. I can try and see if it works.
Original comment by krunal77...@gmail.com
on 28 Aug 2013 at 2:10
The tool is available here:
http://download.wiztools.org/rest-client/rest-client-history-rm-1.0-SNAPSHOT.jar
The tool needs to be run thus:
$ java -jar rest-client-history-rm-1.0-SNAPSHOT.jar -y
(note the cli parameter -y at the end)
If the tool is able to delete the history data, the tool will silently quit (no
feedback). If the tool is not able to find the data, then it will report the
same.
Let me know if this helps.
Original comment by subwiz
on 31 Aug 2013 at 5:47
Issue 184 has been merged into this issue.
Original comment by subwiz
on 6 Sep 2013 at 4:17
Since few people are facing this issue, I think I need to think of a permanent
solution for this. One could be determining the size of history dynamically
(right now last 20 history data is stored in memory), or other solution could
be a cli parameter to NOT load history during startup (this could have
implications on the Mac build).
Original comment by subwiz
on 6 Sep 2013 at 2:34
Issue 185 has been merged into this issue.
Original comment by subwiz
on 23 Sep 2013 at 6:17
Issue 186 has been merged into this issue.
Original comment by subwiz
on 24 Sep 2013 at 6:17
Issue 186 has been merged into this issue.
Original comment by subwiz
on 19 Oct 2013 at 9:38
I am planning to reduce the history list to 15 from current 30. This will save
the tool from unexpected OutOfMemory. I'm being defensive, but this seems to be
the quick solution.
Original comment by subwiz
on 19 Oct 2013 at 10:31
Issue 179 has been merged into this issue.
Original comment by subwiz
on 25 Nov 2013 at 2:52
I regularly get the following error, because somehow my history.xml file
exists, but becomes completely blank. Deleting history.xml fixes the problem.
But otherwise the splash screen just comes up, but with no further action.
Caused by: nu.xom.ParsingException: Premature end of file. at line 1, column 1
in file:///C:/Users/jsmith/.rest-client/history.xml
at nu.xom.Builder.build(Unknown Source)
at nu.xom.Builder.build(Unknown Source)
at nu.xom.Builder.build(Unknown Source)
at org.wiztools.restclient.util.XMLUtil.getDocumentFromFile(XMLUtil.java:482)
Original comment by javaguy...@gmail.com
on 7 Feb 2014 at 4:35
Are you using the latest 3.2.2 version? I had some defensive checks for
validating this. Also can you provide the full stack trace.
Original comment by subwiz
on 7 Feb 2014 at 5:05
Original issue reported on code.google.com by
paul.r...@nsolve.com
on 5 Aug 2013 at 8:42