Question on XML submissions

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Question on XML submissions

Robin Diederen
Question on XML submissions
Hello all,
 
I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).
 

I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY

<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL

<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:

<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):

<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>


When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best,
           



--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Question on XML submissions

HankRatz
<base href="x-msg://248/">Robin,

I realize you are including snippets, but I want to check that your submission and instance 
elements are all in the html head element.

I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what
is submitted and transformed at each step.  I comment out, e.g., the http serializer and 
reference the input or output of each step.  (or use the logs and debug as you do...)

In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?

If your submission replace attribute is "all", then you probably don't also need an 
action in the page flow, since the replace will "take you to a new page" as the 
action will, loading a new url in the browser address bar.

I'm not much help with a specific diagnosis, but if we knew that your submission 
was reaching a target xpl script (even if it just serializes the submitted data 
back), that would be some help to understand.

Cheers,
Hank

On Jan 28, 2010, at 8:07 AM, Robin Diederen wrote:

Hello all,
 
I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).
 
I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY
<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL
<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:
<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):
<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>

When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best, 
            

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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042







--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

RE: Re: Question on XML submissions

Robin Diederen
RE: [ops-users] Re: Question on XML submissions

 Hello Hank,

 

Thanks for the extensive answer!

 

> but I want to check that your submission and instance elements are all in the html head element.

 

Yes, the submission and instance elemets are all placed in the head section.

 

> I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what is submitted and transformed at each step.  I comment out, e.g., the http serializer and reference the input or output of each step.  (or use the logs and debug as you do...)
 
Sounds like an interesting option for debugging. Would you have an example?

 

> In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 

sure what the effect is of using xsl within the pageflow -- is it possible?
 
It should be, according to the Orbeon documentation (I found an example somewhere). Would you have an example of code using the model attribute to initiate a pipeline? I'd like to give that a try.

 

> If your submission replace attribute is "all", then you probably don't also need an action in the page flow, since the replace will "take you to a new page" as the action will, loading a new url in the browser address bar.

 

Well I got the "replace=all" construct from an example too. I was looking into its definition, didn't find any decent documentation though. Is this the preferred way for entering data into pipelines?

 

> I'm not much help with a specific diagnosis, but if we knew that your submission was reaching a target xpl script (even if it just serializes the submitted data back), that would be some help to understand.
 
Actually you've been quite helpful already :-). I don't know for sure, but I'm fairly sure that my submission never ever reaches a target XPL. Using a debug footer, I find that the data I enter on the form is serialized into the document I want to submit.
 
Best, Robin.
 
-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 18:00
To: [hidden email];
Subject: [ops-users] Re: Question on XML submissions

Robin,
 
I realize you are including snippets, but I want to check that your submission and instance 
elements are all in the html head element.
 
I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what
is submitted and transformed at each step.  I comment out, e.g., the http serializer and 
reference the input or output of each step.  (or use the logs and debug as you do...)
 
In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
If your submission replace attribute is "all", then you probably don't also need an 
action in the page flow, since the replace will "take you to a new page" as the 
action will, loading a new url in the browser address bar.
 
I'm not much help with a specific diagnosis, but if we knew that your submission 
was reaching a target xpl script (even if it just serializes the submitted data 
back), that would be some help to understand.
 
Cheers,
Hank

On Jan 28, 2010, at 8:07 AM, Robin Diederen wrote:

Hello all,
 
I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).
 
I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY
<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL
<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:
<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):
<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>

When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best, 
            

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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042
 
 
 

 



--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: RE: Re: Question on XML submissions

HankRatz
<base href="x-msg://271/">

If I may top-post... Its just the way I got started, and likely debug 
attributes are better in the long run, but...


<!-- page-flow.xml -->
<page id="my-service"
model="/my-service.xpl"/>


<!-- my-service.xpl -->

<p:config

<p:param name="instance" type="input"/>

<!-- Get the instance paramters -->
<p:processor name="oxf:request">
<p:input name="config">
<config>
<include>/request/parameters</include>
</config>
</p:input>
<p:output name="data" id="params"/>
</p:processor>

<p:processor name="oxf:xml-serializer">
<p:input name="config">
<config>
  <content-type>text/xml</content-type>
