Orbeon Forms community mailing list

outputs within groups that are bound to a node with type xs:date

Classic

List

Threaded

6 messages Options

David McIntyre

outputs within groups that are bound to a node with type xs:date

I've come across some unexpected behaviour in the following situation:
* I have a group with a bind, and the bind specifies a type of "xs:date".
* Within the group I have an output with a value
Instead of displaying the output with the value as expected, it is using the initial contents of the node that the bind points to. I have reduced it to a sandbox example which contains the following:

            <xforms:instance>
                <data>
			<foo>2006-05-03</foo>
		</data>
            </xforms:instance>

            <xforms:bind nodeset="/data/foo" id="bind-foo" type="xs:date"/>

	<xforms:group bind="bind-foo">
		<xforms:input ref="."/>
		<xforms:output value="'output-foo'"/>
	</xforms:group>

The resulting output displays the string 'Wednesday May 3, 2006' instead of the string 'output-foo'. The output string remains constant if the input value changes.

Any thoughts on what is going on here? In case you're wondering, the reason I want an output inside a group like this is that I want the output to show/hide according to whether the node in question is relevant or not.

Cheers,
Dave

--
Orion Signature

Dave McIntyre
Software Developer

2nd Floor, Orion House, cnr Enfield & Mary St, Mt Eden, PO Box 8273, Auckland, New Zealand
M.+64 21 212 8087 P.+64 9 638 0600 F.+64 9 638 0699
S.<a href="callto:dave.mcintyre">dave.mcintyre E.[hidden email] W.www.orionhealth.com

This e-mail and any attachments are intended only for the person to whom it is addressed and may contain privileged, proprietary, or other data protected from disclosure under applicable law. If you are not the addressee or the person responsible for delivering this to the addressee you are hereby notified that reading, copying or distributing this transmission is prohibited. If you have received this e-mail in error, please telephone us immediately and remove all copies of it from your system. Thank you for your co-operation.

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

David McIntyre

Re: outputs within groups that are bound to a node with type xs:date

Sorry, I failed to attach the sandbox example.

Dave McIntyre wrote:

I've come across some unexpected behaviour in the following situation:
* I have a group with a bind, and the bind specifies a type of "xs:date".
* Within the group I have an output with a value
Instead of displaying the output with the value as expected, it is using the initial contents of the node that the bind points to. I have reduced it to a sandbox example which contains the following:
            <xforms:instance>
                <data>
			<foo>2006-05-03</foo>
		</data>
            </xforms:instance>

            <xforms:bind nodeset="/data/foo" id="bind-foo" type="xs:date"/>

	<xforms:group bind="bind-foo">
		<xforms:input ref="."/>
		<xforms:output value="'output-foo'"/>
	</xforms:group>

  
The resulting output displays the string 'Wednesday May 3, 2006' instead of the string 'output-foo'. The output string remains constant if the input value changes.

Any thoughts on what is going on here? In case you're wondering, the reason I want an output inside a group like this is that I want the output to show/hide according to whether the node in question is relevant or not.

Cheers,
Dave

--
Orion Signature

Dave McIntyre
Software Developer

2nd Floor, Orion House, cnr Enfield & Mary St, Mt Eden, PO Box 8273, Auckland, New Zealand
M.+64 21 212 8087 P.+64 9 638 0600 F.+64 9 638 0699
S.<a href="callto:dave.mcintyre">dave.mcintyre E.[hidden email] W.www.orionhealth.com

This e-mail and any attachments are intended only for the person to whom it is addressed and may contain privileged, proprietary, or other data protected from disclosure under applicable law. If you are not the addressee or the person responsible for delivering this to the addressee you are hereby notified that reading, copying or distributing this transmission is prohibited. If you have received this e-mail in error, please telephone us immediately and remove all copies of it from your system. Thank you for your co-operation.

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

--
Orion Signature

Dave McIntyre
Software Developer

outputs-in-groups.xhtml (1K) Download Attachment

Erik Bruchez

Re: outputs within groups that are bound to a node with type xs:date

Administrator

Dave,

I think this is fixed already: I do see output-foo and output-bar with
the latest code in the online sandbox:

http://www.orbeon.com/ops/xforms-sandbox

-Erik

Dave McIntyre wrote:

