Null pointer opening settings for a session

[Bill Williams]

Getting a null pointer exception trying to open settings for a session.

 

[John Pritchard]

been doing anything special like editing session xml? 

+ ideas..

++ quit; delete|move ~/.jswat; restart

++ reinstall

Getting a null pointer exception trying to open settings for a session.

 

--
http://www.google.com/profiles/john.douglas.pritchard

[Bill]

Yes, that is what I was doing because I have been trying to add an
additional session through the various screens and keep having issues
with that. The source paths keep disappearing not to mention it's a
pain in the rear since you cannot simply copy a session and easily
edit a couple of paths. I'll delete the .jswat directory and try to
do it again through the screens and see what happens.

I've go the old jswat on my computer also and was just wondering why
was the editing ability removed in the new jswat since it seems better
in so many other ways?

Thanks for the help.

[Nathan Fiedler]

Hi Bill

Thanks for sending the messages log that shows the exception. I can't
see how that would happen, as the code just above that line is
checking that the file exists, then uses the NetBeans API to convert
the File to a FileObject. For whatever reason, that results in a null
and then the exception occurs. Could you, by any chance, send me the
classpath that you're trying to set?

Regarding the copy/paste of sessions, the feature is hidden in the
Sessions window. To open the sessions window, open the Window >
Debugging menu and select Sessions. Then in the sessions window,
right-click on the desired session and select Copy.

n

[Bill]

I found the path that causes the problem. First let me say I nuked
the .jswat directory and reinstalled jswat 4.5.

I then went to add class and source paths to Session 1 using bulk load
and after I pressed Okay I got a NullPointerException. I came back
into the settings screen and the source paths were gone. I
nuked .jswat again and then started a slow, methodical approach and
first started adding one directory at a time.

Here is the bulk class path: S:\wlw\Projects\LiaSophia\Classes
\1.6;.\;Q:\Projects\LiaSophia\Classes\1.6;S:\wlw\Products\Classes
\1.6;B:\10.2\Products\Classes\1.6\QcUpdates;B:\10.2\Products\Classes
\1.6;B:\10.2\Products\Classes\JarFiles\*;C:\PROGRA~1\SQLANY~2\Java
\jodbc.jar

I used the bulk load and started with the first directory only for
class path only. It worked. I then removed the directory and did the
bulk load again with the first two directories and it worked. I
continued doing this adding an additional directory every time and
then when I included B:\10.2\Products\Classes\1.6\QcUpdates, I got the
NPE. The directory does exist so I do not know what's up. None of
these times did I mess with the source path portion.

By the way, I did know about the copy feature. My point is when I
start a new project (customer), most of the paths for a previous
customer are fine except for the customer's directory name so it would
be really nice to be able to copy an existing session and then edit a
couple of entries in the class and source paths to account for the
name change.

On Feb 12, 9:28 am, Nathan Fiedler <nathanfied...@gmail.com> wrote:
> Hi Bill
>
> Thanks for sending the messages log that shows the exception. I can't
> see how that would happen, as the code just above that line is
> checking that the file exists, then uses the NetBeans API to convert
> the File to a FileObject. For whatever reason, that results in a null
> and then the exception occurs. Could you, by any chance, send me the
> classpath that you're trying to set?
>
> Regarding the copy/paste of sessions, the feature is hidden in the
> Sessions window. To open the sessions window, open the Window >
> Debugging menu and select Sessions. Then in the sessions window,
> right-click on the desired session and select Copy.
>
> n
>

[Nathan Fiedler]

That's weird, I thought I had fixed that issue before. Well, I've
filed it again. I've also filed the request for editing the
classpath/sourcepath entries. Yes, that feature used to exist a long
time ago.

Thanks

n

> --
> You received this message because you are subscribed to the Google Groups "jswat-discuss" group.
> To post to this group, send email to jswat-...@googlegroups.com.
> To unsubscribe from this group, send email to jswat-discus...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/jswat-discuss?hl=en.
>
>

[Bill]

Is there any kind of work around for this?

Is there an expected time to get this fix because it's basically
making it so I cannot use jswat?

Thanks

On Feb 17, 10:54 am, Nathan Fiedler <nathanfied...@gmail.com> wrote:
> That's weird, I thought I had fixed that issue before. Well, I've
> filed it again. I've also filed the request for editing the
> classpath/sourcepath entries. Yes, that feature used to exist a long
> time ago.
>
> Thanks
>
> n
>

[Bill]

Did this help anyone with the issue I'm having?

[Nathan Fiedler]

You can't use JSwat because you cannot edit a classpath entry, or is
there something more to this issue? One work around, although perhaps
unpalatable, is to copy the session, exit JSwat, edit the sessions.xml
file to change the one path entry, then start JSwat again.

Any promise of a delivery date would be impossible to uphold. There is
a backlog of tasks to complete, and my schedule is made more
complicated by the fact that my two young children take up most of my
spare time. As if that weren't enough, we're trying to sell our house.
So, if you want to see this fixed sooner rather than later, you may
want to consider submitting a patch.

Thanks

n

[Bill]

Okay, thanks. By the way, I have tried editing the session files in
the past and it just does not seem to work properly.

One thing I could try is to run jswat on our linux server and see if
that makes a difference since the paths are different.

On Feb 17, 1:10 pm, Nathan Fiedler <nathanfied...@gmail.com> wrote:
> You can't use JSwat because you cannot edit a classpath entry, or is
> there something more to this issue? One work around, although perhaps
> unpalatable, is to copy the session, exit JSwat, edit the sessions.xml
> file to change the one path entry, then start JSwat again.
>
> Any promise of a delivery date would be impossible to uphold. There is
> a backlog of tasks to complete, and my schedule is made more
> complicated by the fact that my two young children take up most of my
> spare time. As if that weren't enough, we're trying to sell our house.
> So, if you want to see this fixed sooner rather than later, you may
> want to consider submitting a patch.
>
> Thanks
>
> n
>