</config>
</p:input>
<p:input name="data" href="#input"/> 
<!-- or #params, or #whatever-processor-outputs in between -->
</p:processor>

</p:config>

--Hank

On Jan 28, 2010, at 9:59 AM, Robin Diederen wrote:

 Hello Hank,

 

Thanks for the extensive answer!

 

> but I want to check that your submission and instance elements are all in the html head element.

 

Yes, the submission and instance elemets are all placed in the head section.

 

> I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what is submitted and transformed at each step.  I comment out, e.g., the http serializer and reference the input or output of each step.  (or use the logs and debug as you do...)
 
Sounds like an interesting option for debugging. Would you have an example?

 

> In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
It should be, according to the Orbeon documentation (I found an example somewhere). Would you have an example of code using the model attribute to initiate a pipeline? I'd like to give that a try.

 

> If your submission replace attribute is "all", then you probably don't also need an action in the page flow, since the replace will "take you to a new page" as the action will, loading a new url in the browser address bar.

 

Well I got the "replace=all" construct from an example too. I was looking into its definition, didn't find any decent documentation though. Is this the preferred way for entering data into pipelines?

 

> I'm not much help with a specific diagnosis, but if we knew that your submission was reaching a target xpl script (even if it just serializes the submitted data back), that would be some help to understand.
 
Actually you've been quite helpful already :-). I don't know for sure, but I'm fairly sure that my submission never ever reaches a target XPL. Using a debug footer, I find that the data I enter on the form is serialized into the document I want to submit.
 
Best, Robin.
 
-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 18:00
To: [hidden email]; 
Subject: [ops-users] Re: Question on XML submissions

Robin,
 
I realize you are including snippets, but I want to check that your submission and instance 
elements are all in the html head element.
 
I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what
is submitted and transformed at each step.  I comment out, e.g., the http serializer and 
reference the input or output of each step.  (or use the logs and debug as you do...)
 
In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
If your submission replace attribute is "all", then you probably don't also need an 
action in the page flow, since the replace will "take you to a new page" as the 
action will, loading a new url in the browser address bar.
 
I'm not much help with a specific diagnosis, but if we knew that your submission 
was reaching a target xpl script (even if it just serializes the submitted data 
back), that would be some help to understand.
 
Cheers,
Hank

On Jan 28, 2010, at 8:07 AM, Robin Diederen wrote:

Hello all,
 
I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).
 
I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY
<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL
<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:
<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):
<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>

When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best, 
            

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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042
 
 
 

 


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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042







--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: RE: Re: Question on XML submissions

Robin Diederen
[ops-users] Re: RE: Re: Question on XML submissions

Hi Hank,

 

That seems faily straightforward. What code do you use to submit data from the "input" form?

 

Best, Robin
 

-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 20:01
To: [hidden email];
Subject: [ops-users] Re: RE: Re: Question on XML submissions

 
If I may top-post... Its just the way I got started, and likely debug 
attributes are better in the long run, but...
 
 
<!-- page-flow.xml -->
<page id="my-service"
model="/my-service.xpl"/>
 
 
<!-- my-service.xpl -->
 
<p:config
 
<p:paramname="instance"type="input"/>
 
<!-- Get the instance paramters -->
<p:processorname="oxf:request">
<p:inputname="config">
<config>
<include>/request/parameters</include>
</config>
</p:input>
<p:outputname="data"id="params"/>
</p:processor>

<p:processorname="oxf:xml-serializer">
<p:inputname="config">
<config>
  <content-type>text/xml</content-type>
</config>
</p:input>
<p:inputname="data"href="#input"/> 
<!-- or #params, or #whatever-processor-outputs in between -->
</p:processor>
 
</p:config>
 
--Hank

On Jan 28, 2010, at 9:59 AM, Robin Diederen wrote:

 Hello Hank,

 

Thanks for the extensive answer!

 

> but I want to check that your submission and instance elements are all in the html head element.

 

Yes, the submission and instance elemets are all placed in the head section.

 

> I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what is submitted and transformed at each step.  I comment out, e.g., the http serializer and reference the input or output of each step.  (or use the logs and debug as you do...)
 
