RE: Classpath problem

Your description of the change in classpath before/after Attach makes
sense. But your statement that "everything that is on the sourcepath
will not generate error stripes." doesn't seem to align with what I'm
seeing in the tool.  In lieu of a screenshot, since I'm not sure what my
boss would think about that, I'll try to describe it more clearly in
words:

-----------------------------------
Before Attach:=20
-----------------------------------
* The "Session Settings/Classes" tab contains the root directory of my
application's class files.=20
* The "Session Settings/Sources" tab contains the root directory of my
application's source files. =20
* An import statement in one of my source files that imports another one
of my app's classes has NO red wavy line e.g. In
"com.mycompany.report.Top10.java", the line "import
com.mycompany.beans.Channel;" has no red wavy line.
* I can see both "com.mycompany.report.Top10.java" and
"com.mycompany.beans.Channel.java" in my Sources tab and open both files
in the editor.

-----------------------------------
After Attach:
-----------------------------------
* The "Session Settings/Classes" tab now contains just tools.jar and
bootstrap.jar, and my previous setting is gone. (This aligns with what
you said about the debuggee.)
* The "Session Settings/Sources" tab contains the root directory of my
application's source files (as it did previously).
* The previous line of source in JSwat that references one of my app's
classes NOW HAS a red wavy line!
* I can still see both files in my Sources tab and open them in the
editor.

Again, this isn't a huge deal, and I can turn off the red wavy line in
Annotation Types.  I just wanted to make sure I wasn't missing
something.

Jay

-----Original Message-----
From: Nathan Fiedler [mailto:[email protected]]=20
Sent: Saturday, April 29, 2006 2:12 AM
To: Burgess, Jay S
Cc: [email protected]
Subject: Re: [jswat-user] Classpath problem

The difference will be in the contents of the classpath. While attached,

the classpath will be whatever is reported by the debuggee, which may=20
not be everything that you specified in the session settings. This will=20
cause some symbols to not be found by the NetBeans Java parser. You=20
should be seeing error stripes for those missing symbols, but everything

that is on the sourcepath will not generate error stripes. However, that

does not mean that source files on the source path will not contain=20
error stripes themselves, if they refer to symbols only found on the=20
classpath you defined.

If that doesn't explain what you're seeing, then send me a screen shot=20
and maybe I can get an understanding of your situation.

n


Burgess, Jay S wrote:
> Thank you for the prompt response.  Everything you say makes complete
> sense.  However, unless I'm misunderstanding something, the workaround
> doesn't really solve my problem.
>=20
> My servlet source is available in the Sources tab whether I'm
Attach'ed
> or not. But when I'm not attached, I have no error stripes.  After I
> attach, however, the error stripes usually appear. =20
>=20
> Your description of the classpath handling sounds right, but there
must
> be some combination of classpath AND sourcepath after I Attach that
> causes files that are available on the sourcepath to suddenly be
> considered "cannot find symbol".
> =20
> This isn't a major issue for now.  I just wanted to make sure I wasn't
> missing something obvious.