New window

Before submitting my form to the database I would like to have preview
of the instance data.
And I would like to open preview in a new window.
For that I use html serializer and some XSLT, but how do I open a new
window for serializer?
Shall I use page flow or there is a hidden setting like:
 <p:processor name="oxf:http-serializer" target="new" />???

Thanks in advance.
-Taras



--
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.



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

This behaviour is controlled client-side.

One option is to have a link in your XHTML, which points to a URL in
your page-flow, which then makes the correct pipeline call to get the
data, eg
<a href="/path/defined/in/page/flow" target="_blank"/>

Another option is to do it with some client-side javascript.

-----Original Message-----
From: Taras Bahnyuk [mailto:[hidden email]]
Sent: 16 January 2006 11:11
To: [hidden email]
Subject: [ops-users] New window

Before submitting my form to the database I would like to have preview
of the instance data.
And I would like to open preview in a new window.
For that I use html serializer and some XSLT, but how do I open a new
window for serializer?
Shall I use page flow or there is a hidden setting like:
 <p:processor name="oxf:http-serializer" target="new" />???

Thanks in advance.
-Taras



--

The information contained in this communication and any attachments is
confidential and may be privileged, and is for the sole use of the
intended recipient(s). Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient,
please notify the sender immediately by replying to this message and
destroy all copies of this message and any attachments. ASML is neither
liable for the proper and complete transmission of the information
contained in this communication, nor for any delay in its receipt.





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

Now the issue arises if you are trying to have the new window access the
instance of the previous window. Somehow, you need to pass some
information between the two.

One solution (unfortunately) is to use the session: store the instance
from the first page into the session with a unique id, and pass that id
on the URL of the new window. Not too clean.

Another solution is to not use another window, but use an HTML DIV
within the same window. The preview would just show the div, which can
overlay the rest of the page.

A solution for the future could be to enhance xforms:message to support
full XHTML + XForms markup. The XForms engine would take care of opening
the window or the overlay. But that's for the future.

-Erik

Stephen Bayliss wrote:


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

Hi,

I'm really confused at the moment.

I'm using a pipeline like:

---------------------------------------------------------------------------------------------------
<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
        xmlns:oxf="http://www.orbeon.com/oxf/processors">
   
    <p:param type="input"  name="data"  debug="input-data"/>
        <p:param type="input"  name="create_data" debug="create_data"/>
        <p:param type="output" name="data"  debug="output-data"/>

    <p:processor name="oxf:xslt">
              <p:input  name="data"   href="#data"/>
        <p:input  name="create_data"   href="#create_data"/>      
              <p:input  name="config" href="paratestTemplate.xsl"/>
              <p:output name="data" ref="data" debug="basti"/>
          </p:processor>
    </p:config>
---------------------------------------------------------------------------------------------------
Called from a pipeline like
---------------------------------------------------------------------------------------------------
 <p:processor name="oxf:pipeline">
        <p:input name="config" href="paratest2.xpl"/>
        <p:input name="data" href="#input"/>        
        <p:output name="data" id="result"/>  
    </p:processor>
---------------------------------------------------------------------------------------------------