Sounds like an interesting option for debugging. Would you have an example?

 

> In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
It should be, according to the Orbeon documentation (I found an example somewhere). Would you have an example of code using the model attribute to initiate a pipeline? I'd like to give that a try.

 

> If your submission replace attribute is "all", then you probably don't also need an action in the page flow, since the replace will "take you to a new page" as the action will, loading a new url in the browser address bar.

 

Well I got the "replace=all" construct from an example too. I was looking into its definition, didn't find any decent documentation though. Is this the preferred way for entering data into pipelines?

 

> I'm not much help with a specific diagnosis, but if we knew that your submission was reaching a target xpl script (even if it just serializes the submitted data back), that would be some help to understand.
 
Actually you've been quite helpful already :-). I don't know for sure, but I'm fairly sure that my submission never ever reaches a target XPL. Using a debug footer, I find that the data I enter on the form is serialized into the document I want to submit.
 
Best, Robin.
 
-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 18:00
To: [hidden email]
Subject: [ops-users] Re: Question on XML submissions

Robin,
 
I realize you are including snippets, but I want to check that your submission and instance 
elements are all in the html head element.
 
I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what
is submitted and transformed at each step.  I comment out, e.g., the http serializer and 
reference the input or output of each step.  (or use the logs and debug as you do...)
 
In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
If your submission replace attribute is "all", then you probably don't also need an 
action in the page flow, since the replace will "take you to a new page" as the 
action will, loading a new url in the browser address bar.
 
I'm not much help with a specific diagnosis, but if we knew that your submission 
was reaching a target xpl script (even if it just serializes the submitted data 
back), that would be some help to understand.
 
Cheers,
Hank

On Jan 28, 2010, at 8:07 AM, Robin Diederen wrote:

Hello all,
 
I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).
 
I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY
<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL
<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:
<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):
<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>

When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best, 
            

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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042
 
 
 

 


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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042
 
 
 




--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: RE: Re: Question on XML submissions

HankRatz
<base href="x-msg://282/">
On Jan 28, 2010, at 11:10 AM, Robin Diederen wrote:

Hi Hank,

 

That seems faily straightforward. What code do you use to submit data from the "input" form?

you can use get or post.  use replace="all" to see the results in the browser. 

Mostly I don't move the user off the page, so eventually I use replace="instance" when 
I know things are working, and the inspector at the bottom of my page if I need
to look at specific results.

Cheers,
Hank


 

Best, Robin
 
-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 20:01
To: [hidden email]; 
Subject: [ops-users] Re: RE: Re: Question on XML submissions

 
If I may top-post... Its just the way I got started, and likely debug 
attributes are better in the long run, but...
 
 
<!-- page-flow.xml -->
<page id="my-service"
model="/my-service.xpl"/>
 
 
<!-- my-service.xpl -->
 
<p:config
 
<p:paramname="instance"type="input"/>
 
<!-- Get the instance paramters -->
<p:processorname="oxf:request">
<p:inputname="config">
<config>
<include>/request/parameters</include>
</config>
</p:input>
<p:outputname="data"id="params"/>
</p:processor>

<p:processorname="oxf:xml-serializer">
<p:inputname="config">
<config>
  <content-type>text/xml</content-type>
</config>
</p:input>
<p:inputname="data"href="#input"/> 
<!-- or #params, or #whatever-processor-outputs in between -->
</p:processor>
 
</p:config>
 
--Hank

On Jan 28, 2010, at 9:59 AM, Robin Diederen wrote:

 Hello Hank,

 

Thanks for the extensive answer!

 

> but I want to check that your submission and instance elements are all in the html head element.

 

Yes, the submission and instance elemets are all placed in the head section.

 

> I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what is submitted and transformed at each step.  I comment out, e.g., the http serializer and reference the input or output of each step.  (or use the logs and debug as you do...)
 
Sounds like an interesting option for debugging. Would you have an example?

 

> In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
It should be, according to the Orbeon documentation (I found an example somewhere). Would you have an example of code using the model attribute to initiate a pipeline? I'd like to give that a try.

 

> If your submission replace attribute is "all", then you probably don't also need an action in the page flow, since the replace will "take you to a new page" as the action will, loading a new url in the browser address bar.

 

