Form Runner TextFields behave erratically

DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.

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

Ankur,

ankur.badoni wrote

I have been looking for exact settings that needs to be modified to
persist forms (created through form builder) and their instances
(created through form runner) in MySql database.

The trick is to do a new implementation of the persistence API for MySQL. We already have one for Oracle, which you can find in resources/apps/fr/persistence/oracle, and you can use it as a model.

Note that we are doing a number of things for Oracle that you won't necessarily want to do for MySQL. For instance, the implementation of Oracle persistence API has built-in support for auditing, which you won't necessarily need or want in your implementation for MySQL. There will be other differences, including:

* Oracle provides a special type to store XML (XMLType), while MySQL uses TEXT.
* Using XPath will be a little different (see the MySQL ExtractValue() function).

You can find more about the current Oracle persistence API at:
http://wiki.orbeon.com/forms/doc/developer-guide/form-runner-oracle-persistence-layer

And about support for auditing with the Oracle persistence API at:
http://wiki.orbeon.com/forms/doc/developer-guide/form-runner-auditing

Alex

Naresh,

Naresh Vaddepalli wrote

In Form Runner the textfields erases the characters if typed in fast during this time I notice to the extreme right the browser shows "Loading..."  which I pressume is some ajax request to server.
Is there a fix to this problem.

The controls you create with Form Builder are right now marked as incremental, which means that users' changes to the fields are taken into account as they type in the fields. This makes the UI update as you type (vs. when you move from one field to the next), but adds to the amount of processing necessary. This is also the reason for the Ajax requests you see as you type. We have talked about not marking controls as incremental by default, but I see this hasn't been done yet. When we do that, I think your problem will be resolved.

Now, even if the fields are incremental, you shouldn't have text you typed being erased. Are you using a recent nightly build? What browser are you using? If this is with a recent nightly build, could you make a screencast of what you are seeing with Jing (http://www.jingproject.com/) or a similar tool, so we can see what you are seeing?

Alex

Naresh,

Alessandro Vernet wrote

The controls you create with Form Builder are right now marked as incremental, [...]

Erik noticed that actually only the first control (that is inserted when create a form) was incremental. If you have a recent build, all the other controls you create won't be incremental. And now the issue with the first control being incremental is fixed as well.

Alex