> Sorry, I failed to attach the sandbox example.
>
> Dave McIntyre wrote:
>> I've come across some unexpected behaviour in the following situation:
>> * I have a group with a bind, and the bind specifies a type of "xs:date".
>> * Within the group I have an output with a value
>> Instead of displaying the output with the value as expected, it is
>> using the initial contents of the node that the bind points to. I
>> have reduced it to a sandbox example which contains the following:
>> <xforms:instance>
>> <data>
>> <foo>2006-05-03</foo>
>> </data>
>> </xforms:instance>
>>
>> <xforms:bind nodeset="/data/foo" id="bind-foo" type="xs:date"/>
>>
>> <xforms:group bind="bind-foo">
>> <xforms:input ref="."/>
>> <xforms:output value="'output-foo'"/>
>> </xforms:group>
>>
>>
>> The resulting output displays the string 'Wednesday May 3, 2006'
>> instead of the string 'output-foo'. The output string remains
>> constant if the input value changes.
>>
>> Any thoughts on what is going on here? In case you're wondering, the
>> reason I want an output inside a group like this is that I want the
>> output to show/hide according to whether the node in question is
>> relevant or not.
>>
>> Cheers,
>> Dave
>> --
>> * Dave McIntyre
>> Software Developer*
>>
>> 2nd Floor, Orion House, cnr Enfield & Mary St, Mt Eden, PO Box 8273,
>> Auckland, New Zealand
>> M.+64 21 212 8087 P.+64 9 638 0600 F.+64 9 638 0699
>> S.dave.mcintyre <callto:dave.mcintyre>
>> [hidden email]
>> <mailto:[hidden email]> W.www.orionhealth.com
>> <http://www.orionhealth.com>
>>
>>
>>
>>
>> This e-mail and any attachments are intended only for the person to
>> whom it is addressed and may contain privileged, proprietary, or other
>> data protected from disclosure under applicable law. If you are not
>> the addressee or the person responsible for delivering this to the
>> addressee you are hereby notified that reading, copying or
>> distributing this transmission is prohibited. If you have received
>> this e-mail in error, please telephone us immediately and remove all
>> copies of it from your system. Thank you for your co-operation.
>>
>> ______________________________________________________________________
>> This email has been scanned by the MessageLabs Email Security System.
>> For more information please visit http://www.messagelabs.com/email
>> ______________________________________________________________________
>
>
> --
> * Dave McIntyre
> Software Developer*
>
> 2nd Floor, Orion House, cnr Enfield & Mary St, Mt Eden, PO Box 8273,
> Auckland, New Zealand
> M.+64 21 212 8087 P.+64 9 638 0600 F.+64 9 638 0699
> S.dave.mcintyre <callto:dave.mcintyre> [hidden email]
> <mailto:[hidden email]> W.www.orionhealth.com
> <http://www.orionhealth.com>
>
>
>
>
> This e-mail and any attachments are intended only for the person to whom
> it is addressed and may contain privileged, proprietary, or other data
> protected from disclosure under applicable law. If you are not the
> addressee or the person responsible for delivering this to the addressee
> you are hereby notified that reading, copying or distributing this
> transmission is prohibited. If you have received this e-mail in error,
> please telephone us immediately and remove all copies of it from your
> system. Thank you for your co-operation.
>
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

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

Paul Warner-2

HSQLDB tablenames must begin with 'oxf'

Hi all,

I have discovered after some work with the address-book example, that the
embedded sql database that is configured with Orbeon by default (HSQLDB)
requires table names beginning with the letters 'oxf', in order to make inserts
and deletes after the table is created. I thought it would be worth mentioning,
since it seems like an obscure requirement, and I haven't seen it in the
documentation.

Simply put, I have taken the address-book example and changed *one* thing, the
table name. If I change it to something that does not start with 'oxf', then I
can see what is in the table if I initialise it with data, but I cannot insert
or delete via the buttons in the form. I get no error message or message of any
kind - it looks and acts like it succeeds, but no change in the data set is
visible. The form displays the original, initialised data set just fine - so
the create table statement, the original inserts (!), and the select statement
are all working.

Then, if I change the table name to something beginning with 'oxf' (it does not
need to be followed by an underscore), the form works fine: I can read, write,
and delete.

Regards,
Paul

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

Erik Bruchez

Re: HSQLDB tablenames must begin with 'oxf'

Administrator

Paul,

Here is the SQL that creates the tables, init-script.xpl:

create table oxf_address_book (
id integer not null identity primary key,
first varchar(255) not null,
last varchar(255) not null,
phone varchar(255) not null
)

Then model.xpl uses this to list the content of that table:

select * from oxf_address_book

and add-action.xpl inserts with:

insert into oxf_address_book values ...

etc.

The bottom line is that you must just use the same table name all over
the place, but I don't think there is another requirement. So I am a
little puzzled by the issue you mention! Did you modify the table name
everywhere?

-Erik

