You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de> on 2002/11/01 09:37:03 UTC

Re: Accessing the output of a modular db action in xsl

On 31.Oct.2002 -- 01:08 PM, pwcml@blackbearsolutions.com wrote:
> Is there an example of how to do this available?

>From XSL? I don't think so. At least not specifically with database
actions. There sure is one on accessing request attributes from xsl
-- although I don't know off head.

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Phil Craven <pj...@mail.com>.
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-info>true</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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
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-info>true</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.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Phil Craven <pj...@mail.com>.
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-info>true</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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 03.Nov.2002 -- 12:03 PM, Phil Craven wrote:
> 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}" ?

Phil, when you are at level 2, level 3 does not exist yet. Therefore
you can only move up. Perhaps you can illustrate with a sitemap
snippet what you are trying to achieve, maybe it would be clearer.

	Chris.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Phil Craven <pw...@blackbearsolutions.com>.
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
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.
-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Phil Craven <pj...@mail.com>.
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=bbs&content_item_id=gold+building+image&content_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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>


Re: Accessing the output of a modular db action in xsl

Posted by Antonio Gallardo Rivera <ag...@agsoftware.dnsalias.com>.
Dont know if this can helps you, but maybe XSP session can help you.

Antonio Gallardo.

El Viernes, 01 de Noviembre de 2002 02:37, Christian Haul escribió:
> On 31.Oct.2002 -- 01:08 PM, pwcml@blackbearsolutions.com wrote:
> > Is there an example of how to do this available?
>
> From XSL? I don't think so. At least not specifically with database
> actions. There sure is one on accessing request attributes from xsl
> -- although I don't know off head.
>
> 	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:     <co...@xml.apache.org>
For additional commands, e-mail:   <co...@xml.apache.org>