RE: Some Design Help, please
Thanks. I have learnt much from this link. Best Regards, Sreedhar -Original Message- From: Andrew John Savory [mailto:[EMAIL PROTECTED]]On Behalf Of Andrew Savory Sent: Wednesday, March 06, 2002 4:16 AM To: Sreedhar Chintalapaty Cc: Cocoon Users Subject: Re: Some Design Help, please Hi, On Tue, 5 Mar 2002, Sreedhar Chintalapaty wrote: How would I do something like that in Cocoon? Can one XSP page dynamically include other XSP pages? I would appreciate -any- examples/sample code! As others have said, there are several ways of doing it. For some examples and sample code, take a look at this: http://www.cocooncenter.de/cocooncenter/tutorials/navigation/tutorial.html The tutorial shows one possibility for creating the navigation elements of a typical website with a simple hierarchic structure. All pages contain a menu bar on the left, the currently selected item is highlighted. You might also like to look at the way the Cocoon documentation pages are generated, which uses aggregation to achieve a similar thing (start in cocoon-2.0.1/src/documentation/). Hope that helps, Andrew. -- Andrew SavoryEmail: [EMAIL PROTECTED] Managing Director Tel: +44 (0)20 8553 6622 Luminas Internet Applications Fax: +44 (0)870 28 47489 This is not an official statement or order.Web:www.luminas.co.uk - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Some Design Help, please
I am trying to fit bonebreaker into a new folder structure to learn some
site map fundas, and I am getting the following error:
org.apache.cocoon.ResourceNotFoundException:
No pipeline matched request: gvs//home/home.section
The Bonebreaker application itself works perfectly. I wonder why it is
trying to find a match for gvs//home/home.section instead of
gvs/home/home.section? This is probably a frequently made newbie faux paus
with a stock answer, perhaps?
Differences between Bonebreaker and MyApplication:
My directory Structure is quite different from that of Bonebreaker; however,
I am using only the files that came with Bonebreaker, but relocated
according to my desired directory structure.
--
Bonebreaker Folder Structure
Bonebreaker
| css
| | default.css
|
| documents
| | cc
| | home.xml
|
| | company
| | home.xml
|
| | dh
| | home.xml
|
| | fr
| | home.xml
|
| | home
| | home.xml
|
| | links
| | home.xml
| stylesheets
| bike.xsl
| menu.xsl
| menupage.xsl
| page.xsl
| section.xsl
--
My Application Folder Structure
GVS
| content
| control
| config
| toc.xml
| home
| home.xml
| view
| xsl
| html
| bike.xsl
| menu.xsl
| menupage.xsl
| page.xsl
| section.xsl
--
--
Pipeline in Bonebreaker Sitemap:
map:pipeline
!-- == homepage == --
map:match pattern=
map:redirect-to session=false uri=bonebreaker/home/home.section/
/map:match
!-- == pages == --
map:match pattern=*/*.**
map:act type=request
map:parameter name=parameters value=true/
map:generate src=documents/{../1}/{../2}.xml{requestQuery}/
map:transform type=xslt src=stylesheets/{../3}.xsl
map:parameter name=section value={1}/
map:parameter name=toc-file
value=../documents/toc.xml/
map:parameter name=base-url
value=/cocoon/bonebreaker/
/map:transform
map:transform type=xslt src=stylesheets/menupage.xsl
map:parameter name=section value={../1}/
map:parameter name=request-url
value={../2}.{../3}/
map:parameter name=toc-file
value=../documents/toc.xml/
map:parameter name=css-stylesheet
value=default.css/
map:parameter name=base-url
value=/cocoon/bonebreaker/
/map:transform
map:serialize/
/map:act
/map:match
!-- == css stylesheets == --
map:match pattern=*.css
map:read src=css/{1}.css mime-type=text/css/
/map:match
/map:pipeline
--
Pipeline in MyApplication Sitemap (All matchers look like the one for home
below, only with home replaced by something else):
map:pipeline
!-- home/*.** --
map:match pattern=home/*.**
map:select type=request
map:parameter name=parameters value=true/
map:generate src=control/home/{../1}.xml{requestQuery}/
!-- Setup Transformation #1 --
map:transform type=xslt src=view/xsl/html/{../2}.xsl
map:parameter name=section value=home/
map:parameter name=toc-file
value=/control/config/toc.xml/
map:parameter name=base-url value=/cocoon/gvs/
/map:transform
!-- Setup Transformation #2 --
map:transform type=xslt src=view/xsl/html/menupage.xsl
map:parameter name=section value=home/
map:parameter name=request-url
value={../1}.{../2}/
map:parameter name=toc-file
value=/control/config/toc.xml/
map:parameter name=css-stylesheet
value=default.css/
map:parameter name=base-url value=/cocoon/gvs/
Re: Some Design Help, please
On Thu, Mar 07, 2002, Sreedhar Chintalapaty wrote: The Bonebreaker application itself works perfectly. I wonder why it is trying to find a match for gvs//home/home.section instead of gvs/home/home.section? This is probably a frequently made newbie faux paus with a stock answer, perhaps? I'm no expert, but in other areas (like working with the shell) multiple slashes dont change anything. Meaning: ls /usr/bin ls /usr//bin ls /usrbin all produce the same result HTH, -Tom - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Some Design Help, please
Hi Sreedhar,
I am trying to fit bonebreaker into a new folder structure to learn some
site map fundas, and I am getting the following error:
org.apache.cocoon.ResourceNotFoundException:
No pipeline matched request: gvs//home/home.section
That might be a problem with your URI prefix.
Could you post a snippet from your main sitemap?
Greetings,
Andreas
The Bonebreaker application itself works perfectly. I wonder why it is
trying to find a match for gvs//home/home.section instead of
gvs/home/home.section? This is probably a frequently made newbie faux
paus
with a stock answer, perhaps?
Differences between Bonebreaker and MyApplication:
My directory Structure is quite different from that of Bonebreaker;
however,
I am using only the files that came with Bonebreaker, but relocated
according to my desired directory structure.
--
Bonebreaker Folder Structure
Bonebreaker
| css
| | default.css
|
| documents
| | cc
| | home.xml
|
| | company
| | home.xml
|
| | dh
| | home.xml
|
| | fr
| | home.xml
|
| | home
| | home.xml
|
| | links
| | home.xml
| stylesheets
| bike.xsl
| menu.xsl
| menupage.xsl
| page.xsl
| section.xsl
--
My Application Folder Structure
GVS
| content
| control
| config
| toc.xml
| home
| home.xml
| view
| xsl
| html
| bike.xsl
| menu.xsl
| menupage.xsl
| page.xsl
| section.xsl
--
--
Pipeline in Bonebreaker Sitemap:
map:pipeline
!-- == homepage == --
map:match pattern=
map:redirect-to session=false uri=bonebreaker/home/home.section/
/map:match
!-- == pages == --
map:match pattern=*/*.**
map:act type=request
map:parameter name=parameters value=true/
map:generate src=documents/{../1}/{../2}.xml{requestQuery}/
map:transform type=xslt src=stylesheets/{../3}.xsl
map:parameter name=section value={1}/
map:parameter name=toc-file
value=../documents/toc.xml/
map:parameter name=base-url
value=/cocoon/bonebreaker/
/map:transform
map:transform type=xslt src=stylesheets/menupage.xsl
map:parameter name=section value={../1}/
map:parameter name=request-url
value={../2}.{../3}/
map:parameter name=toc-file
value=../documents/toc.xml/
map:parameter name=css-stylesheet
value=default.css/
map:parameter name=base-url
value=/cocoon/bonebreaker/
/map:transform
map:serialize/
/map:act
/map:match
!-- == css stylesheets == --
map:match pattern=*.css
map:read src=css/{1}.css mime-type=text/css/
/map:match
/map:pipeline
--
Pipeline in MyApplication Sitemap (All matchers look like the one for home
below, only with home replaced by something else):
map:pipeline
!-- home/*.** --
map:match pattern=home/*.**
map:select type=request
map:parameter name=parameters value=true/
map:generate src=control/home/{../1}.xml{requestQuery}/
!-- Setup Transformation #1 --
map:transform type=xslt src=view/xsl/html/{../2}.xsl
map:parameter name=section value=home/
map:parameter name=toc-file
value=/control/config/toc.xml/
map:parameter name=base-url value=/cocoon/gvs/
/map:transform
!-- Setup Transformation #2 --
map:transform type=xslt src=view/xsl/html/menupage.xsl
map:parameter name=section value=home/
map:parameter name=request-url
value={../1}.{../2}/
map:parameter name=toc-file
value=/control/config/toc.xml/
map:parameter name=css-stylesheet
value=default.css/
map:parameter name=base-url
RE: Some Design Help, please
Thanks for the clue.
I looked into my Cocoon/sitemap.xmap. Here's what I found for Bonebreaker
AND MyApplication:
map:match pattern=bonebreaker/**
map:mount uri-prefix=bonebreaker/ src=bonebreaker/
check-reload=yes/
/map:match
map:match pattern=MyApplication/**
map:mount uri-prefix=MyApplication/ src=MyApplication/
check-reload=yes/
/map:match
With this, bonebreaker works but myapplication doesn't.
I changed the mount src for MyApplication, so it looks like:
map:match pattern=MyApplication/**
map:mount uri-prefix=MyApplication/ src=MyApplication/sitemap.xmap
check-reload=yes/
/map:match
While waiting for the replies, I changed my Pipeline to have nested
matchers:
--
map:pipeline
!-- homepage --
map:match pattern=
map:redirect-to session=false uri=gvs/home/home.section/
/map:match
!-- pages --
map:match pattern=*/*.**
!-- Home --
map:match pattern=home/*.**
map:act type=request
map:parameter name=parameters value=true/
map:generate
src=control/home/{../../1}.xml{requestQuery}/
map:transform type=xslt
src=view/xsl/html/{../../2}.xsl
map:parameter name=section value=home/
map:parameter name=toc-file
value=/control/config/toc.xml/
map:parameter name=base-url
value=/cocoon/gvs/
/map:transform
map:transform type=xslt
src=view/xsl/html/menupage.xsl
map:parameter name=section value=home/
map:parameter name=request-url
value={../../1}.{../../2}/
map:parameter name=toc-file
value=/control/config/toc.xml/
map:parameter name=css-stylesheet
value=default.css/
map:parameter name=base-url
value=/cocoon/gvs/
/map:transform
map:serialize/
/map:act
/map:match
!-- ... More Matchers here ... --
map:pipeline
--
Now it works.
Thanks a lot,
Sreedhar
-Original Message-
From: Andreas Hartmann [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 4:22 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: Some Design Help, please
Hi Sreedhar,
I am trying to fit bonebreaker into a new folder structure to learn some
site map fundas, and I am getting the following error:
org.apache.cocoon.ResourceNotFoundException:
No pipeline matched request: gvs//home/home.section
That might be a problem with your URI prefix.
Could you post a snippet from your main sitemap?
Greetings,
Andreas
The Bonebreaker application itself works perfectly. I wonder why it is
trying to find a match for gvs//home/home.section instead of
gvs/home/home.section? This is probably a frequently made newbie faux
paus
with a stock answer, perhaps?
Differences between Bonebreaker and MyApplication:
My directory Structure is quite different from that of Bonebreaker;
however,
I am using only the files that came with Bonebreaker, but relocated
according to my desired directory structure.
--
Bonebreaker Folder Structure
Bonebreaker
| css
| | default.css
|
| documents
| | cc
| | home.xml
|
| | company
| | home.xml
|
| | dh
| | home.xml
|
| | fr
| | home.xml
|
| | home
| | home.xml
|
| | links
| | home.xml
| stylesheets
| bike.xsl
| menu.xsl
| menupage.xsl
| page.xsl
| section.xsl
--
My Application Folder Structure
GVS
| content
| control
| config
| toc.xml
| home
| home.xml
| view
| xsl
| html
| bike.xsl
| menu.xsl
| menupage.xsl
| page.xsl
| section.xsl
--
--
Pipeline in Bonebreaker Sitemap:
map:pipeline
!-- == homepage == --
map:match pattern=
map:redirect-to session=false uri
Re: Some Design Help, please
Hi, On Tue, 5 Mar 2002, Sreedhar Chintalapaty wrote: How would I do something like that in Cocoon? Can one XSP page dynamically include other XSP pages? I would appreciate -any- examples/sample code! As others have said, there are several ways of doing it. For some examples and sample code, take a look at this: http://www.cocooncenter.de/cocooncenter/tutorials/navigation/tutorial.html The tutorial shows one possibility for creating the navigation elements of a typical website with a simple hierarchic structure. All pages contain a menu bar on the left, the currently selected item is highlighted. You might also like to look at the way the Cocoon documentation pages are generated, which uses aggregation to achieve a similar thing (start in cocoon-2.0.1/src/documentation/). Hope that helps, Andrew. -- Andrew SavoryEmail: [EMAIL PROTECTED] Managing Director Tel: +44 (0)20 8553 6622 Luminas Internet Applications Fax: +44 (0)870 28 47489 This is not an official statement or order.Web:www.luminas.co.uk - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Some Design Help, please
cool - Original Message - From: Andrew Savory [EMAIL PROTECTED] To: Sreedhar Chintalapaty [EMAIL PROTECTED] Cc: Cocoon Users [EMAIL PROTECTED] Sent: Wednesday, March 06, 2002 10:15 AM Subject: Re: Some Design Help, please Hi, On Tue, 5 Mar 2002, Sreedhar Chintalapaty wrote: How would I do something like that in Cocoon? Can one XSP page dynamically include other XSP pages? I would appreciate -any- examples/sample code! As others have said, there are several ways of doing it. For some examples and sample code, take a look at this: http://www.cocooncenter.de/cocooncenter/tutorials/navigation/tutorial.html The tutorial shows one possibility for creating the navigation elements of a typical website with a simple hierarchic structure. All pages contain a menu bar on the left, the currently selected item is highlighted. You might also like to look at the way the Cocoon documentation pages are generated, which uses aggregation to achieve a similar thing (start in cocoon-2.0.1/src/documentation/). Hope that helps, Andrew. -- Andrew SavoryEmail: [EMAIL PROTECTED] Managing Director Tel: +44 (0)20 8553 6622 Luminas Internet Applications Fax: +44 (0)870 28 47489 This is not an official statement or order.Web:www.luminas.co.uk - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Some Design Help, please
Hi all, Thanks a lot for the guidance. I will try out all the options... Sreedhar - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Some Design Help, please
You can do this kind of conditional include in Cocoon quite easily. In an xsl script you can use xsl:if to conditionally produce xinclude references to your other xml documents (toolbar, header, etc). Then your pipeline can use the xinclude transformer to process these include elements and actually include the referenced documents together into a single document. -Original Message- From: Sreedhar Chintalapaty [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 6 March 2002 09:39 To: Cocoon Users Subject: Some Design Help, please Hi, I am an absolute newbie to Cocoon. Being from a JSP background, I suspect there are some fundamental differences in the way a database driven web site is designed for Cocoon (with XSP/XML/XSL). Let's say the users enter the site by the way of index. This page draws its content from several other component pages, namely header, majorTabs, toolBar and contentPage. The requirement is: The active majorTab must be highlighted, each majorTab has a different toolBar associated with it, and the contentPage can be either a static XML file or a database search results page. In the JSP world, I would create an index.jsp page that took in a bunch of request parameters like 'toolBarName', etc., and dynamically include the jsp components specified therein. How would I do something like that in Cocoon? Can one XSP page dynamically include other XSP pages? I would appreciate -any- examples/sample code! Best Regards, Sreedhar Chintalapaty Consultant, PTC - 140 Kendrick St., Needham MA 02494 __ A computer is like an Old Testament god, with a lot of rules and no mercy - Joseph Campbell - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Some Design Help, please
...or you can build up the different pieces using pipelines, later aggregated (using map:aggregate) and finally rendered in HTML using your favorite skin (an XML-to-HTML stylesheet). Well, in my opinion, XSP is not that different from JSP (though, inherenthly better). If I were you, I'd try to make a prototype of my app without using XSP, just to see the potential (and limits) of pure XML/XSL. Best regards, - Luca Morandini GIS Consultant [EMAIL PROTECTED] http://utenti.tripod.it/lmorandini/index.html - -Original Message- From: Conal Tuohy [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 10:53 PM To: Cocoon Users Subject: RE: Some Design Help, please You can do this kind of conditional include in Cocoon quite easily. In an xsl script you can use xsl:if to conditionally produce xinclude references to your other xml documents (toolbar, header, etc). Then your pipeline can use the xinclude transformer to process these include elements and actually include the referenced documents together into a single document. -Original Message- From: Sreedhar Chintalapaty [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 6 March 2002 09:39 To: Cocoon Users Subject: Some Design Help, please Hi, I am an absolute newbie to Cocoon. Being from a JSP background, I suspect there are some fundamental differences in the way a database driven web site is designed for Cocoon (with XSP/XML/XSL). Let's say the users enter the site by the way of index. This page draws its content from several other component pages, namely header, majorTabs, toolBar and contentPage. The requirement is: The active majorTab must be highlighted, each majorTab has a different toolBar associated with it, and the contentPage can be either a static XML file or a database search results page. In the JSP world, I would create an index.jsp page that took in a bunch of request parameters like 'toolBarName', etc., and dynamically include the jsp components specified therein. How would I do something like that in Cocoon? Can one XSP page dynamically include other XSP pages? I would appreciate -any- examples/sample code! Best Regards, Sreedhar Chintalapaty Consultant, PTC - 140 Kendrick St., Needham MA 02494 __ __ __ A computer is like an Old Testament god, with a lot of rules and no mercy - Joseph Campbell - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faqs.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
