Pedro,
Thank you for your feedback. This question has been answered many times
before and maybe we should put an FAQ out there for it. We cannot have an
XSD for HiveMind because we allow users to specify their own <schema>s to
define their own configuration syntax. You might get farther by not saying
something sucks (sorry I take offense, but I'm on the HiveMind team).
Constructive criticism is always more welcome than slamming. Is there a
particular part of the documentation that you feels needs some attention?
James
On 5/18/06, Pedro Garcia <[EMAIL PROTECTED]> wrote:
Hi, I'm writing to complain about the difficulties that I am facing with
hivemind integration.
I think it should exist a XSD specific for configuring hivemind with
tapestry, because hivemind documentation sucks.
And one more thing, I know that you guys already know, but tapestry
documentation has a mistake
<implementation service-id="tapestry.multipart.MultipartDecoder">
<create-instance class="
org.apache.tapestry.multipart.MultipartDecoderImpl,maxSize=-1"
model="threaded" />
</implementation>
I spent hours to find the documentation had this mistake and that the
service had changed to
<implementation service-id="tapestry.multipart.ServletMultipartDecoder
">
<create-instance class="
org.apache.tapestry.multipart.MultipartDecoderImpl,maxSize=-1"
model="threaded" />
</implementation>
The mistake is in "tapestry-4.0.1-docs
/tapestry/ComponentReference/Upload.html"
thanks for your attention,
Pedro