Well I got the "replace=all" construct from an example too. I was looking into its definition, didn't find any decent documentation though. Is this the preferred way for entering data into pipelines?

 

> I'm not much help with a specific diagnosis, but if we knew that your submission was reaching a target xpl script (even if it just serializes the submitted data back), that would be some help to understand.
 
Actually you've been quite helpful already :-). I don't know for sure, but I'm fairly sure that my submission never ever reaches a target XPL. Using a debug footer, I find that the data I enter on the form is serialized into the document I want to submit.
 
Best, Robin.
 
-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 18:00
To: [hidden email]
Subject: [ops-users] Re: Question on XML submissions

Robin,
 
I realize you are including snippets, but I want to check that your submission and instance 
elements are all in the html head element.
 
I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what
is submitted and transformed at each step.  I comment out, e.g., the http serializer and 
reference the input or output of each step.  (or use the logs and debug as you do...)
 
In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 
sure what the effect is of using xsl within the pageflow -- is it possible?
 
If your submission replace attribute is "all", then you probably don't also need an 
action in the page flow, since the replace will "take you to a new page" as the 
action will, loading a new url in the browser address bar.
 
I'm not much help with a specific diagnosis, but if we knew that your submission 
was reaching a target xpl script (even if it just serializes the submitted data 
back), that would be some help to understand.
 
Cheers,
Hank

On Jan 28, 2010, at 8:07 AM, Robin Diederen wrote:

Hello all,
 
I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).
 
I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY
<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL
<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:
<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):
<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>

When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best, 
            

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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042
 
 
 

 


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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042
 
 
 



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

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042







--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

RE: Re: Re: RE: Re: Question on XML submissions

Robin Diederen
<base href="x-msg://282/">

Hello Hank,

 

Thanks for the help, it’s working now!

 

Best, Robin

 


Van: Hank Ratzesberger [mailto:[hidden email]]
Verzonden: donderdag 28 januari 2010 21:03
Aan: [hidden email]
Onderwerp: [ops-users] Re: Re: RE: Re: Question on XML submissions

 

 

On Jan 28, 2010, at 11:10 AM, Robin Diederen wrote:



Hi Hank,

 

That seems faily straightforward. What code do you use to submit data from the "input" form?

 

you can use get or post.  use replace="all" to see the results in the browser. 

 

Mostly I don't move the user off the page, so eventually I use replace="instance" when 

I know things are working, and the inspector at the bottom of my page if I need

to look at specific results.

 

Cheers,

Hank

 



 

Best, Robin
 

-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 20:01
To: [hidden email]; 
Subject: [ops-users] Re: RE: Re: Question on XML submissions

 

If I may top-post... Its just the way I got started, and likely debug 

attributes are better in the long run, but...

 

 

<!-- page-flow.xml -->

<page id="my-service"

model="/my-service.xpl"/>

 

 

<!-- my-service.xpl -->

 

<p:config

 

<p:paramname="instance"type="input"/>

 

<!-- Get the instance paramters -->

<p:processorname="oxf:request">

<p:inputname="config">

<config>

<include>/request/parameters</include>

</config>

</p:input>

<p:outputname="data"id="params"/>

</p:processor>

 

<p:processorname="oxf:xml-serializer">

<p:inputname="config">

<config>

  <content-type>text/xml</content-type>

</config>

</p:input>

<p:inputname="data"href="#input"/> 

<!-- or #params, or #whatever-processor-outputs in between -->

</p:processor>

 

</p:config>

 

--Hank

 

On Jan 28, 2010, at 9:59 AM, Robin Diederen wrote:



 Hello Hank,

 

Thanks for the extensive answer!

 

> but I want to check that your submission and instance elements are all in the html head element.

 

Yes, the submission and instance elemets are all placed in the head section.

 

> I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what is submitted and transformed at each step.  I comment out, e.g., the http serializer and reference the input or output of each step.  (or use the logs and debug as you do...)

 

Sounds like an interesting option for debugging. Would you have an example?

 

> In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 

sure what the effect is of using xsl within the pageflow -- is it possible?

 

