This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Currently Monitor records context attributes only before the request is processed. Since this does not allow the user to see context attributes set by filters, forwarding servlets or the JSPs and servlets, the context attributes should probably be recorded after the request.
I'm not sure what makes sense to do here... It is kind of unusual for servlet requests to result in new context attributes. The reason I recorded them beforehand was that I believed most context attributes that set at startup so they would be set when the servlet processes or not at all. What I think I might to is to check if there are any new ones post fact and report the differences if there are any. Setting them as results of request is kind of unusual.
I don't think this is a P3. Or at least it's an RFE rather than a bug. Context attributes are usually set through the deployment descriptor or through the init method of a servlet. It is not something that the web components update as they go along. I can try to add facilities for displaying context attributes that have changed as a result of the request, but I think that's a new feature, not a bug.
Agreed. Changing to an enhancement and lowering priority. So, if a servlet sets a context attribute in its init() method and that servlet is not loaded on startup, then the first time the servlet is requested the context attributes will be set but won't be recorded until subsequent requests are made. I'm sure this is not a big deal. I just filed this bug when I was trying to figure out how to test context attributes being recorded and they weren't being recorded because I was in the situation above.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss