Angelo Turetta wrote:
I'm a would-be user, evaluating lenya for a site possibly going online
later this fall. I know the Open Source way of doing things is "if
something doesn't work for you, fix-it", but I frankly cannot get up to
the knowledge required to debug the things I'm reporting in this
message. I hope my contribution as a tester is of some value to the team.
Thanks for your report!
I guess some problems were caused by recent changes to the repository layer.
I'll try to track them down asap and send an answer.
-- Andreas
I think this is a time where one of the developers should try a basic
lenya-1.4.x setup (preferably on a clean machine, not their dev
machine), and fix the handful show-stoppers that must really just be
small mistakes/omissions in some past commit.
My tests are run on Windows XP SP2, java -version:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
I just 'svn update' both cocoon-2.1.x and lenya-1.4.x, and then 'build
clean' followed by 'build'. The build for lenya fails with:
BUILD FAILED
D:\Java\apache\lenya-1.4.x\src\targets\webapp-build.xml:69: Unable to
delete file
D:\Java\apache\lenya-1.4.x\build\lenya\webapp\WEB-INF\cocoon.xconf.ant_patch
(already reported on this list) which can be avoided with the attached
build.patch
Once built, here is the first problem: some jar need to be copied from
cocoon-2.1.x/lib/endorsed into build/lenya/webapp/lib/endorsed (already
reported on the list). This is a change brought in from the latest
cocoon, should be coded in some of the src/targets/*.xml files.
Start lenya with lenya.bat. At the default page, I choose New
Publication and named it 'test', using 'default' as a template. Log in
as editor.
In the authoring page, click on 'Document type examples', and watch a
wonderful 'Invalid byte 2 of 3-byte UTF-8 sequence' error. I've found
the cause of the problem: every page that has non-ASCII chars in the
meta information fails almost every operation.
Ok, back to the index. Go to site map. Note that 'Features' and
'Document Type Examples' cannot be selected because of the previous
problem. Select Home, it's available in 'en' and 'de' languages. Go to
'de', select File/Remove Language Version, confirm and you'll be back on
the english Overview, but the available languages has not changed.
Well, do Workflow/Submit on the home page for both english and german.
Then login as a reviewer and try to publish the home page. Publish
Complete Subtree (which should publish all the languages) will fail
with: The source
[lenya://lenya/pubs/test/content/authoring/index/index_de.xml] does not
exist! OK, publish only the english home page (the first time I got
another error, but selecting another node then back to the home just
worked)
Well, let's test adding a new document. File/New XHTML Document (english
language, ID:test Navigation_title: Test, Sibling after). Good. You are
now in Authoring, and you see the default page text. Select Edit/With
Kupu. Change any text, choose save. Surprise! the default page comes
back and you lose your changes. OK, quit and then select Edit/With BXE.
This works better, Save&quit. Workflow/Submit (if you followed me, you
are still logged in as a reviewer), then Workflow/Publish.
Now select File/New Language Version (Navigation_Title: German Test).
The english text is correctly copied to the new german page. Edit/With
BXE (change anything), File/Save&Quit. Uh oh, why cannot I 'Submit' this
page? Publish will enable by default the 'complete subtree' option,
let's try it. Verify with 'LIVE': Ooops, "The requested document is not
available for language: 'de'". Note that from now on, no further
revision of the 'test' document can be published, in any language.
I think that's enough for tonight.
Please beware I value your work to the maximum extent, and I know 1.4 is
the unstable- devel- version which is not guaranteed to work, but it's
really not possible to evaluate 1.4 in this condition, and I think this
is bad because it's not possible to get a good release unless a lot of
people try to use it in the early stages.
In my opinion, it's hard to get a wide real-world test if the minimum
basic set of functionality (repeated submit/publish, for example) is not
working at least since Alpha1 (included).
Best regards,
Angelo Turetta
------------------------------------------------------------------------
Index: src/targets/publets-build.xml
===================================================================
--- src/targets/publets-build.xml (revision 233325)
+++ src/targets/publets-build.xml (working copy)
@@ -50,7 +50,7 @@
<isfalse value="${cocoon.xconf.isEqual}"/>
</condition>
<antcall target="copy-cocoon.xconf"/>
- <delete file="${build.webapp}/WEB-INF/cocoon.xconf.ant_patch"/>
+ <delete file="${build.webapp}/WEB-INF/cocoon.xconf.ant_patch"
failonerror="false"/>
</target>
<target name="deploy-publets"
Index: src/targets/webapp-build.xml
===================================================================
--- src/targets/webapp-build.xml (revision 233325)
+++ src/targets/webapp-build.xml (working copy)
@@ -66,7 +66,7 @@
<isfalse value="${cocoon.xconf.isEqual}"/>
</condition>
<antcall target="copy-cocoon.xconf"/>
- <delete file="${build.webapp}/WEB-INF/cocoon.xconf.ant_patch"/>
+ <delete file="${build.webapp}/WEB-INF/cocoon.xconf.ant_patch"
failonerror="false"/>
<!-- Patch web.xml -->
<!--
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
