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.
| Summary: | Bean properties changes not propagated to <jsp:set/getProperty .../> completion | ||
|---|---|---|---|
| Product: | javaee | Reporter: | Marek Fukala <mfukala> |
| Component: | JSP | Assignee: | Marek Fukala <mfukala> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | blocker | ||
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
correction of the point #8: repeat #4 => the new property is NOT offered. may be related to the parsing.api vs jasper parser synchronization issue - see my comments in issue #158716 This is almost for sure a consequence of the mentioned issue #158716 *** This issue has been marked as a duplicate of 158716 *** |
1) create a bean with a property 2) in a JSP page declare the bean: <jsp:useBean class="beans.Bean" id="b"/> 3) use it: <jsp:setProperty name="b" property="|" value="test"/> 4) if you invoke the completion on the pipe position, the bean properties are not offered 5) restart netbeans 6) repeat #4 => property is offered 7) add a new property to the bean 8) repeat #4 => the new property is offered. The problem doesn't look like a parser failure since the expression language completion properly offers the modified bean propertis just after you do that. Try to type: {b.|} + CC after step #2 or #7.