Orbeon Forms community mailing list

request url

Classic

List

Threaded

5 messages Options

Frank

request url

Hi all,

I was wondering if there is a OPS function/variable etc accessible in
any of the epilogue processing files (such as epilogue.xpl, theme-
plain.xsl etc) that holds the
URL of the http request?

Regards,

Franco

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

Alessandro Vernet

Re: request url

Administrator

Franco,

You can place the request processor in the epilogue to access the
request path (path-info). Does this make sense?

Alex

On Thu, Mar 4, 2010 at 2:20 PM, Franco Pace <[hidden email]> wrote:

> Hi all,
>
> I was wondering if there is a OPS function/variable etc accessible in any of
> the epilogue processing files (such as epilogue.xpl, theme-plain.xsl etc)
> that holds the
> URL of the http request?
>
> Regards,
>
> Franco
>
>
>
>
>
> --
> 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
>
>

--
Orbeon Forms - Web forms, open-source, for the Enterprise -
http://www.orbeon.com/
My Twitter: http://twitter.com/avernet

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

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

Frank

Re: Re: request url

Yes - i'll give it a try

Thanks,

Franco

On 05/03/2010, at 9:44 AM, Alessandro Vernet wrote:

> Franco,
>
> You can place the request processor in the epilogue to access the
> request path (path-info). Does this make sense?
>
> Alex
>
> On Thu, Mar 4, 2010 at 2:20 PM, Franco Pace <[hidden email]>
> wrote:
>> Hi all,
>>
>> I was wondering if there is a OPS function/variable etc accessible
>> in any of
>> the epilogue processing files (such as epilogue.xpl, theme-
>> plain.xsl etc)
>> that holds the
>> URL of the http request?
>>
>> Regards,
>>
>> Franco
>>
>>
>>
>>
>>
>> --
>> 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
>>
>>
>
>
>
> --
> Orbeon Forms - Web forms, open-source, for the Enterprise -
> http://www.orbeon.com/
> My Twitter: http://twitter.com/avernet
>
> --
> 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

Franco Pace
[hidden email]

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

Frank

Re: Re: request url

In reply to this post by Alessandro Vernet

Hi Alex,

Following your suggestion and after investigating the current
epilogue.xpl and epilogue-servlet.xpl, I found all I needed to do
to get the info I need was to change the request generator config (in
epilogue-servlet.xpl) to:


<p:processor name="oxf:request">
<p:input name="config">
<config>
<include>/request</include>
</config>
</p:input>
<p:output name="data" id="request"/>
</p:processor>

thereby allowing all request data to filter through instead of the
default config:

<p:processor name="oxf:request">
<p:input name="config">
<config>
<include>/request/container-type</include>
<include>/request/request-path</include>
<include>/request/headers/header[name = 'accept']</
include>
<include>/request/parameters/parameter[starts-
with(name, 'orbeon')]</include>
</config>
</p:input>
<p:output name="data" id="request"/>
</p:processor>

Is there a strong reason why the default config limits what request
data gets passed on? I can only assume
some efficiency issues - are there any other dangers I am not seeing?

Thanks again,
Franco

On 05/03/2010, at 9:44 AM, Alessandro Vernet wrote:

Alessandro Vernet

Re: Re: Re: request url

Administrator

Hi Franco,

It is a question of performance. The whole request can contain a lot
of information (e.g. all the headers, the body of the POST if there is
one). Asking the request generator to produce a document will all this
information at every HTTP request if you only need a smal portion of
it would use unnecessary resources, both CPU time and memory.

Alex

On Thu, Mar 4, 2010 at 7:58 PM, Franco Pace <[hidden email]> wrote:

> Hi Alex,
>
> Following your suggestion and after investigating the current epilogue.xpl
> and epilogue-servlet.xpl, I found all I needed to do
> to get the info I need was to change the request generator config (in
> epilogue-servlet.xpl) to:
>
> 
> <p:processor name="oxf:request">
> <p:input name="config">
> <config>
> <include>/request</include>
> </config>
> </p:input>
> <p:output name="data" id="request"/>
> </p:processor>
>
> thereby allowing all request data to filter through instead of the default
> config:
>
> <p:processor name="oxf:request">
> <p:input name="config">
> <config>
> <include>/request/container-type</include>
> <include>/request/request-path</include>
> <include>/request/headers/header[name = 'accept']</include>
> <include>/request/parameters/parameter[starts-with(name,
> 'orbeon')]</include>
> </config>
> </p:input>
> <p:output name="data" id="request"/>
> </p:processor>
>
> Is there a strong reason why the default config limits what request data
> gets passed on? I can only assume
> some efficiency issues - are there any other dangers I am not seeing?
>
> Thanks again,
> Franco
>
>
> On 05/03/2010, at 9:44 AM, Alessandro Vernet wrote:
>
>> Franco,
>>
>> You can place the request processor in the epilogue to access the
>> request path (path-info). Does this make sense?
>>
>> Alex
>>
>> On Thu, Mar 4, 2010 at 2:20 PM, Franco Pace <[hidden email]>
>> wrote:
>>>
>>> Hi all,
>>>
>>> I was wondering if there is a OPS function/variable etc accessible in any
>>> of
>>> the epilogue processing files (such as epilogue.xpl, theme-plain.xsl etc)
>>> that holds the
>>> URL of the http request?
>>>
>>> Regards,
>>>
>>> Franco
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>>
>> --
>> Orbeon Forms - Web forms, open-source, for the Enterprise -
>> http://www.orbeon.com/
>> My Twitter: http://twitter.com/avernet
>>
>> --
>> 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
>
> Franco Pace
> [hidden email]
>
>
>
>
>
> --
> 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
>
>

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet