Re: Eclipse, Tomcat and Sysdeo Plugin
Hi, I can't tell you why you get this error, but i can tell you how we are debugging cocoon enabled web applications in a similar environment as yours: We are running eclipse, cocoon-2.0.4, tomcat-4.1.18 on solaris and linux. We run eclipse on a PC-frontend and we always start the tomcat server with the startup scripts. When debuging whichever webapp (including cocoon) we set the JAVA_OPTS as follows: -server -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000 Then we (re)start the tomcat server as usual with startup.sh or startup.bat. Please note, that we set the JAVA_OPTS, not the CATALINA_OPTS for this, although the docs at the tomcat site state something else (that does not work for us) On eclipse we set up a remote debugging session on port 8000. This works perfectly! It should also work, when the tomcat server is running locally. regards, hussayn Helmut Tammen wrote: Hi, I try to use the combination of Eclipse, Tomcat and the Sysdeo Plugin to debug the cocoon source in Eclipse. This doesnt work (error message when trying to access any Cocoon resource at the end). When I start Tomcat via the startup.bat everything works fine. My environment: Windows 2000 Eclipse 2.1 (Beta) JDK 1.4.1_02 Tomcat 4.0.6 Sysdeo plugin for Eclipse 2.1 (Beta) Cocoon 2.1-dev Ive also tried JDK 1.4.0, Tomcat 4.1.18 and Cocoon 2.0.4 in various combinations with no success. All the Xerces and Xalan libs are replaced with the ones from Cocoon in the directories [JAVA_HOME]/jre/lib/endorsed, [CATALINA_HOME]/common/endorsed and in [ECLIPSE_HOME]/plugins/org.apache.xerces_4.0.7 (probably not necessary because not in the classpath of my webapp) Does anyone have an idea whats going wrong here? Thanks in advance Helmut ERROR (2003-03-20) 08:33.54:103 [access] (Unknown-URI) Unknown- thread/CocoonServlet: Cocoon got an Exception while trying to close stream. java.io.IOException: The stream has been closed at org.apache.catalina.connector.ResponseStream.flush(ResponseStream.java:237) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1145) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) FATAL_E (2003-03-20) 08:33.57:218 [access] (/cocoon21/samples/welcome) HttpProcessor[8080][4]/CocoonServlet: The Cocoon engine failed to process the request.
Re: use gmane.org instead of subscribing to the cocoon-lists ???
Hy, Martin; Thank you for this tip. I will give it an instant try. It's a funny coincidence, that we talked about newsgroups instead of mailing-lists some days ago... regards, hussayn Martin Holz wrote: Hello, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] writes: Hy, all; * Is it possible to post mails to the cocoon-lists without subscribing to them ? * Is it possible to subscribe to the cocoon-lists without actually receiving emails from them ? Don't know, if this is possible if you are directly communicate with the list, but it is possible, if you go through gmane.org. Make news.gmane.org your (secondary) news server and subscribe to gmane.text.xml.cocoon.user. Now you can read and post to this list using the standard news methods. If you post to a list for the first time, you will have to answer a authorization mail. There are some more filters against spamming the mailing lists, but they don't get in the way of normal postings. Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: use gmane.org instead of subscribing to the cocoon-lists ???
Hy, Martin; It worked; Thank you very much for this really usefull hint ;-) regards, hussayn SAXESS - Hussayn Dabbous wrote: Hy, Martin; Thank you for this tip. I will give it an instant try. It's a funny coincidence, that we talked about newsgroups instead of mailing-lists some days ago... regards, hussayn Martin Holz wrote: Hello, SAXESS - Hussayn Dabbous [EMAIL PROTECTED] writes: Hy, all; * Is it possible to post mails to the cocoon-lists without subscribing to them ? * Is it possible to subscribe to the cocoon-lists without actually receiving emails from them ? Don't know, if this is possible if you are directly communicate with the list, but it is possible, if you go through gmane.org. Make news.gmane.org your (secondary) news server and subscribe to gmane.text.xml.cocoon.user. Now you can read and post to this list using the standard news methods. If you post to a list for the first time, you will have to answer a authorization mail. There are some more filters against spamming the mailing lists, but they don't get in the way of normal postings. Martin - 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]
Re: [heads-up] wiki abuse: your advice please
what about simply reusing the userlist from the cocoon-dev, cocoon-user, cocoon-doc mailing lists and allow write access only to these registered users ? That should make life easy... I think, authors, who are NOT members of one of the mailinglists, cant be serious authors, because there is no feedback chain ... as a small benefit we even could associate the emailadress to all the wikiauthors, who have NO wiki name ;-) regards, hussayn Niclas Hedhman wrote: On Friday 14 March 2003 21:46, Steven Noels wrote: Your thoughts, please: what kind of policy would you come up with, or are willing to live up to? IP address blocking is no good. A lot of people have dynamic IPs (either by dial-up or ADSL). I favour a simple self-registration, with email address as user name (so that the community can bombard the intruder with hate mail - just kidding). Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BeginnerSimpleWebappOrganisation strange evolution ...
Hy, Derek;
I did a major revision of the Wiki-page.
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation
Maybe you take a little time and review my changes.
My big concern here is, that within the original verison
of the page this stuff was already explained correctly.
The errors have been added later. Now i have removed them again.
Ok, the benefit we got from this intermezzo is another
review of the page, which hopefully clearifies some
additional points ;-)
regards, Hussayn
p.s.: apologize for my conclusion, about you beeing
a windows user. Indeed i have added a few words to make
clear, why i want absolute pathes here. That was not
explained at all in the original text ;-)
Derek Hohls wrote:
Hussayn
yes, it does! (and I am both a windows user - local
machine and UNIX user - for the production site)
can you add these gems to the relevant wiki pages?!
derek
[EMAIL PROTECTED] 20/02/2003 04:15:00
Hy, Derek;
upps...
From your question may i conclude, that you are a windows user?
I am not very familiar with the windows file syntax, but i
think, the translation is something like:
src=work/sitemap.xmap == $cocoonroot\work\sitemap.xmap
src=D://work/sitemap.xmap == D://work/sitemap.xmap
By specifying an absolute path, i can separate my project sources
physically from the cocoon-distrib. Does this answer your question ?
regards, hussayn
Derek Hohls wrote:
Hussayn
$cocoonroot/work/sitemap.xmap - I understand, but
where exactly is
/work/sitemap.xmap ??? and why do you want it?
Derek
[EMAIL PROTECTED] 20/02/2003 03:22:54
Hy, Derek;
If you specify a relative src it will be resolved relative to the
current sitemap. If you specify an absolute source, it will be
resolved as is ==
suppose you put a submount into the rottsitemap, then:
src=work/sitemap.xmap == $cocoonroot/work/sitemap.xmap
src=/work/sitemap.xmap == /work/sitemap.xmap
If this is NOT correct, then i really missunderstood something ;-)
regards, hussayn
Derek Hohls wrote:
Hussayn
From the Cocoon docs site:
http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html
map:match pattern=faq/*
map:mount uri-prefix=faq
check-reload=no
src=faq/sitemap.xmap/
/map:match
The src attribute is where the sub-sitemap is located.
If it ends in a slash sitemap.xmap is appended to find the sitemap,
otherwise the src value is used. A check-reload attribute can be used
to determine if the modification date of the sub-sitemap file
should be
checked.
The uri-prefix is the part that should be removed from the request
URI.
The engine will correctly check for a trailing slash (which you may
write,
of course). If in the example above faq/cocoon is requested, faq/
is removed from the URI and cocoon is passed to the sub-sitemap
which is loaded from faq/sitemap.xmap.
So - the Cocoon docs writer seems to be saying that src DOES NOT NEED
a leading '/' (of course, I am not sure if one is permissible??)
I think we need clarity from one of the gurus and for both sites
to
be updated with this detailed clarification !
Derek
[EMAIL PROTECTED] 20/02/2003 01:59:54
Hy;
I noticed a slight modification in
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation
which from my understanding has introduced two severe errors!
As i don't exactly know, why these changes have been made,
i want to ask if i missunderstood something. Here is, what i
find suspect:
1.) Advanced Issue: separating your work folder from cocoon
...
map:pipeline
map:match pattern=work/**
map:mount check-reload=yes
reload-method=synchron
src=work/sitemap.xmap
uri-prefix=work/
/map:match
/map:pipeline
This snippet i found in the doc. In my eyes this does NOT
what is explained in the doc. From my understanding the
source must be declared as absolute path as follows:
src=/work/sitemap.xmap
Why has the leading slash been deleted in the doc?
2.) Advanced issue: Setting up a generic mount point outside of Cocoon
I found a similar modification:
src=work/{1}/sitemap.xmap
Shouldn't it be:
src=/work/{1}/sitemap.xmap
I post this email only, because i don't understand, why these mods
have
been made. From the history i can see, these mods have been made by
two
different persons... hmm...
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL
Re: BeginnerSimpleWebappOrganisation strange evolution
Hy, Derek; Derek Hohls wrote: I think the page is fine - if we add any more we will need to make 2 pages! otherwise the simple beginners will get put off... I was close to split this page into two this morning: basic_issue + advanced_issue I simply didn't do it, because i was disturbed by a phone call ;-) i was thinking we also need a central index page which ties all the bits and pieces together and gives some indication of reading order, level of complexity etc. (the wiki is easy to add to, but hard to see where everything fits in..) What do you mean by central index page ? Can you explain in a little more detail ? hussayn [EMAIL PROTECTED] 21/02/2003 11:12:22 Hy, Derek; I did a major revision of the Wiki-page. http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation Maybe you take a little time and review my changes. My big concern here is, that within the original verison of the page this stuff was already explained correctly. The errors have been added later. Now i have removed them again. Ok, the benefit we got from this intermezzo is another review of the page, which hopefully clearifies some additional points ;-) regards, Hussayn p.s.: apologize for my conclusion, about you beeing a windows user. Indeed i have added a few words to make clear, why i want absolute pathes here. That was not explained at all in the original text ;-) Derek Hohls wrote: Hussayn yes, it does! (and I am both a windows user - local machine and UNIX user - for the production site) can you add these gems to the relevant wiki pages?! derek [EMAIL PROTECTED] 20/02/2003 04:15:00 Hy, Derek; upps... From your question may i conclude, that you are a windows user? I am not very familiar with the windows file syntax, but i think, the translation is something like: src=work/sitemap.xmap == $cocoonroot\work\sitemap.xmap src=D://work/sitemap.xmap == D://work/sitemap.xmap By specifying an absolute path, i can separate my project sources physically from the cocoon-distrib. Does this answer your question ? regards, hussayn Derek Hohls wrote: Hussayn $cocoonroot/work/sitemap.xmap - I understand, but where exactly is /work/sitemap.xmap ??? and why do you want it? Derek [EMAIL PROTECTED] 20/02/2003 03:22:54 Hy, Derek; If you specify a relative src it will be resolved relative to the current sitemap. If you specify an absolute source, it will be resolved as is == suppose you put a submount into the rottsitemap, then: src=work/sitemap.xmap == $cocoonroot/work/sitemap.xmap src=/work/sitemap.xmap == /work/sitemap.xmap If this is NOT correct, then i really missunderstood something ;-) regards, hussayn Derek Hohls wrote: Hussayn From the Cocoon docs site: http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html map:match pattern=faq/* map:mount uri-prefix=faq check-reload=no src=faq/sitemap.xmap/ /map:match The src attribute is where the sub-sitemap is located. If it ends in a slash sitemap.xmap is appended to find the sitemap, otherwise the src value is used. A check-reload attribute can be used to determine if the modification date of the sub-sitemap file should be checked. The uri-prefix is the part that should be removed from the request URI. The engine will correctly check for a trailing slash (which you may write, of course). If in the example above faq/cocoon is requested, faq/ is removed from the URI and cocoon is passed to the sub-sitemap which is loaded from faq/sitemap.xmap. So - the Cocoon docs writer seems to be saying that src DOES NOT NEED a leading '/' (of course, I am not sure if one is permissible??) I think we need clarity from one of the gurus and for both sites to be updated with this detailed clarification ! Derek [EMAIL PROTECTED] 20/02/2003 01:59:54 Hy; I noticed a slight modification in http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation which from my understanding has introduced two severe errors! As i don't exactly know, why these changes have been made, i want to ask if i missunderstood something. Here is, what i find suspect: 1.) Advanced Issue: separating your work folder from cocoon ... map:pipeline map:match pattern=work/** map:mount check-reload=yes reload-method=synchron src=work/sitemap.xmap uri-prefix=work/ /map:match /map:pipeline This snippet i found in the
Re: BeginnerSimpleWebappOrganisation strange evolution
Do you think, the CocoonCompetenceCenter main page http://wiki.cocoondev.org/Wiki.jsp?page=CocoonCompetenceCenter can fullfill the role as central index ? CocoonCompetenceCenter beginners ... advanced ... experts ... I think, this can be done without disturbing the current wiki organisation too much: * Simply reorg the existing CCC main page as sketched above. * Then create a new CCC-beginners index-page with the content of the current CCC main page. * Then start to link other pages from the Wiki into the advanced-CCC / expert-CCC index-pages. Or do you think of an index spanning over the whole Wiki ? Hussayn Derek Hohls wrote: A central index = a guide to the guides... perhaps in a nested hierachy showing where all the topics and subtopics fit together. [EMAIL PROTECTED] 21/02/2003 03:58:40 Hy, Derek; Derek Hohls wrote: I think the page is fine - if we add any more we will need to make 2 pages! otherwise the simple beginners will get put off... I was close to split this page into two this morning: basic_issue + advanced_issue I simply didn't do it, because i was disturbed by a phone call ;-) i was thinking we also need a central index page which ties all the bits and pieces together and gives some indication of reading order, level of complexity etc. (the wiki is easy to add to, but hard to see where everything fits in..) What do you mean by central index page ? Can you explain in a little more detail ? hussayn [EMAIL PROTECTED] 21/02/2003 11:12:22 Hy, Derek; I did a major revision of the Wiki-page. http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation Maybe you take a little time and review my changes. My big concern here is, that within the original verison of the page this stuff was already explained correctly. The errors have been added later. Now i have removed them again. Ok, the benefit we got from this intermezzo is another review of the page, which hopefully clearifies some additional points ;-) regards, Hussayn p.s.: apologize for my conclusion, about you beeing a windows user. Indeed i have added a few words to make clear, why i want absolute pathes here. That was not explained at all in the original text ;-) Derek Hohls wrote: Hussayn yes, it does! (and I am both a windows user - local machine and UNIX user - for the production site) can you add these gems to the relevant wiki pages?! derek [EMAIL PROTECTED] 20/02/2003 04:15:00 Hy, Derek; upps... From your question may i conclude, that you are a windows user? I am not very familiar with the windows file syntax, but i think, the translation is something like: src=work/sitemap.xmap == $cocoonroot\work\sitemap.xmap src=D://work/sitemap.xmap == D://work/sitemap.xmap By specifying an absolute path, i can separate my project sources physically from the cocoon-distrib. Does this answer your question ? regards, hussayn Derek Hohls wrote: Hussayn $cocoonroot/work/sitemap.xmap - I understand, but where exactly is /work/sitemap.xmap ??? and why do you want it? Derek [EMAIL PROTECTED] 20/02/2003 03:22:54 Hy, Derek; If you specify a relative src it will be resolved relative to the current sitemap. If you specify an absolute source, it will be resolved as is == suppose you put a submount into the rottsitemap, then: src=work/sitemap.xmap == $cocoonroot/work/sitemap.xmap src=/work/sitemap.xmap == /work/sitemap.xmap If this is NOT correct, then i really missunderstood something ;-) regards, hussayn Derek Hohls wrote: Hussayn From the Cocoon docs site: http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html map:match pattern=faq/* map:mount uri-prefix=faq check-reload=no src=faq/sitemap.xmap/ /map:match The src attribute is where the sub-sitemap is located. If it ends in a slash sitemap.xmap is appended to find the sitemap, otherwise the src value is used. A check-reload attribute can be used to determine if the modification date of the sub-sitemap file should be checked. The uri-prefix is the part that should be removed from the request URI. The engine will correctly check for a trailing slash (which you may write, of course). If in the example above faq/cocoon is requested, faq/ is removed from the URI and cocoon is passed to the sub-sitemap which is loaded from faq/sitemap.xmap. So - the Cocoon docs writer seems to be saying that src DOES NOT NEED a leading '/' (of course, I am not sure if one
Re: BeginnerSimpleWebappOrganisation strange evolution
Hy;
thank you for this contrib. I have updated the page again and
introduced the pattern concept. Although my original intention
was to give the beginners a simple cookbook at hand, where they
just can take the snippets by cut'n paste and get their first
transformation to work. Now the whole thing is near to the original
documentation ;-) seems as if all documentation tends to become
as explicit as possible...
anyway, thank you.
Lets hope, others will find the page usefull as it is now.
By the way, NOW i have separated the page into two ;-)
regards, hussayn
Brandes, Wayne wrote:
The BeginnerSimpleWebappOrganisation page is much clearer now, IMO.
One observation I would make, as an advanced beginner: becasue the use
of wildcards hasn't been explained in detail I think that statements
like When the interpreter hits a '*' or a '**' in the pattern, it will
automatically resolve the actual value into local /sitemap-parameters/
named {1}, {2} as described in the following example: can be
misinterpreted to mean that the {1} refers to one * and the {2} refers
to two *'s, rather than to order in which the variables were set. I
have been confused by that in other tutorials.
Thanks for your work on this
Wayne
-Original Message-
*From:* Derek Hohls [mailto:[EMAIL PROTECTED]]
*Sent:* Friday, February 21, 2003 9:21 AM
*To:* [EMAIL PROTECTED]
*Subject:* Re: BeginnerSimpleWebappOrganisation strange evolution
A central index = a guide to the guides...
perhaps in a nested hierachy showing where
all the topics and subtopics fit together.
[EMAIL PROTECTED] 21/02/2003 03:58:40
Hy, Derek;
Derek Hohls wrote:
I think the page is fine - if we add any more
we will need to make 2 pages! otherwise the
simple beginners will get put off...
I was close to split this page into two this morning:
basic_issue + advanced_issue
I simply didn't do it, because i was disturbed by a
phone call ;-)
i was thinking we also need a central index page
which ties all the bits and pieces together and
gives some indication of reading order, level of
complexity etc. (the wiki is easy to add to, but
hard to see where everything fits in..)
What do you mean by central index page ?
Can you explain in a little more detail ?
hussayn
[EMAIL PROTECTED] 21/02/2003 11:12:22
Hy, Derek;
I did a major revision of the Wiki-page.
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation
Maybe you take a little time and review my changes.
My big concern here is, that within the original verison
of the page this stuff was already explained correctly.
The errors have been added later. Now i have removed them again.
Ok, the benefit we got from this intermezzo is another
review of the page, which hopefully clearifies some
additional points ;-)
regards, Hussayn
p.s.: apologize for my conclusion, about you beeing
a windows user. Indeed i have added a few words to make
clear, why i want absolute pathes here. That was not
explained at all in the original text ;-)
Derek Hohls wrote:
Hussayn
yes, it does! (and I am both a windows user - local
machine and UNIX user - for the production site)
can you add these gems to the relevant wiki pages?!
derek
[EMAIL PROTECTED] 20/02/2003 04:15:00
Hy, Derek;
upps...
From your question may i conclude, that you are a windows user?
I am not very familiar with the windows file syntax, but i
think, the translation is something like:
src=work/sitemap.xmap == $cocoonroot\work\sitemap.xmap
src=D://work/sitemap.xmap == D://work/sitemap.xmap
By specifying an absolute path, i can separate my project sources
physically from the cocoon-distrib. Does this answer your
question ?
regards, hussayn
Derek Hohls wrote:
Hussayn
$cocoonroot/work/sitemap.xmap - I understand, but
where exactly is
/work/sitemap.xmap ??? and why do you want it?
Derek
[EMAIL PROTECTED] 20/02/2003 03:22:54
Hy, Derek;
If you specify a relative src it will be resolved relative
to the
current sitemap. If you specify an absolute source, it will be
resolved as is ==
suppose you put a submount into the rottsitemap, then:
src=work/sitemap.xmap == $cocoonroot/work/sitemap.xmap
src=/work/sitemap.xmap == /work/sitemap.xmap
If this is NOT correct, then i really missunderstood
something ;-)
regards, hussayn
BeginnerSimpleWebappOrganisation strange evolution ...
Hy;
I noticed a slight modification in
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation
which from my understanding has introduced two severe errors!
As i don't exactly know, why these changes have been made,
i want to ask if i missunderstood something. Here is, what i
find suspect:
1.) Advanced Issue: separating your work folder from cocoon
...
map:pipeline
map:match pattern=work/**
map:mount check-reload=yes
reload-method=synchron
src=work/sitemap.xmap
uri-prefix=work/
/map:match
/map:pipeline
This snippet i found in the doc. In my eyes this does NOT
what is explained in the doc. From my understanding the
source must be declared as absolute path as follows:
src=/work/sitemap.xmap
Why has the leading slash been deleted in the doc?
2.) Advanced issue: Setting up a generic mount point outside of Cocoon
I found a similar modification:
src=work/{1}/sitemap.xmap
Shouldn't it be:
src=/work/{1}/sitemap.xmap
I post this email only, because i don't understand, why these mods have
been made. From the history i can see, these mods have been made by two
different persons... hmm...
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
is tomcat a bad choice? (Re: alternative to tomcat?)
I followed the other thread with interest. I didn't find a single argument, why i should continue using tomcat. Can anyone convince me, that my choice to use tomcat was a good choice after all ??? From the ongoing discussion and from the fact, that jetty is now included in cocoon what shall i conclude ? I'm planning to use apache/tomcat/cocoon in a production environment. But wouldn't it be more appropriate to use apache/jetty/cocoon in the future ? And finally, wouldn't it be wise to add a cocoon with Jetty page in CocoonCompetenceCenter ? ;-) regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: BeginnerSimpleWebappOrganisation strange evolution ...
Hy, Derek;
If you specify a relative src it will be resolved relative to the
current sitemap. If you specify an absolute source, it will be
resolved as is ==
suppose you put a submount into the rottsitemap, then:
src=work/sitemap.xmap == $cocoonroot/work/sitemap.xmap
src=/work/sitemap.xmap == /work/sitemap.xmap
If this is NOT correct, then i really missunderstood something ;-)
regards, hussayn
Derek Hohls wrote:
Hussayn
From the Cocoon docs site:
http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html
map:match pattern=faq/*
map:mount uri-prefix=faq
check-reload=no
src=faq/sitemap.xmap/
/map:match
The src attribute is where the sub-sitemap is located.
If it ends in a slash sitemap.xmap is appended to find the sitemap,
otherwise the src value is used. A check-reload attribute can be used
to determine if the modification date of the sub-sitemap file should be
checked.
The uri-prefix is the part that should be removed from the request URI.
The engine will correctly check for a trailing slash (which you may
write,
of course). If in the example above faq/cocoon is requested, faq/
is removed from the URI and cocoon is passed to the sub-sitemap
which is loaded from faq/sitemap.xmap.
So - the Cocoon docs writer seems to be saying that src DOES NOT NEED
a leading '/' (of course, I am not sure if one is permissible??)
I think we need clarity from one of the gurus and for both sites
to
be updated with this detailed clarification !
Derek
[EMAIL PROTECTED] 20/02/2003 01:59:54
Hy;
I noticed a slight modification in
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation
which from my understanding has introduced two severe errors!
As i don't exactly know, why these changes have been made,
i want to ask if i missunderstood something. Here is, what i
find suspect:
1.) Advanced Issue: separating your work folder from cocoon
...
map:pipeline
map:match pattern=work/**
map:mount check-reload=yes
reload-method=synchron
src=work/sitemap.xmap
uri-prefix=work/
/map:match
/map:pipeline
This snippet i found in the doc. In my eyes this does NOT
what is explained in the doc. From my understanding the
source must be declared as absolute path as follows:
src=/work/sitemap.xmap
Why has the leading slash been deleted in the doc?
2.) Advanced issue: Setting up a generic mount point outside of Cocoon
I found a similar modification:
src=work/{1}/sitemap.xmap
Shouldn't it be:
src=/work/{1}/sitemap.xmap
I post this email only, because i don't understand, why these mods have
been made. From the history i can see, these mods have been made by
two
different persons... hmm...
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: BeginnerSimpleWebappOrganisation strange evolution ...
Hy, Derek;
upps...
From your question may i conclude, that you are a windows user?
I am not very familiar with the windows file syntax, but i
think, the translation is something like:
src=work/sitemap.xmap == $cocoonroot\work\sitemap.xmap
src=D://work/sitemap.xmap == D://work/sitemap.xmap
By specifying an absolute path, i can separate my project sources
physically from the cocoon-distrib. Does this answer your question ?
regards, hussayn
Derek Hohls wrote:
Hussayn
$cocoonroot/work/sitemap.xmap - I understand, but
where exactly is
/work/sitemap.xmap ??? and why do you want it?
Derek
[EMAIL PROTECTED] 20/02/2003 03:22:54
Hy, Derek;
If you specify a relative src it will be resolved relative to the
current sitemap. If you specify an absolute source, it will be
resolved as is ==
suppose you put a submount into the rottsitemap, then:
src=work/sitemap.xmap == $cocoonroot/work/sitemap.xmap
src=/work/sitemap.xmap == /work/sitemap.xmap
If this is NOT correct, then i really missunderstood something ;-)
regards, hussayn
Derek Hohls wrote:
Hussayn
From the Cocoon docs site:
http://xml.apache.org/cocoon/userdocs/concepts/sitemap.html
map:match pattern=faq/*
map:mount uri-prefix=faq
check-reload=no
src=faq/sitemap.xmap/
/map:match
The src attribute is where the sub-sitemap is located.
If it ends in a slash sitemap.xmap is appended to find the sitemap,
otherwise the src value is used. A check-reload attribute can be used
to determine if the modification date of the sub-sitemap file should be
checked.
The uri-prefix is the part that should be removed from the request URI.
The engine will correctly check for a trailing slash (which you may
write,
of course). If in the example above faq/cocoon is requested, faq/
is removed from the URI and cocoon is passed to the sub-sitemap
which is loaded from faq/sitemap.xmap.
So - the Cocoon docs writer seems to be saying that src DOES NOT NEED
a leading '/' (of course, I am not sure if one is permissible??)
I think we need clarity from one of the gurus and for both sites
to
be updated with this detailed clarification !
Derek
[EMAIL PROTECTED] 20/02/2003 01:59:54
Hy;
I noticed a slight modification in
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation
which from my understanding has introduced two severe errors!
As i don't exactly know, why these changes have been made,
i want to ask if i missunderstood something. Here is, what i
find suspect:
1.) Advanced Issue: separating your work folder from cocoon
...
map:pipeline
map:match pattern=work/**
map:mount check-reload=yes
reload-method=synchron
src=work/sitemap.xmap
uri-prefix=work/
/map:match
/map:pipeline
This snippet i found in the doc. In my eyes this does NOT
what is explained in the doc. From my understanding the
source must be declared as absolute path as follows:
src=/work/sitemap.xmap
Why has the leading slash been deleted in the doc?
2.) Advanced issue: Setting up a generic mount point outside of Cocoon
I found a similar modification:
src=work/{1}/sitemap.xmap
Shouldn't it be:
src=/work/{1}/sitemap.xmap
I post this email only, because i don't understand, why these mods have
been made. From the history i can see, these mods have been made by
two
different persons... hmm...
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This message has been scanned for viruses and dangerous content by
*MailScanner* http://www.mailscanner.info/, and is believed to be clean.
The CSIR exercises no editorial control over E-mail messages and/or
attachments thereto/links referred to therein originating in the
organisation and the views in this message/attachments thereto are
therefore not necessarily those of the CSIR and/or its employees.
The sender of this e-mail is, moreover, in terms of the CSIR's Conditions
of Service, subject to compliance with the CSIR's internal E-mail and
Internet Policy.
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been
dynamic sitemap dependent on response mimetype ?
Hy; Can i overcome following problem: Within a match i read or aggregate some XML-sources from another server, e.g.: map:match pattern=mypage map:generate src=http://myserver/mypage.xml/ map:transform src=mypage.xsl/ map:serialize type = html/ /map:match Now suppose, myserver does not send back the content of mypage.xml, but another HTTP-200 response containing an HTML message with some informal message in it, like site is currenlty down, or something similar. What happens in the above case is, that my style sheet simply gets something very different from what it expected. Possibly even the response is not well formed... In fact getting the wrong mimetype is an error, but what i received is still valuable and i want to send this back instead of the expected xml-data: What i search is a possibility to simply skip the transformation if i get something else, than say plain/xml as mimetype back from myserver. Instead doing the transformation, i want directly send back what i gathered from myserver so far. How can this be done ? And going one step further what can i do in this case: map:match pattern=mypage map:generate src=http://myserver/mypage/ ... /map:match Now lets say, i don't know at all, what mimetype myserver will return, but i wanted to do something, if mimetype is plain/xml and simply return the data as is in any other case... How could i achieve this ? Or is there something, that is so obvious and i simply don't see it ? regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dynamic sitemap dependent on response mimetype ?
Hy, Geoff; Thank's for the info. I hoped there was a better integrated solution. Ok, then i have to think about what that means for my current project in more detail. Anyway i think, your answer saved me from doing unnecessary experiments... regards, Hussayn Geoff Howard wrote: Sounds like you're asking to dynamically affect the pipeline setup after the generator is called which is by design impossible. If so, you'll need a component that executes before pipeline setup (which therefore can alter pipeline setup) which limits you to actions, matchers, and selectors. (did i miss one?) Most likely, you're going to want an action. Geoff At 06:20 AM 2/18/2003, you wrote: Hy; Can i overcome following problem: Within a match i read or aggregate some XML-sources from another server, e.g.: map:match pattern=mypage map:generate src=http://myserver/mypage.xml/ map:transform src=mypage.xsl/ map:serialize type = html/ /map:match Now suppose, myserver does not send back the content of mypage.xml, but another HTTP-200 response containing an HTML message with some informal message in it, like site is currenlty down, or something similar. What happens in the above case is, that my style sheet simply gets something very different from what it expected. Possibly even the response is not well formed... In fact getting the wrong mimetype is an error, but what i received is still valuable and i want to send this back instead of the expected xml-data: What i search is a possibility to simply skip the transformation if i get something else, than say plain/xml as mimetype back from myserver. Instead doing the transformation, i want directly send back what i gathered from myserver so far. How can this be done ? And going one step further what can i do in this case: map:match pattern=mypage map:generate src=http://myserver/mypage/ ... /map:match Now lets say, i don't know at all, what mimetype myserver will return, but i wanted to do something, if mimetype is plain/xml and simply return the data as is in any other case... How could i achieve this ? Or is there something, that is so obvious and i simply don't see it ? regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dynamic sitemap dependent on response mimetype ?
Hy; My original problem came up, when i started to gather data from another site under authentication. This site happened to send back a login form instead of the expected XML-data stream uppon first request. Unfortuntely the site did NOT send back a HTTP-401 from which i could setup some error handling. It would have been great, when this login form could be processed instead of the original datastream and handed over to my browser instead of the expected data. But the only hint i have here is the mime type i get back. And even this gets broken, if the errorpage would also be an XML-document. OK, the whole things needs a major rethought anyway... thanks again for your support ;-) hussayn Geoff Howard wrote: At 10:23 AM 2/18/2003, you wrote: Anyway i think, your answer saved me from doing unnecessary experiments... regards, Hussayn Good - that's why I wrote that despite not really having time to understand fully what you were trying to do. ;) Geoff Geoff Howard wrote: Sounds like you're asking to dynamically affect the pipeline setup after the generator is called which is by design impossible. If so, you'll need a component that executes before pipeline setup (which therefore can alter pipeline setup) which limits you to actions, matchers, and selectors. (did i miss one?) Most likely, you're going to want an action. Geoff At 06:20 AM 2/18/2003, you wrote: Hy; Can i overcome following problem: Within a match i read or aggregate some XML-sources from another server, e.g.: map:match pattern=mypage map:generate src=http://myserver/mypage.xml/ map:transform src=mypage.xsl/ map:serialize type = html/ /map:match Now suppose, myserver does not send back the content of mypage.xml, but another HTTP-200 response containing an HTML message with some informal message in it, like site is currenlty down, or something similar. What happens in the above case is, that my style sheet simply gets something very different from what it expected. Possibly even the response is not well formed... In fact getting the wrong mimetype is an error, but what i received is still valuable and i want to send this back instead of the expected xml-data: What i search is a possibility to simply skip the transformation if i get something else, than say plain/xml as mimetype back from myserver. Instead doing the transformation, i want directly send back what i gathered from myserver so far. How can this be done ? And going one step further what can i do in this case: map:match pattern=mypage map:generate src=http://myserver/mypage/ ... /map:match Now lets say, i don't know at all, what mimetype myserver will return, but i wanted to do something, if mimetype is plain/xml and simply return the data as is in any other case... How could i achieve this ? Or is there something, that is so obvious and i simply don't see it ? regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : Scheduler with cocoon
1.) There are some java -packages around, that mimic cron. wasn't there a cron component in the avalon-excalibur framework ??? You might write something like an action, which opens a runtime-thread, which would organise the rest. shouldn't be a big deal if you really need it. or you write a servlet, that does it and let it autostart on container startup ... 2.) another thought: If you want the user to change something easily, you will provide a config file. (probably). You still could use cron (if you stay onlunux/unix) and generate the cron scripts ;-) But cron scripts are very easy to understand and is it really worthwhile to make something else ??? Except of course you are NOT running on unix and/or you MUST provide platform independence, then i would reconsider 1.) above .. regards, hussayn Xavier RODRIGUEZ wrote: But I would like something to be integrated into cocoon, in this way the final user will easily change the hours for example... Someone tells me about wyona cms (http://www.wyona.org) that integrates a scheduler ... I'm now probing this solution Thanks || -Original Message- || From: Niclas Hedhman [mailto:[EMAIL PROTECTED]] || Sent: Friday, February 14, 2003 7:11 AM || To: [EMAIL PROTECTED] || Subject: Re: Scheduler with cocoon || || || On Friday 14 February 2003 05:17, Guenther Schmidt wrote: || provided you're using Linix, you might want to create a || cron job a'la wget || http://url that triggers your pipeline. || || If you are not Linux expert, but using it more casually, the || above can seem a || bit cryptic. || || cron is a time scheduler in Linux, which executes shell || scripts according to || settings in a table. Most Linux Distros has a default cron || configuration that || is pretty is to use. For RedHat, create a sheel script and || place it in || /etc/cron.daily, and it will execute once a day (think it is || in the middle of || night). || || The script should look like this; || || #!/bin/sh || # || || wget http://www.mydomain.com/cocoon/theResource || || and I think you need to set the x flag on the script file, such as; || || chmod +x mydailyrequest.sh || || || That should be crystal clear. || || This is just a fallback possibility if nobody comes up || with a better || answer. || || I think this is a perfect solution, as cron is extremely reliable. || || Guenther (turning 35 in 2.5 hours) || || Niclas , turned 35 29680 hours ago ;o) New yardstick for age? || || - || Please check that your question has not already been answered in the || FAQ before posting. http://xml.apache.org/cocoon/faq/index.html || || To unsubscribe, e-mail: [EMAIL PROTECTED] || For additional commands, e-mail: [EMAIL PROTECTED] || - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
anyone got websphere running on solaris???
Hy, i know this is absolutely off topic, but maybe there is someone who could help me: i want to run my app on websphere-4.0.4. the problem is (currently) not how to get cocoon running on it, but how to get websphere running with LDAP-authentification. Anyone near cologne, who can help ? i'll pay for it ;-) regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Meeting in cologne!
Hy, Thorsten. thanks for your offer. Great, i think some help is really needed, let's get into touch offlist. Here is a first proposal for agenda,timeshedule,location... There is still some commitment needed for talks, or other contribs ;-) the aim of the meeting -- Preliminary i see this as a possibillity to get together, see what others are doing whith cocoon, brainstorming, generating new ideas, ... The meeting could be setup as a one day workshop. The topics are not yet completely specified, but there is a promising preliminary commitment available(see below). The results shall be published in an convenient form, possibly in this list as summary, or if applicable as a collection of ppt's, docs, whatever on the Wiki? ... possible types of activities freely collected from all inputs i got so far: I workshop activities - basics (history, future, concepts) - cocoon for admins (setup, maintenacne) - best practices II information exchange - use of cocoon in business apps - use cases What do you use Cocoon for? III open issues with cocoon - Howto to improve cocoon documentation First proposal for an agenda: - begin around 9:30 in the morning ? 1 warm up (30 minutes) - who are you? - What are you doing with cocoon? (very short!) 2 Hot spot (Mathew,Carsten, 30 minutes (is this enough time?)) Mathew or Carsten will try to attend the meeting. Mathew agreed on preparing a talk about Sunshine Portal. 3 talk about one or two active projects (2*30 minutes, N.N) getting insight into the project and how cocoon is used. content is mainly up to the talker ... 4 questions and answers (60 minutes) much like within the cocoon-users list, but face to face ... Break for lunch 5 brain storming ( ??? ) what would help us to get more out of cocoon ? 6 ??? possible dates for the meeting -- Various constraints apply. From what i got so far, we should setup a meeting on monday, or friday, but not during Karneval. Currently the time interval is moving towards the first two weeks in March, hence we keep with 4 possible days ;-) any further restrictions apply? location, further organisational issues --- In my company i can arrange a room for about 10 persons. It would be great if someone had a beamer at hand. I can supply a huuuge whiteboard. For lunch i can arrange something near the company location (10 minutes to walk) And after the meeting we'll see then ... If anyone wants to stay overnight, just give me a note. I can arrange something for you. I have setup a mailinglist for this meeting issues to keep the cocoon-users list free from this stuff. i'm still not fully convinced, if this was a good idea... So far there are 13 interested people on the list: [EMAIL PROTECTED] If others are also interested, please send me a note. Ill put you on the list too. But if the list keeps on growing as it does so far, we will need to look for another location ;-) regards, Hussayn Scherler, Thorsten wrote: Hi list, hi Hussayn, how many people want to come to cologne so far? When should the event take place? Where should it be? How can we help you organise it? Any proposals for the agenda so far? ...I volunteer for organisation. King regards Thorsten Mit freundlichem Gruss, Thorsten Scherler Marketing / Telefonmarketing Weidmüller GmbH Co. P.O. Box 2807 33058 Paderborn Tel.:+ 49 - 5252-960-350 Fax:+ 49 - 5252-960-116 eMail: [EMAIL PROTECTED] http://www.weidmueller.de - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies : problem with sitemap.xmap
You can make your life very easy by simply adding this to the beginning of your sitemap: + begin of sitemap - ?xml version=1.0? map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:components map:generators default=file/ map:transformers default=xslt/ map:readers default=resource/ map:serializers default=html/ map:matchers default=wildcard/ /map:components !-- now your own stuff as you expressed it in your email ... -- + end of sitemap --- By this you get all comoponents from $rootsitemap ready at hand in your subsitemap. Dont bother with component definitions until you really need to express something different from the rootsitemap ;-) regards, hussayn Lionel Crine wrote: you need a reader : map:readers default=resource map:reader logger=sitemap.reader.resource name=resource pool-max=32 src=org.apache.cocoon.reading.ResourceReader/ /map:readers in the components see the sitemaAt 09:55 13/02/2003 +0100, you wrote: hi i got a problem with cocoon 2 i would like to serve static page so i write sitemap.xmap like this - map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:components map:generators map:generator name=serverpages src=org.apache.cocoon.generation.ServerPagesGenerator/ /map:generators map:serializers map:serializer name=xml mime-type=text/xml src=org.apache.cocoon.serialization.XMLSerializer/ /map:serializers map:matchers map:matcher name=wildcard src=org.apache.cocoon.matching.WildcardURIMatcher/ /map:matchers /map:components map:pipelines map:pipeline map:match pattern=index.html map:read src=index.html mime-type=text/html/ /map:match /map:pipeline /map:pipelines /map:sitemap but it doesnt work in browser i always obtaint this message Cocoon 2 - Internal server error type fatal message Language Exception description org.apache.cocoon.ProcessingException: Language Exception: org.apache.cocoon.components.language.LanguageException: Error compiling sitemap_xmap: Line 241, column 54: '}' expected Line 63, column 11: class org.apache.cocoon.www.sitemap_xmap should be declared abstract; it does not define method process(org.apache.cocoon.environment.Environment, org.apache.cocoon.components.pipeline.StreamPipeline, org.apache.cocoon.components.pipeline.EventPipeline) in class org.apache.cocoon.sitemap.AbstractSitemap Line 0, column 0: 2 errors sender org.apache.cocoon.servlet.CocoonServlet source Cocoon servlet stack-trace org.apache.cocoon.ProcessingException: Language Exception: org.apache.cocoon.components.language.LanguageException: Error compiling sitemap_xmap: Line 241, column 54: '}' expected Line 63, column 11: class org.apache.cocoon.www.sitemap_xmap should be declared abstract; it does not define method process(org.apache.cocoon.environment.Environment, org.apache.cocoon.components.pipeline.StreamPipeline, org.apache.cocoon.components.pipeline.EventPipeline) in class org.apache.cocoon.sitemap.AbstractSitemap Line 0, column 0: 2 errors at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createR esource(ProgramGeneratorImpl.java:360) at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.load(Pr ogramGeneratorImpl.java:312) at org.apache.cocoon.sitemap.Handler.run(Handler.java:267) at java.lang.Thread.run(Thread.java:536) Caused by: org.apache.cocoon.components.language.LanguageException: Error compiling sitemap_xmap: Line 241, column 54: '}' expected Line 63, column 11: class org.apache.cocoon.www.sitemap_xmap should be declared abstract; it does not define method process(org.apache.cocoon.environment.Environment, org.apache.cocoon.components.pipeline.StreamPipeline, org.apache.cocoon.components.pipeline.EventPipeline) in class org.apache.cocoon.sitemap.AbstractSitemap Line 0, column 0: 2 errors at org.apache.cocoon.components.language.programming.java.JavaLanguage.compile( JavaLanguage.java:243) at org.apache.cocoon.components.language.programming.CompiledProgrammingLanguag e.load(CompiledProgrammingLanguage.java:207) at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.generat eResource(ProgramGeneratorImpl.java:417) at org.apache.cocoon.components.language.generator.ProgramGeneratorImpl.createR esource(ProgramGeneratorImpl.java:353) ... 3 more org.apache.cocoon.components.language.LanguageException: Error compiling sitemap_xmap: Line 241, column 54: '}' expected Line 63, column 11: class org.apache.cocoon.www.sitemap_xmap should be declared abstract; it does not define method process(org.apache.cocoon.environment.Environment,
Re: newbies : problem with sitemap.xmap
you have an error in you components def. try this I assume, your index.html contains html (not xml) right ? map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:components map:generators default=file/ map:transformers default=xslt/ map:readers default=resource/ map:serializers default=html/ map:matchers default=wildcard/ /map:components map:pipelines map:pipeline map:match pattern=index.html map:read src=index.html/ /map:match /map:pipeline /map:pipelines /map:sitemap or try this, if your index-file has xml code in it: i propose then, you rename the file index.html to index.xml to be explicit: map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:components map:generators default=file/ map:transformers default=xslt/ map:readers default=resource/ map:serializers default=html/ map:matchers default=wildcard/ /map:components map:pipelines map:pipeline map:match pattern=index.html== you ask for this map:generate src=index.xml/ == but you process this ;-) map:serialize/ /map:match /map:pipeline /map:pipelines /map:sitemap === or make it explicit (best practice): map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:components map:generators default=file/ map:transformers default=xslt/ map:readers default=resource/ map:serializers default=html/ map:matchers default=wildcard/ /map:components map:pipelines map:pipeline map:match pattern=index.html map:generate type=file src=index.xml/ map:serialize type=html / /map:match /map:pipeline /map:pipelines /map:sitemap regards, hussayn arnaud wrote: i dont understand (im thinking im stupid) it doesnt work too (im using tomcat 4.1.12, jdk sun 1.4.1, cocoon 2.0.4) i make a lot of changes (thanks lionel hussayn) but i got always the same message in tomcat stdout Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 java.lang.RuntimeException: Fatal: Errors in XSLT transformation: Warning: File jar:file:/C:/etango/tomcat/webapps/cocoonsamples/WEB-INF/lib/cocoo n-2.0.4.jar!/org/apache/cocoon/components/language/markup/sitemap/java/sitem ap.xsl; Line 1817; Column 34; [Logicsheet processor] Attribute 'type' missing in dynamic tag map:match Fatal: Ach?vement dirigU de la feuille de style at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3170) at java.lang.Thread.run(Thread.java:536) last sitemap.xmap - map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:components map:components map:generators default=file/ map:generator name=html src=org.apache.cocoon.generation.HTMLGenerator/ map:transformers default=xslt/ map:readers default=resource/ map:serializers default=html/ map:matchers default=wildcard/ /map:components /map:components map:pipelines map:pipeline map:match pattern=index.html map:generate type=html src=index.html/ map:serialize/ /map:match /map:pipeline /map:pipelines /map:sitemap - -Message d'origine- De : Lionel Crine [mailto:[EMAIL PROTECTED]] Envoye : jeudi 13 fevrier 2003 10:21 A : [EMAIL PROTECTED] Objet : RE: newbies : problem with sitemap.xmap in my sitemap i write that : map:generator name=html src=org.apache.cocoon.generation.HTMLGenerator/ ... map:match pattern=html map:generate type=html src=test.html/ map:serialize/ /map:match It's working fine .. The reader is used for the css, jpg, etc Hope that help At 10:09 13/02/2003 +0100, you wrote: i had it in sitemap.xmap but it doesnt work in catalina stdout i obtaint this -- Starting service Tomcat-Standalone Apache Tomcat/4.1.12-LE-jdk14 java.lang.RuntimeException: Fatal: Errors in XSLT transformation: Warning: File jar:file:/C:/etango/tomcat/webapps/cocoonsamples/WEB-INF/lib/cocoo n-2.0.4.jar!/org/apache/cocoon/components/language/markup/sitemap /java/sitem ap.x sl; Line 1817; Column 34; [Logicsheet processor] Attribute 'type' missing in dynamic tag map:match Fatal: Ach?vement dirigU de la feuille de style at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java :3170) at java.lang.Thread.run(Thread.java:536) - and exactely the same message in browser -Message d'origine- De : Lionel Crine [mailto:[EMAIL PROTECTED]] Envoye : jeudi 13 fevrier 2003
Re: newbies : problem with sitemap.xmap
hmm.
what's the name of your cocoon webapplication ?
is it cocoonsamples ?
or do you have a subdirectory named cocoonsamples
in your cocoon webapp ?
in the latter case try:
http://localhost:8080/cocoon/cocoonsamples/staticpages/index.html
dont like cocoon in your URL ? then look at
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerDefaultContext
regards, hussayn
arnaud wrote:
ok now its work
just one problem
when i request http://localhost:8080/cocoonsamples/staticpages/index.html
i obtain this error in browser (nothing in tomcat stdout)
--
Cocoon 2 - Resource not found
type resource-not-found
message Resource not found
description The requested URI /cocoonsamples/staticpages/index.html was
not found.
sender org.apache.cocoon.servlet.CocoonServlet
source Cocoon servlet
request-uri
/cocoonsamples/staticpages/index.html
path-info
staticpages/index.html
--
but index.html exist in staticpages directory
cocoonsamples +
|
+- staticpages
|
+- WEB-INF +
|
+- classes
any idea ?
--
map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0;
map:components
map:generators
map:generator name=html
src=org.apache.cocoon.generation.HTMLGenerator/
/map:generators
map:transformers default=xslt/
map:serializers default=html/
map:matchers
map:matcher name=referer-match
src=org.apache.cocoon.matching.WildcardHeaderMatcher/
/map:matchers
/map:components
map:pipelines
map:pipeline
map:match type=referer-match pattern=staticpages/*.html
map:generate type=html src=staticpages/{1}.html/
map:serialize/
/map:match
/map:pipeline
/map:pipelines
/map:sitemap
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies : problem with sitemap.xmap
you have something like this in your rootsitemap ?:
map:pipeline
map:match pattern=staticpages/**
map:mount check-reload=yes src=staticpages/{1}/
uri-prefix=staticpages/{1}/
/map:match
/map:pipeline
no more ideas ...
regards, hussayn
arnaud wrote:
-Message d'origine-
De : SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]]
Envoyé : jeudi 13 février 2003 16:25
À : [EMAIL PROTECTED]
Objet : Re: newbies : problem with sitemap.xmap
hmm.
what's the name of your cocoon webapplication ?
is it cocoonsamples ?
yes
webapps +
|
+- cocoonsamples +
or do you have a subdirectory named cocoonsamples
in your cocoon webapp ?
in the latter case try:
http://localhost:8080/cocoon/cocoonsamples/staticpages/index.html
dont like cocoon in your URL ? then look at
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerDefaultContext
regards, hussayn
arnaud wrote:
ok now its work
just one problem
when i request
http://localhost:8080/cocoonsamples/staticpages/index.html
i obtain this error in browser (nothing in tomcat stdout)
--
Cocoon 2 - Resource not found
type resource-not-found
message Resource not found
description The requested URI
/cocoonsamples/staticpages/index.html was
not found.
sender org.apache.cocoon.servlet.CocoonServlet
source Cocoon servlet
request-uri
/cocoonsamples/staticpages/index.html
path-info
staticpages/index.html
--
but index.html exist in staticpages directory
cocoonsamples +
|
+- staticpages
|
+- WEB-INF +
|
+- classes
any idea ?
--
map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0;
map:components
map:generators
map:generator name=html
src=org.apache.cocoon.generation.HTMLGenerator/
/map:generators
map:transformers default=xslt/
map:serializers default=html/
map:matchers
map:matcher name=referer-match
src=org.apache.cocoon.matching.WildcardHeaderMatcher/
/map:matchers
/map:components
map:pipelines
map:pipeline
map:match type=referer-match pattern=staticpages/*.html
map:generate type=html src=staticpages/{1}.html/
map:serialize/
/map:match
/map:pipeline
/map:pipelines
/map:sitemap
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies : problem with sitemap.xmap
ah, i see the problem !!!
its in your sitemap. i assume you have
put a subsitemap in your staticpages directory and use the mount
as in my last email:
map:pipeline
map:match pattern=staticpages/**
map:mount check-reload=yes src=staticpages/{1}/
uri-prefix=staticpages/{1}/
/map:match
/map:pipeline
then use in the staticpages/sitemap.xmap:
...
map:pipelines
map:pipeline
map:match type=referer-match pattern=*.html == here !!!
map:generate type=html src={1}.html/ === and here
map:serialize/
/map:match
/map:pipeline
/map:pipelines
...
SAXESS - Hussayn Dabbous wrote:
you have something like this in your rootsitemap ?:
map:pipeline
map:match pattern=staticpages/**
map:mount check-reload=yes src=staticpages/{1}/
uri-prefix=staticpages/{1}/
/map:match
/map:pipeline
no more ideas ...
regards, hussayn
arnaud wrote:
-Message d'origine-
De : SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]]
Envoyé : jeudi 13 février 2003 16:25
À : [EMAIL PROTECTED]
Objet : Re: newbies : problem with sitemap.xmap
hmm.
what's the name of your cocoon webapplication ?
is it cocoonsamples ?
yes
webapps +
|
+- cocoonsamples +
or do you have a subdirectory named cocoonsamples
in your cocoon webapp ?
in the latter case try:
http://localhost:8080/cocoon/cocoonsamples/staticpages/index.html
dont like cocoon in your URL ? then look at
http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerDefaultContext
regards, hussayn
arnaud wrote:
ok now its work
just one problem
when i request
http://localhost:8080/cocoonsamples/staticpages/index.html
i obtain this error in browser (nothing in tomcat stdout)
--
Cocoon 2 - Resource not found
type resource-not-found
message Resource not found
description The requested URI
/cocoonsamples/staticpages/index.html was
not found.
sender org.apache.cocoon.servlet.CocoonServlet
source Cocoon servlet
request-uri
/cocoonsamples/staticpages/index.html
path-info
staticpages/index.html
--
but index.html exist in staticpages directory
cocoonsamples +
|
+- staticpages
|
+- WEB-INF +
|
+- classes
any idea ?
--
map:sitemap xmlns:map=http://apache.org/cocoon/sitemap/1.0;
map:components
map:generators
map:generator name=html
src=org.apache.cocoon.generation.HTMLGenerator/
/map:generators
map:transformers default=xslt/
map:serializers default=html/
map:matchers
map:matcher name=referer-match
src=org.apache.cocoon.matching.WildcardHeaderMatcher/
/map:matchers
/map:components
map:pipelines
map:pipeline
map:match type=referer-match pattern=staticpages/*.html
map:generate type=html src=staticpages/{1}.html/
map:serialize/
/map:match
/map:pipeline
/map:pipelines
/map:sitemap
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
how can i get static files REALLY been processed by apache ???
Hy; When i setup apache/tomcat/cocoon, i run into following fancy problem. Although what i want seems trivial, but i did not manage to get it done (I might not know the magic command to get round it) Here is the problem: 1.) I want all static files been served by apache, i.e.: *.gif, *.html, *.jpg 2.) I want *ALL* other files be served by cocoon. Now how should i setup mod_jk.conf this doesn't help: IfModule mod_jk.c JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel error JkMount /cocoon cocoon JkMount /cocoon/ cocoon JkMount /cocon/* cocoon /IfModule because it redirects everything to cocoon. But apache shall serve the files mentioned above ... This is not complete (Indeed it can never be complete): IfModule mod_jk.c JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel error JkMount /cocoon/*.xml cocoon JkMount /cocoon/*.jsp cocoon JkMount /cocon/*.foococoon ... /IfModule The list could potentially go down endlessly. There MUST be an obvious solution to this! Anyone can help me here ? regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how can i get static files REALLY been processed by apache ???
Hy; yes, it is a typo... but my problem remains when i correct the typo .. remember: i want to EXCLUDE some files to be forwarded to cocoon, and i didn't find HOW i can get JK to do this... JkMount /cocoon/* cocoon == mount everything JkNoMount *.gif, *.jpg cocoon == but not these while the first directive is well documented, the secnd is what i need, but it doesn't exist. so the question is, how can i get what i want ? ;-( regards, hussayn Ryan Hoegg wrote: SAXESS - Hussayn Dabbous wrote: JkMount /cocon/* cocoon Not sure you meant cocon here... typo in your e-mail or your config? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how can i get static files REALLY been processed by apache ???
hy, thats a very pragmatic idea. i like such approaches. but, hmm... wouldn't this need lots of static links in your pages ??? i mean, you really must point to the myapp-static pages with absolute links. What about maintenance ... ??? seems as if i need to do it in this way, or let cocoon serve everything ;-( Maybe i can plugin something in to apache, or would it be a big problem to get mod_JK do what i want (hacking ...) ??? I'll go and ask the apache-group ... and report back, what i get from there maybe in a Wiki ;-) ? anyway thanks for the tip... regards, hussayn Luca Morandini wrote: Hussayn, I know it is not a smart solution, but it worked for me. 1) Setup mod_jk to redirect everything starting with myapp to Tomcat/Cocoon 2) Setup an alias named myapp-static pointed to a directory containing your static files 3) Use URI like /myapp/dynamic.htlm for dynamic content and URI like /myapp-static/static.html for static content This has the advantage of scaling up well: we have three web-servers serving the static content (/myapp-static/*) and one app-server serving the Cocoon-generated content (/myapp/*). Regards. - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 13, 2003 6:14 PM To: [EMAIL PROTECTED] Subject: how can i get static files REALLY been processed by apache ??? Hy; When i setup apache/tomcat/cocoon, i run into following fancy problem. Although what i want seems trivial, but i did not manage to get it done (I might not know the magic command to get round it) Here is the problem: 1.) I want all static files been served by apache, i.e.: *.gif, *.html, *.jpg 2.) I want *ALL* other files be served by cocoon. Now how should i setup mod_jk.conf this doesn't help: IfModule mod_jk.c JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel error JkMount /cocoon cocoon JkMount /cocoon/ cocoon JkMount /cocon/* cocoon /IfModule because it redirects everything to cocoon. But apache shall serve the files mentioned above ... This is not complete (Indeed it can never be complete): IfModule mod_jk.c JkWorkersFile /etc/httpd/conf/workers.properties JkLogFile /var/log/httpd/mod_jk.log JkLogLevel error JkMount /cocoon/*.xml cocoon JkMount /cocoon/*.jsp cocoon JkMount /cocon/*.foococoon ... /IfModule The list could potentially go down endlessly. There MUST be an obvious solution to this! Anyone can help me here ? regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how can i get static files REALLY been processed by apache ???
Hy, Your last comment sounds very promising. How could i let cocoon throw in the static refs ??? Wouldn't that mean i need cocoon to find the hrefs and do some replacement stuff there. Or how would i do that? any pointers to howto, docs or so ? regards, hussayn Its not that elegant to have references to http://static.example.com/path/to/myhelp.html; but hey, it gets the job done. You can tell cocoon to throw in the static a href for you so it wouldn't be that much work. Chris Wilkes wrote: On Thu, Feb 13, 2003 at 06:14:22PM +0100, SAXESS - Hussayn Dabbous wrote: Here is the problem: 1.) I want all static files been served by apache, i.e.: *.gif, *.html, *.jpg 2.) I want *ALL* other files be served by cocoon. I ran into the same thing and from what I could find out is that you really want a ! operator on the JkMount directive. Now how should i setup mod_jk.conf ... The list could potentially go down endlessly. There MUST be an obvious solution to this! Here's what I did, its just for the images but you could extend it to anything: Create a new website called images.examples.com in your httpd.conf file. Here's some snippets of my Apache2 one: VirtualHost 10.0.0.181 ServerName www.example.com # this all goes to cocoon, but need a docroot anyway DocumentRoot /usr/local/www/data/example # send all these requests to the coyote connector JkMount /* cocoon /VirtualHost VirtualHost 10.0.0.181 ServerName images.example.com DocumentRoot /usr/local/www/data/example /VirtualHost So now when a request comes in you'll have Apache handle it differently for www vs images Its not that elegant to have references to http://static.example.com/path/to/myhelp.html; but hey, it gets the job done. You can tell cocoon to throw in the static a href for you so it wouldn't be that much work. Chris - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how can i get static files REALLY been processed by apache ???
Hey, Lajos;
i see we are all very creative people ;-)
Another cool idea how to get around the problem.
The one thing i am *really* uncomfortable with this
solution is the sequence:
1.) browser requests .img
2.) apache forwards request to tomcat
3.) tomcat forwards request to cocoon
4.) cocoon processes and redirects.
5.) apache redirects
6.) browser calls apache
7.) apache serves the file
hmm. performance again ??
i really would prefer something like:
1.) browser requests .img
2.) apache serves the file
ill need to switch on my hackers-brain-partition ;-)
Thanks again for your answers...
regards, hussayn
Lajos wrote:
Hi Hussayn -
Here is what I do in almost every cocoon app I do:
map:match pattern=styles.css
map:read mime-type=text/css src=/styles/styles.css/
/map:match
map:match pattern=**/styles.css
map:read mime-type=text/css src=/styles/styles.css/
/map:match
map:match pattern=*.gif
map:read mime-type=image/gif src=/images/{1}.gif/
/map:match
map:match pattern=**/*.gif
map:read mime-type=image/gif src=/images/{2}.gif/
/map:match
Any gif or css (and you can do the same for jpg, js, etc.) gets
redirected to the appropriate directory off the webserver root, and
hence is served by Apache. So, under Apache's DocumentRoot I have
/images, /styles, /scripts, etc., etc.
Regards,
Lajos
SAXESS - Hussayn Dabbous wrote:
hy,
thats a very pragmatic idea. i like such approaches.
but, hmm... wouldn't this need lots of static links
in your pages ???
i mean, you really must point to the myapp-static pages
with absolute links. What about maintenance ... ???
seems as if i need to do it in this way, or let cocoon
serve everything ;-(
Maybe i can plugin something in to apache, or would it be
a big problem to get mod_JK do what i want (hacking ...) ???
I'll go and ask the apache-group ...
and report back, what i get from there maybe in a Wiki ;-) ?
anyway thanks for the tip...
regards, hussayn
Luca Morandini wrote:
Hussayn,
I know it is not a smart solution, but it worked for me.
1) Setup mod_jk to redirect everything starting with myapp to
Tomcat/Cocoon
2) Setup an alias named myapp-static pointed to a directory
containing your static files
3) Use URI like /myapp/dynamic.htlm for dynamic content and URI
like /myapp-static/static.html for static content
This has the advantage of scaling up well: we have three web-servers
serving the static content (/myapp-static/*) and one
app-server serving the Cocoon-generated content (/myapp/*).
Regards.
-
Luca Morandini
GIS Consultant
[EMAIL PROTECTED]
http://utenti.tripod.it/lmorandini/index.html
-
-Original Message-
From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 13, 2003 6:14 PM
To: [EMAIL PROTECTED]
Subject: how can i get static files REALLY been processed by apache ???
Hy;
When i setup apache/tomcat/cocoon, i run into following
fancy problem. Although what i want seems trivial, but i did not
manage to get it done (I might not know the magic command to get
round it)
Here is the problem:
1.) I want all static files been served by apache, i.e.:
*.gif, *.html, *.jpg
2.) I want *ALL* other files be served by cocoon.
Now how should i setup mod_jk.conf
this doesn't help:
IfModule mod_jk.c
JkWorkersFile /etc/httpd/conf/workers.properties
JkLogFile /var/log/httpd/mod_jk.log
JkLogLevel error
JkMount /cocoon cocoon
JkMount /cocoon/ cocoon
JkMount /cocon/* cocoon
/IfModule
because it redirects everything to cocoon. But apache shall
serve the files mentioned above ...
This is not complete (Indeed it can never be complete):
IfModule mod_jk.c
JkWorkersFile /etc/httpd/conf/workers.properties
JkLogFile /var/log/httpd/mod_jk.log
JkLogLevel error
JkMount /cocoon/*.xml cocoon
JkMount /cocoon/*.jsp cocoon
JkMount /cocon/*.foococoon
...
/IfModule
The list could potentially go down endlessly.
There MUST be an obvious solution to this!
Anyone can help me here ?
regards, Hussayn
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
The cocoon-sandwich-use-case(was :Session managing problem)
Hy, all; I see one special use case for cocoon, which i call the cocoon-sandwich. The raising amount of questions in the past few weeks triggered me to write down this text. Lajos Moczar and myself we are in this since about two months now. This message summarizes some of our results. I think, this issue is of common interest. Hence i want to give you an insight into what we found and how we solved the problems in general. scenario: - You have a webapplication, that is already up and running. This webapp uses conventional interaction (jsp, servlets) possibly it is built up with struts, expresso or whatever. The webapp is independent of cocoon. You need to setup an intelligent presentation-layer that talks to the browser on one side and to the webapp on the other side. This presentation layer thus acts as client to the webapp and as server to the browser: client/server ... client/server +-+ ++ ++ | BROWSER |-| PRESENTATION |-| WEBAPP | +-+ ++ ++ implementation scenarios 0.) The poor mans scenario -- This scenario can be implemented with standard-cocoon under certain circumstances: 1.) the webapp is stateless 2.) the webapp does not use sessions 3.) the webapp has an XML-interface (responds with XML-content) For jsp's i mean this: %@ page contentType=text/xml% 3.) there is no hidden flow between webapp and browser, i.e. no COOKIES You can get around by using the http: ptocol handler coming with cocoon. I name this poor man's scenario, because you simply get it for free and can set it up in two minutes. But if you need to make your presentation layer transparent to session-infos and hidden flows (cookies), you need to make some additional work, that is currently not available from standard-cocoon. Even the WebappProxyGenerator mentioned often in this context, does NOT provide transparent session preserving! 1.) The hacker's solution - We created one solution, that works almoust perfect under following conditions: * Your webapp and your presentation layer are running in the same ip-domain * You can modify your webapp in a way, that it does its own session handling. Basically you would setup a Hashtable containing the session-data. The access key is the sessionid. You put the sessionid into your very special cookie and tell the browser to send this cookie whenever it sends a request to your ip-domain. Now when your webapp gets such a cookie, it can refer to the session in the hashtable. We still have to provide a facility to move Cookies forth and back through the presentation layer. For this purpose we have written a special proxy-protocol handler, that can be used similar to the standard http: protocol: map:match pattern=result/canvas/search_mask map:generate src=proxy://myserver/getdata.jsp/ map:serialize type = xml/ /map:match When using this proxy: handler, it will take care of your cookies in both directions (request and response) The major advantage here is, that you can use the proxy: handler wherever you can place a src into the sitemap. i.e. you could enable cookies with the WebProxyGenerator (hope, that's true. of course it depends heavily on what the generator does ;- ) There are two drawbacks to this: 1.) You must login to your webapp first and create the session environment and the cookie. Only after you did this, you can use your presentation layer to go on. 2.) You must modify your webapp after all. Because of these drawbacks i call this solution the hacker's solution 2.) The versatile solution -- Now what could you do, if you wanted to keep your webapp as is? There are two points here: 1.) You need to login to your webapp through the presentation layer. Basically you would login to the presentation layer and the presentation layer would login to your webapp. 2.) In order to get this done, you need to use the SAME credentials in the presentation layer as you need in your webapp. You would not need to move COOKIES between the browser and the webapp for session tracking. This would now be done internally by cocoon and the proxy: handler. But you may still want to pass cookies for other purposes. No problem, proxy: already does what you need. There is still one drawback to this solution: You need to use the same authentification database in presentation layer and webapp. This may be no problem at all if you can manage to run your webapp and the presentation layer on the same container, or at least in the same environment (using the same user database). But when you want to setup a scenario with SSO over far servers, you need just another
anyone interested in a cocoon-users meeting in Köln/germany ?
Hy; If there is interest, i could organise something in Köln. (maybe not as nice a place as some of you offered in this list ;-) ) Just send me a note (possibly include a proposal for an agenda ... ) regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: anyone interested in a cocoon-users meeting in Köln/germany ?
yes! Thorsten Scherler wrote: Hi Hussayn, I would be interested. Agenda: - welcome - basics (history, future, concepts) - use of cocoon in business apps - ... ...did you though about something like this? King regards Thorsten SAXESS - Hussayn Dabbous wrote: Hy; If there is interest, i could organise something in Köln. (maybe not as nice a place as some of you offered in this list ;-) ) Just send me a note (possibly include a proposal for an agenda ... ) regards, Hussayn - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Passing parameters
Hy; i think, that depends on where your jsp-generator runs. if you want to call another webapp (same server, or other server), this is not possible with standard cocoon. For this special case Lajos Moczar and me, we have built an add on, that allows to pass COOKIES from the browser to another webapp via cocoon. We set up a new protocol handler for this... if you want to address the cocoon internal jsp-processor, there may be another solution, i'm not aware of. Interested in more - send me a note. regards, Hussayn Eduardo Zurita wrote: Hello, I would like to pass a parameter to a JSP generator. This parameter must be a cookie value from the user's browser. is It possible? How to? Thanks in advance. Eduardo. -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: more specific question about parameters from querystring to JSP
You dont need the ?
try (error marked with '== look here ':
map:pipeline
map:match pattern=test.html
map:act type=request
map:parameter name=parameters value=true/
map:generate type=jsp
src=services/myservice.jsp{requestQuery}/ == look here
/map:act
map:transform src=services/stylesheets/myservice.xsl/
map:serialize type=html/
/map:match
/map:pipeline
/map:pipelines
Eduardo Zurita wrote:
I want to pass the parameter username with value joe to my generator
(myservice.jsp)
The problem is:
The user tries the page http://myserver/test.html?username=joe
And i have the following in sitemap.xmap:
map:pipeline
map:match pattern=test.html
map:act type=request
map:parameter name=parameters value=true/
map:generate type=jsp
src=services/myservice.jsp?{requestQuery}/
/map:act
map:transform src=services/stylesheets/myservice.xsl/
map:serialize type=html/
/map:match
/map:pipeline
/map:pipelines
Well, it doesn't work !!! :-(
Is this the correct way?
Please help,
thanks in advance.
Eduardo.
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: more specific question about parameters from querystring to JSP
you can make it even simpler:
map:pipeline
map:match pattern=test.html
map:act type=request
map:generate type=jsp
src=services/myservice.jsp{requestQuery}/
/map:act
map:transform src=services/stylesheets/myservice.xsl/
map:serialize type=html/
/map:match
/map:pipeline
/map:pipelines
SAXESS - Hussayn Dabbous wrote:
You dont need the ?
try (error marked with '== look here ':
map:pipeline
map:match pattern=test.html
map:act type=request
map:parameter name=parameters value=true/
map:generate type=jsp
src=services/myservice.jsp{requestQuery}/ == look here
/map:act
map:transform src=services/stylesheets/myservice.xsl/
map:serialize type=html/
/map:match
/map:pipeline
/map:pipelines
Eduardo Zurita wrote:
I want to pass the parameter username with value joe to my
generator (myservice.jsp)
The problem is:
The user tries the page http://myserver/test.html?username=joe
And i have the following in sitemap.xmap:
map:pipeline
map:match pattern=test.html
map:act type=request
map:parameter name=parameters value=true/
map:generate type=jsp
src=services/myservice.jsp?{requestQuery}//map:act
map:transform src=services/stylesheets/myservice.xsl/
map:serialize type=html/
/map:match
/map:pipeline
/map:pipelines
Well, it doesn't work !!! :-(
Is this the correct way?
Please help,
thanks in advance.
Eduardo.
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Session managing problem
i created a cocoon add on for exactly your scenario.
I do also access my webapp via jsp pages, that return XML
content and let cocoon do the presentation issues.
works fine and reasonably perormant so far.
I manage to pass session cookies through cocoon and
i'm happy with it.
we (Lajos and me) implemented a new protocol handler for this
purpose.
more info - send me a note
hussayn
Nesto wrote:
Hi!
I have a problem with the session managing.
I'm trying to write a user interface of an existing system using cocoon
as publishing framework.
The system is composed of a set of JSPs that generates xml data from a
database.
So the pipelines in the sitemap I wrote are all of this type:
map:match pattern=*.jsp
map:act type=request
map:parameter name=parameters value=true/
map:generate type=file
src=http://remoteHost:8080/remoteApp/{../1}.jsp{requestQuery};
mime-type=text/xml/
map:transform src=stylesheets/{../1}.xsl/
map:serialize type=xhtml/
/map:act
/map:match
The REMOTE application manage itself the user sessions, but i don't how
i have to modify my sitemap in order to let client and the remote
application exchange session informations.
In this moment the presence of Cocoon between client and Remote App
causes the loss of session information (accessing through IE directly, I
can see the correct xml data)
I read the documentation on Cocoon site, and on Wiki, and I found
something that looks interesting: the matchers of type cookie and
sessionstate.
But the problem is that I really haven't understand how I can use them.
Thanks for your answers!
Nesto
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: A note about the best(?) (cocoon-) development environment...
Hy, All; Would you mind to open another thread about your JDO-theme ? regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
what is the common delopment environment used by the cocoon-userscomunity ...
Hy, all; I want to ask again for some opinions on the most commonly used tools of the cocoon-users. I want to setup a Wiki-page on this theme, so that new users can get most out of cocoon. And since we already write about howto install Servlet Containers to get cocoon users happy, in the next step it seems natural for me to write about development environement for cocoon users ... I opened another thread this weekend, but it quickly left off the theme... The original thread start can be found at http://www.mail-archive.com/cocoon-users@xml.apache.org/msg24320.html Here the short list of what i grabbed together into my development workbench: free tools: 1.) OS: linux and solaris (maybe a mater of taste) 2.) apache 1.3.26 (mod_jk2, mod_SSL) 3.) tomcat 4.1.18 4.) cocoon-2.0.4 5.) eclipse 6.) sunbow eclipse tools (xml/sitemap) 7.) ant 8.) java-1.3.1 (sun JDK on all platforms) 9.) Secureway LDAP Server (i'll switch to Open LDAP soon) Besides this i use some comercial tools like clearcase and xml-spy. although i know most of the OS comunity does not like such tools, i use them with great success. I mentioned these tools too in my first mailing (see link above)just to be complete. Any hints on what you think is missing in the list, or could be replaced by something more convenient would help me getting the (not yet existing) Wiki page into a cleaner shape. regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: global sitemap parameters and programatic cocoon configuration
Hy, Marco;
Thank you for your infos so far. The keyword DefaultsMetaModule
brought me to a thread within the users archive:
http://www.mail-archive.com/cocoon-users@xml.apache.org/msg18831.html
From the thread i learned, that DefaultsMetaModule would NOT
pass parameters to subsitemaps when mounted. But there seems
to be the concept of global parameters around in cocoon, although
some problems are reported (i.e. /myserver would not work either).
hmm... i didn't find the docs about global parameters yet...
I also learned, that input modules is something not yet released,
and under discussion...
I'll start experimenting with DefaultsMetaModule and add some
stuff into cocoon.xconf and look into this in more depth. I would
appreciate, if anyone could add a little more light to this ...
regards, Hussayn
Marco Rolappe wrote:
hi hussayn,
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Im
Auftrag von SAXESS - Hussayn Dabbous
Gesendet: Montag, 10. Februar 2003 15:20
An: [EMAIL PROTECTED]
Betreff: global sitemap parameters and programatic cocoon
configuration
Hy, all
I just fall over a configuration issue:
1.) assume you like to use a global parameter ${myserver}
within several places in your sitemap AND all subsitemaps.
Is the following (or something equivalent) possible
to do:
map:sitemap
map:parameter name=myserver value=http://myserver; /
...
map:match pattern=*/canvas/collection
map:read src=html:${/myserver}/index.xml/
/map:match
...
I think there's an input module available for stuff like that which IIRC
makes those variables also available to subsitemaps.
2.) Is it possible to also add such parameters programatically
to the rootsitemap and use them all over in cocoon?
I.e. i want the variable ${myserver} be preset from an
external configuration, which happens to be separate from
sitemap.xmap.
background: I would like to keep the customisation at one
place and keep my customers away from sitemap.xmap if possible.
is something like this possible with cocoon:
1.) on-startup of cocoon process an additional java-class-instance
(a servlet, or better an initilisation-component
specified in cocoon.xconf)
you can of course have another servlet declared in the web.xml and have it
automatically loaded/started via load-on-startup (see servlet spec).
the other alternative you pointed out also works and is probably the better
way to go (also thought about this, needing to have something like an
application core running which could be accessible as a Component). I think
for this to work you have to make your 'instance' an avalon component (i.e.
implements Component interface) with a defined role (you can specify your
own roles in a separate file which you can reference from the cocoon.xconf,
/cocoon/@user-roles IIRC).
2.) the initialisation-class reads a customisationfile and
adds a set of global variables to the rootsitemap.
it might be possible to get hold of the above mentioned input module via a
ComponentManager (within your Component) and add those variables
programmatically.
3.) After cocoon came up the global sitemap parameters are
available within any sitemap.xmap
as I said, I think the variables should be visible in sub-sitemaps also, but
I might be wrong. But from the fact that the modules declared in the root
sitemap are available in sub-sitemaps I assume that the global variable
module's scope is not limited to the root sitemap.
Does anyone know, if this could be achieved and if yes, could you
point me to an example or a document about this ?
Just had a quick look and I think the DefaultsMetaModule is what I had in
mind.
thanks you
Hussayn
HTH
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq
Re: AW: global sitemap parameters and programatic cocoon configuration
Hy, Jeremy;
Thank you for this hint. That's great, because this comes
in fact very close to what i want. The only thing
i would have to change in my current setup is switching
from property-notation to XML-notation in my customisation
files. I planned this move anyway.
Only one last question, before i dive into it. Does this
also work on cocoon-2.0.4, or do i have to wait until 2.1
is released ?
regards, Hussayn
Jeremy Quinn wrote:
On Monday, February 10, 2003, at 06:44 PM, SAXESS - Hussayn Dabbous wrote:
I also learned, that input modules is something not yet released,
and under discussion...
I'll start experimenting with DefaultsMetaModule and add some
stuff into cocoon.xconf and look into this in more depth. I would
appreciate, if anyone could add a little more light to this ...
Here's an example from my config in Cocoon 2.1:
WEB-INF/cocoon.xconf:
component-instance
class=org.apache.cocoon.components.modules.input.XMLFileModule
logger=core.modules.xml name=my-org-conf
file src=WEB-INF/my-org.xconf/
/component-instance
component-instance
class=org.apache.cocoon.components.modules.input.ChainMetaModule
logger=core.modules.input name=my-org
input-module name=request-param/
input-module name=simple-map
prefix/vars//prefix
input-module name=my-org-conf/
/input-module
/component-instance
WEB-INF/my-org.xconf:
vars
start0/start
count25/count
xsltparts/xsl/xslt
/vars
my-org.xmap (a sub site-map)
map:transform src={my-org:xslt}/process-sql.xsl
map:parameter name=count value={my-org:count}/
map:parameter name=start value={my-org:start}/
/map:transform
Values from the xml file can be used as values in the sitemap.
In this example, any of the 'vars' can be overridden by a request
parameter.
Hope this helps
regards Jeremy
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
A note about the best(?) (cocoon-) development environment ...
Hy, all; During the last months of activities i learned a lot from this mailing list. while i followed the discussions i started getting my development environment a bit up to date. I plan to setup a Wiki page on this theme. Although this may be a bit off topic, it still would be great, if someone could comment on this issue. the tools collection Here is what i have put together so far. Of course this is driven at least partially by what i do for my customers... free tools: 1.) OS: linux and solaris (maybe a mater of taste) 2.) apache 1.3.26 (mod_jk2, mod_SSL) 3.) tomcat 4.1.18 4.) cocoon-2.0.4 5.) eclipse 6.) sunbow eclipse tools (xml/sitemap) 7.) ant 8.) java-1.3.1 (sun JDK on all platforms) 9.) Secureway LDAP Server (i'll switch to Open LDAP soon) commercial tools: 10.) clearcase cms (see below) 11.) xml-spy 12.) several DB-Systems notes about the collection -- * All tools mentioned above fit tightly together. I use apache/tomcat since about three years now. The above combination also works fine with SSL. * After i got eclipse setup in tomcat debugging mode, i could at least double my productivity. Thanks to the tomcat site it was a matter of seconds to get it up see: http://jakarta.apache.org/site/idedev-rdtomcat.html * I also managed to setup eclipse with Cocoon in less than 10 minutes. OK, i did a lousy trick, but for debugging and learning how cocoon internals work it's absolutley satisfying... * about SCM in general and Clearcase in particular: Clearcase is a quite expensive and known to be very slow SCM tool. On the other hand it is super easy to integrate. Due to exposing the data within a virtual filesystem you just don't see it from the users viewpoint (except checkin checkout your files). Having the clearcase integration kit for eclipse up and running comes near to a developers dream. I hope, after Rational has been incorporated into IBM, clearcase or a derivate of it will eventually find it's way into the ongoing eclipse efforts to build just another SCM. See http://www.eclipse.org/technology/index.html follow the link to stellation at the bottom of the page. Another interesting new SCM could be subversion from http://subversion.tigris.org/ ... All of these SCM's provide directory versioning (something once you got it, you'll never want to miss again...) * I happen to use XML-Spy since a couple of years now. Maybe i just got used to it. I like it, although i have to pay for the license. At least it helps me getting my XSCHEMA's generated in no time. My personal SAXESS story ... SAXESS stands for System AXESS, just to get this clear;-) I write this down, mainly because i got very very satisfied with this especially when i compare this to what i was used to in former times when open source was something, nobody ever heard of... I'm running my webserver on some linux box and my webapps on solaris driven by tomcat. All of my code is dropped into a company wide multiplatform SCM system. I'm developing with the eclipse IDE right on my Desktop machine. I'm running Cocoon for the visualisation part of my projects. This is just a great XML publishing tool, and i'm still only using the basics of it for now. By saving my work to the SCM, my testwebapp gets autodeployed on a solaris box, which happens to be our testenvironment. I can setup remote debuggig sessions from my desktop directly into the heart of my webapplications... Once i checked in my work into the SCM, my webapp gets autodeployed on linux, which happens to be our website server. And i bet, after fiddeling around a bit, i could setup a debugging session on my customers site, while sitting somewhere at a beach, quickfix a bug, and then turn back to the real life just beeing happy for the rest of the day... A personal thank to the Open Source comunity Folks, Thank you very much all you, who have contributed to get such a powerfull toolset up and running. I just get very excited seeing this developer's dream becoming reality... And sad enough i'm not sitting at a beach, but in good ol'e germany getting to much rain and too few sun (solaris is not good for everything...). thanks for your attention, if your patience lasted until here ;-) regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 D-50935 Köln tel.:+49 221 56011 0 fax.:+49 221-56011 20 email:[EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: !HELP! Cocoon global errors !HELP!
If you look into the logs and search for the FIRST occurence of a stack trace, you see this message: org.apache.cocoon.ResourceNotFoundException: The element type content must be terminated by the matching end-tag /content.: org.xml.sax.SAXParseException: The element type content must be terminated by the matching end-tag /content. This means, that in one of your XML or XSL files you have a problem with wellformedness. what can you do against it ? 1.) search for the content tag in your document, or your XSL file that you retrieve with your request. 2.) consider using an XML aware editor. there was a discussion about this recently on this mailing list. just look into the archives... regards, hussayn [EMAIL PROTECTED] wrote: Hi, Sorry, I have just receive a mailer-deamon message that my mail failed. So are the complete logs. -Original Message- Hello everybody, I've installed Cocoon and developed a bit with it. I didn't change anything special in cocoon, but now I get following error on all my pages : HTTP Status 404 - typeStatus report message descriptionThe requested resource () is not available. And my logfile is like this (here is my last request): Thanks for your HELP! Maxi me - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using the results of an aggregate part.
Hy, I need to transform one source into two different views and finally collect these views into one single output page. I do this with an aggregation, that implicitly calls the same source twice and feeds the result into different transformers: map:match pattern=search/canvas map:aggregate element=canvas map:part element = coll src=cocoon:/search/coll/ map:part element = mask src=cocoon:/search/mask/ /map:aggregate map:transform src = canvas.xsl/ map:serialize type = html/ /map:match map:match pattern=/search/coll map:generate src=http://myserver/collection.xml/ map:transform src=collection.xsl/ map:serialize type = xml/ /map:match map:match pattern=/search/mask map:generate src=http://myserver/collection.xml/ map:transform src=mask.xsl/ map:serialize type = xml/ /map:match The goal is to call the http: request only once, not twice as is done with the sitemap above. One possible solution would be to create one single XSL-transform by merging the rules of canvas.xsl and collection.xsl into one merge.xsl and add a template that actually controls the merge. That would result in calling the http only once, but i do not want to solve it like this, because the only place, where i want to define the merge shall be the sitemap i.e. within the first match rule above. Now the question raises, how i can gather an xml-fragment, put it into some temporary place (ideally in memory) and refer to this fragement from another part of the pipeline. On top of this the xml-fragment should be kept local to the request (each request retrieves the fragment and puts it into a request-bound place and after the request terminates throw away the fragment) any ideas, how this could be achieved ? regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Location of cocoon webapp on server
There is a brand new wiki page on this. You may look into it at http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation It is in the draft state right now, but i would be pleased, if you comment on it. the page misses one step that is needed for your requirements. Howto omitt cocoon from your http request. there is some documentation on this withion the official cocoon docs. in short terms: go to tomcat conf/server.xml add a Default Context for your app. If you use a NEWER version of tomcat, (tomcat-4.1.16++) you MUST take out cocoon from the default webapps directory and put it somewherre else and define that location within the Context. this is very brief answer. for more detailed look into the Wiki or the cocoon docs. regards, hussayn Anna Afonchenko wrote: Hi all. We have our web app under CATALINA_HOME/webapps/cocoon/ub which can be accessed on the webserver by http://domain.name:8080/cocoon/ub/* However, we want to put the ub directory under /home/cocoon/ub and to access it by http://domain.name/ub/* We can move the directory to /home/cocoon/ub, and therefore not under webapps/cocoon and call it by using a sub sitemap with the URL http://domain.name:8080/cocoon/ub/* But how do we lose the :8080/cocoon from the request URL? We are using apache 1.1 and the latest tomcat and cocoon and the jk1 bridge between tomcat and apache. The system is a linux box. I can modify the workers.properties file so that it mounts http://domain.name/ub to tomcat and then put a symbolic link in the tomcat web-apps directory to /home/cocoon/ub but this is both an ugly and not very stable solution. Thank you very much for your help Anna Afonchenko and Spencer Bruce -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhofer Allee 125 50935 Koln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: matcher of a request
You can make this even more generic:
map:match pattern=*.jsp
map:act type=request
map:generate type=file
src=http://anotherhost:8080/anotherApp{../1}.jsp{requestQuery};
mime-type=text/xml/
map:transform src=stylesheets/{../1}.xsl/
map:serialize type=xhtml/
/map:act
/map:match
This will simply copy the GET-parameters from your original request ;-)
and i think it's slightly more performant ...
regards, Hussayn
Nesto wrote:
Thank you Jan for your help!!
Finally I wrote a matcher that works fine!
I post it to the group because it could be interesting.
I wanted to write a matcher for an URI of this type:
http://myhost.com:8080/cocoon/myApp/list.jsp?user=tompassword=tom
http://myhost.com:8080/cocoon/myApp/list.jsp?user=tompassword=tom
The matcher is:
map:match pattern=*.jsp
map:act type=request
map:parameter name=parameters value=true /
map:generate type=file
src=http://anotherhost:8080/anotherApp{../1}.jsp?username={username}amp;password={password};
mime-type=text/xml/
map:transform src=stylesheets/{../1}.xsl/
map:serialize type=xhtml/
/map:act
/map:match
Hope this helps someone else!
Nesto!
- Original Message -
*From:* Jan Harms mailto:[EMAIL PROTECTED]
*To:* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
*Sent:* Wednesday, February 05, 2003 3:29 PM
*Subject:* AW: matcher of a request
Nesto,
I´m not sure if this works, but try
/map:match
map:match pattern=*.jsp
map:generate type=file
src=http://anotherHost:8080/theApp/{1}.jsp?user={request:user}password={request:password}
http://anotherHost:8080/theApp/{1}.jsp?user={request:user}password={request:password}
/
map:transform src={1}.xsl/
map:serialize type=xhtml/
/map:match
The {request:yourparam} parts are so called input-modules. See:
http://xml.apache.org/cocoon/userdocs/concepts/modules.html
Be careful with the generator type you choose. The JSP generator
expects the location of a JSP-File. You are calling a jsp from
another server, that means you have to use a generator that matches
the *output* of this jsp. I.e if the jsp produces HTML you need the
HTML-generator. In your case you need the file-generator since the
jsp produces XML.
Hope this helps,
-Jan Harms
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuring Cocoon to run under Apache/Tomcat virtual host?
i am running an apache/tomcat/cocoon combination with authentication driven by tomcat (just setting the correct security-constraints within the web.xml and adding the right REALM in tomcat/server.xml ... i did never touch the apache server itself for authentification issues... And i'm using form based authentification. regards, hussayn Derek Hohls wrote: Hi I am looking for help with configuring an Apache/Tomcat setup, trying to support a password-protected Cocoon site that must be accessed by a virtual host name. The UNIX support has tried to set it up (see below), but trying to access the site results in an error 302, which just repeats over and over in the log file: 111.11.1.1 - - [06/Feb/2003:14:11:00 -0200] GET /cocoon/myapp/index HTTP/1.1 302 0 and of course the site is not accessible. Any help with this is *much* appreciated; maybe a small help file can be added to the Wiki. Thanks Derek *** The configuration entry looks as follows: VirtualHost 111.11.11.2 ServerAdmin joe@mydomain mailto:joe@mydomain ServerName myapp.csir.co.za:80 DocumentRoot /usr/local/tomcat/webapps Directory /usr/local/tomcat/webapps AuthType Basic AuthName myappis a restricted area ! AuthUserFile /usr/local/apache/users Require valid-user /Directory RewriteEngine on RewriteRule ^/(.*) /cocoon/appdir [PT] WebAppConnection appdirConnection warp server.host.com:8008 WebAppDeploy cocoon appdirConnection /cocoon/ /VirtualHost -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Session problems
hy, i would like to understand, in which context your servlet is running. Is it located within the cocoon webapp, or is it located elsewhere? from the redirect url i guess you are crossing webapplications ... If this is the case, you have another problem with session preserving over multiple webapps. there are solutions to this, but this is far from trivial... If your servlet runs in the same context as cocoon, then i can't see at the moment, why you loose your session. from the standard behaviour of a servlet container i would expect, that once a session is created within one context, this session is kept. I dont think, that xsp will always create new sessions. if create-session=true I would expect, it creates a session, if none is existing, but once a session is created it should be keep living for subsequent requests... After having saying this, i bet you cross webapp boundaries ... regards, hussayn Marco Rolappe wrote: hi roberto, the reason why your elements are empty probably are the following; the session accessed in your XSP might be different from the JSP's session. since you redirect without url encoding the redirect url, the session probably doesn't survive the redirect. now in the XSP you didn't specify the xsp:page's attribute create-session=false (which is handled by the session logicsheet), which defaults to true, thus a new session is created in the XSP. I don't know if your sessions are cookie or url rewriting based. anyway, you should be url encoding the redirect url, see inline comments below. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von Roberto Cipollini Gesendet: Donnerstag, 6. Februar 2003 18:40 An: [EMAIL PROTECTED] Betreff: Session problems Hi. I have a problem with a jsp page and a cocoon page. I use jsp to simply check a user/password and if all is right then set some variables in the session.setAttribute. I then redirect the user to a cocoon page in wich i should grab the session variable with some xsp-logic commands buti can't see them! Ok...all of you are saying What a stupid newbie :). I know, but pls, it's been a lot of headaches trying to solve this but i still.have headaches. This is the code inside the jsp page: check_login.jsp * session.setAttribute( username, theRealUser ); session.setAttribute( azienda, theRealFirm); //pfw is my custom file format :) response.sendRedirect( /pfw/rv3/setup_env.pfw ); this line should be something like: response.sendRedirect(response.encodeRedirectURL (/pfw/rv3/setup_env.pfw)); ** cocoon page setup_env.pfw *** ?xml version=1.0? ?cocoon-process type=xsp? ?cocoon-process type=xslt? xsp:page language=java xmlns:xsp=http://apache.org/xsp; xmlns:xsp-session=http://apache.org/xsp/session/2.0; xmlns:xsp-request=http://apache.org/xsp/request/2.0; xsp:structure xsp:includejava.util.*/xsp:include xsp:includejava.io.*/xsp:include xsp:includejava.text.*/xsp:include xsp:includejavax.*/xsp:include xsp:includejavax.*/xsp:include xsp:includeorg.apache.cocoon.environment.Session/xsp:include /xsp:structure PAGE AZIENDA xsp-session:get-attribute name=azienda / /AZIENDA UTENTE xsp-session:get-attribute name=username / /UTENTE /PAGE /xsp:page the tag AZIENDA and UTENTE are always empty!!! Can anyone help this stupid problem? thanks! R.C. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 D-50935 Köln tel.:+49 221 56011 0 fax.:+49 221-56011 20 email:[EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie
You may look at the following place to get the portal running. http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install in fact this page doesnt tell explicitly how the portal is comnpiled, this jaust happens under the hood. so just follow the cookbook and your done (im speeking for cocoon-2.0.4 only, no idea about the HEAD version) hussayn Sean McKaharay wrote: I just started looking at Cocoon and I find the portal piece really nice. I tried building the src with the correct option but I don't know how to build and deploy the portal piece. When you run the option and then build it comes up with 2 jar files. Are they independent files or do they get dropped in the web-apps directory and explode by themselves? Any help would be great Sean -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 D-50935 Köln tel.:+49 221 56011 0 fax.:+49 221-56011 20 email:[EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
about commercial adds of cocoon consultants ...
Hy, all; Maybe it is a good idea to create a commercial corner for cocoon somewhere ? Consultants and companies, who are supporting cocoon on a commercial base may put their footprint there. This may be a clear signal for possibly interested customers to see, there is a growing commercial support on cocoon... As i'm just getting a big fan of Wiki, maybe there is a prominent place where such a page could be set up ??? Maybe there are other ideas about this topic ? any comments are welcome ... regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Directories
ok,
1.) you must be pretty clear, that simply moving your
directories into another folder under webapps wont be the
solution of your problem.
2.) it depends what you want to achieve. the simplest solution
would be to make a sitemap mount. this is done as follows
(i pray, i did no mistake here, shout at me, if its wrong..)
1.) go to your cocoon main folder.
2.) cretae a folder named soundpool
3.) move your xsl xml files to that folder
4.) create a file named sitemap.xmap
put all that YOU(!) have put into the original
cocoon sitemap.xmap into this new file
5.) revert the cocoon.xmap in the cocoon main directory
to its delivery state.
6.) Now edit the reverted sitemap.xmap and add the following:
a. search for the line map:pipelines
b. directly beneath this line add the following to your sitemap:
map:pipeline
map:match pattern=*/**
map:mount check-reload=yes
reload-method=synchron
src={1}/
uri-prefix={1}/
/map:match
/map:pipeline
7.) go to the subfolder soundpool and edit the sitemap.xconf there
a. at the top of the file add the following:
map:components
map:generators default=file/
map:transformers default=xslt/
map:serializers default=html/
map:matchers default=wildcard/
/map:components
im not shure if this is really needed...
8.) Now you can enter on your URL
http://192.168.0.5:8080/soundpool/soundpool.html
and you will get what you want.
Maybe you are seeking for a solution where you can completely
separate cocoon and your soundpool physically. If you want this,
you can by creating a backend webapp soundpool and use cocoon as
frontend webapp, but this is far more complex. I just did this for
a very complex environment. But you have to think twice, if you
really want to do it like that.
regards, hussayn
Richard Cunliffe wrote:
Jonathan,
I have just tried the suggestion by Konstantin, which was this:
Context path= docBase=cocoon
...
/Context
This has changed the address, but has not changed the physical directory
that they are in. I am trying to clean up my directories!
I have made a new folder called soundpool in webapps like you suggested,
but what do I need to change in the server.xml. I have found the section
vitual host and have copied it below:
!-- Define the default virtual host --
Host name=localhost debug=0 appBase=webapps unpackWARs=true
Listener className=org.apache.ajp.tomcat4.config.ApacheConfig
append=true/
Which part of this would I change for it to point it in the right
direction?
I am also not sure what you mean by my cocoon's main sitemap is mounting
my soundpool sitemap. The way I have it set up at the moment is that I
have main sitemap in the following directory:
C:\tomcat\webapps\cocoon\sitemap.xml
My XML and XSL files are also stored in this directory, hence the need
for some organisation. Obviously I would need to move my sitemap with
the files to there new folder, so how would I my main sitemap mount the
soundpool sitemap?
Thanks,
Richard.
(By the way I had a quick look on the wiki site, and couldn't find
anything, hence my ask for help here)
-Original Message-
From: Jonathan Patrick Freeman [mailto:[EMAIL PROTECTED]]
Sent: 04 February 2003 15:35
To: [EMAIL PROTECTED]
Subject: Re: Directories
Richard,
Unless I'm wrong (and usually I am :) I think you need to move your
directory soundpool to a webapp level and update the virtual host
section
of your server.xml file in tomcat's conf directory. Your cocoon's main
sitemap is mounting your soundpool sitemap, correct? The cocoon
directory is
already a webapp. You simply need to make soundpool a webapp with its
main
sitemap and WEB-INF folder, jars, libs, etc...
Something like: C:\tomcat\webapps\soundpool
This really should be documented on Wiki too. Maybe it already is?
Regards,
-Jonathan
- Original Message -
From: Richard Cunliffe [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 04, 2003 10:20 AM
Subject: Directories
Hi,
Cocoon 2.0.4
Tomcat 4.0.6
Can someone point me in the right direction for setting up
directories?
For example my current URI and hard disk location looks like this:
http://192.168.0.5:8080/cocoon/soundpool/soundpool.html
C:\tomcat\webapps\cocoon\soundpool.xml
If I wanted to change the URI address to this:
http://192.168.0.5:8080/soundpool/soundpool.html
How would I change the disk location, and in what files would I need
to
change for it to direct the incoming request to the right disk
location?
Is there an equivalent to flash guide on this subject?
Thanks,
Richard.
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Added a beginners page on basic cocoonapp organisation
Hy; After a break i made up my mind and added a simple tutorial on webapp organisation using subsitemaps. Most of this has already been adressed in several places, but maybe it fits best in the Cocoon Competence Center. I would be glad, if someone could review this and eventually clearify parts of it, if i failed to find the right words. http://wiki.cocoondev.org/Wiki.jsp?page=BeginnerSimpleWebappOrganisation regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 D-50935 Köln tel.:+49 221 56011 0 fax.:+49 221-56011 20 email:[EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Competence Center Updates
Hy, Robert; Thank you very much for the contributions. I propose to move parts of your contrib into another page. reasons: 1.) this page deals with deploying cocoon. it should not cover essentials of cocoon internals. this is the next story to be covered, once cocoon is deployed. 2.) i want this document to be for beginning beginners, (we used to name them nebies ;-). Yes we should prepare a doc, that contains your hints and tips, but maybe this is an add on page ? if nobody complains, i will move your contribs to another page, but keep the super esssentials in the doc (and point to the new pages where relevant) is that ok for you Robert? regards, Hussayn Robert Simmons wrote: Greetings, I have added the following information to the cocoon competence center page on installing cocoon. Please feel free to review the following sections and smack me around if I said anything incorrect. The new sections are. * Deploying on an application server. * What is essential? -- Robert -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon Competence Center Updates
Hy Robert, I appreciate your honesty. I hope, you keep with us. I think you can really help getting this into the next generation... just a few of my experiences if you don't mind ... 0.) i use to install minimalistic components when i start investigating. in this sense i only needed tomcat-4.*.* to start. just installed it and ready to go... 1.) When i started working with cocoon i first got very very frustrated: sitemap not working as i expected actions, uhh? logicsheets, sounds good, howto??? and so on ... I even did not know, what to ask in detail. 3.) very slowly i got a first overview. i only scratched the surface and one day (after about two weeks) i got hit by realizing the hidden mightiness of the beast. Hey that's great, this works fine, ahh what easy going here and there... Until now i still only was playing with the very basics (sitemap, generator, protocol handlers) 4.) After reviewing my first experiences with cocoon i came to the conclusions: - its very complex - it has great oportunities - it is complex documented - it moves fast - it neads quality assurance to get mature My decisions: - use cocoon in my own projects - help cocoon users to get a clear understanding with less frustrations I'm still happy with cocoon and im still only using the very basics. I am curious where i can get with XSP and ESQL ;-) regards, hussayn Robert Simmons wrote: Fine ... I'm beginning to loose interest to be honest. Right now I cant do anything with XSP with cocoon at all. because of the classpath bug it looks like two weeks of my work are about to explode in my face. Sigh. -- Robert - Original Message - From: SAXESS - Hussayn Dabbous [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 30, 2003 9:12 AM Subject: Re: Cocoon Competence Center Updates Hy, Robert; Thank you very much for the contributions. I propose to move parts of your contrib into another page. reasons: 1.) this page deals with deploying cocoon. it should not cover essentials of cocoon internals. this is the next story to be covered, once cocoon is deployed. 2.) i want this document to be for beginning beginners, (we used to name them nebies ;-). Yes we should prepare a doc, that contains your hints and tips, but maybe this is an add on page ? if nobody complains, i will move your contribs to another page, but keep the super esssentials in the doc (and point to the new pages where relevant) is that ok for you Robert? regards, Hussayn Robert Simmons wrote: Greetings, I have added the following information to the cocoon competence center page on installing cocoon. Please feel free to review the following sections and smack me around if I said anything incorrect. The new sections are. * Deploying on an application server. * What is essential? -- Robert -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Apache error on startup
The error message says, you are missing one parameter. Check, that on your line 4 you have the following content. If you have, check that you are looking at the right file ;-) LoadModule jk_module modules/mod_jk.so regards, hussayn Richard Cunliffe wrote: Hi, I have installed Apache 2.0.43 and tomcat 4.0.6, using mod_jk 2.0.43. I am following the flash guide produced by Lajos. I am getting the following error after I have started tomcat and then try and start Apache: Sntax error on line 4 of c:/tomcat/conf/auto/mod_jk.conf: LoadModule takes two arguments, a module name and the name of a shared object file to load it from How should I go about fixing this? Thanks, Richard. -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 29 January 2003 21:53 To: [EMAIL PROTECTED] Subject: Re: WARP, Jserv or mod_jk? just one tip. As far as i see, you dont need to build the java components for mod_jk if you are planning to run a binary distribution of tomcat-4.*.*. The java components are already included in these tomcat distributions. You would only have to build the apache mod_jk module ... Therefor you may simply skip all the java and ant related topics... maybe that helps you getting faster to your goal. regards, hussayn Richard Cunliffe wrote: Lajos, I have reached point 6, where you build ant, but it is coming up with the following error: Warning: JAVA_HOME environment variable not set. If build fails because sun.* classes could not not be found You will need to set the JAVA_HOME environment variable To the installation directory of java. Bulidfile: build.xml does not exist! Build failed So, 1. How do you set the JAVA_HOME? (I have java 1.3 installed) 2. I checked if build.xml exsits and it does. Is it not finding it because it cant find the JAVA_HOME? Thanks, Richard -Original Message- From: Lajos [mailto:[EMAIL PROTECTED]] Sent: 29 January 2003 15:17 To: [EMAIL PROTECTED] Subject: Re: WARP, Jserv or mod_jk? Is that a link off my guide? Sorry, if it is - I have to update the damn things every couple of weeks 'cause they change so often. Anyhow, if you are using 4.0.6, you need the attached zip file. But you can also check for binaries at http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1 .2.2/bin/ and save yourself some time. Regards, Lajos Richard Cunliffe wrote: Lajos, The following link is not working http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.3/src/j akarta-tomcat-connectors-4.0.2-01-src.zip. If you have the zip file could you e-mail it to me at [EMAIL PROTECTED] Thanks for the advice Richard. -Original Message- From: Lajos [mailto:[EMAIL PROTECTED]] Sent: 29 January 2003 14:46 To: [EMAIL PROTECTED] Subject: Re: WARP, Jserv or mod_jk? Hi Richard - mod_jk by far is the best. WARP is buggy and is may not even be actively developed any more. mod_jk is stable, widely used, and generally has few bugs reported. If you need help with the integration, my FlashGuides (www.galatea.com/flashguides) have instructions on connecting Apache 2.x with Tomcat 4.x using Jk. Regards, Lajos Richard Cunliffe wrote: Hi, I?m upgrading! Can anyone suggest the best way to connect Apache 2.0.42 and Tomcat 4.0.6. I will be using Cocoon 2.0.4. I have read that the WARP connecter is the best, but I used Jserv on my older version. There is also the mod_jk. Which is the most reliable etc. Thanks Richard. -- This message has been scanned for viruses and dangerous content by MailScanner http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. -- Lajos Moczar Open Source Support, Consulting and Training Cocoon Developer's Handbook (www.amazon.com/exec/obidos/tg/detail/-/0672322579) _ _ / \ / /___\ / / \ / http://www.galatea.com -- powered by AzSSL - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail
Create a new thread, if discussions leave off ground
Nowadays threads keep on growing, but the discussions sometimes turn away from the thread title. then it becomes really a problem to guess the content from the title. It would take less time to get hold on personally relevant mails ;-) thank you, Hussayn Luca Morandini wrote: -Original Message- From: Robert Simmons [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 1:08 PM To: [EMAIL PROTECTED] Subject: Re: Cocoon Competence Center Updates No no no... you dont get it. Im a consumer. Im a professional programmer. Im not some guy hackign in his dorm room between classes. I dotn have TIME to learn the detailed integrated architecture of every little product I use. ... Once I figured out how it worked I would have to figure out a resolution to the problem and THEN get apache to accept the resolution. All this before my product is done and my customers are looking to download and use it. NOT. Robert, I agree on the sorry state of the doc in Cocoon; sorry state which I take, partially, as a fault of mine, since I wrote only 3-4 FAQ entries and a couple pages... and I could have done more. I don't agree on the bug resolution part: I uncovered a couple problems with the SQLTranformer: it was easy to fix them and have them (well, actually one) accepted by the committers. Compare that with a closed-source product: it would have taken me days struggling with the tech support to just have the problem recognised as such; and then, I would have ended up waiting for the next release. Regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Time to go back to JSP. Cocoon just isnt ready.
Robert, this was NOT POLITE ! stop this attacks! thats useless and distracting! no more words on this. hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon hosting - experiences?
i'm using this combination: apache-1.3.26 (mod_jk, SSL) tomcat-4.1.18 cocoon-2.0.4 DB2-UDB-7.1 Secureway-LDAP-3.2.1 i'm serving my companies website with this. My overall Uptime of the site is 100% but that may not say anything, because the site is only running since one month. My site is rather simple (int terms of cocoon usage) at the moment. But it serves the pages dynamically directly from xml (the navigation is dynamically created). i'm satisfied in all aspects. But im running the service on my own hardware (PC/Linux), so i have no problems with any provider. i dont know, how problematic it is to get a provider to run a webapp. but that shouldn't be a big technical problem... Besides this i'm currently building a highly dynamic webapplication, that serves as a metasearch engine. the frontend is pure cocoon. also here im satisfied with the current results. regards, hussayn gv wrote: Hello, I am curious about people's experiences with setting up live Cocoon sites with a Web host: Any hosts that seem particularly good (or bad)? How about uptime for the Cocoon servlet and the servlet container? Any controls for restarting if needed? Satisfied with the version of Cocoon, Java, and whatever database is provided? Or, are you using an ordinary Web host and pushing out the Cocoon-created content as static pages? I'd appreciate anything you could share on this. I'm a huge fan of Cocoon and am finding it very useful to build sites. I'm still mostly using it to create static pages, but wondering if there are brighter options out there. Thank you, John __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: How can I send XML as HTTP POST to a URL?
It may be adequate to write a protocol Handler for this purpose. I think you can get hold on the original request from the Environment. Maybe .../components/source/URLSource.java is a good starting point ... hussayn Marco Rolappe wrote: you should probably code that as an action, that you can use in your sitemap. please see relevant docs. -Ursprungliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von gv Gesendet: Dienstag, 28. Januar 2003 21:13 An: [EMAIL PROTECTED] Betreff: How can I send XML as HTTP POST to a URL? Hello, I need to have Cocoon send an XML structure as an HTTP POST request to a URL. Anyone know how to do this? Thank you, John __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: How to run 2 tomcat-coocon web server
Hy: this message: VGJ0607E - Une inadéquation de version s'est produite entre le serveur et le circuit my.pkg.JAH0001WUIBean. translates to something like: differing versions between server and package my.pkg.JAH0001WUIBean seems to point to EJBeans stuff ... ??? i cant help more ... regards, hussayn Marco Rolappe wrote: one might be able to better help you if the error message was translated. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag von CARLETTA ANGELO Gesendet: Dienstag, 28. Januar 2003 12:16 An: [EMAIL PROTECTED] Betreff: How to run 2 tomcat-coocon web server --- Reçu de INFETUDE.G145193 02/250.96.71 28-01-03 12.16 Hi, I need to run 2 server tomcat-cocoon in one machine One server use \\localhost:8080\ (port 8080) and the other server use \\localhost\ (port 80 in config tomcat server.xml) I have a probleme in de second server with the used JSP Program In Error: Date of error: 28-janv.-03 Time of Error 12:15:57 Error messages: VGJ0607E - Une inadéquation de version s'est produite entre le serveur et le circuit my.pkg.JAH0001WUIBean. Thanks. Angelo 28-01-03 12.16 Envoyé à - [EMAIL PROTECTED] ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. [EMAIL PROTECTED] *** - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using the results of an aggregate part.
thats interesting... i got a similar usecase yesterday: o An application can be asked to give away some configuration parameters in an XML stream. i.e a list of search engines with names, links, search-parameter-descriptors and so on. o now i ask my application once for the config to get the list of search engines. then i create a search engine-selector (using an xsl transform) o then i ask my application to deliver the data for the currently selected search-engine. i use a different xslt to build the inputmask for the engine. o finally i take the results and bundle them to the final page with just another xslt. assume, the application can't be changed, then i am forced to either create a transformer for search-engine-selector + input-mask that does not use aggregation, or i have to call my app twice, getting back the same data twice and transforming it differently. If it where possible to call the application once, then apply two map:part to the result, this would help enormously in my use case. What i can think of is something like dropping the data to a file, then aggregating from the file. that should be possible in one call, but how could that be done ? regards, hussayn Geoff Howard wrote: At first glance, this does not look very natural in Cocoon, but I don't think there's enough information given to advise you. What needs to happen in the rest of the pipeline? Are you truly aggregating the content of those two items, or are you merely trying to use the aggregate feature to trigger the two pipelines in order? What does each individual pipeline do/return? Geoff -Original Message- From: Joe Latty [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 5:42 PM To: Cocoon Users Subject: Using the results of an aggregate part. Greetings Firstly I should warn you I am a complete newbie. On the following url http://wiki.cocoondev.org/Wiki.jsp?page=Aggregator I found this quote: (Aggregator) Allows the combination of multiple XML documents. An individual aggregator contains one or more parts. Each part is a document fragment, these become children of a new document root, whose element name is defined by an attribute on the aggregator. I am trying to get the results from one part and use these to obtain the correct results from the second part. map:aggregate element=site map:part src=cocoon:/getSomeDataFromACall.xml/ !-- and put the result in the session -- map:part src=cocoon:/toUseToObtainDetailsFromThisCall.xml/ !-- using the data in the session object -- /map:aggregate Is this possible? Is the aggregator the place to be looking? Is there a simple way to do this? Thanks for any help. Joe - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: How to run 2 tomcat-coocon web server
Probably you must change two things : 1.) in cocoon/WEB-INF/cocoon.xconf This section may cause the problem ... hsqldb-server class=org.apache.cocoon.components.hsqldb.ServerImpl logger=core.hsqldb-server pool-max=1 pool-min=1 parameter name=port value=9002/ parameter name=silent value=true/ parameter name=trace value=false/ /hsqldb-server 2.) in tomcat/conf/server.xml look for this snippet: !-- Define a Coyote/JK2 AJP 1.3 Connector on port 8009 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8009 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=0 useURIValidationHack=false protocolHandlerClassName= org.apache.jk.server.JkCoyoteHandler/ and change 8009 to something else or comment out the Coyote connector, if you dont use a webserver .. hussayn CARLETTA ANGELO wrote: --- Reçu de INFETUDE.G145193 02/250.96.71 29-01-03 10.10 Hy, I have tomcat 4.1.12, cocoon 2.04, JDK 1.3.1, MySQL 3.21 and VisualAge for genarate the JSP I have the first Tomcat in c:\tomcat and the second in c:\tomcatProd In startup.bat i have add the environement var setting for CLASSPATH -- (cut and paste from dos screen) -- SET CLASSPATH=c:\tomcat\Webapps\VagenWebModule\WEB- INF\lib;c:\tomcat\Webapps\VagenWebModule\WEB- INF\classes\my\pkg;C:\IBMVAGEN\VGWGS45\;C:\IBMVAGEN\VGWGS45\hptGateway.jar;C :\IBMVAGEN\VGWGS45\vgjwgs.jar;C:\IBMVAGEN\VGCSO45\;C:\IBMVAGEN\VGCSO45\hpt.j ar SET COBPATH=c:\tomcat\Webapps\VagenWebModule\WEB-INF\dll_eti; SET LIBPATH=c:\tomcat\Webapps\VagenWebModule\WEB-INF\dll_eti; SET Path=%PATH%;C:\IBMVAGEN\VGWGS45\;C:\IBMVAGEN\VGWGS45\MSVC;C:\IBMVAGEN\VGCSO4 5\;C:\IBMVAGEN\VGCSO45\MSVC;C:\IBMVAGEN\VGCSO45\exe;c:\jdk\bin;c:\tomcat\Web apps\VagenWebModule\WEB- INF\dll_eti;c:\ibmvagen\dll_pli;c:\ibmvagen\dll_cobol -- And the startup of tomcat give [INFO] Registry - -Loading registry information [INFO] Registry - -Creating new Registry instance [INFO] Registry - -Creating MBeanServer [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 server.properties not found, using command line or default properties Opening database: C:\Tomcat\webapps\cocoon\WEB-INF\db\cocoondb HSQLDB server 1.7.1 is running Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly Wed Jan 29 09:46:04 CET 2003 Listening for connections ... -- GatewaySessionData.readObject GatewaySessionData.readObject - initialize transients CSOServerCommunications(GatewaySessionData) VGJ0612I - Une session passerelle est connectTe au SessionIDManager pour l'utili sateur g145193. -- GatewaySessionData.readObject [INFO] Http11Protocol - -Starting Coyote HTTP/1.1 on port 8080 [INFO] ChannelSocket - -JK2: ajp13 listening on tcp port 8009 [INFO] JkMain - -Jk running ID=0 time=32/140 config=C:\Tomcat\bin\..\conf\jk2.p roperties For the tomcatProd, i have replace port 8080 with 80 in server.xml In startup.bat i have add the environement var setting for CLASSPATH -- (cut and paste from dos screen) -- SET CLASSPATH=c:\tomcatProd\Webapps\VagenWebModule\WEB- INF\lib;c:\tomcatProd\Webapps\VagenWebModule\WEB- INF\classes\my\pkg;C:\IBMVAGEN\VGWGS45\;C:\IBMVAGEN\VGWGS45\hptGateway.jar;C :\IBMVAGEN\VGWGS45\vgjwgs.jar;C:\IBMVAGEN\VGCSO45\;C:\IBMVAGEN\VGCSO45\hpt.j ar SET LIB=C:\IBMVAGEN\VGWGS45\LIB;C:\IBMVAGEN\VGWGS45\MSVC\LIB;C:\IBMVAGEN\VGCSO45 \LIB;C:\IBMVAGEN\VGCSO45\MSVC\LIB; SET COBPATH=c:\tomcatProd\Webapps\VagenWebModule\WEB-INF\dll_eti; SET LIBPATH=c:\tomcatProd\Webapps\VagenWebModule\WEB-INF\dll_eti; SET Path=%PATH%;C:\IBMVAGEN\VGWGS45\;C:\IBMVAGEN\VGWGS45\MSVC;C:\IBMVAGEN\VGCSO4 5\;C:\IBMVAGEN\VGCSO45\MSVC;C:\IBMVAGEN\VGCSO45\exe;c:\jdk\bin;c:\tomcatProd \Webapps\VagenWebModule\WEB- INF\dll_eti;c:\ibmvagen\dll_pli;c:\ibmvagen\dll_cobol -- And the startup of tomcat give [INFO] Registry - -Loading registry information [INFO] Registry - -Creating new Registry instance [INFO] Registry - -Creating MBeanServer [INFO] Http11Protocol - -Initializing Coyote HTTP/1.1 on port 80 Starting service Tomcat-Standalone Apache Tomcat/4.1.12 server.properties not found, using command line or default properties Opening database: C:\TomcatProd\webapps\cocoon\WEB-INF\db\cocoondb HSQLDB server 1.7.1 is running Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly Server.run/init: java.net.BindException: Address in use: JVM_Bind java.net.BindException: Address in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:452) at java.net.ServerSocket.init(ServerSocket.java:170) at java.net.ServerSocket.init(ServerSocket.java:82) at org.hsqldb.Server.run(Unknown
Re: WARP, Jserv or mod_jk?
You may also look into http://www.saxess.com/JSPWiki/Wiki.jsp?page=Howto if you need more infos about building and configuring apache/tomcat/mod_jk ... (unfortunately some of the pages are only in german, but maybe it still can help. seems as if it would have been better to write it in english ;-) regards, hussayn Lajos wrote: Hi Richard - mod_jk by far is the best. WARP is buggy and is may not even be actively developed any more. mod_jk is stable, widely used, and generally has few bugs reported. If you need help with the integration, my FlashGuides (www.galatea.com/flashguides) have instructions on connecting Apache 2.x with Tomcat 4.x using Jk. Regards, Lajos Richard Cunliffe wrote: Hi, I?m upgrading! Can anyone suggest the best way to connect Apache 2.0.42 and Tomcat 4.0.6. I will be using Cocoon 2.0.4. I have read that the WARP connecter is the best, but I used Jserv on my older version. There is also the mod_jk. Which is the most reliable etc. Thanks Richard. -- This message has been scanned for viruses and dangerous content by MailScanner http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: proposal: The Newbies Competence Center
seems as if my round up generqted even more input ;-) thanks to all of you. so what do we have now? i reround up here: 1.) there is a strong push towards role based documentation 2.) there is a strong recommendation to use cocoon-wiki 3.) the discussion roles on over the whole documentation set hmm... seems so as if this gets a bigger task, than expected ;-) by the way, i looked up the word newbie. It may be of interst, that this is the short from of new boy. Hey, we can't do that ... I'd recommend to rename this to The Cocoon Competence Center and start with the beginners section on the cocoon wiki... any doubts ? regards, Hussayn Derek Hohls wrote: This is getting periously close to documentation ;-) Seriously, this is the kind of description that is incredibly useful to have up front - never mind arguing over who should have what skills and how they should work together ... that is a project/company issue and will differ from case-case (the current view is that most people are multi-skilled anyway) BUT we can all agree on what skills are needed to work with Cocoon and can link our documentation (see other mail on wiki classifications) to those skills; what Peter elsewhere has called role based documentation. It will be of great help to the new user to see what he/she might be expected to know (or learn) before getting up in the intricacies of sitemaps, generators and the rest of the jargon! [EMAIL PROTECTED] 27/01/2003 11:59:41 Tony Collen wrote: For instance, with a typical installation of Cocoon, we could define the following roles: - Content Creator. This person authors XML for the site to be transformed. This role works when most of the content is static. However, if a lot of the data is being pulled out of a database, they would be in charge of something like data entry into the database, etc. I've been seeing this role work out well in practice. There is grumbling when they can't mark up their content significantly like they used to in Frontpage or Dreamweaver, but after seeing a demo, they usually acquiesce. - Graphic/Web designer. This person is in charge of the style of the site. Not only do they come up with how the site looks through the design of the final HTML, but they also write the XSL to transform the content into the desired format. Sometimes this person is also the content creator. This role, however, falls apart quickly. There are three roles here and it's rare that any one person satisfies all of the roles successfully. 1) The graphic designer: The artist/production manager who is a whiz with Photoshop/Paint Shop Pro/The GIMP. They design the overall look and feel for the site. Anyone who has seen a good graphic artist can attest to the fact that not everyone can do the job. 2) The HTML/CSS web monkey (term of endearment -- not meant to offend): Can take the layout design from the graphic artist and turn it into clean and useable HTML/CSS markup. Frontpage et al are useless in this regard. 3) The XSLT author: Transforms the internal XML document to the web monkey's HTML model. This role is commonly found in the engineering department and is needed for the non-presentational transformations that occur quite often in Cocoon as well. In my opinion, it is by far the greatest amount of work in site production in terms of getting off the ground. - Administrator. In charge of the servlet container, and modifying the main sitemap. Monitors logs, and able to identify when a component would need to be cacheable, poolable, etc. Sometimes this role can further be separated out into servlet container admin and sitemap admin. Developers too often need to edit the sitemap for this. The Administrator definitely deals with installing software packages (would be in charge of installing blocks for example) and maintaining the servlet container/EJB container. But the sitemap is definitely drifting into the lead developer's domain with subsitemaps handled by subproject leads. Could you imagine asking a sysadmin to switch the cinclude transformer to a non-caching variety on URL pattern X? I can, however, see a lead developer editing the sitemap locally on a development box and asking the sysadmin to upload the changes. - Programmer. I think this is what we now call developer -- this person is capable of developing custom components, e.g. Generators, XSPs, etc. This person might also code the Flow layer logic. But maybe not. And this person would definitely need to have access to a sitemap for testing and deployment. They can't work in a bubble. New generators and XSPs go hand in hand with at least one new URL pattern in the sitemap. Ideally, all of these roles work together in order to get things done, but they only have to worry about their specific role. I have come to believe this is a fairy tale. No individual in a development group, in my opinion, can *ever* worry about just their
Re: proposal: The Newbies Competence Center
Hy, the Cocoon Competence Center is Born ;-) I have changed the link on the WIki leftMenu from new to cocoon? into For Beginners and added the cocoon in 15 minutes: page. I invented a first set of metadata: - TARGET-AUDIENCE: beginners - COCOON-RELEASES: 2.0.3, 2.0.4 - AUTHOR: Hussayn Dabbous - AUTHOR-CONTACT: [EMAIL PROTECTED] - REVIEWED-BY: - REVIEWER-CONTACT: Maybe this needs review. regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: I cant get cocoon to process??
once i looked hours and hours for a problem similar to what you report. finally i detected, that i introduced two match patterns, that would match on the same url within my sitemap. Since i was looking at the secnd definition wondering, why nothing helped i completely ignored the true causeing match further up in the sitemap. maybe this is what your problem causes: simply another more generic matcher, that sucks the file before your matcher comes into play ? just to mention it: first match wins... regards, hussayn Richard Cunliffe wrote: Derek, Ok I changed the match pattern, but it made no difference (its still loading the xml source as text in the browser). I managed to get text in the logs, and I can not see anything in there to say that I have just tried to access the address http://192.168.0.5:8080/soundpool/soundpool.xml. I have attached the log with this e-mail. I obviously don't know what is supposed be in there, but there are a lot of unknowns (I don't know if this is healthy?). Thank you so much for taking the time to help! Richard. -Original Message- From: Derek Hohls [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 09:55 To: [EMAIL PROTECTED] Subject: RE: I cant get cocoon to process?? Richard Well, I think Tomcat/Cocoon are working OK, otherwise the basic Hello World would not not be working. You say you cannot see anything in the log files that makes sense - well, this is an area that its very useful (and I speak from bitter experience) and worth the time getting up to speed in! If unsure, then: stop Tomcat, delete the log files, restart - they *should* be clear. If not, note what is there and carry on. Try your URL and then immediately look in the files again - any new messages should be related to what you have just tried. If these do not make sense, then post them here. Anyway - to your problem below. I think the issue is that your typed URL: ...soundpool/soundpool.xml does not match the pattern in the pipeline - which is expecting only: soundpool So, either change your typed URL to: http://192.168.0.5:8080/soundpool or change the match to: map:match pattern=soundpool/soundpool.xml or some other combination that links one to the other... you could have: http://192.168.0.5:8080/soundpool/soundpool and: map:match pattern=soundpool/soundpool for example - this is quite neat because it clearly shows that the URI that Cocoon processes can be quite different from where the physical files are located; a key concept in good pipeline design. Derek [EMAIL PROTECTED] 28/01/2003 11:22:21 Derek, Thank you for the big welcome! I have had a quick look at the logs, but to be honest I'm not sure how to interrupt them. When I did the install examples I got cocoon to do the Hello world example. So yes that's working. Here is the pipeline I have created for a soundpool example (this will just show the word soundpool) map:pipeline map:match pattern=soundpool map:generate src=soundpool.xml/map:transform src=soundpool.xsl/map:serialize/ /map:match/map:pipeline So when I type the my local address http://192.168.0.5:8080/soundpool/soundpool.xml this is what is displayed: ?xml version=1.0 ? - document textsoundpool/text /document It looks like tomcat is not forwarding the request to cocoon to me, what do you think? Richard. -Original Message- From: Derek Hohls [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 09:03 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? Richard Welcome to the wonderful world of Cocoon application debugging ! First off, I assume that the Cocoon samples are up-and- running, so that you have tested that the Cocoon servlet as such is working OK. Next thing is to check the log files; you will find them located under the [cocoon] directory (which I guess you have installed somewhere under tomcat) in a subdir called WEB-INF/logs. Finally - and this is the hard part! - you will need to try and understand what is causing the missing link - it *seems* like it might be the entry in your site map - perhaps you can post that part of the site map that should be doing the xml/xsl matching so we can try and figure where there might be an error. Derek [EMAIL PROTECTED] 28/01/2003 10:40:03 Apache - v1.3Cocoon - v2.0Tomcat - v3.3aJserv - 1.1.1 Operating system -Windows XP I can not get cocoon to work. The problem I have is that when I try and load an xml page, it will not use the style sheet and show the desired page. Instead the browser only shows the xml document (source code). I have linked cocoon and tomcat, and tomcat with apache using Jserv. What suggestions do you have? Richard.
Re: I cant get cocoon to process??
I learned to get very simple minded when it comes to cocoon debugging ;-) so i would ask: 1.) are you shure, cocoon is receiving the request at all you can verify by looking at WEB-INF/logs/access.log 2.) do any stack traces pop up in the cocoon log files ? besides access.log there are three others ... 3.) Are you using IE as browser? then try to delete the browser cache. sometimes this has driven me crasy. 4.) have you checked your servlet mounts from the webserver to tomcat are correct ? no other ideas. if cocoon is processing your request at all, the cocoon logs should reveal what happens... regards, hussayn Richard Cunliffe wrote: Hussayn, I have just had a look, and its only been matched once. Any other suggestions? Thanks, Richard. -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 15:00 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? once i looked hours and hours for a problem similar to what you report. finally i detected, that i introduced two match patterns, that would match on the same url within my sitemap. Since i was looking at the secnd definition wondering, why nothing helped i completely ignored the true causeing match further up in the sitemap. maybe this is what your problem causes: simply another more generic matcher, that sucks the file before your matcher comes into play ? just to mention it: first match wins... regards, hussayn Richard Cunliffe wrote: Derek, Ok I changed the match pattern, but it made no difference (its still loading the xml source as text in the browser). I managed to get text in the logs, and I can not see anything in there to say that I have just tried to access the address http://192.168.0.5:8080/soundpool/soundpool.xml. I have attached the log with this e-mail. I obviously don't know what is supposed be in there, but there are a lot of unknowns (I don't know if this is healthy?). Thank you so much for taking the time to help! Richard. -Original Message- From: Derek Hohls [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 09:55 To: [EMAIL PROTECTED] Subject: RE: I cant get cocoon to process?? Richard Well, I think Tomcat/Cocoon are working OK, otherwise the basic Hello World would not not be working. You say you cannot see anything in the log files that makes sense - well, this is an area that its very useful (and I speak from bitter experience) and worth the time getting up to speed in! If unsure, then: stop Tomcat, delete the log files, restart - they *should* be clear. If not, note what is there and carry on. Try your URL and then immediately look in the files again - any new messages should be related to what you have just tried. If these do not make sense, then post them here. Anyway - to your problem below. I think the issue is that your typed URL: ...soundpool/soundpool.xml does not match the pattern in the pipeline - which is expecting only: soundpool So, either change your typed URL to: http://192.168.0.5:8080/soundpool or change the match to: map:match pattern=soundpool/soundpool.xml or some other combination that links one to the other... you could have: http://192.168.0.5:8080/soundpool/soundpool and: map:match pattern=soundpool/soundpool for example - this is quite neat because it clearly shows that the URI that Cocoon processes can be quite different from where the physical files are located; a key concept in good pipeline design. Derek [EMAIL PROTECTED] 28/01/2003 11:22:21 Derek, Thank you for the big welcome! I have had a quick look at the logs, but to be honest I'm not sure how to interrupt them. When I did the install examples I got cocoon to do the Hello world example. So yes that's working. Here is the pipeline I have created for a soundpool example (this will just show the word soundpool) map:pipeline map:match pattern=soundpool map:generate src=soundpool.xml/map:transform src=soundpool.xsl/map:serialize/ /map:match/map:pipeline So when I type the my local address http://192.168.0.5:8080/soundpool/soundpool.xml this is what is displayed: ?xml version=1.0 ? - document textsoundpool/text /document It looks like tomcat is not forwarding the request to cocoon to me, what do you think? Richard. -Original Message- From: Derek Hohls [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 09:03 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? Richard Welcome to the wonderful world of Cocoon application debugging ! First off, I assume that the Cocoon samples are up-and- running, so that you have tested that the Cocoon servlet as such is working OK. Next thing is to check the log files; you will find them located under the [cocoon] directory (which I guess you have installed somewhere under tomcat) in a subdir called WEB-INF/logs. Finally
Re: I cant get cocoon to process??
hmm.. I would do this: take your webserver out of the way for a moment. you want to test cocoon, not the webserver/tomcat connection, right ? then: 1.) setup tomcat so that you can direct access it from your browser. Look for these lines in tomcat/conf/server.xml: !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / this should be already setup. test it: http://yourserver:8080 tomcat should show up. if it does not, double check that your tomcat has a HTTP connection and on whoich port it is serving. 2.) now test your cocoon: http://yourserver:8080/cocoon i suppose your cocoon startpage comes up. you already reported this. but double check it... 3.) now dive into your sitemap: http://192.168.0.5:8080/cocoon/soundpool/soundpool.xml or whatever... by the way, have you deployed cocoon under the name soundpool? or is the link i found further down missspelled ??? Maybe you did something wrong within your tomcat Context definition also in tomcat/conf/server.xml ? regards, hussayn Richard Cunliffe wrote: Hussayn, It sounds to me, like cocoon is not being forwarded the requested page and perhaps thats why there is no processing going on. I installed cocoon by copying in cocoon.war, and set-up apache and tomcat, by using jserv. Is there anything else I should do here? Richard. -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 15:33 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? I learned to get very simple minded when it comes to cocoon debugging ;-) so i would ask: 1.) are you shure, cocoon is receiving the request at all you can verify by looking at WEB-INF/logs/access.log 2.) do any stack traces pop up in the cocoon log files ? besides access.log there are three others ... 3.) Are you using IE as browser? then try to delete the browser cache. sometimes this has driven me crasy. 4.) have you checked your servlet mounts from the webserver to tomcat are correct ? no other ideas. if cocoon is processing your request at all, the cocoon logs should reveal what happens... regards, hussayn Richard Cunliffe wrote: Hussayn, I have just had a look, and its only been matched once. Any other suggestions? Thanks, Richard. -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 15:00 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? once i looked hours and hours for a problem similar to what you report. finally i detected, that i introduced two match patterns, that would match on the same url within my sitemap. Since i was looking at the secnd definition wondering, why nothing helped i completely ignored the true causeing match further up in the sitemap. maybe this is what your problem causes: simply another more generic matcher, that sucks the file before your matcher comes into play ? just to mention it: first match wins... regards, hussayn Richard Cunliffe wrote: Derek, Ok I changed the match pattern, but it made no difference (its still loading the xml source as text in the browser). I managed to get text in the logs, and I can not see anything in there to say that I have just tried to access the address http://192.168.0.5:8080/soundpool/soundpool.xml. I have attached the log with this e-mail. I obviously don't know what is supposed be in there, but there are a lot of unknowns (I don't know if this is healthy?). Thank you so much for taking the time to help! Richard. -Original Message- From: Derek Hohls [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 09:55 To: [EMAIL PROTECTED] Subject: RE: I cant get cocoon to process?? Richard Well, I think Tomcat/Cocoon are working OK, otherwise the basic Hello World would not not be working. You say you cannot see anything in the log files that makes sense - well, this is an area that its very useful (and I speak from bitter experience) and worth the time getting up to speed in! If unsure, then: stop Tomcat, delete the log files, restart - they *should* be clear. If not, note what is there and carry on. Try your URL and then immediately look in the files again - any new messages should be related to what you have just tried. If these do not make sense, then post them here. Anyway - to your problem below. I think the issue is that your typed URL: ...soundpool/soundpool.xml does not match the pattern in the pipeline - which is expecting only: soundpool So, either change your typed URL to: http://192.168.0.5:8080/soundpool or change the match to: map:match pattern=soundpool
Re: I cant get cocoon to process??
if you did not touch server.xml forget about this for a moment. look again at following snippet from your last answer: Yes that address was a typing mistake. When I load http://192.168.0.5:8080/soundpool/soundpool.xml it shows the if you did NOT TOUCH server.xml and you did deploy cocoon under the directory webapps/cocoon, then you should connect to your cocoon as follows: http://192.168.0.5:8080/cocoon/soundpool/soundpool.xml ~~ assuming your xslt is named soundpool.xsl and lies besides soundpool.xml and both files live in a folder named soundpool which in turn lives in the cocoon webapplication + cocoon (webapp folder) +- soundpool (folder) +- soundpool.xml (file) +- soundpool.xsl (file) Then your pipeline looks like this: pipelines pipeline map:match pattern=soundpool/soundpool.xml map:generate src=soundpool/soundpool.xml/ map:transform src=soundpool/soundpool.xsl/ map:serialize type=xml/ /map:match /pipeline /pipelines Or have you created a subfolder named soundpool in your cocoon webapp, or is your cocoon webapp named soundpool +- soundpool (webapp folder) +- soundpool.xml (file) +- soundpool.xsl (file) in this case your sitemap would look like this: pipelines pipeline map:match pattern=soundpool.xml map:generate src=soundpool.xml/ map:transform src=soundpool.xsl/ map:serialize type=xml/ /map:match /pipeline /pipelines and your request would look like this: http://192.168.0.5:8080/soundpool/soundpool.xml hussayn -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 15:57 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? hmm.. I would do this: take your webserver out of the way for a moment. you want to test cocoon, not the webserver/tomcat connection, right ? then: 1.) setup tomcat so that you can direct access it from your browser. Look for these lines in tomcat/conf/server.xml: !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=true redirectPort=8443 acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / this should be already setup. test it: http://yourserver:8080 tomcat should show up. if it does not, double check that your tomcat has a HTTP connection and on whoich port it is serving. 2.) now test your cocoon: http://yourserver:8080/cocoon i suppose your cocoon startpage comes up. you already reported this. but double check it... 3.) now dive into your sitemap: http://192.168.0.5:8080/cocoon/soundpool/soundpool.xml or whatever... by the way, have you deployed cocoon under the name soundpool? or is the link i found further down missspelled ??? Maybe you did something wrong within your tomcat Context definition also in tomcat/conf/server.xml ? regards, hussayn Richard Cunliffe wrote: Hussayn, It sounds to me, like cocoon is not being forwarded the requested page and perhaps thats why there is no processing going on. I installed cocoon by copying in cocoon.war, and set-up apache and tomcat, by using jserv. Is there anything else I should do here? Richard. -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 15:33 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? I learned to get very simple minded when it comes to cocoon debugging ;-) so i would ask: 1.) are you shure, cocoon is receiving the request at all you can verify by looking at WEB-INF/logs/access.log 2.) do any stack traces pop up in the cocoon log files ? besides access.log there are three others ... 3.) Are you using IE as browser? then try to delete the browser cache. sometimes this has driven me crasy. 4.) have you checked your servlet mounts from the webserver to tomcat are correct ? no other ideas. if cocoon is processing your request at all, the cocoon logs should reveal what happens... regards, hussayn Richard Cunliffe wrote: Hussayn, I have just had a look, and its only been matched once. Any other suggestions? Thanks, Richard. -Original Message- From: SAXESS - Hussayn Dabbous [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 15:00 To: [EMAIL PROTECTED] Subject: Re: I cant get cocoon to process?? once i looked hours and hours for a problem similar to what you report. finally i detected, that i introduced two match patterns, that would match on the same url within my sitemap. Since i was looking at the secnd definition wondering, why nothing helped i completely ignored the true causeing match further up in the sitemap. maybe this is what your problem causes: simply another
Re: simple question
you can find the access times in the logfile WEB-INF/logs/access.log hussayn Jordi Valldaura wrote: I used cocoon 1.8.* in the past, now I'm using 2.0.4. In the first one each generated page had a line with the time cocoon taked to generate it. I dont see this line in cocoon 2 generated pages is there any easy way to know how much time takes cocoon to generate a page??? - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: proposal: The Newbies Competence Center
Hy, Robert; Robert Simmons wrote: I don't think that the word newbie is such a stigma. People know when they are newbies and not. Rarely do people take it offensively unless its an You may be right, that people have been used to the word newbie. What brought me off from this title were two points: 1.) Looking at the history of the word newbie i got a bit uncomfortable with it. Not that i wouldn't say newbie any more, but i'd prefer to keep the documentation more ... let's say professional ? 2.) As you state yourself this documentation effort makes it's start with the concerns of beginners. But it may affect also the rest of the documentation. Hence the title Cocoon Competence Center seems to be more adequate and promising ... What I would like to see now is a style guide for XML documents that will be common to all published cocoon info. In this manner we can apply a standard XSLT transform to all documents and the writers would just be using XML to accomplish the task. This would give us allot of flexibility. What I am I think you are right, but i'm afraid, we could go on discussing for weeks... The reason why i started with wiki was the very strong recomendation to start with what we have and move slowly and iteratively towards the better world of total cocoonisation ... There is no doubt, that eventually the documentation shall find its way into something better publishable, either by cocoon or whatever appropriate. All of this has been discussed in the proposal http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=104369287706014w=2 If there is an infrastructure right at hand,that allows me to start of with producing content immediately, i would be happy to switch. Until then i follow the guidance of the more experienced cocoon users and developers and write my docs in Wiki. If this approach is replaced tomorrow, it's ok for me. I even stated in the proposal, that we need the step of clearification and then decide what to do. Let's take the Wiki-approach as an experiment... regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 D-50935 Köln tel.:+49 221 56011 0 fax.:+49 221-56011 20 email:[EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wiki broken with IE (was: The Newbies Competence Center)
Robert Simmons wrote: Incidentally, I find that when I hit the Wiki page, I don't see half of the left menu until I pass my mouse over the links. IE6 problem? -- I had the very same problem today in the morning. Seems to be an IE problem. You can avoid it as follows: Make your IE-window smaller. The behaviour is affected by the hight of the window, not by the width ... Steven knows already about this. I think he's doing something ... Husayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhfer Allee 125 D-50935 Kln tel.:+49 221 56011 0 fax.:+49 221-56011 20 email:[EMAIL PROTECTED]
Creating a CocoonBook review page ?
Hy e nio, Antonio and all the other readers of the cocoon printed literatur For me it would make sense to create a CocoonBookReview page in the wiki. May i tear all infos about the available books from this mailing list and make a start ? regards, hussayn e nio wrote: Imho, yeah the CTWIG is helpful as a starting point for a newbie. The other tutorial that I thought that was helpful was from the www.cocooncenter.de topic auto-mount, except that it needs a litle change instead of WildcardURIMatcherFactory it should use WildcardURIMatcher on the sitemap.xmap. I believe galatea.com have listed the minimum jar files required to make up a working cocoon environment. It sure do take lots of efforts to know where these goodies resources are. Jeremy and Lajos Cocoon Developer's handbook is excellent for newbies (I am a newbie). Chapter 11 is very insightful covering the heart of Cocoon, sitemap.xmap. The other two books imho is more for framework designers and cocoon component developers. I did not get to read the two in depth but looking at the samples(as a newbie I like to see lots of working samples) I would say Jeremy Lajos is by far the friendliest. e nio -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
newbies documentation (was: Cocoon is too complex for consumption?)
Hy; as a newbie (of three months age ;) ) i'd like to contribute my thoughts to the documentation area: 1.) From my now 20 years experience in computer art i learned that the newbies can tell much more about the features of a program, than the developers can. Why? because the newbie always tries the wrong pathes through the software therefore detect the weaknesses and strenghts of the app and often walk through pathes the developers never thought of inventing new use cases , etc. In turn the developers always are biased from their architectural insights... 2.) In several projects i was faced with the situation of lacking or inappropriate user documentation. One strategy for improvement was always to let the users start writing down what they think the app does and how they would use it. Then the developers had the time to start thinking over what they implemented. This is an iterative approach that fits better to the real world, than smacking at the developers and force them to start documenting ... My *personal* conclusions on this: 1.) Instead of shouting against the developers i started writing down my experiences within my company wiki. I did this because i wanted a clear separation from all the masters of the art articles turning up in the cocoon wiki. Besides this some of the points i tackled have to give at least little insight into tomcat and other loosely coupled themes which i didn't want to add to the ever growing cocoon wiki. 2.) Whoever writes docs for the newbies MUST get help from an experienced user or a developer at least for review. This could be the start of a productive user centric quality assurance. This may eventually get all these very interesting but (sorry) unneaded explanations of avalon and other base technologies out of the docs or at least into separated docs. 3.) Writing docs MUST be made as simple as possible. But it should be surveyed from one or a few editors who keep the docs in right shape, and right organisation. so i would propose (as Derek does): 1.) Provide a platform separate from the already existing documentation areas, which is clearly labeled as the newbies competence center, accessible to everyone with most ease (start getting productive in a minute) 2.) I would recommend to use a separate Wiki for this purpose. 3.) Instead of letting such a wiki free floating, get at least one person into the role of the responsible editor And despite any possibly upcoming thoughts like this is open source, everyone (thus noone?) is responsible i would gladly get into the role of the responsible editor for some time at least. And if it makes sense, i also would start hosting such a cocoon CC Wiki. Meanwhile i will continue writing down my personal insights and eventually donate all this stuff to whatever will come up as a newbies documentation infrastructure ... regards, hussayn Derek Hohls wrote: Tony In case you missed my other wandering thought pattern; its my strong feeling we need a SINGLE section of the website - preferably one well-insulated from the ramblings on the other site which is always under construction that (including any formal guides) solely addresses ONLY the needs of newbies and has ALL the documents AND faqs AND minimal downloads AND simple sitemaps etc in ONE place - no obscure wikis/mailing list links. (Gee, we are working with a web publishing platform here - how hard can this be to put together *technically*?? ) The trick is writing good, clear, simple pages - and that's a matter of write - read - edit recycle until your target newbie - not your average developer/contributor - can make sense of it... Derek [EMAIL PROTECTED] 27/01/2003 06:29:12 In light of this ginormous thread, do we need more newbie guides to getting started with Cocoon? Obviously the CTWIG or whatever is out of date, so perhaps there's a demand for something like a Busy Developer's Guide to getting started with Cocoon? I'd be more that willing to write stuff up that for direct inclusion with the Cocoon documentation that is distributed with the releases. If so, I'll start writing up a Cocoon BDG (or even a series) in Document 1.1 format. P.S. Docs team: Perhaps it's time to start assimilating Wiki content into the distribution docs? Tony -- Cocoon: Internet Glue (A Cocoon Weblog) http://manero.org/weblog/ - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over
Re: Getting a generator class to reload.
Assuming you run tomcat: When you enable reloadable='true' in your Context the whole webapp should restart every time a class is changed. Once in a while i get unpredictable behaviour like webapp doesnt restart, or hangs during restart or even VM exits. I never figured out, what my container complains about, but in general i'm happy with reloadable='true' during development. For production it would be a very bad idea to enable this feature ;-) I heard rumours about the possibility with tomcat to only reload the changed resources while keeping the webapp up and running, but i never found the howto... regards, hussayn Robert Simmons wrote: Nope .. didn't work. Still has the old class cached. I hope I don have to redeploy the whole damn thing every time I update a class. -- Robert - Original Message - From: Niclas Hedhman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 9:20 AM Subject: Re: Getting a generator class to reload. On Monday 27 January 2003 16:21, Robert Simmons wrote: I am working to create a custom generator and I have deployed my WAR in exploded format. The problem is that now when I change the class file that the generator uses, cocoon keeps using the old class file. How can I get the classloader in cocoon to reload the class? When that happens, I touch the sitemap. Always works. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies documentation - yet another wiki?
Hy, Bertrand short answer: join the party of course! long answer: when we want to count on newbies efforts they should be given instant access: edit deploy, online. this is what wiki does. hence i would consider the work on the cocoon documentation as secnd step towards the ultimate documentation set. this should be done as proposed from the cocoon wiki by assimilating the wiki into the cocoon docs step by step... I would like to help there too sometime... when i started with cocoon i also took a look at JSPWiki, which powers the cocoon wiki. In the first place i could not figure out, how to set up this wiki with different layouts or even how to create different sections with different start pages. This may be possible somehow, but would possibly generate additional work *before* starting. What about the following idea: set up 2nd Wiki in the same domain (parallel to the cocoon-wiki) dedicated to the newbies. this would come close to my thoughts but would not force us to start with work on the infrastructure. instead just deploy JSPWiki a secnd time, use different layout, interlink the two wikis, start ... regards, hussayn Bertrand Delacretaz wrote: Hi Hussayn, I mostly agree with your point of view, except on the separate wiki thing. (And by the way, thanks a lot for your less talking, more doing approach!) What worries me *a lot* with starting yet another documentation site is the dispersion of resources - wouldn't it be much more efficient to have you, Derek and possibly others joing the (mythical) Cocoon docs team with the aim of creating these newbies docs? See also http://wiki.cocoondev.org/Wiki.jsp?page=CocoonDocsPlan, I think your concept can fit nicely into this. I'm convinced that it is possible to create the newbies competence center that you mention *inside* the existing wiki - a well-designed start page and navigation should help newbies find their way. Maybe this needs some improvements to the existing wiki system, to help newbies find pages that are targeted for them, namely: a) Being able to search the wiki for NCC pages only or everything so that newbies are not distracted by deep technical discussions. b) Being able to clearly label pages as being part of the NCC, different color, icons or something. This might well be possible with JSPwiki, maybe by writing some kind of extension? We need to ask Steven or the JSPWiki folks if you think this is worth studying. What do you think? Join the party, or throw yet another one? :-) -Bertrand - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies documentation (was: Cocoon is too complex for consumption?)
hy, Derek; what you say makes perfect sense ;-) only one suggestion for the first two pages: 1.) HOWTO setup cocoon in 15 minutes ;-) should be easy by condensing the other thread 2.) HOWTO setup your intranet with XML in 1 day it took me two weeks to figure it out, but i could give away 2 style sheets 1 document xschema 1 sitemap that would be sufficient to drive a very basic intranet site like mine at http://www.saxess.de simply by taking the files, putting them into cocoon and then generating your content... regards, hussayn Derek Hohls wrote: A quick addition to what Hussayn suggests - which is well explained and makes perfect sense - is to take this one step further - lets have a wiki for people to add/suggest etc BUT we need to take from it the most polished and relevant material and make it into a formal and well laid-out website (yes, I do use wikis and I do host one inside my company - but they are not always very accessible or well-structured from a newbie point-of-view) - if we do our design correctly ;-) this should not require much more than a stylesheet or two for the conversion. Maybe the first topic on the Cocoon Newbie Wiki could be : Framework for a Cocoon Newbie Web (non-wiki) Site?? I second Hussayn as editor for the new site (wow, a *real* volunteer) Derek [EMAIL PROTECTED] 27/01/2003 10:52:47 Hy; as a newbie (of three months age ;) ) i'd like to contribute my thoughts to the documentation area: 1.) From my now 20 years experience in computer art i learned that the newbies can tell much more about the features of a program, than the developers can. Why? because the newbie always tries the wrong pathes through the software therefore detect the weaknesses and strenghts of the app and often walk through pathes the developers never thought of inventing new use cases , etc. In turn the developers always are biased from their architectural insights... 2.) In several projects i was faced with the situation of lacking or inappropriate user documentation. One strategy for improvement was always to let the users start writing down what they think the app does and how they would use it. Then the developers had the time to start thinking over what they implemented. This is an iterative approach that fits better to the real world, than smacking at the developers and force them to start documenting ... My *personal* conclusions on this: 1.) Instead of shouting against the developers i started writing down my experiences within my company wiki. I did this because i wanted a clear separation from all the masters of the art articles turning up in the cocoon wiki. Besides this some of the points i tackled have to give at least little insight into tomcat and other loosely coupled themes which i didn't want to add to the ever growing cocoon wiki. 2.) Whoever writes docs for the newbies MUST get help from an experienced user or a developer at least for review. This could be the start of a productive user centric quality assurance. This may eventually get all these very interesting but (sorry) unneaded explanations of avalon and other base technologies out of the docs or at least into separated docs. 3.) Writing docs MUST be made as simple as possible. But it should be surveyed from one or a few editors who keep the docs in right shape, and right organisation. so i would propose (as Derek does): 1.) Provide a platform separate from the already existing documentation areas, which is clearly labeled as the newbies competence center, accessible to everyone with most ease (start getting productive in a minute) 2.) I would recommend to use a separate Wiki for this purpose. 3.) Instead of letting such a wiki free floating, get at least one person into the role of the responsible editor And despite any possibly upcoming thoughts like this is open source, everyone (thus noone?) is responsible i would gladly get into the role of the responsible editor for some time at least. And if it makes sense, i also would start hosting such a cocoon CC Wiki. Meanwhile i will continue writing down my personal insights and eventually donate all this stuff to whatever will come up as a newbies documentation infrastructure ... regards, hussayn Derek Hohls wrote: Tony In case you missed my other wandering thought pattern; its my strong feeling we need a SINGLE section of the website - preferably one well-insulated from the ramblings on the other site which is always under construction that (including any formal guides) solely addresses ONLY the needs of newbies and has ALL the documents AND faqs AND minimal downloads AND simple sitemaps etc in ONE place - no obscure wikis/mailing list links. (Gee, we are working with a web publishing platform here - how hard can this be to put together
Re: newbies documentation (was: Cocoon is too complex for consumption?)
hy, steven; you are right: no good idea to create another documentation source. i remember, i also complained about that when i started with cocoon: documentation sites all around and uncoordinated. The point is uncoordinated here: I propose to coordinate the newbies site with the existing cocoon wiki. If this can be done technically within the same wiki, different layout, different startpage and so on, its ok for me. if it can be set up as parallel deployed JSPWiki, what the hell, a link is a link and you can interlink two wikis with ease... The major point is to remember, that the newbies wiki is a part of the cocoon wiki, independent of the underlaying technology, thus coordinating the content, not the technology. regards, hussayn Steven Noels wrote: SAXESS - Hussayn Dabbous wrote: My *personal* conclusions on this: 1.) Instead of shouting against the developers i started writing down my experiences within my company wiki. I did this because i wanted a clear separation from all the masters of the art articles turning up in the cocoon wiki. Besides this some of the points i tackled have to give at least little insight into tomcat and other loosely coupled themes which i didn't want to add to the ever growing cocoon wiki. Hussayn, pardon my insistence, but the idea of starting yet another Cocoon documentation resource is troubling me a bit, especially if that means setting up another Wiki. Given the easy proliferation of Wiki content, people will not know anymore where to submit and retrieve information. Why not start a section within the existing Wiki? I'd be _very_ willing to provide you guys _any_ assistance you might need. And even if the users would insist in having 'their own Wiki' (although I think the existing wiki.cocoondev.org is there for _anybody_), I'd be happy in providing hosting for that under the neutral cocoondev.org domain. /Steven -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies documentation - yet another wiki?
Hy, Derek; Something else crawled into my mind: I agree with you, that using a wiki as playing ground for growing knowledge, it makes perfect sense to extract mature infos from that site and fill them into the cocoon information site. But i would disagree, if this would lead to a newbies site and an experts site. By the way, why not use the sunshine portal for that purpose? lets get a bit visionary: what about having: o the cocoon documentation set for distribution manual pages possibly pdf for printout version o the cocoon online site including online access to the docs (multiple versions of course, difference viewer as option) o the cocoon documentation playground (wikipages) o access to other related sites, bookstores, this mailing list, commercial project enabler, ... All of this tied together by the sunshine portal, or jetspeed, or whatever Give it a newbies view, an experts view, a developers view, a personal view I would personally be very excited, if some people could come together and start something like that... im ever willing to learn and put some spare time into this... regards, hussayn Derek Hohls wrote: Bertrand I think you are making the same point as me... just proposing a different solution. I still feel that if we are using a system that is based on the philisopy of write once, publish anywhere we should be able to create documents in one place and have them published in more than one place in more than one style. If the JSPWiki folks can do all that you suggest, then great - but in the meanwhile a simple and effective traditional web site should be a snap to set up once your docs are in XML PS we need to avoid creating more jargon - I always think of NCC as part of the Starship Enterprise 's call sign (there, that gives *my* age away!) Derek [EMAIL PROTECTED] 27/01/2003 11:14:33 Hi Hussayn, I mostly agree with your point of view, except on the separate wiki thing. (And by the way, thanks a lot for your less talking, more doing approach!) What worries me *a lot* with starting yet another documentation site is the dispersion of resources - wouldn't it be much more efficient to have you, Derek and possibly others joing the (mythical) Cocoon docs team with the aim of creating these newbies docs? See also http://wiki.cocoondev.org/Wiki.jsp?page=CocoonDocsPlan, I think your concept can fit nicely into this. I'm convinced that it is possible to create the newbies competence center that you mention *inside* the existing wiki - a well-designed start page and navigation should help newbies find their way. Maybe this needs some improvements to the existing wiki system, to help newbies find pages that are targeted for them, namely: a) Being able to search the wiki for NCC pages only or everything so that newbies are not distracted by deep technical discussions. b) Being able to clearly label pages as being part of the NCC, different color, icons or something. This might well be possible with JSPwiki, maybe by writing some kind of extension? We need to ask Steven or the JSPWiki folks if you think this is worth studying. What do you think? Join the party, or throw yet another one? :-) -Bertrand - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie question
from my experience i can say, cocoon can be used for highly dynamic pages. You have to individually check on performance issues, but in general until today i have been quite satisfied with what i can gain from using it. I must admit, that i currently only use the basics. never tried the esql thing, and more sophisticated onse, but so far im very shure, it can be used especially in a multi channel environment. hussayn Tellis George wrote: Hi, I am quite new to cocoon. I am evaulating web publishing frameworks for my company. Although Cocoon sounds very promising I am not entiely sure because the pages in my web application are not static. All of them are dynamically generated on the fly. The backend services although still under design may be developed using JINI, object databases, LDAP etc The main reason why I was drawn to cocoon was its multichanel capabilities. We may want to target the pages to a number of devices - mobiles, PDAs, PCs etc My original (very simplistic) design was to simply have servlets generate XML and then transform these using XSLT. This is where I thought cocoon would help. My question is - is cocoon good for static pages or can it be used for highly interactive dynamic pages? Regards Tellis _ Stay in touch with absent friends - get MSN Messenger http://messenger.msn.co.uk - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies documentation - requirements?
Hy, Bertrand; yes, you are right: first determine the requirements, then start thinking about how to reach them ... One additional comment to your list: 4) SHOULD make these docs and their comments searchable, separately from the technical and/or unchecked existing docs to prevent beginners from being overwhelmed with irrelevant search results. I would say, this is a MUST (giving one argument against separate wikis ;-) And one question: 6) SHOULD be integrated with existing Cocoon community tools to avoid fragmentation of skills and resources (for me it is actually a MUST ;-) I'm just curious: What tools do you mean ? (maybe i should have a look into the cocoon documentation framework first?) regards, hussayn Bertrand Delacretaz wrote: Cocoon newbie docs requirements: 1) GOAL: create a source of reliable information for Cocoon newbies, along the lines of how to setup Cocoon in 15 minutes and HOWTO setup your intranet with XML in 1 day 2) MUST allow users to comment/improve these docs, in wiki mode to make it as easy as possible 3) MUST clearly identify these docs as being for beginners and reviewed by an editor of the Cocoon team to prevent beginners from getting lost in obsolete/unreliable docs 4) SHOULD make these docs and their comments searchable, separately from the technical and/or unchecked existing docs to prevent beginners from being overwhelmed with irrelevant search results. 5) MUST allow all wiki docs (these and existing ones) to be searchable simultaneously, to prevent users from having to search in X different places for info. 6) SHOULD be integrated with existing Cocoon community tools to avoid fragmentation of skills and resources (for me it is actually a MUST ;-) What do you think? -Bertrand - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbie question
hy, Tellis im just working on a project, where: 1.) an existing webapp can't be merged with the cocoon-webapp due to incompatible jar versions 2.) the existing webapp may not be modified, except the creation of an additional XML-layer for read/write access. I am working on howto get a cocoon-based presentation layer in the middle between the legacyapp and the browser frontend. Things start working and i make quick progress at the moment. If you are interested, i can tell more about this... regards, hussayn Tellis George wrote: Thanks for the excellent information. One of my main concern was how to integrate cocoon with existing services and servlets without necessarily making them part of cocoon ... -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: newbies documentation - yet another wiki?
i personally enjoy XML-SPY, although it's tied to MS... regards, hussayn Robert Simmons wrote: Ya, I know MSoffice can save into HTML. I want it to save into XML. -- Robert - Original Message - From: Emmanuil Batsis (Manos) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 1:31 PM Subject: Re: newbies documentation - yet another wiki? Star/OpenOffice as well as the new MSOffice. Then again, WYSIWYG HTML Editors - Tidy works great too. Manos Robert Simmons wrote: What I don't get is why not put the new documentation in cocoon distribution? Everything else is in there: *smirk* Cocoon is built for web publishing, we could conspire to write volumes right in the product. Which reminds me, anyone know a word processor that saves primarily in XML and is good? -- Robert - Original Message - From: Bertrand Delacretaz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 10:14 AM Subject: Re: newbies documentation - yet another wiki? Hi Hussayn, I mostly agree with your point of view, except on the separate wiki thing. (And by the way, thanks a lot for your less talking, more doing approach!) What worries me *a lot* with starting yet another documentation site is the dispersion of resources - wouldn't it be much more efficient to have you, Derek and possibly others joing the (mythical) Cocoon docs team with the aim of creating these newbies docs? See also http://wiki.cocoondev.org/Wiki.jsp?page=CocoonDocsPlan, I think your concept can fit nicely into this. I'm convinced that it is possible to create the newbies competence center that you mention *inside* the existing wiki - a well-designed start page and navigation should help newbies find their way. Maybe this needs some improvements to the existing wiki system, to help newbies find pages that are targeted for them, namely: a) Being able to search the wiki for NCC pages only or everything so that newbies are not distracted by deep technical discussions. b) Being able to clearly label pages as being part of the NCC, different color, icons or something. This might well be possible with JSPwiki, maybe by writing some kind of extension? We need to ask Steven or the JSPWiki folks if you think this is worth studying. What do you think? Join the party, or throw yet another one? :-) -Bertrand - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can i preserve POST and GET parms while forwarding a request?
Hy again;
I would like to pass POST parameters from a request to an
aggregation call and keep them as POST. From the sources i
learned, that the following sitemap would pass POST parameters
as GET params (is this true at all?) :
snip .../
map:actions
map:action name=request
logger=sitemap.action.request
src =org.apache.cocoon.acting.RequestParamAction
/map:action
/map:actions
snip .../
map:match pattern=*
map:act type=request
map:parameter name=parameters value=true/
map:aggregate element=page
snip .../
map:part
src=cocoon:/canvas{requestQuery}/
/map:aggregate
/map:act
map:transform src=xsl/page.xsl/
map:serialize/
/map:match
What would be the best approach to get my POST parameters forwarded
to the map:part src... as POST parameters ?
regards, hussayn
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
50935 Köln
Telefon: +49-221-56011-0
Fax: +49-221-56011-20
E-Mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
proposal: The Newbies Competence Center
hy, everyone It's time to round up i think. I have taken all the emails from today and some from yesterday dealing with this theme and extracted all information therein. The following summary therefore contains snippets of many people. I did some editing though to get things into one document. Hopefully i didn't miss too much. But you are invited to complete this roundup, if you feel there is something missing. The next steps should be : clearification, decision happy reading hussayn Proposal for the Newbies Competence Center I. The problem statement Users can not get quickly started with Cocoon probable Causes: 1. The existing Cocoon documentation is poorly written 2. The existing Cocoon documentation is poorly structured 3. There are gaps in the existing Cocoon documentation 4. Some of the existing Cocoon documentation is located in more than one site 5. ...(other issues related to installation/file size etc etc) I. The goal of the Newbies Competence Center == There is need to create documentation for people, who are new to cocoon and want to try their first steps in this technology. Some thoughts have been written down in the cocoon-users mailing list. The goal of this effort is to create a well defined, self contained source of reliable information for Cocoon newbies, along the lines of how to setup Cocoon in 15 minutes and HOWTO setup your intranet with XML in 1 day. The effort shall keep as tight as possible with the already existing cocoon infrastructure and shall be coordinated with the ongoing efforts on the cocoon core documentation. II. The requirements general remark: There are severe doubts in creating a new documentation platform, namely a new wiki site or a new documentation portal or whatever disperses from the existing infrastructure. On the other hand the existing infrastructure needs additional work in order to fit for the requirements mentioned in the following list. The most important requirements are: 2.1 MUST allow users to comment/improve the docs online to make it as easy as possible 2.2 MUST clearly identify these docs as being for beginners and reviewed by an editor of the Cocoon team to prevent beginners from getting lost in obsolete/unreliable docs. This could be achieved by labeling the pages, using different layouts, colors, etc. 2.3 SHOULD make these docs and their comments searchable, separately from the technical and/or unchecked existing docs to prevent beginners from being overwhelmed with irrelevant search results. 2.4 MUST allow all docs to be searchable simultaneously, to prevent users from having to search in X different places for info. 2.5 SHOULD if ever possible be integrated with existing Cocoon community tools (documentation pages, cocoon wiki) to avoid fragmentation of skills and resources 2.6 MUST provide constant editors effort to keep the documentation set correlated, cleanly structured and up to date. III. Additional thoughts o have a look at http://wiki.cocoondev.org/, you'll see a very prominent link to a currently unexisting Main page for this 'NewbiesGuide'. Could be populated instantly. o It was discussed, if the newbies documentation effort shall take place within the cocoon core documentation team or coordinated with that team and deveoped in parallel. o There was an idea to redesign the cocoon documentation entry page and provide chapters like: 1) First steps 2) User's Manual 3) User's Reference 4) Architecture 5) Developer's Guide This could basically be achieved by reorganising existing documentation. o The complete cocoon documentation including the Newbies Competence Center should be self contained, published by cocoon itself and included into the distribution, or set up as a separate documentation set, which can be downloaded and integrated into cocoon webapp for online publishing. o We need to be crystal clear and display on each page exactly - who the target audience is - what we assume of them in terms of background, knowledge and skills We possibly can add pointers to XSLT, basics of XML and give them some tips as to get up to speed ASAP. o Another more visionary idea was: What about having - the cocoon documentation set for distribution . manual pages . possibly pdf for printout version - the cocoon online site including online access to the docs (multiple versions of course, difference viewer as option) - the cocoon documentation playground (wikipages) - access to other related sites, bookstores, this mailing list, commercial project enabler, ... All of this tied together by the sunshine portal, or jetspeed, or whatever Give it a newbies view, an experts view, a developers
Re: proposal: The Newbies Competence Center
From the ongoing discussion we (the users) stated, that : * currently the docs do not really separate between cocoon-users and cocoon-developers and cocoon doesn't imply an obvious separation. * the documentation seems to be more developer centric, less user centric. * especially the newbies often get into trouble, because they feel, they have to learn the concepts in depths before they can get someth8ing out of cocoon. therefore we started this newbies competence center approach. i personnaly whish, that eventually the whole cocoon documentation will be better separated into developers issues and users issues, where my definition (biased from the discussions) is a bit fuzzy: user: *uses*the given infrastructure as is developer: *creates* his own add ons to given infrastructure I get troubles when it comes to xsp programming, which clearly sits between the chairs. But even there i see a bunch of prepacked ready to use logicsheets ready made for the users and the self made extra logicsheets from the developers... maybe this is a little simplistic, but it may hold as a first approach towards separating user concerns from developer concerns. another argument was: the user does not deal with internals nor with philosophy under the hood (like avalon framework, etc.) The developer in contrary does. But even here there seem to be at least two kinds of developers at work: those who do simple add ons (whatever simple means) i name them application programmers (they won't dive deep into avalon) and those who create complex additions to the cocoon base, who may be labeled as system programmers. all of this is not so easy and should be separated out more clearly in the next steps. I am pretty shure, if we keep with KISS, we should come out at least with a usable beginners doc though ;-) regards, hussayn Tony Collen wrote: Remember, the docs are for the users, and unfortunately, the developers might have a different idea about how the information should be categorized.Or maybe our problem is making the distinction between users and developers ... I would guess that eventually, most users become developers, so then, it's just a matter of beginning user vs. power user, and so on. -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: proposal: The Newbies Competence Center
Hy Miles; thank you for the very deep insight to several points here; i take this all very serious and will keep it in mind. especially because i consider my self beeing in the middle of step 3 (see below) now and still have lots to learn about cocoon. just let me put one thing correct: the proposal is not a proposal for a beginners tutorial. It is a proposal for a beginners documentation set, that should allow a newbie to start digging into cocoon up to step 3 (i assume) of your list... In this sense a tutorial might be only one peace of the whole set... Concerning the significance of avalon in XSP programming: i simply never touched XSP in cocoon-2 until today (although i am quite familiar with the concepts as i learned from cocoon-1 about two years ago, but it changed alot...). Hopefully XSP will be my next step towards mastering cocoon-2. I thought from the ongoing discussion, that the underlaying technology wouldn't be soo evident as you state. as i said before i take you very serious and once i get to the point i will remember your very valuable insight to the theme. thanks again, regards, hussayn Miles Elam wrote: SAXESS - Hussayn Dabbous wrote: * currently the docs do not really separate between cocoon-users and cocoon-developers and cocoon doesn't imply an obvious separation. On the contrary, on the homepage, there is a User Guide and a Dev Guide. I don't think that there lacks an obvious separation, but rather an arbitrary separation. * the documentation seems to be more developer centric, less user centric. Think of Cocoon's target audience. The greenest newbie is still expected to be a web developer. My aunt who's not in web development or publishing couldn't care less about Cocoon. The documentation *should* be developer-centric. A separation could be Cocoon introduction for developers and advanced Cocoon hacking for developers, but still, this isn't technology for Joe Sixpack walking in off the street. If all someone wants is to publish a few HTML pages, even Microsoft's personal web server would do the trick; Cocoon is overkill. If someone off the street wants to make an image slideshow/gallery, they shouldn't be looking at Cocoon; They should be looking at a project built *on top of* Cocoon. The Cocoonpart of it should be transparent to them: just upload images and view in the web browser. On the other hand, Cocoon docs should definitely be geared toward someone wanting to *write* an image slideshow/gallery engine. * especially the newbies often get into trouble, because they feel, they have to learn the concepts in depths before they can get something out of cocoon. You have to learn what a sitemap is, what its purpose is, and how to use it and the enclosed pipelines. That's a must just as you must learn Java and the basic tenets of OOP before you can get anything out of servlets and JSP. The only question is how this can be accomplished the best. therefore we started this newbies competence center approach. i personnaly whish, that eventually the whole cocoon documentation will be better separated into developers issues and users issues, where my definition (biased from the discussions) is a bit fuzzy: user: *uses*the given infrastructure as is developer: *creates* his own add ons to given infrastructure When a user writes an XSP file, they are effectively creating a generator -- create their own add on. XSP files are definitely in the category of user introductory knowledge, however. Would a more appropriate distinction be: user: uses or extends the given infrastructure as is developer: creates new infrastructure or alters existing infrastructure Creating a generator for file format foo is the domain of the user. Editing or replacing AbstractGenerator or making fixes to the cache store (shared resources) are the domain of the developer. I get troubles when it comes to xsp programming, which clearly sits between the chairs. But even there i see a bunch of prepacked ready to use logicsheets ready made for the users and the self made extra logicsheets from the developers... maybe this is a little simplistic, but it may hold as a first approach towards separating user concerns from developer concerns. I see XSP as the middle of the user bell-shaped curve. What you are talking about is not the documentation but the introductory tutorial. The tutorial is important, but it is only a part of the overall documentation. another argument was: the user does not deal with internals nor with philosophy under the hood (like avalon framework, etc.) The developer in contrary does. Here we very much disagree. In order to have your XSP file cache its results, you need to reference Avalon components. It's not an all-or-nothing affair. Almost everyone I've ever seen come to the list has wondered about how fast Cocoon is. If your XSPs aren't able to cache, the answer is not impressively fast
Re: proposal: The Newbies Competence Center
Thinking about the concept of roles is really the best conceptual input to the docs i heard so far. Yes, i have the instant feeling, that your list of roles is highly significant. That should be taken into account when going into the newbies documentation ... thanks alot for this contrib regards, hussayn Tony Collen wrote: On Mon, 27 Jan 2003, SAXESS - Hussayn Dabbous wrote: therefore we started this newbies competence center approach. i personnaly whish, that eventually the whole cocoon documentation will be better separated into developers issues and users issues, where my definition (biased from the discussions) is a bit fuzzy: user: *uses*the given infrastructure as is developer: *creates* his own add ons to given infrastructure Hrmm... this gives me an idea, tell me if you follow along: Cocoon was developed with SoC in mind. You have the content separated from the style, and you have the logic of the site separated from the content. So, instead of trying to define what a user is and what a developer is, we should define the different roles that a person would have when using or developing with Cocoon. For instance, with a typical installation of Cocoon, we could define the following roles: - Content Creator. This person authors XML for the site to be transformed. This role works when most of the content is static. However, if a lot of the data is being pulled out of a database, they would be in charge of something like data entry into the database, etc. - Graphic/Web designer. This person is in charge of the style of the site. Not only do they come up with how the site looks through the design of the final HTML, but they also write the XSL to transform the content into the desired format. Sometimes this person is also the content creator. - Administrator. In charge of the servlet container, and modifying the main sitemap. Monitors logs, and able to identify when a component would need to be cacheable, poolable, etc. Sometimes this role can further be separated out into servlet container admin and sitemap admin. - Programmer. I think this is what we now call developer -- this person is capable of developing custom components, e.g. Generators, XSPs, etc. This person might also code the Flow layer logic. But maybe not. Ideally, all of these roles work together in order to get things done, but they only have to worry about their specific role. Now that we have defined roles, its easy to classify the documentation we have now. Obviously, the content creator doesn't have to worry about performance issues, so perhaps that info would go into the Administrator section. Likewise for information about logging. Conversely, people writing a custom generator obviously fall into the Programmer category, and they would probably know not to have to stumble into the Administrator section. To sum up, Cocoon was developed with SoC in mind. IMHO, the current documentation managed to comingle the concerns, so we ended up with 4 or 5 different places that something could go. If we mirror the SoC model in the documentation, I think we'll end up with some successful and useful docs. Regards, Tony -- Cocoon: Internet Glue (A Cocoon Weblog) http://manero.org/weblog/ - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Single JAR with all the libs? - rejar the distrib ...
If i understand you correct, you simply want to avoid deploying several cocoon-based webapps all containing tons of the same jar files ? And in order to keep your customers happy, you want to simplify the deployment by bundling all cocoon jars into one big jar, deploying this golfball.jar independently from cocoon into your appserver? Then your webapps get significantly smaller because you only have to deploy the cocoon configs and the webapp specifics ...? If this is what you want, you can do it in two ways: WAY I - this is a very simplistic approach with some caveats, but it works. There may be a license problem here, but i don't know this for shure: 1.) unwar your cocoon distribution to any convenient place 2.) go to the WEB-INF/lib directory 3.) Now for each jarfile in the directory simply do: jar xf thefile.jar Of course you may skip all jars you dont need for your distribution ... 4.) throw away the .jar files 5.) jar cf golfball.jar * Now you have one single jar file, that you can distribute to whereever your container needs it to serve as common cocoon classes for your webapps. Finally you could repack the cocoon.war from step 1.) without the lib/*.jar files, add your webapp specific data (config/files/ programs) and deploy the result as co-webapps into your container ... But you have to keep one caveat in your mind: You may fall into strongly hidden compatibility issues when your webapps use other versions of the .jar modules you just have bundled to allclasses.jar If you take the single jars as they are, at least you can easier track down which module (.jar file) causes compatibility issues. And you can easier exchanche module jars if needed although i must admit, sometimes exchanging one jar out of a bunch may not be trivial at all ;-) The golfball.jar only allows to determine, which classes cause problems. WAY II -- If you are under unix, you can reach your goal by clever use of softlinks. In my development environment we sometimes have to run 5 to 10 cocoon-based webapps all across multiple platforms, multiple containers and so on. And we found a nice solution, that fits for our purposes. If this is something, anyone would be interested in, we could share knowledge here, but since this is kind of special i wouldn't bother this list and do this offline. just drop me an email. regards, hussayn hope, that helps Robert Simmons wrote: Is there a way to compress all the cocoon jars into one jar so I can just drop in my application server like a golf ball and all cocoon deployments will have access to it ? -- Robert -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How can i use RequestParamAction and match fields in parallel ?
Hy;
I want to use the RequestParam action to pass a parameter into
an aggregation. In parallel the parts of the agregation shall
be assembled from the match parameters {1} {2} ...
My original sitemap leads to an Resource not found error:
snip .../
map:actions
map:action name=request
logger=sitemap.action.request
src =org.apache.cocoon.acting.RequestParamAction
/map:action
/map:actions
snip .../
map:match pattern=*
map:act type=request
map:parameter name=parameters value=true/
map:aggregate element=page
map:part element = menusrc=cocoon:/{1}/menu/
map:part element = canvas
src=cocoon:/{1}/canvas?usercollection={usercollection}/
/map:aggregate
/map:act
map:transform src=xsl/page.xsl/
map:serialize/
/map:match
From what i see in the logs i guess {1} is filled with blank or null.
i get an error stating Resource 'menu' not found
I can't see, whether {usercollection} is also blanked out...
first experiment:
If i take out the action, the aggregation takes
place as expected ({useracollection} is now empty of course):
map:match pattern=*
map:aggregate element=page
map:part element = menusrc=cocoon:/search/menu/
map:part element = canvas
src=cocoon:/search/canvas?usercollection={usercollection}/
/map:aggregate
map:transform src=xsl/page.xsl/
map:serialize/
/map:match
secnd experiment:
--
The flow works as expected when i keep the action but eliminate
the {1} reference as follows:
map:match pattern=*
map:act type=request
map:parameter name=parameters value=true/
map:aggregate element=page
map:part element = menusrc=cocoon:/search/menu/
map:part element = canvas
src=cocoon:/search/canvas?usercollection={usercollection}/
/map:aggregate
/map:act
map:transform src=xsl/page.xsl/
map:serialize/
/map:match
Can anyone explain me, what i am doing wrong in the original sitemap above ?
any hint would help...
regards, husayn
--
Dr. Hussayn Dabbous
SAXESS Software Design GmbH
Neuenhöfer Allee 125
D-50935 Köln
tel.:+49 221 56011 0
fax.:+49 221-56011 20
email:[EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon is complex, but worth it! Some Answers to your dilemma
I am with cocoon for about three months now and i remember my own frustrations when i started as a newbie. From this thread and other emails within this list and from my personal experience with cocoon i conclude: 1.) cocoon gains high (initial) attraction (many newbies questions) 2.) cocoon is not easy to apply by newbies (see this thread ;-) 3.) cocoon is far away from getting mature (focus on dev HEAD) dont missunderstand me: i mean it's robust but complex, fast evolving and ever changing ... But if you look under the hood you also find: 4.) cocoon provides a very exciting technology. 5.) cocoon IS actively developed. 6.) cocoon attracts commercial interests (projects) I assume everybody getting attracted to cocoon has some ideas in mind what he/she wants to do with it, but after opening the box it is (at first) hard to see how you could gain from cocoon within your projects. And i think that at least in commercial projects what counts is the amount of time you need to get it mastered. The (non developing) users seem to suffer from * undocumented features (wholes in documentation) * complexity, even if the parts of interest are well documented. * huge amount of loosely coupled docs and documentation sites. * lack of out of the box applications that can be used right from the initial installation (maybe the cocoon portal is an exception, but it's also really complex for the newbies, isn't it ?) * functional overkill * Lack of debugging facilities especially for sitemap checking. * very poor error reporting. You have to dig within tons of stack traces to get a clue ... Sometimes you even get no error report at all, it simply doesn't work. But it is also true, that once you have mastered the cocoon basics and once you start understanding how things work, you suddenly get so much out of it, that all your initial efforts get payed back. Because cocoon is something i really want to support, i started a Wiki page that adresses some of the most hearting issues. Hopefully this work can be used (and improved) also by others: http://wiki.cocoondev.org/Wiki.jsp?page=SurvivalTips Besides this i recommend to have a look at the cocoon developer's handbook (developer's library) This book is now my good companion in the cocoon adventure. Since i use cocoon within commercial projects i had the oportunity to give away a small subproject to one of the cocoon developers and i was really positively surprised from the quality of the work i got back. Hence i would recommend to all other project managers out in the world: simply ask for support from the cocoon comunity and i am shure, you will either get your problems solved on the fly or you will find excellent experts who will be happy to get involved in your projects as freelancers... I hope that cocoon will master it's own future and eventually become the tomcat of XML-publishing regards, Hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon. More Answers to your dilemma
There is one problem with your approach: What if your webapp uses different versions of commonly used jars ? I had this problem with one of my webapps, that internally used an older version of the avalon framework and some other jars incompatible to my cocoon-2.0.4. I tried hard to get my webapp integrated into cocoon and finally i gave up and came to following solution: 1.) I set up a clean cocoon webapp 2.) I create a sitemap only for presentation issues (the web frontend of my webapp) and instrument what i need for this purpose into a subdirectory within the cocoon app. 3.) I set up my legacy application completely separated from cocoon 4.) I created an XML interface that consists primarily of a bunch of jsp's that interact with my legacy app and spill out XML to cocoon. I could have used exis of course, but the interface was not soo complex... By this a could cleanly separate my legacy application from my frontend. I had not to deal with compatibility issues and i ended up in a very nice presentation layer. What i liked most about this is the (almoust) total separation of logic from presentation ;-) There was only one caveat to master: My apps are under authentification control. Therefore we implemented a session aware protocol named proxy: that allows under certain circumstances to transparently transfer cookies between the browser and the legacyapplication. Currently both apps must run in the same container and the container must provide SSO. But i hope this limitation can be eliminated in the near future... regards, hussayn Julian Klein wrote: Robert, I want all the framework configs out of my way. I want all of the options and jars and so on neatly tucked away and where I can just drop them in a directory and forget about them. You can do one of two things with the jars. 1)The Cocoon war by default has all of them stored in a certain lib directory. When you unpack the war in Tomcat on startup the path would be as follows (assuming the war is in the $TOMCAT_HOME/webapps directory on startup): $TOMCAT_HOME/webapps/cocoon/WEB-INF/lib. This way all the jars are available to the servlet container that is running the cocoon app and localized to this directory. 2)You could move all these jars to $TOMCAT_HOME/lib or if you are running a newer version of Tomcat (e.g.4.1.12) then it would be $TOMCAT_HOME/common/lib. If you put the jars here they will be available to all webapps running in Tomcat and be localized. Unlike the first option, this allows a more public feel to your jars (the first is more like a protected feel to the jars). NOTE:All that was Tomcat specific deployment info, not Cocoon. So the Cocoon developers have used the first option to allow these jars to be localized and clean. The jars can also be found at: xml-cocoon/build/cocoon/webapp/WEB-INF/lib Now Id like to have a war that is THAT small and without having to have an intimate knowledge of cocoon to accomplish it. You would have to build Cocoon from the CVS source code and modify the Ant build script to stop the packaging of jars in the cocoon war. This requires a minimal knowledge of Ant. web.xml (NOT a 40 meg file) Finally, the web.xml that comes with Cocoon in only a few Ks. So it should never be more, unless you have added A LOT of servlet mappings, but that must be proprietary. Hope this helps, Julian = Live simply so others may simply live. -Ghandi Pluralitas non est ponenda sine neccesitate. Entities should not be multiplied unneccesarily -William of Occam __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon is complex, but worth it! Some Answers to your dilemma
depending on what you are doing with cocoon, you get quite amazing performance due to caching. My website is completely done in XML and using cocoon. and its almost as performant as with ordinary html. I was really amazed when i saw this although the site is super simple... http://www.saxess.de I your use case is more complex, you are hitting databases and creating dynamic data, you will allways suffer from performance. This has nothing to do with cocon. And if you talk about performace, you have to take into account, what cocoon does under the hood (XSLT is always a performance problem). regards, hussayn Robert Simmons wrote: Thanks for the reply. I still, however, cant figure out how to get a hello world working on a clean war without all of the other crap in the cocoon war. The configuration file is just plain staggering to say the least. And looking at some pages that use cocoon, I'm starting to have second thoughts about its performance in high traffic situation. Quite honestly I'm pretty close to saying hell with it and just coding the interface in JSP. Although it might be powerful, if it isn't easy, its trash. No professional dev wants, or has the time, to blow 2 to three weeks just to get separation of logic and presentation. Too high of a price for too little gain. Powerful? I believe you. I believe its powerful. Scalable? I don't know. The Wiki page runs very slow for me and a tutorial linked to me from the IBM site (which was done in cocoon) was taking 10 to 15 seconds per page to render. Put that in production and your company can kiss sales goodbye. Internet users are impatient and any guy with a DSL isn't going to wait 15 seconds for your page. User friendly? You've got to be joking. No, I don't want to take up any more time from folks. I just simply don't have the time to mess with it. Reading config files and figuring out how the hell to build a new application just isn't what I want to do a very trivial part of my project with. -- Robert - Original Message - From: SAXESS - Hussayn Dabbous [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, January 25, 2003 9:52 PM Subject: Re: Cocoon is complex, but worth it! Some Answers to your dilemma I am with cocoon for about three months now and i remember my own frustrations when i started as a newbie. From this thread and other emails within this list and from my personal experience with cocoon i conclude: 1.) cocoon gains high (initial) attraction (many newbies questions) 2.) cocoon is not easy to apply by newbies (see this thread ;-) 3.) cocoon is far away from getting mature (focus on dev HEAD) dont missunderstand me: i mean it's robust but complex, fast evolving and ever changing ... But if you look under the hood you also find: 4.) cocoon provides a very exciting technology. 5.) cocoon IS actively developed. 6.) cocoon attracts commercial interests (projects) I assume everybody getting attracted to cocoon has some ideas in mind what he/she wants to do with it, but after opening the box it is (at first) hard to see how you could gain from cocoon within your projects. And i think that at least in commercial projects what counts is the amount of time you need to get it mastered. The (non developing) users seem to suffer from * undocumented features (wholes in documentation) * complexity, even if the parts of interest are well documented. * huge amount of loosely coupled docs and documentation sites. * lack of out of the box applications that can be used right from the initial installation (maybe the cocoon portal is an exception, but it's also really complex for the newbies, isn't it ?) * functional overkill * Lack of debugging facilities especially for sitemap checking. * very poor error reporting. You have to dig within tons of stack traces to get a clue ... Sometimes you even get no error report at all, it simply doesn't work. But it is also true, that once you have mastered the cocoon basics and once you start understanding how things work, you suddenly get so much out of it, that all your initial efforts get payed back. Because cocoon is something i really want to support, i started a Wiki page that adresses some of the most hearting issues. Hopefully this work can be used (and improved) also by others: http://wiki.cocoondev.org/Wiki.jsp?page=SurvivalTips Besides this i recommend to have a look at the cocoon developer's handbook (developer's library) This book is now my good companion in the cocoon adventure. Since i use cocoon within commercial projects i had the oportunity to give away a small subproject to one of the cocoon developers and i was really positively surprised from the quality of the work i got back. Hence i would recommend to all other project managers out in the world: simply ask for support from the cocoon comunity and i am shure, you will either get your problems solved on the fly or you will find excellent experts who will be happy to get involved in your
Re: Cocoon is complex, HOLD ON, WHY IS THIS BOILING UP ?
I wonder why sometimes when it comes to criticism of cocoon the arguments fly higher and higher until someone gets really pissed of and angry ... And why is it so many times a newbie who becomes the center of this game ? (Also one of my first newbie questions boiled up beyond the limits, but i'm still there ...) Please dont missunderstand me. In general i think the comunity takes care of many many questions and very valuable information is flowing around, but we also should take special care about any strong criticism on cocoon. And especially the newbies can give so valuable insight, even if they seem to be ignorant (they aren't ignorant at all. They are new to this !!!) Maybe we should calm down a bit and take this thread really serious. It contains much of material to think about. And in many senses the criticism here can't be discussed away. regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon is complex, HOLD ON, WHY IS THIS BOILING UP ?
Antonio, sorry, i really misinterpreted your last email. Seems i was wrong (big apologize!) this was really not meant against you. Let me explain what i have in mind: In the OpenSources the things goes a diferent way. This is not a company where are people getting money to support you. Then the less you can do is thanks people that use his time to help you. How you will fell if somebody stop you at the street and start attacking you just because you dont know where is the street called X? This is ridiculous, right? I think some people here had the same feel. You are right in all points. i agree. But i did not understand robert's criticism in this direction. I understand, he attacks some severe critical points, which should be taken into concern (hope this is correct english...) I did not hear, the cocooners shall do it, i heard this is may be a severe problem, which is a completely different message so far ... From my point of view: cocoon can only proove it's long turn significance, if it is introduced into business, where business does not necessarily mean commercial business. It means to prove cocoon to be * customisable * developer friendly (not userfriendly!) * stable * performant * scalable * well documented * downward (upward?) compatible * ... and much much more... This proof is partially performed from all of those who use cocoon in their business (including me ;-). But this proof is not in first place a task of the cocoon comunity, but it may be a task of a possibly commercial group, which takes care on these things and stays in constant discussion with the core development of cocoon. Yes and everyone, who wants to get this cocoon++ should have to pay for it in some way, or has to enhance it on his/her own ;-) For me currently the most significant problem is, that cocoon is moving too fast to get a grasp on it and start quality assurance issues. Maybe this is what the cocoon comunity really have to take care about: Getting the system into a state, where it can be quality assured... And this is where a must agree with Robert ... You see: I am with cocoon, i love it, but i also see the big big potential success leaks ;-) regards, hussayn Antonio Gallardo wrote: Yes I know this point, but for this reason you cannot just come here and after 12 hours, start attacking something you dont know. This is the worng way. In place you can ask in another way. Maybe we should calm down a bit and take this thread really serious. It contains much of material to think about. And in many senses the criticism here can't be discussed away. I never got angry. I agree. Antonio Gallardo. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cocoon2
i have written two cookbook examples for tomcat 4 with cocoon-2.0.4. This may help you... for tomcat: http://www.saxess.com/JSPWiki/Wiki.jsp?page=TomcatInitial for cocoon under tomcat: http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install regards, hussayn Mustafa Ali, Halgurt wrote: Hello, I am trying to configer cocoon-2.0.4 under win XP with tomcat-5, but i am really stuck, I do´nt know what to do, I get the message servlet cocoon2 is not available. Can you please tell me how I can configer cocoon-2.0.4 with tomcat-5 apache http Server-2.0.43. Thank you very much for help; Halgurt - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Administrator in need of help on new install
Hy, can you send your tomcat/apache/cocoon config files ? That should be a solvable problem ... If the mailing list agent refuses your email (due to size limitations) you can send it directly to my personal email adress if you like... regards, hussayn Jim McCullough wrote: Have you setup a JkMount in your httpd.conf file for cocoon? JkMount /cocoon/* ajp13 Jim McCullough Risk Analytics Inc. - Las Vegas Software Engineering [EMAIL PROTECTED] [EMAIL PROTECTED] (702) 407-1814 (voice) (702) 407-1824 (fax) - Original Message - From: Gerstel, Rachel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, January 23, 2003 8:25 AM Subject: Administrator in need of help on new install Hello All, Apologies if this has already been covered, but I have not been able to find a similar problem in the archives. I have no experience with xml whatsoever and have a brand-new developer with no experience whatsoever wanting to start playing around with cocoon. I have installed: Tomcat 4.0.4, Apache 1.3.26 and Cocoon 2.0.4 (also uninstalled and tried 2.0.3, but got the same results). I have a feeling I am missing some really basic item, but haven't been able to figure it out and am getting a headache so I hope someone can please help. :--) My tomcat and apache are configured with mod_jk to talk to each other (via auto config in tomcat ../conf/auto/mod_jk.conf) with apache serving static pages and tomcat serving servlet, java stuff. That works fine. I put the cocoon.war into webapps and it auto-deploys, no error messages anywhere!!! But when I click on http://mymachin/cocoon the only thing I see is the directory index. No welcome page that I keep hearing so much about. Can someone smack me over the head and tell me what vital thing I have missed? Thanks, Rachel - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 10 basic survival tips for cocoon users (was: Logicsheet problems- global XSLT variables)
Hy Mark H wrote: For XSLT processing i have added Saxon-6.5.2. Are you saying that Xerces doesn't deal with global XSLT variables properly? NO. Of course xalan can handle globals and i am using this feature with xalan too.. I say, that some aspects of xslt can be done with saxon, which can't be done with xalan and vice versa, e.g. there is a (possible) bug with entity resolving within style sheets, that is (partially) solved when using saxon... interested people can see: http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver (last chapter focusses on saxon) 4.) Proceed in baby steps when changing things in your cocoon app But it really slows up development The survival tips adress newbies. expereinced users may use different (more efficient) strategies... 8.) I started using the coocon developers handbook I got Cocoon - Building XML Applications and Coocoon 2 Programming but they don't get into the development site of things very deeply, especially the first book. Might try out the book you mentioned. i prefer the cocoon developers handbook because it really goes into real life examples with code snippets and so on. It adresses my programmers needs quite well. Of course it doesn't go into the depest secrets of cocoon, but cocoon is anyway a running target, hence using the book plus the cocoon wiki fits at least my basic needs. regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
10 basic survival tips for cocoon users (was: Logicsheet problems- global XSLT variables)
Mark Horgan wrote: Also, do others find working with Cocoon very frustrating? When you make a change it takes forever for the web-app to reload and re-compile the java class, espcially when it takes up so much memory. Also even when using the logs its very hard to track down bugs in ones code especially logicsheets. But generally I like Cocoon though I wish it was more straight-forward to develop with it. Thx in advance, Mark Hy, When i started with cocoon i got really mad with hunting errors and understanding, how all this fits together. But after about three months of working with the beast, i built up some survival strategies. It is how I do it. It may help as a guide, but it does not claim to be the best approach: 1.) Instead of restarting the whole container, i only restart the cocoon app, when needed. This takes a few seconds with tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8) 2.) During development i use tomcat and i set the reloadable=true within the Context/ of my webapp. By this any changes in the classpath causes an automatic webapp restart. 3.) use released versions if possible (cocoon-2.0.4 seems quite mature) 4.) Proceed in baby steps when changing things in your cocoon app 5.) follow KISS (keep it simple, stupid) i keep as much as possible with the basics of cocoon and don't use (yet) the more fancy stuff. 6.) Separate your app into subsitemaps and subdirs with related issues 7.) use the cocoon-wiki Especially the search function unhides interesting docs 8.) I started using the coocon developers handbook It's written from Lajos Moczar and some other active cocoon developers... Here are two of my personal favorites. I have documented this in our company wiki: 9.) For XSLT processing i have added Saxon-6.5.2. It's not straight forward to install, but sometimes it can be utilised with less pain, than xalan (just a matter of taste) Look into cocoon wiki for a quick description or look at http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install for a quickinstall step by step instruction. 10.)use entity resolver wherever possible. look at the cocoon docs for the basics or at http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver for a quickinstall description. hope, that helps someone ... regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 10 basic survival tips for cocoon users (was: Logicsheet problems-global XSLT variables)
I use the following tomcat definition for a cocoon based webapp that restarts automatically, when classes or jars change: Context path=/mywebapp docBase=/opt/cocoon/develop reloadable=true debug=0 Resources className=org.apache.naming.resources.FileDirContext allowLinking=true/ /Context /Context interpretation: docbasepoints to where the cocoon app resides reloadable tells tomcat to restart on changes in webapp the Resources tag is only needed, if your webapp directory contains symbolic links or the docbase itself is a symbolic link. NOT NOTE NOTE!!! caveat: Your webapp MUST NOT BE DEPLOYED WITHIN THE webapps Directory, if you use this approach. Otherwise your cocoon app would be started twice !!! Just another hint: Befoire cocoon-2.0.4 the sitemap reloading had a bug, that crashed cocoon under certain circumstances. This bug has been fixed with cocoon-2.0.4. regards, hussayn Derek Hohls wrote: Hussayn These tips would be useful on the Cocoon Wiki too! One question - just *how* do you restart only the cocoon app without restarting tomcat (and do you delete the work files somewhere in that process as well?) Thanks Derek [EMAIL PROTECTED] 20/01/2003 12:50:26 Mark Horgan wrote: Also, do others find working with Cocoon very frustrating? When you make a change it takes forever for the web-app to reload and re-compile the java class, espcially when it takes up so much memory. Also even when using the logs its very hard to track down bugs in ones code especially logicsheets. But generally I like Cocoon though I wish it was more straight-forward to develop with it. Thx in advance, Mark Hy, When i started with cocoon i got really mad with hunting errors and understanding, how all this fits together. But after about three months of working with the beast, i built up some survival strategies. It is how I do it. It may help as a guide, but it does not claim to be the best approach: 1.) Instead of restarting the whole container, i only restart the cocoon app, when needed. This takes a few seconds with tomcat 4.1.* (~300 MHz sparc dual processor, solaris 2.8) 2.) During development i use tomcat and i set the reloadable=true within the Context/ of my webapp. By this any changes in the classpath causes an automatic webapp restart. 3.) use released versions if possible (cocoon-2.0.4 seems quite mature) 4.) Proceed in baby steps when changing things in your cocoon app 5.) follow KISS (keep it simple, stupid) i keep as much as possible with the basics of cocoon and don't use (yet) the more fancy stuff. 6.) Separate your app into subsitemaps and subdirs with related issues 7.) use the cocoon-wiki Especially the search function unhides interesting docs 8.) I started using the coocon developers handbook It's written from Lajos Moczar and some other active cocoon developers... Here are two of my personal favorites. I have documented this in our company wiki: 9.) For XSLT processing i have added Saxon-6.5.2. It's not straight forward to install, but sometimes it can be utilised with less pain, than xalan (just a matter of taste) Look into cocoon wiki for a quick description or look at http://www.saxess.com/JSPWiki/Wiki.jsp?page=Install for a quickinstall step by step instruction. 10.)use entity resolver wherever possible. look at the cocoon docs for the basics or at http://www.saxess.com/JSPWiki/Wiki.jsp?page=EntityResolver for a quickinstall description. hope, that helps someone ... regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by *MailScanner* http://www.mailscanner.info/, and is believed to be clean. The CSIR exercises no editorial control over E-mail messages and/or attachments thereto/links referred to therein originating in the organisation and the views in this message/attachments thereto are therefore not necessarily those of the CSIR and/or its employees. The sender of this e-mail is, moreover, in terms of the CSIR's Conditions of Service, subject to compliance with the CSIR's internal E-mail and Internet Policy. -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in
new wiki-page: SurvivalTips for cocoon users
Hy; I added my list of survivalTips to the bestPractices page on cocoon wiki: http://wiki.cocoondev.org/Wiki.jsp?page=SurvivalTips Please feel free to modify/move it as appropriate. regards, hussayn -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 10 basic survival tips for cocoon users (was: Logicsheet problems- global XSLT variables)
hy Antonio; What about adding your contrib directly to http://wiki.cocoondev.org/Wiki.jsp?page=SurvivalTips or related pages ;-) ? Maybe you could contrib a link to jEdit.org ? Maybe it is even worthwhile to add a new wikipage for XML-authoring tools ... What do you mean ? regards, hussayn 9.01) I use jEdit.org to all my development in Cocoon. jEdit has a plugins called XML and XSLT. The XML plugin helps writing XML stuff checking the tags. The XSLT pluging helps to see the results of applying 1 or more Stylesheets to a page. This is useful to check what are the stylesheets doing. comment I think it will be fine to write a survival guide in wiki. :-) /comment Antonio Gallardo -- Dr. Hussayn Dabbous SAXESS Software Design GmbH Neuenhöfer Allee 125 50935 Köln Telefon: +49-221-56011-0 Fax: +49-221-56011-20 E-Mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
