« Return to Thread: Error obtaining data from session

Re: Error obtaining data from session

by Raitis :: Rate this Message:

Reply to Author | View in Thread

Hi Florian, this solution don't work, i prepared real example!
At first need to update page-flow file with those records:

<page id="pipe2" path-info="/niis/pipe2" matcher="oxf:glob-matcher" default-submission="schemas/parameters.xml" model="actions/pipe2.xpl">
        <setvalue ref="/*/transname" parameter="transname" />
</page>
<page id="pipe3" path-info="/niis/pipe3" model="actions/pipe3.xpl" />

Pipe1.xpl get data from session and from result with xslt returns one parameter.
Pipe2.xpl get data from url parameter (?transname=), and pipeline return results from pipe1.
And final is pipe3.xpl which use parameters to get from pipe2 service transformation and include it in xslt transformation.

Problem is that if i call from browser ..../niis/pipe2?transname=1 i get result, because pipe1 get session data, but if i call it via pipe3, the input session is null.

So, is there any solution, why pipeline can't access to session!?

actions.zip

fs(ops-users) wrote:
Hi Raitis,

> I have problem when I try to obtain data from session.
> I have created .xpl pipe which use data from session, but there is problem
> when I try to call .xpl pipe from other .xpl pipe.
> Namely, when I open that .xpl pipe (who use session data) directly from
> browser like:
>   http://localhost:8080/orbeon/test1;
> it return session data, but when I call it from other .xpl pipe with any
> processor like:
>   <p:input name="config" href="http://localhost:8080/orbeon/niis/test1"/>;
> I get null.

i'm not whether i understand your problem properly. Should pipeline 1
use the output of pipeline 2? Then you don't need to address a page flow
entry, instead you could use the pipeline processor:

http://www.orbeon.com/ops/doc/processors-pipeline

This is much easier then defining a page-flow entry for the output of
pipeline 2. With the pipeline processor, you can put the complete name
of the second xpl file using a relative path:

<p:input name="config" href="oxf:/niis/test1.xpl"/>

Could this be a solution for you?

If you want to address the xpl using the page flow, you may have to make
sure to use the view attribute instead of the model attribute:

<page id="test1"
     path-info="/niis/test1"
     view="oxf:/niis/test1.xpl"/>


HTH
florian




--
You receive this message as a subscriber of the ops-users@ow2.org mailing list.
To unsubscribe: mailto:ops-users-unsubscribe@ow2.org
For general help: mailto:sympa@ow2.org?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

 « Return to Thread: Error obtaining data from session

LightInTheBox - Buy quality products at wholesale price