> Class1 and Class2 in both then: > MY_PAGE1_xsp.class > MY_PAGE1_xsp$Class1.class > MY_PAGE1_xsp$Class2.class > and > MY_PAGE2_xsp.class > MY_PAGE2_xsp$Class1.class > MY_PAGE2_xsp$Class2.class > will get generated. Obviously *Class1.class and *Class2.class are identical > for each page. > > > The implication of this (I'm sure) must be inefficiency. > > > Questions: > ---------- > Does having many repeated (e.g. helper classes) provide a run-time > inefficiency (i.e. in cases where that code -- for example Class1 and Class2 > -- could reside in a library)?
The trick is not to have a helper class for each xsp page but one for all using the specific (probably static) methods. I guess that's what you talking about - but again... this has already been done and became a common practice. Have a look at the sources... -- Torsten --------------------------------------------------------------------- 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]>
