Hi
When an XSP page that contains class definitions is generated we get in the
"Tomcat work" directory a series of class files: 1 for the XSP and 1 for
each class defined in the XSP page.
e.g. if I have a page called MY_PAGE.xsp with classes Class1 and Class2
defined within it then:
MY_PAGE_xsp.class
MY_PAGE_xsp$Class1.class
MY_PAGE_xsp$Class2.class
will get generated.
I would like to know what advantage there is to moving these classes (Class1
and Class2) to a jar file and refering to them there. Obviously if these
classes are only used on one page then I can see no immediate advantage.
However when many pages are generated with the same classes defined on each
(perhaps because of the application of a logicsheet) then the
{page_name}_xsp${class_name}.class will be generated many times for what
will be identical code. How will efficiency be affected? Is it purely a
memory problem? Or are there issues of time to load classes etc.?
This has come to light from using the ESQL logicsheet (for example) in
Cocoon2. It generates EsqlConnection and EsqlQuery classes for each page
that uses the ESQL logicsheet. BTW This isn't a critism of ESQL -- just an
observation! :-) (in fact I think this may have been resolved in the lastest
ESQL.)
Cheers
Pete
---
Cognos, London, UK
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
