Okay, this one has resolved itself after I did some lib-containing-folder
management.
Apparently, this was one of those classpath madness issues.
On Tue, Apr 15, 2008 at 2:35 PM, Sergey Podatelev <
[EMAIL PROTECTED]> wrote:
> Hello Wicket people,
>
> I'm experiencing a strange behavior of Netbeans (6.0.1) IDE working with
> Wicket-Security components. Maybe this question is more Netbeans- than
> Wicket-related, but I thought I'd better ask here first.
>
> I have a BaseSecurePage class that implements ISecurePage.
> Its constructor looks like this:
>
> public BaseSecurePage() {
> super();
> setSecurityCheck(new ComponentSecurityCheck(this));
> }
>
> Wasp-0.1 and Swarm-0.1 were included in a library class
> Wicket-Security-0.1 in Netbeans IDE and everything was fine.
> Once I created Wicket-Security-1.3, added Wasp-1.3 and Swarm-1.3 in it,
> removed old Wicket-Security-0.1 and added the Wicket-Security-1.3 to the
> project, strange thing had happened:
>
> Netbeans now says it "can't find symbol ComponentSecurityCheck(this)".
> Moreover, when I Ctrl+click the ComponentSecurityCheck(this), it takes me to
> the sources (which I didn't import, just swarm/wasp-1.3.0 and
> swarm/wasp-javadoc-1.3.0), and there in the sources of
> ComponentSecurityCheck I can see Netbeans complaining about the fact that it
> can't find Component class.
>
> There's one good thing though -- it builds with no problems, but still I'd
> like to fix somehow.
>
> --
> sp
--
sp
