Re: 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 
not be everything that you specified in the session settings. This will 
cause some symbols to not be found by the NetBeans Java parser. You 
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 
error stripes themselves, if they refer to symbols only found on the 
classpath you defined.

If that doesn't explain what you're seeing, then send me a screen shot 
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.
> 
> 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.  
> 
> 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".
>  
> This isn't a major issue for now.  I just wanted to make sure I wasn't
> missing something obvious.