Orbeon Forms community mailing list

Reactivationg a dynamically built page

Classic

List

Threaded

6 messages Options

Florian Schmitt-2

Reactivationg a dynamically built page

Hi,

i've got a problem regarding the navigation between dynamically build pages.

My application has three pages, A, B and C. A and B are XForms Pages
displaying the content of eXist-db collections, C displays a single XML
resource. B is dynamically built depending on the submission of page A,
C on that of B. The user should have the possibility to navigate from
C back to B:

----- ----- -----
| A | --> | B | --> | C |
----- ----- -----
^ |
| |
---------

The problem is how to (re)build page B if the user leaves C. One way
would be to pass the submission A-B to C, but page C already gets a big
XML file submitted so i don't want to increase the amount of data passed
to C. Is there a way to make the submission that B received "persistent"
so it could get "re-activated" if the user leaves C?

florian

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

marc-62

Re: Reactivationg a dynamically built page

Hi florian,

Could eXist be a way to keep the information to build page B ?

--
Marc

Florian Schmitt a écrit :

> Hi,
>
> i've got a problem regarding the navigation between dynamically build
> pages.
>
> My application has three pages, A, B and C. A and B are XForms Pages
> displaying the content of eXist-db collections, C displays a single
> XML resource. B is dynamically built depending on the submission of
> page A,
> C on that of B. The user should have the possibility to navigate from
> C back to B:
>
> ----- ----- -----
> | A | --> | B | --> | C |
> ----- ----- -----
> ^ |
> | |
> ---------
>
> The problem is how to (re)build page B if the user leaves C. One way
> would be to pass the submission A-B to C, but page C already gets a
> big XML file submitted so i don't want to increase the amount of data
> passed to C. Is there a way to make the submission that B received
> "persistent" so it could get "re-activated" if the user leaves C?
>
> florian
>
>
>------------------------------------------------------------------------
>
>
>--
>You receive this message as a subscriber of the [hidden email] mailing list.
>To unsubscribe: mailto:[hidden email]
>For general help: mailto:[hidden email]?subject=help
>ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Florian Schmitt-2

Re: Reactivationg a dynamically built page

Hi Marc,

> Could eXist be a way to keep the information to build page B ?

Good idea, but if there are multiple sessions active i have to ensure
that the saved data contains session information and (ideally) could get
read only by the user that submitted the data. Furthermore, if i write
the data to eXist there should be some kind of "garbage collection" that
removes outdated files if the session is closed. So I hoped that there
would be a solution "inside" OPS.

florian

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

smime.p7s (6K) Download Attachment

marc-62

Re: Reactivationg a dynamically built page

Florian,

>> Could eXist be a way to keep the information to build page B ?

>Good idea, but if there are multiple sessions active i have to ensure
that the saved data contains session information and (ideally) could get
read only by the user that >submitted the data. Furthermore, if i write
the data to eXist there should be some kind of "garbage collection" that
removes outdated files if the session is closed. So I >hoped that there
would be a solution "inside" OPS.

I'm facing the same problem : ( "XForms error: Unable to retrieve
XForms engine state from session cache" ) and multiple instances
So I planned to keep session informations with the "scope-serializer"
and put the necessary datas for the "back button" in eXist with the
session infos.
Of course it would be cool if we could have the information that the
session is over.
BTW, is there any way to intercept the use of the "previous" button of
the browser ?

Marc

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Florian Schmitt-2

Re: Reactivationg a dynamically built page

Hi marc,

> I'm facing the same problem : ( "XForms error: Unable to retrieve
> XForms engine state from session cache" ) and multiple instances
> So I planned to keep session informations with the "scope-serializer"
> and put the necessary datas for the "back button" in eXist with the
> session infos.

thank you for the hint regarding the scope-serializer - that's the tool
i was searching for, because it could lead to a solution without
saving the data to eXist. Using its data input one can make the data
needed to build page B "session-persistent" and read it again using the
scope generator:

At the beginning of the XPL pipeline that collects the data to build
page B, one can test if the input is a "null" document or not.

- If there's data (user proceeds from page A), it gets
"scope-serialized" and the pipeline continues as usual.

- If there's no data (user returns from page C), a scope-generator is
used to retrieve any persistent data, and the pipeline continues with
that data as input.

Seems to work fine :-)

florian

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

marc-62

Re: Reactivationg a dynamically built page

Florian Schmitt a écrit :

> Hi marc,
>
> thank you for the hint regarding the scope-serializer - that's the
> tool i was searching for, because it could lead to a solution without
> saving the data to eXist. Using its data input one can make the data
> needed to build page B "session-persistent" and read it again using
> the scope generator:
>
eXist can help if the amount of data is to big to be
"session-persistent". Of course if the data is a small XML that's ok
with the scope-serializer.

> At the beginning of the XPL pipeline that collects the data to build
> page B, one can test if the input is a "null" document or not.
>
> - If there's data (user proceeds from page A), it gets
> "scope-serialized" and the pipeline continues as usual.
>
> - If there's no data (user returns from page C), a scope-generator is
> used to retrieve any persistent data, and the pipeline continues with
> that data as input.
>

Yes it should works.

Marc

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws