Re: need example of modular db select at work
Right, those are great, but i need an example of the select at work and can't seem to find one. On Tuesday 12 November 2002 09:21 pm, Antonio Gallardo R. wrote: Check the examples of mod-db in your Cocoon installation. Antonio Gallardo Is there anyone that can provide a working example of the modular db select. An addtional bonus would be to see how to get at the values output from the action in the sitemap. Thanks, Phil - 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]
Re: Accessing the output of a modular db action in xsl
I tried that as well, and only row-count would come through, I was unable to get the selected parameters even though I used map:parameter name= value= so what would the correct map:parameter look like to get at the output of a mod-db select. Just to reiterate I appologize for being dense and greatly appreciate the help (in case I forgot to mention earlier) On Tuesday 05 November 2002 01:39 pm, Christian Haul wrote: On 04.Nov.2002 -- 07:43 PM, Phil Craven wrote: here is the sitemap segment that shows what I am trying to do. map:match pattern=group2.xsp map:act type=mod-db-sel action=sel-ci map:parameter name=table-set value=content_item/ map:generate type=serverpages src=group2.xsp/ map:transform src=xsl/dynamic-page2html.xsl/ map:transform src=xsl/stupid.xsl map:parameter name=use-request-parameters value=true/ use-session-infotrue/use-session-info /map:transform map:serialize/ /map:act map:read src=finished.html/ map:serialize type=html/ /map:match The kicker is that I can see the values in the logs, but I cannot see the values reflected in the xsl. On a related not, if I add row-count in as a parameter, then it will show up in the xsl, but no other values will. Phil, what do you mean with not in the xsl? Which xsl? Sitemap variables are never automatically propagated to any other component. This needs to be done explicitly e.g. using map:parameter/ Results from a database action are available as request attributes as well. 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]
Re: Accessing the output of a modular db action in xsl
I tried that as well, and only row-count would come through, I was unable to get the selected parameters even though I used map:parameter name= value= so what would the correct map:parameter look like to get at the output of a mod-db select. Just to reiterate I appologize for being dense and greatly appreciate the help (in case I forgot to mention earlier) On Tuesday 05 November 2002 01:39 pm, Christian Haul wrote: On 04.Nov.2002 -- 07:43 PM, Phil Craven wrote: here is the sitemap segment that shows what I am trying to do. map:match pattern=group2.xsp map:act type=mod-db-sel action=sel-ci map:parameter name=table-set value=content_item/ map:generate type=serverpages src=group2.xsp/ map:transform src=xsl/dynamic-page2html.xsl/ map:transform src=xsl/stupid.xsl map:parameter name=use-request-parameters value=true/ use-session-infotrue/use-session-info /map:transform map:serialize/ /map:act map:read src=finished.html/ map:serialize type=html/ /map:match The kicker is that I can see the values in the logs, but I cannot see the values reflected in the xsl. On a related not, if I add row-count in as a parameter, then it will show up in the xsl, but no other values will. Phil, what do you mean with not in the xsl? Which xsl? Sitemap variables are never automatically propagated to any other component. This needs to be done explicitly e.g. using map:parameter/ Results from a database action are available as request attributes as well. 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]
Re: Accessing the output of a modular db action in xsl
here is the sitemap segment that shows what I am trying to do. map:match pattern=group2.xsp map:act type=mod-db-sel action=sel-ci map:parameter name=table-set value=content_item/ map:generate type=serverpages src=group2.xsp/ map:transform src=xsl/dynamic-page2html.xsl/ map:transform src=xsl/stupid.xsl map:parameter name=use-request-parameters value=true/ use-session-infotrue/use-session-info /map:transform map:serialize/ /map:act map:read src=finished.html/ map:serialize type=html/ /map:match The kicker is that I can see the values in the logs, but I cannot see the values reflected in the xsl. On a related not, if I add row-count in as a parameter, then it will show up in the xsl, but no other values will. Once again any help greatly appreciated. --- - 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: Accessing the output of a modular db action in xsl
here is the sitemap segment that shows what I am trying to do. map:match pattern=group2.xsp map:act type=mod-db-sel action=sel-ci map:parameter name=table-set value=content_item/ map:generate type=serverpages src=group2.xsp/ map:transform src=xsl/dynamic-page2html.xsl/ map:transform src=xsl/stupid.xsl map:parameter name=use-request-parameters value=true/ use-session-infotrue/use-session-info /map:transform map:serialize/ /map:act map:read src=finished.html/ map:serialize type=html/ /map:match The kicker is that I can see the values in the logs, but I cannot see the values reflected in the xsl. On a related not, if I add row-count in as a parameter, then it will show up in the xsl, but no other values will. Once again any help greatly appreciated. - 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: Accessing the output of a modular db action in xsl
because that is going the wrong way, I don't want one level up, I want one
level down. Also I would be just as happy getting the values out of the
request attributes (in the xsl), but I cannot seem to figure out how to do
so. If anyone has any help on either getting at those values in xsl I would
greatly appreciate the help.
phil
On Saturday 02 November 2002 10:48 am, Christian Haul wrote:
On 02.Nov.2002 -- 07:22 AM, Phil Craven wrote:
When I try and get the bulk of the params that I am looking for, it seems
as if they are lost between level 3 and level 2. I believe that my
stylesheet is trying to access the params at level 2. How do I force the
propagation of the values from level 3 to level 2? Any help greatly
appreciated.
Here is the relevant section of the sitemap log:
LEVEL 3
PARAM: 'content_item_id[0]' VALUE: 'gold building image'
LEVEL 2
PARAM: '../context' VALUE: '/cocoon'
LEVEL 1
PARAM: '../../1' VALUE: 'group2'
Why don't you use {../context} ?
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]
Re: Accessing the output of a modular db action in xsl
When I try and get the bulk of the params that I am looking for, it seems as if they are lost between level 3 and level 2. I believe that my stylesheet is trying to access the params at level 2. How do I force the propagation of the values from level 3 to level 2? Any help greatly appreciated. Here is the relevant section of the sitemap log: LEVEL 3 PARAM: 'content_item_id[0]' VALUE: 'gold building image' PARAM: 'row-count' VALUE: '1' PARAM: 'width[0]' VALUE: '150' PARAM: 'align[0]' VALUE: 'right' PARAM: 'site_id[0]' VALUE: 'bbs' PARAM: 'class[0]' VALUE: '' PARAM: 'verbage[0]' VALUE: '' PARAM: 'content_item_type[0]' VALUE: 'image' PARAM: 'height[0]' VALUE: '100' PARAM: 'href[0]' VALUE: 'gold_building.jpg' LEVEL 2 PARAM: '../href' VALUE: '' PARAM: '../width' VALUE: '' PARAM: '../context' VALUE: '/cocoon' PARAM: '../class' VALUE: '' PARAM: '../requestURI' VALUE: '/cocoon/formsample/group2.xsp' PARAM: '../content_item_type' VALUE: '' PARAM: '../verbage' VALUE: '' PARAM: '../cocoon-action-sel-ci' VALUE: 'new ci' PARAM: '../align' VALUE: '' PARAM: '../site_id' VALUE: 'bbs' PARAM: '../requestQuery' VALUE: '?site_id=bbscontent_item_id=gold+building+imagecontent_item_type=class=verbage=href=align=height=width=cocoon-action-sel-ci=new+ci' PARAM: '../content_item_id' VALUE: 'gold building image' PARAM: '../height' VALUE: '' LEVEL 1 PARAM: '../../1' VALUE: 'group2' PARAM: '../../0' VALUE: 'group2.xsp' - 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]
mod-db not working in latest build
I have tried the last few cvs drops, and mod-db is not working. When you try and add a group, a row is added, but the values are null. Am I missing something or doing something wrong. i would really like to try mod-db out, so any hints would be greatly appreciated. Thanks, Phil - 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]
