0.9.1 component property hierarchy not detected

[giannidoe]

I just switched from 0.8.2 to 0.9.1 and the component hierarchy no
longer seems to be detected.

e.g. in the following code snippet "roofFacing.answerChoice" reports
"Wicket ID not found in HTML/Markup":

DropDownChoice<SurveyAnswerChoice> roofFacingChoice = new
DropDownChoice<SurveyAnswerChoice>(
"roofFacing.answerChoice", answersModel,
answerRenderer);
qualifyForm.add(new
FormFieldFeedbackBorder("roofFacingBorder").add(roofFacingChoice));

This was working in 0.8.2.

Also I see the gutter navigation has been removed between components,
this is a real shame as I found it to be one of the most useful
featured.

> - Removed: Show components in gutter of markup and java file
> (introduced in 0.7.0). Sorry, not longer possible with enhancement 50.

Any chance this will return?

[Minas Manthos]

Please create a issue for not recognized Border hierarchy. Some sample
code/markup to reproduce would be nice.

Building hierarchy is very extensive because there are many ways how
components get added. Before 0.9, WicketForge only scanned for
Components, no matter where they added. Now it has to find all add's
in correct context... thats extensive. For gutter navigation this
means, that for every candidate-'element' in source I have to parse
markup/java. I will look into it again if I can do this with some
caching...

How ever... Doesn't Ctrl+click (or Ctrl+B, F4) fit your needs to jump
from java to markup?

[Phillip Ashworth]

On 02/mar/2011, at 12.56, Minas Manthos wrote:

> Please create a issue for not recognized Border hierarchy. Some sample
> code/markup to reproduce would be nice.
>
> Building hierarchy is very extensive because there are many ways how
> components get added. Before 0.9, WicketForge only scanned for
> Components, no matter where they added. Now it has to find all add's
> in correct context... thats extensive. For gutter navigation this
> means, that for every candidate-'element' in source I have to parse
> markup/java. I will look into it again if I can do this with some
> caching...
>
> How ever... Doesn't Ctrl+click (or Ctrl+B, F4) fit your needs to jump
> from java to markup?

Now I'm aware of that option, yes it does :)
I had always used the gutter icons previously to go directly to the component... should have read the documentation properly.

I'll submit an issue for the Border hierarchy.
Many thanks.