Form Builder - nightly compatibility

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

Form Builder - nightly compatibility

Louis Ratzesberger

 
Hi,

We had developed a form, then had some problems saving it -- error writing
to database.  It sounded very similar to a post which was reported fixed.

So we saved our expanded war directory and put in the latest nightly
war file.  After it was expanded, we copied back the pevious exist-data
files.

But there was a problem reported by every phone, date and upload file control.
The last is at the end of this message.  I commented out these statements and
the form loads in Form Runner. I used the eXist admin tool to edit the form.xhtml
file directly.

Anyway, the question is what kind of compatibilty to expect between builds
and what steps can we take to save our efforts.  I suppose I am assuming there
is some compatibility difference between builds, but that seems
reasonable to expect.

(Yes, we know FR is "preliminary" but can you blame us?)

Thanks,
Hank
 

Error Message

Binding exception for target: Upload-Docs-Files-control

<a onclick="hideShowSection(this)" class="orbeon-error-panel-hide-details">Hide DetailsHide details

Call Stack

Resource URL Line Column Description XML Element
oxf:/ops/pfc/xforms-epilogue.xpl 135 60
reading processor output
name ? document
id ? xhtml-data
<p:output name="document" id="xhtml-data"/>
oxf:/ops/pfc/xforms-epilogue.xpl 146 59
reading processor output
name ? data
ref ? xformed-data
<p:output name="data" ref="xformed-data"/>
oxf:/config/epilogue.xpl 41 58
reading processor output
name ? xformed-data
id ? xformed-data
<p:output name="xformed-data" id="xformed-data"/>
oxf:/config/epilogue-servlet.xpl 31 48
reading processor output
name ? xformed-data
<p:param type="input" name="xformed-data"/>
oxf:/config/epilogue.xpl 60 46
executing processor
name ? {http://www.orbeon.com/oxf/processors}pipeline
<p:processor name="oxf:pipeline">...</p:processor>
oxf:/apps/fr/page-flow.xml 204 47
executing processor
name ? {http://www.orbeon.com/oxf/processors}pipeline
 
oxf:/page-flow.xml 34 106
reading page model data output
page id ? apps
model ? apps/${1}/page-flow.xml
<page id="apps" path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher" model="apps/${1}/page-flow.xml"/>

Java Exceptions (4 total)

Java Exceptions are the native mechanism by which Orbeon Forms reports errors. More than one exception may be provided below but usually the first exception along with the Orbeon Forms Stack Trace above provide enough information to track down an issue.

<span onclick="hideShowTBody('exception-1')">Toggle org.orbeon.oxf.common.ValidationException
Exception Class org.orbeon.oxf.common.ValidationException
Message Binding exception for target: Upload-Docs-Files-control
Resource URL  
Line N/A
Column N/A
Servlet Stack Trace
(311 method calls)
Class Name Method Name File Name Line Number
org.orbeon.oxf.xforms.xbl.XBLContainer performDefaultAction XBLContainer.java 757
org.orbeon.oxf.xforms.xbl.XBLContainer dispatchEvent XBLContainer.java 979
org.orbeon.oxf.xforms.XFormsContextStack pushBinding XFormsContextStack.java 335
org.orbeon.oxf.xforms.XFormsContextStack pushBinding XFormsContextStack.java 246
org.orbeon.oxf.xforms.XFormsControls pushBinding XFormsControls.java 520
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 434
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 498
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458

 

--
Hank Ratzesberger
[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

y4o8iswzfcg@secureweb.ic.ucsb.edu (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Form Builder - nightly compatibility

Erik Bruchez
Administrator
Louis,

It looks like a new bug or a regression, although I am not sure why this should have started happening! I have identified a case where that particular exception can happen and we'll try to fix it ASAP:


We keep a list of potential compatibility issues in the release notes for the upcoming 3.8:


In general, we try to keep compatibility as much as possible, and we have lots of automatic unit tests to help with that, but the reality is that nightly builds have not received any extra testing, and unit tests don't necessarily cover everything (although we keep adding new ones).

-Erik

On Sun, Apr 4, 2010 at 9:35 PM, Louis Ratzesberger <[hidden email]> wrote:

 
Hi,

We had developed a form, then had some problems saving it -- error writing
to database.  It sounded very similar to a post which was reported fixed.

So we saved our expanded war directory and put in the latest nightly
war file.  After it was expanded, we copied back the pevious exist-data
files.

But there was a problem reported by every phone, date and upload file control.
The last is at the end of this message.  I commented out these statements and
the form loads in Form Runner. I used the eXist admin tool to edit the form.xhtml
file directly.

Anyway, the question is what kind of compatibilty to expect between builds
and what steps can we take to save our efforts.  I suppose I am assuming there
is some compatibility difference between builds, but that seems
reasonable to expect.

(Yes, we know FR is "preliminary" but can you blame us?)

Thanks,
Hank
 

Error Message

Binding exception for target: Upload-Docs-Files-control

Hide DetailsHide details

Call Stack

Resource URL Line Column Description XML Element
oxf:/ops/pfc/xforms-epilogue.xpl 135 60
reading processor output
name ? document
id ? xhtml-data
<p:output name="document" id="xhtml-data"/>
oxf:/ops/pfc/xforms-epilogue.xpl 146 59
reading processor output
name ? data
ref ? xformed-data
<p:output name="data" ref="xformed-data"/>
oxf:/config/epilogue.xpl 41 58
reading processor output
name ? xformed-data
id ? xformed-data
<p:output name="xformed-data" id="xformed-data"/>
oxf:/config/epilogue-servlet.xpl 31 48
reading processor output
name ? xformed-data
<p:param type="input" name="xformed-data"/>
oxf:/config/epilogue.xpl 60 46
executing processor
<p:processor name="oxf:pipeline">...</p:processor>
oxf:/apps/fr/page-flow.xml 204 47
executing processor
 
oxf:/page-flow.xml 34 106
reading page model data output
page id ? apps
model ? apps/${1}/page-flow.xml
<page id="apps" path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher" model="apps/${1}/page-flow.xml"/>

Java Exceptions (4 total)

Java Exceptions are the native mechanism by which Orbeon Forms reports errors. More than one exception may be provided below but usually the first exception along with the Orbeon Forms Stack Trace above provide enough information to track down an issue.

Toggle org.orbeon.oxf.common.ValidationException
Exception Class org.orbeon.oxf.common.ValidationException
Message Binding exception for target: Upload-Docs-Files-control
Resource URL  
Line N/A
Column N/A
Servlet Stack Trace
(311 method calls)
Class Name Method Name File Name Line Number
org.orbeon.oxf.xforms.xbl.XBLContainer performDefaultAction XBLContainer.java 757
org.orbeon.oxf.xforms.xbl.XBLContainer dispatchEvent XBLContainer.java 979
org.orbeon.oxf.xforms.XFormsContextStack pushBinding XFormsContextStack.java 335
org.orbeon.oxf.xforms.XFormsContextStack pushBinding XFormsContextStack.java 246
org.orbeon.oxf.xforms.XFormsControls pushBinding XFormsControls.java 520
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 434
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 498
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458

 

--
Hank Ratzesberger
[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




--
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: Form Builder - nightly compatibility

Erik Bruchez
Administrator
I have now fixed this bug. Hopefully it's the one you hit!

-Erik

On Mon, Apr 5, 2010 at 11:22 AM, Erik Bruchez <[hidden email]> wrote:
Louis,

It looks like a new bug or a regression, although I am not sure why this should have started happening! I have identified a case where that particular exception can happen and we'll try to fix it ASAP:


We keep a list of potential compatibility issues in the release notes for the upcoming 3.8:


In general, we try to keep compatibility as much as possible, and we have lots of automatic unit tests to help with that, but the reality is that nightly builds have not received any extra testing, and unit tests don't necessarily cover everything (although we keep adding new ones).

-Erik

On Sun, Apr 4, 2010 at 9:35 PM, Louis Ratzesberger <[hidden email]> wrote:

 
Hi,

We had developed a form, then had some problems saving it -- error writing
to database.  It sounded very similar to a post which was reported fixed.

So we saved our expanded war directory and put in the latest nightly
war file.  After it was expanded, we copied back the pevious exist-data
files.

But there was a problem reported by every phone, date and upload file control.
The last is at the end of this message.  I commented out these statements and
the form loads in Form Runner. I used the eXist admin tool to edit the form.xhtml
file directly.

Anyway, the question is what kind of compatibilty to expect between builds
and what steps can we take to save our efforts.  I suppose I am assuming there
is some compatibility difference between builds, but that seems
reasonable to expect.

(Yes, we know FR is "preliminary" but can you blame us?)

Thanks,
Hank
 

Error Message

Binding exception for target: Upload-Docs-Files-control

Hide DetailsHide details

Call Stack

Resource URL Line Column Description XML Element
oxf:/ops/pfc/xforms-epilogue.xpl 135 60
reading processor output
name ? document
id ? xhtml-data
<p:output name="document" id="xhtml-data"/>
oxf:/ops/pfc/xforms-epilogue.xpl 146 59
reading processor output
name ? data
ref ? xformed-data
<p:output name="data" ref="xformed-data"/>
oxf:/config/epilogue.xpl 41 58
reading processor output
name ? xformed-data
id ? xformed-data
<p:output name="xformed-data" id="xformed-data"/>
oxf:/config/epilogue-servlet.xpl 31 48
reading processor output
name ? xformed-data
<p:param type="input" name="xformed-data"/>
oxf:/config/epilogue.xpl 60 46
executing processor
<p:processor name="oxf:pipeline">...</p:processor>
oxf:/apps/fr/page-flow.xml 204 47
executing processor
 
oxf:/page-flow.xml 34 106
reading page model data output
page id ? apps
model ? apps/${1}/page-flow.xml
<page id="apps" path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher" model="apps/${1}/page-flow.xml"/>

Java Exceptions (4 total)

Java Exceptions are the native mechanism by which Orbeon Forms reports errors. More than one exception may be provided below but usually the first exception along with the Orbeon Forms Stack Trace above provide enough information to track down an issue.

Toggle org.orbeon.oxf.common.ValidationException
Exception Class org.orbeon.oxf.common.ValidationException
Message Binding exception for target: Upload-Docs-Files-control
Resource URL  
Line N/A
Column N/A
Servlet Stack Trace
(311 method calls)
Class Name Method Name File Name Line Number
org.orbeon.oxf.xforms.xbl.XBLContainer performDefaultAction XBLContainer.java 757
org.orbeon.oxf.xforms.xbl.XBLContainer dispatchEvent XBLContainer.java 979
org.orbeon.oxf.xforms.XFormsContextStack pushBinding XFormsContextStack.java 335
org.orbeon.oxf.xforms.XFormsContextStack pushBinding XFormsContextStack.java 246
org.orbeon.oxf.xforms.XFormsControls pushBinding XFormsControls.java 520
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 434
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 498
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458
org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat XFormsControls.java 458

 

--
Hank Ratzesberger
[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





--
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: Form Builder - nightly compatibility

Louis Ratzesberger

Thank you Erik.  I will probably look for it in the nightly build and let you know
if there are any further issues.

Best,
Hank

Quoting Erik Bruchez <[hidden email]>:

> I have now fixed this bug. Hopefully it's the one you hit!
>
> -Erik
>
> On Mon, Apr 5, 2010 at 11:22 AM, Erik Bruchez <[hidden email]> wrote:
>
>> Louis,
>>
>> It looks like a new bug or a regression, although I am not sure why this
>> should have started happening! I have identified a case where that
>> particular exception can happen and we'll try to fix it ASAP:
>>
>>
>> http://forge.ow2.org/tracker/index.php?func=detail&aid=314885&group_id=168&atid=350207
>>
>> We keep a list of potential compatibility issues in the release notes for
>> the upcoming 3.8:
>>
>>
>> http://sites.google.com/a/orbeon.com/forms/doc/developer-guide/release-orbeon-forms-38#TOC-Compatibility-notes
>>
>> In general, we try to keep compatibility as much as possible, and we have
>> lots of automatic unit tests to help with that, but the reality is that
>> nightly builds have not received any extra testing, and unit tests don't
>> necessarily cover everything (although we keep adding new ones).
>>
>> -Erik
>>
>> On Sun, Apr 4, 2010 at 9:35 PM, Louis Ratzesberger <[hidden email]
>> > wrote:
>>
>>>
>>> Hi,
>>>
>>> We had developed a form, then had some problems saving it -- error writing
>>> to database.  It sounded very similar to a post which was reported fixed.
>>>
>>> So we saved our expanded war directory and put in the latest nightly
>>> war file.  After it was expanded, we copied back the pevious exist-data
>>> files.
>>>
>>> But there was a problem reported by every phone, date and upload file
>>> control.
>>> The last is at the end of this message.  I commented out these statements
>>> and
>>> the form loads in Form Runner. I used the eXist admin tool to edit the
>>> form.xhtml
>>> file directly.
>>>
>>> Anyway, the question is what kind of compatibilty to expect between builds
>>> and what steps can we take to save our efforts.  I suppose I am assuming
>>> there
>>> is some compatibility difference between builds, but that seems
>>> reasonable to expect.
>>>
>>> (Yes, we know FR is "preliminary" but can you blame us?)
>>>
>>> Thanks,
>>> Hank
>>>
>>>  Error Message
>>>
>>> Binding exception for target: Upload-Docs-Files-control
>>>
>>> [image: Show Details]Show details
>>>
>>> [image: Hide Details]Hide details
>>>  Call Stack
>>>   Resource URL  Line  Column  Description  XML Element 
>>> oxf:/ops/pfc/xforms-epilogue.xpl 135 60
>>> reading processor output
>>> name ? document
>>> id ? xhtml-data
>>>   <p:output name="document" id="xhtml-data"/> 
>>> oxf:/ops/pfc/xforms-epilogue.xpl 146 59
>>> reading processor output
>>> name ? data
>>> ref ? xformed-data
>>>   <p:output name="data" ref="xformed-data"/>   
>>> oxf:/config/epilogue.xpl 41 58
>>> reading processor output
>>> name ? xformed-data
>>> id ? xformed-data
>>>   <p:output name="xformed-data" id="xformed-data"/> 
>>> oxf:/config/epilogue-servlet.xpl 31 48
>>> reading processor output
>>> name ? xformed-data
>>>   <p:param type="input" name="xformed-data"/>   
>>> oxf:/config/epilogue.xpl 60 46
>>> executing processor
>>> name ?
>>> {<a target="_blank" href="http://www.orbeon.com/oxf/processors}pipeline">http://www.orbeon.com/oxf/processors}pipeline<http://www.orbeon.com/oxf/processors%7Dpipeline>
>>>   <p:processor name="oxf:pipeline">...</p:processor> 
>>> oxf:/apps/fr/page-flow.xml 204 47
>>> executing processor
>>> name ?
>>> {<a target="_blank" href="http://www.orbeon.com/oxf/processors}pipeline">http://www.orbeon.com/oxf/processors}pipeline<http://www.orbeon.com/oxf/processors%7Dpipeline>
>>>       oxf:/page-flow.xml  34  106
>>> reading page model data output
>>> page id ? apps
>>> model ? apps/${1}/page-flow.xml
>>>   <page id="apps" path-info="/([^/]+)/.*" matcher="oxf:perl5-matcher"
>>> model="apps/${1}/page-flow.xml"/>
>>>  Java Exceptions (4 total)
>>>
>>> Java Exceptions are the native mechanism by which Orbeon Forms reports
>>> errors. More than one exception may be provided below but usually the first
>>> exception along with the Orbeon Forms Stack Trace above provide enough
>>> information to track down an issue.
>>>   [image: Toggle] org.orbeon.oxf.common.ValidationException    Exception
>>> Class  org.orbeon.oxf.common.ValidationException   Message Binding
>>> exception for target: Upload-Docs-Files-control  Resource URL   
>>> Line N/A  Column N/A  Servlet Stack Trace
>>> (311 method calls)    Class Name  Method Name  File Name  Line
>>> Number   org.orbeon.oxf.xforms.xbl.XBLContainer
>>> performDefaultAction XBLContainer.java 757 
>>> org.orbeon.oxf.xforms.xbl.XBLContainer dispatchEvent
>>> XBLContainer.java 979  org.orbeon.oxf.xforms.XFormsContextStack
>>> pushBinding XFormsContextStack.java 335 
>>> org.orbeon.oxf.xforms.XFormsContextStack pushBinding
>>> XFormsContextStack.java 246  org.orbeon.oxf.xforms.XFormsControls
>>> pushBinding XFormsControls.java 520 
>>> org.orbeon.oxf.xforms.XFormsControls
>>> visitControlElementsHandleRepeat XFormsControls.java 434 
>>> org.orbeon.oxf.xforms.XFormsControls
>>> visitControlElementsHandleRepeat XFormsControls.java 498 
>>> org.orbeon.oxf.xforms.XFormsControls
>>> visitControlElementsHandleRepeat XFormsControls.java 458 
>>> org.orbeon.oxf.xforms.XFormsControls
>>> visitControlElementsHandleRepeat XFormsControls.java 458 
>>> org.orbeon.oxf.xforms.XFormsControls
>>> visitControlElementsHandleRepeat XFormsControls.java 458
>>>
>>>
>>>
>>> --
>>> Hank Ratzesberger
>>> [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
>>>
>>>
>>
>

 

--
Hank Ratzesberger
[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
Reply | Threaded
Open this post in threaded view
|

Re: Re: Form Builder - nightly compatibility

Louis Ratzesberger
In reply to this post by Erik Bruchez
Hi Erik,

I re-deployed the nightly build war file, then copied the exist-data
files back and restarted. But again all the phone and date controls
have a binding error.

Well, perhaps it is better to try to re-create these controls. The rest
appear to be fine.  Perhaps handling of these controls has changed?

But if you want we can send the db backup files.

Thanks,
Hank

<fr:us-phone xmlns="http://orbeon.org/oxf/xml/form-builder"
xmlns:fb="http://orbeon.org/oxf/xml/form-builder"
xmlns:xbl="http://www.w3.org/ns/xbl"
xmlns:pipeline="java:org.orbeon.oxf.processor.pipeline.PipelineFunctionLibrary"
bind="Phone-bind" id="Phone-control" class="fr-email-recipient">
<xforms:label ref="$form-resources/Phone/label"/>
<xforms:hint ref="$form-resources/Phone/hint"/>
<xforms:help ref="$form-resources/Phone/help"/>
<xforms:alert ref="$fr-resources/detail/labels/alert"/>
</fr:us-phone>
</xhtml:td>
<xhtml:td>
<!--
<fr:dropdown-date xmlns="http://orbeon.org/oxf/xml/form-builder"
xmlns:xbl="http://www.w3.org/ns/xbl"
xmlns:fb="http://orbeon.org/oxf/xml/form-builder"
xmlns:pipeline="java:org.orbeon.oxf.processor.pipeline.PipelineFunctionLibrary"
bind="Birth-Date-bind" id="Birth-Date-control"
class="fr-email-recipient">
<xforms:label ref="$form-resources/Birth-Date/label"/>
<xforms:hint ref="$form-resources/Birth-Date/hint"/>
<xforms:help ref="$form-resources/Birth-Date/help"/>
<xforms:alert ref="$fr-resources/detail/labels/alert"/>
</fr:dropdown-date>
-->

Quoting Erik Bruchez <[hidden email]>:

> I have now fixed this bug. Hopefully it's the one you hit!
>
> -Erik
>
> On Mon, Apr 5, 2010 at 11:22 AM, Erik Bruchez <[hidden email]>
wrote:
>
>> Louis,
>>
>> It looks like a new bug or a regression, although I am not sure
why this
>> should have started happening! I have identified a case where that
>> particular exception can happen and we'll try to fix it ASAP:
>>
>>
>>
http://forge.ow2.org/tracker/index.php?func=detail&aid=314885&group_id=168&atid=350207
>>
>> We keep a list of potential compatibility issues in the release
notes for
>> the upcoming 3.8:
>>
>>
>>
http://sites.google.com/a/orbeon.com/forms/doc/developer-guide/release-orbeon-forms-38#TOC-Compatibility-notes
>>
>> In general, we try to keep compatibility as much as possible, and
we have
>> lots of automatic unit tests to help with that, but the reality is
that
>> nightly builds have not received any extra testing, and unit tests
don't
>> necessarily cover everything (although we keep adding new ones).
>>
>> -Erik
>>
>> On Sun, Apr 4, 2010 at 9:35 PM, Louis Ratzesberger
<[hidden email]
>> > wrote:
>>
>>>
>>> Hi,
>>>
>>> We had developed a form, then had some problems saving it --
error writing
>>> to database.  It sounded very similar to a post which was
reported fixed.
>>>
>>> So we saved our expanded war directory and put in the latest
nightly
>>> war file.  After it was expanded, we copied back the pevious
exist-data
>>> files.
>>>
>>> But there was a problem reported by every phone, date and upload
file
>>> control.
>>> The last is at the end of this message.  I commented out these
statements
>>> and
>>> the form loads in Form Runner. I used the eXist admin tool to
edit the
>>> form.xhtml
>>> file directly.
>>>
>>> Anyway, the question is what kind of compatibilty to expect
between builds
>>> and what steps can we take to save our efforts.  I suppose I am
assuming

>>> there
>>> is some compatibility difference between builds, but that seems
>>> reasonable to expect.
>>>
>>> (Yes, we know FR is "preliminary" but can you blame us?)
>>>
>>> Thanks,
>>> Hank
>>>
>>>   Error Message
>>>
>>> Binding exception for target: Upload-Docs-Files-control
>>>
>>> [image: Show Details]Show details
>>>
>>> [image: Hide Details]Hide details
>>>   Call Stack
>>>    Resource URL  Line  Column  Description  XML Element   
>>> oxf:/ops/pfc/xforms-epilogue.xpl 135 60
>>> reading processor output
>>> name ? document
>>> id ? xhtml-data
>>>    <p:output name="document" id="xhtml-data"/>   
>>> oxf:/ops/pfc/xforms-epilogue.xpl 146 59
>>> reading processor output
>>> name ? data
>>> ref ? xformed-data
>>>    <p:output name="data" ref="xformed-data"/>   
>>> oxf:/config/epilogue.xpl 41 58
>>> reading processor output
>>> name ? xformed-data
>>> id ? xformed-data
>>>    <p:output name="xformed-data" id="xformed-data"/>   
>>> oxf:/config/epilogue-servlet.xpl 31 48
>>> reading processor output
>>> name ? xformed-data
>>>    <p:param type="input" name="xformed-data"/>   
>>> oxf:/config/epilogue.xpl 60 46
>>> executing processor
>>> name ?
{http://www.orbeon.com/oxf/processors}pipeline<http://www.orbeon.com/oxf/processors%7Dpipeline>
>>>    <p:processor name="oxf:pipeline">...</p:processor>   
>>> oxf:/apps/fr/page-flow.xml 204 47
>>> executing processor
>>> name ?
{http://www.orbeon.com/oxf/processors}pipeline<http://www.orbeon.com/oxf/processors%7Dpipeline>
>>>        oxf:/page-flow.xml  34  106
>>> reading page model data output
>>> page id ? apps
>>> model ? apps/${1}/page-flow.xml
>>>    <page id="apps" path-info="/([^/]+)/.*"
matcher="oxf:perl5-matcher"
>>> model="apps/${1}/page-flow.xml"/>
>>>   Java Exceptions (4 total)
>>>
>>> Java Exceptions are the native mechanism by which Orbeon Forms
reports
>>> errors. More than one exception may be provided below but usually
the first
>>> exception along with the Orbeon Forms Stack Trace above provide
enough
>>> information to track down an issue.
>>>    [image: Toggle] org.orbeon.oxf.common.ValidationException 
  Exception
>>> Class  org.orbeon.oxf.common.ValidationException   Message
Binding
>>> exception for target: Upload-Docs-Files-control  Resource URL 
 
>>> Line N/A  Column N/A  Servlet Stack Trace
>>> (311 method calls)    Class Name  Method Name  File Name 
Line
>>> Number   org.orbeon.oxf.xforms.xbl.XBLContainer  
>>> performDefaultAction XBLContainer.java 757   
>>> org.orbeon.oxf.xforms.xbl.XBLContainer dispatchEvent  
>>> XBLContainer.java 979  org.orbeon.oxf.xforms.XFormsContextStack  
>>> pushBinding XFormsContextStack.java 335   
>>> org.orbeon.oxf.xforms.XFormsContextStack pushBinding  
>>> XFormsContextStack.java 246 
org.orbeon.oxf.xforms.XFormsControls

>>> pushBinding XFormsControls.java 520   
>>> org.orbeon.oxf.xforms.XFormsControls  
>>> visitControlElementsHandleRepeat XFormsControls.java 434   
>>> org.orbeon.oxf.xforms.XFormsControls  
>>> visitControlElementsHandleRepeat XFormsControls.java 498   
>>> org.orbeon.oxf.xforms.XFormsControls  
>>> visitControlElementsHandleRepeat XFormsControls.java 458   
>>> org.orbeon.oxf.xforms.XFormsControls  
>>> visitControlElementsHandleRepeat XFormsControls.java 458   
>>> org.orbeon.oxf.xforms.XFormsControls  
>>> visitControlElementsHandleRepeat XFormsControls.java 458
>>>
>>>
>>>
>>> --
>>> Hank Ratzesberger
>>> [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
>>>
>>>
>>
>

 

--
Hank Ratzesberger
[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
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Form Builder - nightly compatibility

Erik Bruchez-3
Hi Louis,

I am not sure what's happening, but any minimal example you can send
us would help!

-Erik

On Mon, Apr 5, 2010 at 10:14 PM, Louis Ratzesberger
<[hidden email]> wrote:

> Hi Erik,
>
> I re-deployed the nightly build war file, then copied the exist-data
> files back and restarted. But again all the phone and date controls
> have a binding error.
>
> Well, perhaps it is better to try to re-create these controls. The rest
> appear to be fine.  Perhaps handling of these controls has changed?
>
> But if you want we can send the db backup files.
>
> Thanks,
> Hank
>
> <fr:us-phone xmlns="http://orbeon.org/oxf/xml/form-builder"
> xmlns:fb="http://orbeon.org/oxf/xml/form-builder"
> xmlns:xbl="http://www.w3.org/ns/xbl"
> xmlns:pipeline="java:org.orbeon.oxf.processor.pipeline.PipelineFunctionLibrary"
> bind="Phone-bind" id="Phone-control" class="fr-email-recipient">
> <xforms:label ref="$form-resources/Phone/label"/>
> <xforms:hint ref="$form-resources/Phone/hint"/>
> <xforms:help ref="$form-resources/Phone/help"/>
> <xforms:alert ref="$fr-resources/detail/labels/alert"/>
> </fr:us-phone>
> </xhtml:td>
> <xhtml:td>
> <!--
> <fr:dropdown-date xmlns="http://orbeon.org/oxf/xml/form-builder"
> xmlns:xbl="http://www.w3.org/ns/xbl"
> xmlns:fb="http://orbeon.org/oxf/xml/form-builder"
> xmlns:pipeline="java:org.orbeon.oxf.processor.pipeline.PipelineFunctionLibrary"
> bind="Birth-Date-bind" id="Birth-Date-control"
> class="fr-email-recipient">
> <xforms:label ref="$form-resources/Birth-Date/label"/>
> <xforms:hint ref="$form-resources/Birth-Date/hint"/>
> <xforms:help ref="$form-resources/Birth-Date/help"/>
> <xforms:alert ref="$fr-resources/detail/labels/alert"/>
> </fr:dropdown-date>
> -->
>
> Quoting Erik Bruchez <[hidden email]>:
>
>> I have now fixed this bug. Hopefully it's the one you hit!
>>
>> -Erik
>>
>> On Mon, Apr 5, 2010 at 11:22 AM, Erik Bruchez <[hidden email]>
>
> wrote:
>>
>>> Louis,
>>>
>>> It looks like a new bug or a regression, although I am not sure
>
> why this
>>>
>>> should have started happening! I have identified a case where that
>>> particular exception can happen and we'll try to fix it ASAP:
>>>
>>>
>>>
> http://forge.ow2.org/tracker/index.php?func=detail&aid=314885&group_id=168&atid=350207
>>>
>>> We keep a list of potential compatibility issues in the release
>
> notes for
>>>
>>> the upcoming 3.8:
>>>
>>>
>>>
> http://sites.google.com/a/orbeon.com/forms/doc/developer-guide/release-orbeon-forms-38#TOC-Compatibility-notes
>>>
>>> In general, we try to keep compatibility as much as possible, and
>
> we have
>>>
>>> lots of automatic unit tests to help with that, but the reality is
>
> that
>>>
>>> nightly builds have not received any extra testing, and unit tests
>
> don't
>>>
>>> necessarily cover everything (although we keep adding new ones).
>>>
>>> -Erik
>>>
>>> On Sun, Apr 4, 2010 at 9:35 PM, Louis Ratzesberger
>
> <[hidden email]
>>>
>>> > wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> We had developed a form, then had some problems saving it --
>
> error writing
>>>>
>>>> to database.  It sounded very similar to a post which was
>
> reported fixed.
>>>>
>>>> So we saved our expanded war directory and put in the latest
>
> nightly
>>>>
>>>> war file.  After it was expanded, we copied back the pevious
>
> exist-data
>>>>
>>>> files.
>>>>
>>>> But there was a problem reported by every phone, date and upload
>
> file
>>>>
>>>> control.
>>>> The last is at the end of this message.  I commented out these
>
> statements
>>>>
>>>> and
>>>> the form loads in Form Runner. I used the eXist admin tool to
>
> edit the
>>>>
>>>> form.xhtml
>>>> file directly.
>>>>
>>>> Anyway, the question is what kind of compatibilty to expect
>
> between builds
>>>>
>>>> and what steps can we take to save our efforts.  I suppose I am
>
> assuming
>>>>
>>>> there
>>>> is some compatibility difference between builds, but that seems
>>>> reasonable to expect.
>>>>
>>>> (Yes, we know FR is "preliminary" but can you blame us?)
>>>>
>>>> Thanks,
>>>> Hank
>>>>
>>>>   Error Message
>>>>
>>>> Binding exception for target: Upload-Docs-Files-control
>>>>
>>>> [image: Show Details]Show details
>>>>
>>>> [image: Hide Details]Hide details
>>>>   Call Stack
>>>>    Resource URL  Line  Column  Description  XML Element
>>>> oxf:/ops/pfc/xforms-epilogue.xpl 135 60
>>>> reading processor output
>>>> name ? document
>>>> id ? xhtml-data
>>>>    <p:output name="document" id="xhtml-data"/>
>>>> oxf:/ops/pfc/xforms-epilogue.xpl 146 59
>>>> reading processor output
>>>> name ? data
>>>> ref ? xformed-data
>>>>    <p:output name="data" ref="xformed-data"/>
>>>> oxf:/config/epilogue.xpl 41 58
>>>> reading processor output
>>>> name ? xformed-data
>>>> id ? xformed-data
>>>>    <p:output name="xformed-data" id="xformed-data"/>
>>>> oxf:/config/epilogue-servlet.xpl 31 48
>>>> reading processor output
>>>> name ? xformed-data
>>>>    <p:param type="input" name="xformed-data"/>
>>>> oxf:/config/epilogue.xpl 60 46
>>>> executing processor
>>>> name ?
>
> {http://www.orbeon.com/oxf/processors}pipeline<http://www.orbeon.com/oxf/processors%7Dpipeline>
>>>>
>>>>    <p:processor name="oxf:pipeline">...</p:processor>
>>>> oxf:/apps/fr/page-flow.xml 204 47
>>>> executing processor
>>>> name ?
>
> {http://www.orbeon.com/oxf/processors}pipeline<http://www.orbeon.com/oxf/processors%7Dpipeline>
>>>>
>>>>        oxf:/page-flow.xml  34  106
>>>> reading page model data output
>>>> page id ? apps
>>>> model ? apps/${1}/page-flow.xml
>>>>    <page id="apps" path-info="/([^/]+)/.*"
>
> matcher="oxf:perl5-matcher"
>>>>
>>>> model="apps/${1}/page-flow.xml"/>
>>>>   Java Exceptions (4 total)
>>>>
>>>> Java Exceptions are the native mechanism by which Orbeon Forms
>
> reports
>>>>
>>>> errors. More than one exception may be provided below but usually
>
> the first
>>>>
>>>> exception along with the Orbeon Forms Stack Trace above provide
>
> enough
>>>>
>>>> information to track down an issue.
>>>>    [image: Toggle] org.orbeon.oxf.common.ValidationException
>
>   Exception
>>>>
>>>> Class  org.orbeon.oxf.common.ValidationException   Message
>
> Binding
>>>>
>>>> exception for target: Upload-Docs-Files-control  Resource URL
>
>
>>>>
>>>> Line N/A  Column N/A  Servlet Stack Trace
>>>> (311 method calls)    Class Name  Method Name  File Name
>
> Line
>>>>
>>>> Number   org.orbeon.oxf.xforms.xbl.XBLContainer performDefaultAction
>>>> XBLContainer.java 757  org.orbeon.oxf.xforms.xbl.XBLContainer dispatchEvent
>>>> XBLContainer.java 979  org.orbeon.oxf.xforms.XFormsContextStack pushBinding
>>>> XFormsContextStack.java 335  org.orbeon.oxf.xforms.XFormsContextStack
>>>> pushBinding XFormsContextStack.java 246
>
> org.orbeon.oxf.xforms.XFormsControls
>>>>
>>>> pushBinding XFormsControls.java 520
>>>> org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat
>>>> XFormsControls.java 434  org.orbeon.oxf.xforms.XFormsControls
>>>> visitControlElementsHandleRepeat XFormsControls.java 498
>>>> org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat
>>>> XFormsControls.java 458  org.orbeon.oxf.xforms.XFormsControls
>>>> visitControlElementsHandleRepeat XFormsControls.java 458
>>>> org.orbeon.oxf.xforms.XFormsControls visitControlElementsHandleRepeat
>>>> XFormsControls.java 458
>>>>
>>>>
>>>>
>>>> --
>>>> Hank Ratzesberger
>>>> [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
>>>>
>>>>
>>>
>>
>
>
>
> --
> Hank Ratzesberger
> [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
>
>


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

Redirecting Form Builder URL's

Louis Ratzesberger
Hi,

I'm attempting to run a Form Builder form from another URL than it was
created under and from behind a web server (lighttpd, which acts as a
proxy, not an AJP connector).  e.g.

https://example.com/

from the browser, is redirected to

http://localhost:8080/orbeon/fr/myapp/myform/new/

the  oxf.url-rewriting.service.base-uri property has fixed
some problems (thank you Erik):

http://wiki.orbeon.com/forms/doc/developer-guide/configuration-properties/configuration-properties-base#TOC-URL-rewriting

I set the property to "http://localhost:8080/orbeon" where the tomcat  
server is running.

However, rewriting the url "/" to "/orbeon/fr/myapp/myform/new/" does  
not work.
When the form is submitted, a "Session has expired" exception is thrown:

Orbeon Forms Error
Type class org.orbeon.oxf.common.OXFException
Message Session has expired. Unable to process incoming request.
Location oxf:/ops/xforms/xforms-server-submit.xpl
Line 65
Column 51
Stack Trace

org.orbeon.oxf.common.OXFException: Session has expired. Unable to  
process incoming request.

I have also tried configuring oxf.http.proxy.host, but I don't think that is
applicable.

So, my question is, can Form Builder created forms have their url's rewritten,
or is there something in the form that prevents this?  Admittedly, putting the
form on the home page "/" presents issues, and putting a form on "/" may
not be possible.  But what about another url like "/myform" rewriting the
urls to, e.g., "/orbeon/fr/myapp/myform/..."

Very best,
Louis (Hank) Ratzesberger




--
Hank Ratzesberger
[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
Reply | Threaded
Open this post in threaded view
|

Re: Redirecting Form Builder URL's

Alessandro  Vernet
Administrator
Hank,

I have never tried this, but I would attempt to write my own page flow
that handles / and does just what the FR page flow does when it sees
/fr/myapp/myform/new/. You'll let us know if you have any luck with
that!

Alex

On Sun, Apr 11, 2010 at 5:18 PM, Louis Ratzesberger
<[hidden email]> wrote:

> Hi,
>
> I'm attempting to run a Form Builder form from another URL than it was
> created under and from behind a web server (lighttpd, which acts as a
> proxy, not an AJP connector).  e.g.
>
> https://example.com/
>
> from the browser, is redirected to
>
> http://localhost:8080/orbeon/fr/myapp/myform/new/
>
> the  oxf.url-rewriting.service.base-uri property has fixed
> some problems (thank you Erik):
>
> http://wiki.orbeon.com/forms/doc/developer-guide/configuration-properties/configuration-properties-base#TOC-URL-rewriting
>
> I set the property to "http://localhost:8080/orbeon" where the tomcat server
> is running.
>
> However, rewriting the url "/" to "/orbeon/fr/myapp/myform/new/" does not
> work.
> When the form is submitted, a "Session has expired" exception is thrown:
>
> Orbeon Forms Error
> Type    class org.orbeon.oxf.common.OXFException
> Message Session has expired. Unable to process incoming request.
> Location        oxf:/ops/xforms/xforms-server-submit.xpl
> Line    65
> Column  51
> Stack Trace
>
> org.orbeon.oxf.common.OXFException: Session has expired. Unable to process
> incoming request.
>
> I have also tried configuring oxf.http.proxy.host, but I don't think that is
> applicable.
>
> So, my question is, can Form Builder created forms have their url's
> rewritten,
> or is there something in the form that prevents this?  Admittedly, putting
> the
> form on the home page "/" presents issues, and putting a form on "/" may
> not be possible.  But what about another url like "/myform" rewriting the
> urls to, e.g., "/orbeon/fr/myapp/myform/..."
>
> Very best,
> Louis (Hank) Ratzesberger
>
>
>
>
> --
> Hank Ratzesberger
> [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
>
>


--
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
Reply | Threaded
Open this post in threaded view
|

Re: Re: Redirecting Form Builder URL's

Louis Ratzesberger

Hi Alex,

So, I moved the context to "/"  (ROOT). The property  
oxf.url-rewriting.service.base-uri
is "http://localhost:8080/" as well.  At first, I got a blank page on  
the form.

I recall it was mentioned that there is some context information in  
the form, so  I had
the thought to try this...I re-published the form.

Now that the web server only rewrites the request "^/$" to
/fr/myapp/myform/new/ this single form runs without problems (fingers  
crossed).
The only issue, really, is that it was hoped that the web server would
be a firewall to accessing the tomcat port, but I conclude there is an
issue with rewriting the url of a published form and it seems best
to publish in the context /.

It also appears to be necessary to unzip some of the theme files as
recommended in the apache configuration -- some theme files are
timing out on GET.

I did try using the page flow controller

     <page id="form-new" path-info="/fr/myapp/myform/new/"/>

     <page id="root" path-info="/?" matcher="oxf:perl5-matcher">
         <action><result page="form-new"/></action>
     </page>

but got a blank page.  I may not have tried this after re-publishing.

Best,
Hank


Quoting Alessandro Vernet <[hidden email]>:

> Hank,
>
> I have never tried this, but I would attempt to write my own page flow
> that handles / and does just what the FR page flow does when it sees
> /fr/myapp/myform/new/. You'll let us know if you have any luck with
> that!
>
> Alex
>
> On Sun, Apr 11, 2010 at 5:18 PM, Louis Ratzesberger
> <[hidden email]> wrote:
>> Hi,
>>
>> I'm attempting to run a Form Builder form from another URL than it was
>> created under and from behind a web server (lighttpd, which acts as a
>> proxy, not an AJP connector).  e.g.
>>
>> https://example.com/
>>
>> from the browser, is redirected to
>>
>> http://localhost:8080/orbeon/fr/myapp/myform/new/
>>
>> the  oxf.url-rewriting.service.base-uri property has fixed
>> some problems (thank you Erik):
>>
>> http://wiki.orbeon.com/forms/doc/developer-guide/configuration-properties/configuration-properties-base#TOC-URL-rewriting
>>
>> I set the property to "http://localhost:8080/orbeon" where the tomcat server
>> is running.
>>
>> However, rewriting the url "/" to "/orbeon/fr/myapp/myform/new/" does not
>> work.
>> When the form is submitted, a "Session has expired" exception is thrown:
>>
>> Orbeon Forms Error
>> Type    class org.orbeon.oxf.common.OXFException
>> Message Session has expired. Unable to process incoming request.
>> Location        oxf:/ops/xforms/xforms-server-submit.xpl
>> Line    65
>> Column  51
>> Stack Trace
>>
>> org.orbeon.oxf.common.OXFException: Session has expired. Unable to process
>> incoming request.
>>
>> I have also tried configuring oxf.http.proxy.host, but I don't think that is
>> applicable.
>>
>> So, my question is, can Form Builder created forms have their url's
>> rewritten,
>> or is there something in the form that prevents this?  Admittedly, putting
>> the
>> form on the home page "/" presents issues, and putting a form on "/" may
>> not be possible.  But what about another url like "/myform" rewriting the
>> urls to, e.g., "/orbeon/fr/myapp/myform/..."
>>
>> Very best,
>> Louis (Hank) Ratzesberger
>>
>>
>>
>>
>> --
>> Hank Ratzesberger
>> [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
>>
>>
>
>
>
> --
> Orbeon Forms - Web forms, open-source, for the Enterprise -
> http://www.orbeon.com/
> My Twitter: http://twitter.com/avernet
>


--
Hank Ratzesberger
[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
Reply | Threaded
Open this post in threaded view
|

Re: Re: Redirecting Form Builder URL's

Louis Ratzesberger

Note:  The need to re-publish a form after moving the
context (/orbeon to /) may be due to tomcat6 persistent
sessions.

I'm sure I will be doing this again and will take better
notes.

Cheers,
Hank


Quoting Louis Ratzesberger <[hidden email]>:

>
> Hi Alex,
>
> So, I moved the context to "/"  (ROOT). The property  
> oxf.url-rewriting.service.base-uri
> is "http://localhost:8080/" as well.  At first, I got a blank page  
> on the form.
>
> I recall it was mentioned that there is some context information in  
> the form, so  I had
> the thought to try this...I re-published the form.
>
> Now that the web server only rewrites the request "^/$" to
> /fr/myapp/myform/new/ this single form runs without problems  
> (fingers crossed).
> The only issue, really, is that it was hoped that the web server would
> be a firewall to accessing the tomcat port, but I conclude there is an
> issue with rewriting the url of a published form and it seems best
> to publish in the context /.
>
> It also appears to be necessary to unzip some of the theme files as
> recommended in the apache configuration -- some theme files are
> timing out on GET.
>
> I did try using the page flow controller
>
>     <page id="form-new" path-info="/fr/myapp/myform/new/"/>
>
>     <page id="root" path-info="/?" matcher="oxf:perl5-matcher">
>         <action><result page="form-new"/></action>
>     </page>
>
> but got a blank page.  I may not have tried this after re-publishing.
>
> Best,
> Hank
>
>
> Quoting Alessandro Vernet <[hidden email]>:
>
>> Hank,
>>
>> I have never tried this, but I would attempt to write my own page flow
>> that handles / and does just what the FR page flow does when it sees
>> /fr/myapp/myform/new/. You'll let us know if you have any luck with
>> that!
>>
>> Alex
>>
>> On Sun, Apr 11, 2010 at 5:18 PM, Louis Ratzesberger
>> <[hidden email]> wrote:
>>> Hi,
>>>
>>> I'm attempting to run a Form Builder form from another URL than it was
>>> created under and from behind a web server (lighttpd, which acts as a
>>> proxy, not an AJP connector).  e.g.
>>>
>>> https://example.com/
>>>
>>> from the browser, is redirected to
>>>
>>> http://localhost:8080/orbeon/fr/myapp/myform/new/
>>>
>>> the  oxf.url-rewriting.service.base-uri property has fixed
>>> some problems (thank you Erik):
>>>
>>> http://wiki.orbeon.com/forms/doc/developer-guide/configuration-properties/configuration-properties-base#TOC-URL-rewriting
>>>
>>> I set the property to "http://localhost:8080/orbeon" where the  
>>> tomcat server
>>> is running.
>>>
>>> However, rewriting the url "/" to "/orbeon/fr/myapp/myform/new/" does not
>>> work.
>>> When the form is submitted, a "Session has expired" exception is thrown:
>>>
>>> Orbeon Forms Error
>>> Type    class org.orbeon.oxf.common.OXFException
>>> Message Session has expired. Unable to process incoming request.
>>> Location        oxf:/ops/xforms/xforms-server-submit.xpl
>>> Line    65
>>> Column  51
>>> Stack Trace
>>>
>>> org.orbeon.oxf.common.OXFException: Session has expired. Unable to process
>>> incoming request.
>>>
>>> I have also tried configuring oxf.http.proxy.host, but I don't  
>>> think that is
>>> applicable.
>>>
>>> So, my question is, can Form Builder created forms have their url's
>>> rewritten,
>>> or is there something in the form that prevents this?  Admittedly, putting
>>> the
>>> form on the home page "/" presents issues, and putting a form on "/" may
>>> not be possible.  But what about another url like "/myform" rewriting the
>>> urls to, e.g., "/orbeon/fr/myapp/myform/..."
>>>
>>> Very best,
>>> Louis (Hank) Ratzesberger
>>>
>>>
>>>
>>>
>>> --
>>> Hank Ratzesberger
>>> [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
>>>
>>>
>>
>>
>>
>> --
>> Orbeon Forms - Web forms, open-source, for the Enterprise -
>> http://www.orbeon.com/
>> My Twitter: http://twitter.com/avernet
>>
>
>
>
> --
> Hank Ratzesberger
> [hidden email]


--
Hank Ratzesberger
[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
Reply | Threaded
Open this post in threaded view
|

Out of Office AutoReply: Redirecting Form Builder URL's

pappleby
Out of Office AutoReply: Redirecting Form Builder URL's

I am out of the office until 19th April

***********************************************************************************************

This email, including any attachment, is confidential and may be legally privileged. If you are not the intended recipient or if you have received this email in error, please inform the sender immediately by reply and delete all copies from your system. Do not retain, copy, disclose, distribute or otherwise use any of its contents.

 

Whilst we have taken reasonable precautions to ensure that this email has been swept for computer viruses, we cannot guarantee that this email does not contain such material and we therefore advise you to carry out your own virus checks. We do not accept liability for any damage or losses sustained as a result of such material.

 

Please note that incoming and outgoing email communications passing through our IT systems may be monitored and/or intercepted by us solely to determine whether the content is business related and compliant with company standards.

***********************************************************************************************

The Stationery Office Limited is registered in England No. 3049649 at 10 Eastbourne Terrace, London, W2 6LG