Child Pages/Sort Pages tags

I have been happily using the ChildPages tag and the JSTL c:forEach tag, now that I've tried to integrate the SortPages tag things are falling apart.

My code is as follows:

If I remove the sortPages tag this code works perfectly, I've also changed the id for the sortPages to sortedChildPages and it still doesn't work. The issue appears to be with the output of the childPages tag. I'm getting the following stacktrace:

I've tried stepping through the sortPages tag in debug and this is happening on the setInput method.

Any thoughts?

Thanks,

Mark.

My immediate thought is that the input parameter isn't supposed to get a List. Maybe it should get the id of a list? That is, removed the ${}. Just a guess.

After checking the manual, I must admit I don't think my guess is correct... I see that you've basically followed their example exactly, and yet it fails? Strange.

What happens if you, instead of using a property as root for the child pages, instead use a site node? As in the example:

There is no difference. It fails in exactly the same way, when trying to set the 'input' property in SortPagesTag - failing with the conversion to type List!

In the source (for my version, which I think is 2.9.8.2), the input parameter is handled like this:

Which finally boils down to:

To me it looks like that the input should be an expression, ${...something...}, (like you have) that should evaluate to a List. And that would mean that childPages is not a List... Which is bizarre, but who knows? If you use the code below (not tested), what does it say?

Jaric,

I total agreed with your deductions and had come to the same conclusion, and the code in my version 2.9.7.3 is the same.

When I output the debug message I get:

As should be expected!

Mark.

The stock IG Sitemap component at http://www.infoglue.org/Developers/Components/Component_detail_page/?contentId=539 uses sortPages. Does that one work for you (i.e. do you still have it in your repositories somewhere)? If it does, then you can try to find the difference between your component and that one, otherwise it looks like something broke at some point, I guess.

Jaric,

This is really strange, the Site Map demo does work, when I trap the setInput method on the SortPagesTag the value being passed in is an expression to be evaluated, i.e.
When I debug my own code the input property is being set with the already evaluated expression, i.e.
Any thoughts?

Mark.

Do you have anything in the beginning of your page that affects how expressions are treated? Some JSP directive or something?

That sorted it! I'm not certain what I had before but I overwrote the taglib declarations and everything else at the top of the component and it now works.

Thanks, I knew it would be something simple, I just didn't know what.

Mark.

Great!