Paul Warner wrote:

> Hi all,
>
> I have discovered after some work with the address-book example, that the
> embedded sql database that is configured with Orbeon by default (HSQLDB)
> requires table names beginning with the letters 'oxf', in order to make inserts
> and deletes after the table is created. I thought it would be worth mentioning,
> since it seems like an obscure requirement, and I haven't seen it in the
> documentation.
>
> Simply put, I have taken the address-book example and changed *one* thing, the
> table name. If I change it to something that does not start with 'oxf', then I
> can see what is in the table if I initialise it with data, but I cannot insert
> or delete via the buttons in the form. I get no error message or message of any
> kind - it looks and acts like it succeeds, but no change in the data set is
> visible. The form displays the original, initialised data set just fine - so
> the create table statement, the original inserts (!), and the select statement
> are all working.
>
> Then, if I change the table name to something beginning with 'oxf' (it does not
> need to be followed by an underscore), the form works fine: I can read, write,
> and delete.
>
> Regards,
> Paul

Paul Warner-2

RE: HSQLDB tablenames must begin with 'oxf'

Dear Erik,

Thanks very much for your reply. Yes, I changed the tablename everywhere,
created new names for the initialising inserts so I could be sure I had my new
table - but made no other changes to the address-book files. The create table,
initial inserts, and select all work with the non-'oxf' names. Only the form
inserts and deletes fail (silently).

Steps to recreate this bug:

1. Copy the address-book directory to a new place, and map it with the
page-flow.xml in the resources directory so you can run it.
2. Change the table name in all files to something that does *not* begin with
'oxf', i.e., 'new_table_test' or some other name of your choosing.
3. Modify the initial inserts so you know you have your own data displaying.
Make no other changes to the code, other than the name and the initialised data.

4. Navigate to your url so the table gets created and the initial inserts made.
You will see your data displayed in the list. This demonstrates that the table
has been created and the initial inserts made. It also shows that the select
statement works.
5. Attempt to add or delete a record. Notice that your data list doesn't
change, and that you get no error anywhere.
6. Change the tablename everywhere in your test-address-book directory to a new
name that begins with the letters 'oxf', i.e., 'oxfnew_table', and modify the
initial inserts so you can be sure you have your new table. As in the
beginning, make no other changes.
7. Check that you have created the table by navigating to your directory (if
necessary bounce tomcat).
8. Test adding and deleting via the form. Note that your inserts display and
your deletes are removed from the list.
9. Go back and change the names again to something non-'oxf' to reconfirm, if
you wish.

Regards,
Paul

> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of
> Erik Bruchez
> Sent: 29 August 2006 00:16
> To: [hidden email]
> Subject: Re: [ops-users] HSQLDB tablenames must begin with 'oxf'
>
> Paul,
>
> Here is the SQL that creates the tables, init-script.xpl:
>
> create table oxf_address_book (
> id integer not null identity primary key,
> first varchar(255) not null,
> last varchar(255) not null,
> phone varchar(255) not null
> )
>
> Then model.xpl uses this to list the content of that table:
>
> select * from oxf_address_book
>
> and add-action.xpl inserts with:
>
> insert into oxf_address_book values ...
>
> etc.
>
> The bottom line is that you must just use the same table name
> all over the place, but I don't think there is another
> requirement. So I am a little puzzled by the issue you
> mention! Did you modify the table name everywhere?
>
> -Erik
>
> Paul Warner wrote:
> > Hi all,
> >
> > I have discovered after some work with the address-book
> example, that
> > the embedded sql database that is configured with Orbeon by default
> > (HSQLDB) requires table names beginning with the letters 'oxf', in
> > order to make inserts and deletes after the table is created. I
> > thought it would be worth mentioning, since it seems like
> an obscure
> > requirement, and I haven't seen it in the documentation.
> >
> > Simply put, I have taken the address-book example and changed *one*
> > thing, the table name. If I change it to something that does not
> > start with 'oxf', then I can see what is in the table if I
> initialise
> > it with data, but I cannot insert or delete via the buttons in the
> > form. I get no error message or message of any kind - it looks and
> > acts like it succeeds, but no change in the data set is
> visible. The
> > form displays the original, initialised data set just fine - so the
> > create table statement, the original inserts (!), and the
> select statement are all working.
> >
> > Then, if I change the table name to something beginning
> with 'oxf' (it
> > does not need to be followed by an underscore), the form
> works fine: I
> > can read, write, and delete.
> >
> > Regards,
> > Paul
>
> --
> Orbeon - XForms Everywhere:
> http://www.orbeon.com/blog/
>
>