Processing instance data in non Xform jsp (how to access submitted data?)

> Hello,
>
> I am building up application in separate deployment approach.
>
> The scenario is I have xform (jsp) that makes submission to another jsp
> (nonXform) for processing the data.
>
> How should the nonXform jsp access the instance data submitted?

As I understand (I don't have an app. like this), with XForms 1.1
you can configure the submission to operate the "usual" way, and
so rather than XML (mime-type of application/xml), the POST will be
multipart/form-data, etc. (or perhaps it should be
application/x-www-form-urlencoded).  Note the attributes
serialziation and separator:

http://www.w3.org/TR/xforms11/#submit

HTH,
Hank

Hank Ratzesberger
NEES@UCSB


>
> Madhuri
>




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

Madhuri,

On Jul 7, 2009, at 10:26 PM, Madhuri Deodhar wrote:

As i understand it right, when I write an xform which is rendered as html form by orbeon, the form control names are orbeon defined. If I receive the form data as multipart/form data, how will I know the control names in advance?

Is there any other way to achieve this? I read something about redirect service? Can that be used in some way?

With application/x-www-form-urlencoded, the content is sent as elementName=value.  So, yes, I guess that

is a problem with a jsp expecting the control name.  But even if you use redirect, the content is 

still XML.  Sorry, but I can't provide any more specifics at this time.

--Hank

Madhuri

On Wed, Jul 8, 2009 at 1:13 AM, Hank Ratzesberger <[hidden email]> wrote:

> Hello,
>
> I am building up application in separate deployment approach.
>
> The scenario is I have xform (jsp) that makes submission to another jsp
> (nonXform) for processing the data.
>
> How should the nonXform jsp access the instance data submitted?

As I understand (I don't have an app. like this), with XForms 1.1
you can configure the submission to operate the "usual" way, and
so rather than XML (mime-type of application/xml), the POST will be
multipart/form-data, etc. (or perhaps it should be
application/x-www-form-urlencoded).  Note the attributes
serialziation and separator:

http://www.w3.org/TR/xforms11/#submit

HTH,
Hank

Hank Ratzesberger
NEES@UCSB


>
> Madhuri
>




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

--

You receive this message as a subscriber of the [hidden email] mailing list.

To unsubscribe: [hidden email]

For general help: [hidden email]

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