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: | No code completion for partially typed p-namespace property names | ||
---|---|---|---|
Product: | javaee | Reporter: | Andrei Badea <abadea> |
Component: | Spring | Assignee: | Martin Fousek <marfous> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jayashri, samaresh |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | 129165, 129272 | ||
Bug Blocks: |
Description
Andrei Badea
2008-03-03 15:43:17 UTC
This isn't a problem in the code completion, but in the XML infrastructure. Given <bean id="foo" p:cache| class="FooAbstractController"/> the XML lexer returns an error token starting at the class attribute. The corresponding Element doesn't contain a class attribute, so the code completion can't resolve the bean class name. Filed issue 129165. This would have low impact, since users usually put p-namespace properties after the class name. But, unfortunately, for <bean id="foo" class="FooAbstractController" p: /> <bean id="bar" class="SomeOtherClass"/> the attribute computation seems to "leak" into the bar bean, so the foo bean appears to have the SomeOtherClass class. Filed issue 129272 for the attribute computation. Hopefully it will be fixed for 6.1. moving opened issues from TM <= 6.1 to TM=Dev Andrei, Now that 129272 is fixed, can you close this ? No, since issue 129165 still needs to be fixed. The original scenario is still reproducible. Target milestone revised to future in accordance with the milestone of its dependency issue # 129165. Taking over Alexey's JSF and Spring issues. Issue #129165 is still valid and blocking this issue and I'm afraid that it will not be fixed in nb71 as well. Changing the target milestone to Next and let see what about XML issue then. Blocking issue #129165 still valid so I'm targeting this one to the next release. 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 |