DatabaseSelectAction and results using

2007-06-17 Thread SETIssl
ok, since i couldn't find any example or understandable description on how  
to get a simple DatabaseSelectAction to work, i'll try here, maybe someone  
came across this before :>


deskriptor-file ""database.xml":


   testdb
   
  autoincrement="true" mode="manual"/>

  


  
   


Do i have to list all table coloums here, or just the one(s) i need for  
the select, to get data from?
Must the Select-Request be embbeded in this file or in the action inside  
the pipeline?



Action-Usage in the Sitemap/Pipeline:

  
  
  
  
  
  
  

  
  
value="{request-attr:output}"/>


  ...
  ...
  ...

  

So, i want to get the type_id from the documents-table, in the row, where  
"name"  {3} (document name).
This result should be used as a select-parameter, for different  
proceedings for every id.Ho


How should the Queryparameterpart in the Action look like? Something like  
the part, i tried? :>

How to pass the action-result to the select-parameter?
Can i get a log output or whatever of the select-result?

thx for all useful answers
SETIssl

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: request parameter from sax stream/xml file to sitemap

2007-05-22 Thread SETIssl

"What makes this case really complicated is that you have a
two-step-processing of pipeline content. It would be much easier if you
could determine the norm_id directly"

Hm, thought this was, was actions are used for, among other things.
The Pipeline gets called from an HTML-Href-Link inside of an generated  
html-file:


dokumente/anzeigen/pdf/select="document-type"/>//select="document-name"/>?realpath=select="realpath"/>





  

  test="{request-param:realpath}/letterman/userfiles/{2}/docs/{3}.xml">


  ...

So, when i got the "docname" {3} in the pipeline, would it be so hard to  
insert a database select action there
and request the current norm_id for this document and use the response as  
a parameter for further select-operations?


Problem is, i'm not familiar with the hole flowscript-programming
and i wouldn't like to mix up the Sitemap/Pipeline with the old  
standard-elements

und the new flowscript-system, as it is an old programm which just
should be updated and expanded a little.


Am 29.04.2007, 12:31 Uhr, schrieb Joerg Heinicke <[EMAIL PROTECTED]>:


On 23.04.2007 17:27, SETIssl wrote:

I tried to implement a DatabaseSelectAction like its described in the  
docs and the api, but couldn't find any details or any kind of example  
on how the request/the sitemap pipeline action part actually should  
look like.


 From rereading the thread I get your case is more complex. The actions  
might not work or really complicate your sitemap a lot. I'd go with flow  
script.


To clarify let me rephrase your steps:
1. Get a document from the document system. (How is determined which  
document?)
2. Parse it for whatever to retrieve norm_id with that information from  
the database.

3. Switch pipeline depending on this norm_id.

What makes this case really complicated is that you have a  
two-step-processing of pipeline content. It would be much easier if you  
could determine the norm_id directly from the "How is determined which  
document?"-parameters without parsing pipeline content. Is that an  
option?





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: request parameter from sax stream/xml file to sitemap

2007-04-23 Thread SETIssl

Thanks for your reply.

I tried to implement a DatabaseSelectAction like its described in the docs  
and the api, but couldn't find any details or any kind of example on how  
the request/the sitemap pipeline action part actually should look like.


so if anyone got this action type working or a link to a tutorial showing  
the codeon an example, i would like to take a look at it.


grettings SETIssl


Am 14.03.2007, 08:01 Uhr, schrieb Joerg Heinicke <[EMAIL PROTECTED]>:


On 13.03.2007 23:35, SETIssl wrote:

All working fine till here, the transformer gets the documents norm id  
from the database and puts it in the sax stream(?) in the place where  
 was before.
But now in the next step i need this norm_id value in the sitemap for  
choosing the next transformation file related to the choosen norm.
I wrote the following pipeline code, which should be working fine,  
except from the problem of getting the norm id value loaded as a  
parameter in there (marked with ???):


No chance up to now. Despite existing ideas content-based pipelines have  
never been implemented.


You need to retrieve the database id before the pipeline is set up,  
either via flow script or via an action.


Jörg

-
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]



request parameter from sax stream/xml file to sitemap

2007-03-13 Thread SETIssl
hello, i need some advice for my document management application based on  
cocoon.


i've got an xml-file with the structure

 
 ...


Now this file gets loaded into a pipeline with the file generator and  
transformed in the next step by an xslt-transformer, which contains the  
following template:


  http://apache.org/cocoon/SQL/2.0";>

  SELECT norm_id FROM documents WHERE name = 'test'

  


All working fine till here, the transformer gets the documents norm id  
from the database and puts it in the sax stream(?) in the place where  
 was before.
But now in the next step i need this norm_id value in the sitemap for  
choosing the next transformation file related to the choosen norm.
I wrote the following pipeline code, which should be working fine, except  
from the problem of getting the norm id value loaded as a parameter in  
there (marked with ???):


  

  
type="xslt">


  
  
type="xslt">


  


I found some similar entries by searching the mailing list, but nothing  
clear that was useful for me so far.
I hope i explained my problem clear and somebody can help me with it, as  
it is the last piece of my application puzzle :)


greetings Sebastian

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]