RE: Contribution: MultiPartPostAction & FilePartGenerator

Geoff Howard <cocoon <at> leverageweb.com>
2003-06-30 23:00:28 GMT

Thank you for this work and your interest in contributing. I
hope this is the first of many.
Here are my thoughts after a quick look:
The MultiPartPostAction seems unnecessary. What do you
gain by placing a copy of the uploaded file which is already in
the ObjectModel under the Request object directly in the
ObjectModel?
The FilePartGenerator OTOH seems useful (I don't think the existing
StreamGenerator will do this). As noted above, the action is
not needed in the equation - you can just get the FilePart right
out of the Request in the Generator. Then, I don't see the
reason behind the overloaded getInputSource() - the FilePart
is designed to allow polymorphism there - just cast the Request.get()
to FilePart and call FilePart.getInputStream() on it. If you find
I'm correct, could you look at refactoring this and submitting a
patch to Bugzilla? I'd be more than willing to help with anything
that doesn't make sense to you.
As far as I can see, none of the HSSF stuff is useful without the
GnumericWriter which is GPL. The last I heard someone was working
directly in the poi project on a Gnumeric "generator" from Excel
that could then go straight in cvs. Unless that is now not a
project that will ever happen for some reason, I'd be against
introducing even the hooks for a GPL version that would just get
replaced later. If you want to keep this available for others to
contribute and benefit, I'd recommend approaching cocoondev which
can by its nature accomodate GPL.

http://www.ctg.albany.edu

Derek Hohls <DHohls <at> csir.co.za>
2003-07-01 06:11:56 GMT

Joerg
I was browsing the white paper referred to; in
http://www.ctg.albany.edu/publications/reports/xml?chapter=9
it mentions that XML files are "connected" to XSL files
by placing links to the stylesheets at the top of the XML
files. It then goes on to say:
"This significantly simplifies content management because it
enables you to make changes to only one content file and
make no changes to the stylesheets because the content
is totally separated from the presentation.
Figure 8 illustrates how these XML/XSL transformations occur
within the Cocoon publishing framework. "
This is a little misleading and underplays the true value
added by Cocoon in completely separating content from
presentation - the "connections" happen in the sitemap;
there is no need to specify stylesheets in your XML files;
as soon as you do this you are implicitly mixing content
and presentation.
If you are able, I think some changes would help
clarify the situation.
Regards
Derek
>>> joerg.heinicke <at> gmx.de 30/06/2003 10:03:04 >>>

http://www.ctg.albany.edu

Joerg Heinicke <joerg.heinicke <at> gmx.de>
2003-07-01 06:36:59 GMT

Hello Derek,
yes, that's obviously misleading. But I'm not related to this page.
After the mention on this list last week I only asked them to be listed
on Cocoon's Livesites page and Jim Costello sent me this mail below. I
added the link in the CVS and forwarded this mail, especially because of
the impressive figures.
Now the report: It's the typical Cocoon 1.x handling using processing
instructions. But I don't know if they wrote their own component
handling processing instructions or if the report is outdated or simlpy
wrong. The X-Cocoon header clearly states that they use Cocoon 2.0.4,
but he also wrote (in the mail below) that they still have Cocoon 1.x in
use for a part of their homepage.
I'm cc-ing Jim Costello, so he can read and clarify your objections.
Regards,
Joerg
Derek Hohls wrote:
> Joerg
>
> I was browsing the white paper referred to; in
> http://www.ctg.albany.edu/publications/reports/xml?chapter=9
> it mentions that XML files are "connected" to XSL files
> by placing links to the stylesheets at the top of the XML
> files. It then goes on to say:
>
> "This significantly simplifies content management because it
> enables you to make changes to only one content file and

RuntimeException : The sitemap is null

Hi folks,
I'm currently performing some load tests on the following configuration
:
cocoon 2.0.4
resin 2.1.9
SUN JDK 1.4.003
Linux (RH 9)
After 5-10 minutes, I got the following "well known" RuntimeException :
The sitemap is null.
I've seen on the cocoon-dev archive that a bug report has been recently
posted about this, but I just would like to know :
- if this bug is planned to be fixed in the 2.0.4 or in the 2.1 ?
- if there are some workaround to avoid this problem ? Any hint (change
JVM, system, servlet engine) ?
Many thanks for your help
Gabriel

Mount vs File for logicsheets inside cocoon.xconf

Derek Hohls <DHohls <at> csir.co.za>
2003-07-01 09:06:51 GMT

I'd appreciate a brief explanation (or pointer
to such) as to why:
<parameter name="href" value="file:///my-path-to-cocoon/logic/my-taglib.xsl"/>
works (placed inside the <builtin-logicsheet> section of
cocoon.xconf)
and why:
<parameter name="href" value="resource://logic/my-taglib.xsl"/>
gives an error (the file could not be located). I have seen both
forms of referencing used in examples, but cannot get the latter
to work... can someone suggest why??
Related follow on:
IF I can get the resource:// to work, then it seems there are
other issues, Vadim writes:
http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=102374809216737&w=2
"Ok, after looking into sources, I can say that if logicsheet is built-in
or not is not important. It is important how it is referenced from the
XSP or cocoon.xconf.
If it is referenced as a file then it is checked for modification using
File java API. If not (like resource://) - then it is not checked."
So - using resource:// is better from a development/maintenance

esql:getXXX - wrong diagnostics?

Dmitry Diskin <dda <at> ic.ru>
2003-07-01 09:30:35 GMT

Hello
I have been struggling with the following problem for a while: if I
specify non-existing column name in <esql:get-int column="wrong_column"
/></xsp:attribute> tag, I get the following error message:
org.apache.cocoon.ProcessingException: Exception in
ServerPagesGenerator.generate(): java.lang.RuntimeException: Error
executing statement: select something from somewhere :
java.sql.SQLException: Invalid column name
I think that is misleading, since the error is not in SQL, but in my XSp
text. It was very hard to find it out.
Regards,
Dmitry.