cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Kassanke" <kassanke.n...@gmx.de>
Subject Re: xsp resulting in empty xml doc and the error ComponentSelector could not find the component for hint [serverpages] in core.log
Date Mon, 17 Mar 2003 13:20:04 GMT
Delis, Christopher E. wrote:
> why don't you logically split up the queries?  you can always
> aggregate the results of many into one resulting xml file...
>

Dear Christopher,

may be that is the soltuion, the problem is that I am not very familiar at
this level of modeling with XSP. If I got that right you suggest the
following.

the original XSP has the following structure:

<page>
    <metadata>
            <general>

            </general>
            <technical>

            </technical>

            <!-- several other sections, all filled with queries  -->
    </metadata>
</page>

Does logically splitup mean, I can have several XSP files, such as the
following?

The first main XSP

<page>
    <metadata>
            <!-- results of metadatageneral.xsp here included -->
           <!-- results of metadatatechnical.xsp here included -->
    </metadata>

Is this possible? I am sorry if this sounds a bit dumb, but the problem is
really that I am not familiar with this kind of technique. A hint on where
to find additional documentation on this issue would be great.

Thanks,
Stephan
</page>



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org


Mime
View raw message