Hi Wilson
I had a similar problem,.
Solution exist but is not so elegant but can help until Hippo released
new version of their JSP toolkit
=======================================
<c:set var="dochref" value="/content/site/index.xml" scope="request" />
<c:import url="dasl_get_resource.jspx" var="daslget" scope="page" />
<c:set value="${repository.fetchCollection['/'][daslget][true].documents}"
var="menudoc"/>
<c:if test="${ not empty menudoc }">
... Here You can do whatever You whant...
but access it as zero based
${menudoc[0].content.document.title}
I would also like if there is solution to fetch document wih
fetcDocument to some var
<c:set var="doc" value="${repository.fetchDocument[href].content}" />
and then just test
<c:if test="${ not empty doc}">
that could be Fine.
Hope this help.
Denis Balog
HintTech
On Mon, Jul 21, 2008 at 1:16 PM, Ard Schrijvers
<[EMAIL PROTECTED]> wrote:
>
>> Hi Bart,
>>
>> Thanks for your reply. Let me know when it's available.
>
> Releases are announced on this list :-)
>
> -Ard
>
>>
>> Regards,
>>
>> Wilson
>>
>>
>> 2008/7/21 Bart van der Schans <[EMAIL PROTECTED]>:
>>
>> > Hi Wilson,
>> >
>> > This will be fixed in the next release. Instead of a NPE it
>> will throw
>> > a DocumentNotFoundException which you can check for.
>> >
>> > We hope to release the new version of the Hippo Site Toolkit
>> > (including an update of the Hippo Repository Java Adapter)
>> today or in the next few days.
>> >
>> > Regards,
>> > Bart
>> >
>> >
>> >
>> >
>> > Wilson de Paula Pedro Junior wrote:
>> >
>> >> Hi,
>> >>
>> >> Is there a way in a JSP to check if a specific document
>> exists in the
>> >> repository returning a boolean value?
>> >> I'm using now the fetchDocument to check but if it doesn't exist I
>> >> get an object which is not null but throws a nullpointer
>> when I try
>> >> to display on screen.
>> >>
>> >> Thanks!
>> >>
>> >> Wilson
>> >> ********************************************
>> >> Hippocms-dev: Hippo CMS development public mailinglist
>> >>
>> >> Searchable archives can be found at:
>> >> MarkMail: http://hippocms-dev.markmail.org
>> >> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>> >>
>> >>
>> >
>> > --
>> > Hippo B.V. - Amsterdam
>> > Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
>> >
>> > Hippo USA Inc. - San Francisco
>> > 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
>> > -----------------------------------------------------------------
>> > http://www.onehippo.com - [EMAIL PROTECTED]
>> > -----------------------------------------------------------------
>> > ********************************************
>> > Hippocms-dev: Hippo CMS development public mailinglist
>> >
>> > Searchable archives can be found at:
>> > MarkMail: http://hippocms-dev.markmail.org
>> > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>> >
>> >
>> ********************************************
>> Hippocms-dev: Hippo CMS development public mailinglist
>>
>> Searchable archives can be found at:
>> MarkMail: http://hippocms-dev.markmail.org
>> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>>
>>
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
>
> Searchable archives can be found at:
> MarkMail: http://hippocms-dev.markmail.org
> Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
>
>
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
