RE: xsp resulting in empty xml doc and the error ComponentSelecto r could not find the component for hint [serverpages] in core.log

["Delis, Christopher E." <ce...@uillinois.edu>]

why don't you logically split up the queries?  you can always aggregate the
results of many into one resulting xml file...


-----Original Message-----
From: Stephan Kassanke
To: cocoon-users@xml.apache.org
Sent: 3/15/03 11:08 AM
Subject: Re: xsp resulting in empty xml doc and the error ComponentSelector
could not find the component for hint [serverpages] in core.log

Marco Rolappe wrote:
> hi stephan,
>
> you might also want to take a look at tomcat's logs, if nothing
> appears in cocoon's logs. the 'empty' page is most probably because
> of 'buggy' error-handling (which I think is fixed by now).
>

Dear Marco,

thanks, your hint revealed the problem:

The XSP file is rather large, generating a lot of tags and there seems
to be
a limit on the size of class files (64 kb). So, the problem is, that the
xsp
is simply becoming too large. I searched the web already for a solution
or
workaround and what I found said that there is actually no workaround.
The FAQ states:
----------------
This is due to a fundamental limitation in the Java specifications,
which
means that XSP pages (which turn XML into Java code) cannot be very
large.
We suggest that you put all your data for your page (not logic, just
data),
into a database, and extract it from the database using the esql taglib.
There are a number of free Java databases out there on the web.

The problem is that I already did that, so I am stuck here. The xsp only
consists of  esql statements querying the database and constructing the
page, though it generates a lot of tags.

The XSP file is structured like the following excerpt:



...<esql:connection>
  <esql:pool>dblom_pool</esql:pool>


     <!-- Hypertree URL abfragen-->
    <esql:execute-query>
      <esql:query>
       Select ht_url from network where
network.PK_Network=<xsp:expr>getNetwork()</xsp:expr>
      </esql:query>
      <esql:results>
        <esql:row-results>
   <ht_url><esql:get-string column="ht_url"/></ht_url>
  </esql:row-results>
   </esql:results>
 </esql:execute-query>



  <!-- METADATA -->

  <metadata>
    <PK_Lom><xsp-request:get-parameter name="lom_id"/></PK_Lom>
 <PK_General><xsp-request:get-parameter name="general_id"/></PK_General>
    <learningobjectkey><xsp-request:get-parameter
name="id"/></learningobjectkey>
 <currentlanguage></currentlanguage>

    <!-- METADATA GENERAL -->

    <general>

        <!-- Indentifier -->
        <esql:execute-query>
          <esql:query>
            SELECT identifier
            FROM general
   where PK_General = <xsp-request:get-parameter name="general_id"/>
   and PK_Lom=<xsp-request:get-parameter name="lom_id"/>

          </esql:query>
          <esql:results>
            <esql:row-results>
              <identifier>
                <item><esql:get-string column="indentifier"/></item>
              </identifier>
            </esql:row-results>
          </esql:results>
          <esql:no-results>
            <identifier><i18n:text>empty</i18n:text></identifier>
          </esql:no-results>




etc. I am not a programmer, so may be you can give me a hint how to
"split"
the xsp in order to generate smaller class files. I really need in the
end a
complete XML file, so genrating a subset of it is not an option.

Any help is appreciated,

Thanks.

Stephan











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

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

Re: xsp resulting in empty xml doc and the error ComponentSelector could not find the component for hint [serverpages] in core.log

[Stephan Kassanke <ka...@gmx.de>]

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