The input create_data is never connected.
On my local server everything works fine (that means, I get right results from the XSLT transformation where only the "data" input is used.
On another Server I get an error "Pipeline input "create_data" is not connected" which is obviously correct.

Somebody can explain this behaviour?

Thanks

Sebastian

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

I figured out, that this has something to do wit debug attributes. If they exist it works.
What is the reason?

Sebastian

"Sebastian Kraus/INPLUS/DE" <[hidden email]> 27.06.2006 13:32 Please respond to [hidden email]

To [hidden email] cc Subject [ops-users] Different debug behaviour on different servers

Hi,

I'm really confused at the moment.

I'm using a pipeline like:

---------------------------------------------------------------------------------------------------
<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
       xmlns:oxf="http://www.orbeon.com/oxf/processors">
   
   <p:param type="input"  name="data"  debug="input-data"/>
       <p:param type="input"  name="create_data" debug="create_data"/>
       <p:param type="output" name="data"  debug="output-data"/>

   <p:processor name="oxf:xslt">
             <p:input  name="data"   href="#data"/>
       <p:input  name="create_data"   href="#create_data"/>      
             <p:input  name="config" href="paratestTemplate.xsl"/>
             <p:output name="data" ref="data" debug="basti"/>
         </p:processor>
   </p:config>
---------------------------------------------------------------------------------------------------
Called from a pipeline like
---------------------------------------------------------------------------------------------------
<p:processor name="oxf:pipeline">
       <p:input name="config" href="paratest2.xpl"/>
       <p:input name="data" href="#input"/>        
       <p:output name="data" id="result"/>  
   </p:processor>
---------------------------------------------------------------------------------------------------

The input create_data is never connected.
On my local server everything works fine (that means, I get right results from the XSLT transformation where only the "data" input is used.
On another Server I get an error "Pipeline input "create_data" is not connected" which is obviously correct.

Somebody can explain this behaviour?

Thanks

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

On 6/27/06, Sebastian Kraus/INPLUS/DE <[hidden email]> wrote:
> On my local server everything works fine (that means, I get right results
> from the XSLT transformation where only the "data" input is used.
> On another Server I get an error "Pipeline input "create_data" is not
> connected" which is obviously correct.

Hi Sebastian,

XPL is evaluated lazily. So the create_data input of the XSLT
processor will be read only if the stylesheet reads that input. At
that time XPL will read the create_data input of the pipeline and
realize that this input is not connected.

Could it be the case that the execution path of the stylesheet is
different on both machines, and that on one it reads input:create_data
in the stylesheet but not on the other?

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/



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

Hi Alex,

no, the funny thing is: The create_data input is never read.

When I use
<p:param type="input"  name="create_data" debug="create_data"/>
it works,

Without the debug variable
<p:param type="input"  name="create_data"/>
it doesn't.

Of course an easy solution is not to use this input. But I'm just interested.

Sebastian

"Alessandro Vernet" <[hidden email]> Sent by: [hidden email] 27.06.2006 23:45 Please respond to [hidden email]

To [hidden email] cc Subject Re: [ops-users] Different debug behaviour on different servers

On 6/27/06, Sebastian Kraus/INPLUS/DE <[hidden email]> wrote:
> On my local server everything works fine (that means, I get right results
> from the XSLT transformation where only the "data" input is used.
> On another Server I get an error "Pipeline input "create_data" is not
> connected" which is obviously correct.

Hi Sebastian,

XPL is evaluated lazily. So the create_data input of the XSLT
processor will be read only if the stylesheet reads that input. At
that time XPL will read the create_data input of the pipeline and
realize that this input is not connected.

Could it be the case that the execution path of the stylesheet is
different on both machines, and that on one it reads input:create_data
in the stylesheet but not on the other?

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/


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

On 6/28/06, Sebastian Kraus/INPLUS/DE <[hidden email]> wrote:
> no, the funny thing is: The create_data input is never read.

Sebastian,

Are you saying the the 'create_data' input of the XSLT stylesheet is
never used in the stylesheet? You never do doc('input:create_data') in
that stylesheet?

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/



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

Sebastian,

For reference, see the pipeline below. You can run this in the XPL
sandbox, and I added there an input 'gaga', which I connected to the
identity processor. The 'gaga' input of the pipeline is not connected
as whoever runs that pipeline does not know about the 'gaga' input,
and the identity processor does not read its 'gaga' input. Hence
everything runs fine.

I would be interested if you can create a pipeline similar to the one
below that would generate an error, like the one you have in your
pipeline.

<p:config xmlns:p="http://www.orbeon.com/oxf/pipeline"
    xmlns:oxf="http://www.orbeon.com/oxf/processors">

    <p:param type="input" name="data"/>
    <p:param type="input" name="gaga"/>
    <p:param type="output" name="data"/>

    <p:processor name="oxf:identity">
        <p:input name="data" href="#data"/>
        <p:input name="gaga" href="#gaga"/>
        <p:output name="data" ref="data"/>
    </p:processor>

</p:config>

Alex

On 7/3/06, Alessandro Vernet <[hidden email]> wrote:
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/



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