[java ee programming] Re: MyHellowWeb variable definition conflict

2009-10-19 Thread Mihai DINCA
Hi Peeter, I think the values of myname1 and myname2 are actually used (the "get" methods). When you split on two lines the warning is gone because nameeq is no longer private, so, as package restricted (the default visibility) it might be read by some other class in the package. In the previo

[java ee programming] Re: MyHellowWeb variable definition conflict

2009-10-19 Thread peeter brunch
Hi Alin & Mihai, I only wonder why the other names such as myname1 and myname2 are exactly being used in the way similar to nameeq, but these two variables do not have any warning. Afterall, I declare nameeq on a new line rather than on the same line as myname1. It turns out the warning

[java ee programming] Re: MyHellowWeb variable definition conflict

2009-10-16 Thread Mihai DINCA
Hi, I think that NetBeans (in the 2nd screen) is unable to detect a statement like "String foobar = nameeq" or "System.println( nameeq )" and so on, so it finds that the attribute this.nameeq gets a value but its value is never used, so it issues a warning. This warning doesn't stop the progra