It should be, according to the Orbeon documentation (I found an example somewhere). Would you have an example of code using the model attribute to initiate a pipeline? I'd like to give that a try.

 

> If your submission replace attribute is "all", then you probably don't also need an action in the page flow, since the replace will "take you to a new page" as the action will, loading a new url in the browser address bar.

 

Well I got the "replace=all" construct from an example too. I was looking into its definition, didn't find any decent documentation though. Is this the preferred way for entering data into pipelines?

 

> I'm not much help with a specific diagnosis, but if we knew that your submission was reaching a target xpl script (even if it just serializes the submitted data back), that would be some help to understand.

 

Actually you've been quite helpful already :-). I don't know for sure, but I'm fairly sure that my submission never ever reaches a target XPL. Using a debug footer, I find that the data I enter on the form is serialized into the document I want to submit.

 

Best, Robin.
 

-----Original message-----
From: Hank Ratzesberger <[hidden email]>
Sent: Thu 28-01-2010 18:00
To: [hidden email]
Subject: [ops-users] Re: Question on XML submissions

Robin,

 

I realize you are including snippets, but I want to check that your submission and instance 

elements are all in the html head element.

 

I often trace the steps in my xpl files by using the xml-serializer to quickly look exactly what

is submitted and transformed at each step.  I comment out, e.g., the http serializer and 

reference the input or output of each step.  (or use the logs and debug as you do...)

 

In the page-flow.xml, I always use the model attribute to specify a pipeline.  I'm not 

sure what the effect is of using xsl within the pageflow -- is it possible?

 

If your submission replace attribute is "all", then you probably don't also need an 

action in the page flow, since the replace will "take you to a new page" as the 

action will, loading a new url in the browser address bar.

 

I'm not much help with a specific diagnosis, but if we knew that your submission 

was reaching a target xpl script (even if it just serializes the submitted data 

back), that would be some help to understand.

 

Cheers,

Hank

 

On Jan 28, 2010, at 8:07 AM, Robin Diederen wrote:



Hello all,

 

I'm quite new to Orbeon and kind of stuck. So I'm hoping for some help here... :).

 

I've got this Xform which' data I want to submit to a XPL; it's the submission I can't get working. What I actually want to do is submit an XML document composed from data on my form to the XML pipeline in order to perform some SOAP calls there.

 

First some code snippets from my Xform

           

BODY

<h3 class="form-section-heading">Submit</h3>
<div class="form-section">
<xforms:submit submission="submission">
<xforms:label>Verstuur</xforms:label>
</xforms:submit>

 

MODEL

<xforms:submission action="/myapp/submit" id="submission" replace="all" >
<xforms:message ev:event="xforms-submit-error" level="modal">An error occurred: <xforms:output value="event('error-type')"/></xforms:message>

 

From the page-flow.xml:

<page id="submit" path-info="/myapp/submit" >
<action action="oxf:/myapp/pipeline.nl">
<result page="result" transform="oxf:xslt">
<data xsl:version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:copy-of select="doc('input:action')//output"></xsl:copy-of>
</data>
</result>
</action>
</page>

 

And my pipeline (first part):

<p:param type="input" name="instance" debug="debug" />
        <p:processor name="oxf:xforms-submission">
          <p:input name="submission" href="#instance" />
          <p:output name="data" id="response"/>
        </p:processor>


When I submit this data, all I see on my form is a message saying "xxforms-internal-error". In orbeon.log I find "2010-01-28 16:45:16,661 ERROR XFormsServer  - XForms - submission - xforms-submit-error throwable: java.lang.NullPointerException" and that's all. My guess I'm submitting the information the wrong way, but I wouldn't have a clue how to solve this.

 

Best, 
            


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

 

Hank Ratzesberger

NEES@UCSB

Institute for Crustal Studies,

University of California, Santa Barbara

805-893-8042

 

 

 



 


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

 

Hank Ratzesberger

NEES@UCSB

Institute for Crustal Studies,

University of California, Santa Barbara

805-893-8042

 

 

 

 

 


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

 

Hank Ratzesberger

NEES@UCSB

Institute for Crustal Studies,

University of California, Santa Barbara

805-893-8042

 

 

 



 



--
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
OW2 mailing lists service home page: http://www.ow2.org/wws