Hello,

First of all, there is ambiguity in your question. I'm not sure how the above would tie into a "wicket-specific" question, unless you want to create an XForm-->XHTML renderer/processor using Wicket as the underlying technology (which is not a good idea IMHO). In any case:



1) Are you asking whether Wicket can be used to render XForms files (as in the the XForms specification at http://www.w3.org/TR/xforms11/).

In this case, the answer is NO, I'm not aware of such an XForm renderer. You could create a custom Wicket component that is given an XForm definition document and uses it to render an XHTML page, but that is a lot of work (and probably not a very efficient way to do it, as you would ideally use XSLT or something along those lines to do XML-->XML transformation. There are available open-source tools like Orbeon (see http://www.orbeon.com/) which can give you this kind of functionality (including processing of the "XForm submission").

Now, regarding the online/offline issue:

2) Do you have a rich client application that can render the XForms (e.g. using Swing) and allow the user to save such forms locally? In that case, you would need to write code that submits the forms when the rich client has network access. The submission should probably go to some servlet (e.g. an Orbeon-managed URL). Again, I don't think this would be wicket-related.

3) If you have a web-based application for this (e.g. a bundled Tomcat running on the user machine, which they access via the browser) then the principle is a combination of (1) and (2): You would need:

a) to render the forms using something like Orbeon to present HTML to the browser b) to store the form submission to the local FS (or a locally running DB which could be something like Derby) c) to implement an "uploader" where the user can send "locally saved" forms to a central server (same as what I talked about in (2) above)

On 11/7/2011 4:09 μμ, sramay wrote:
Hi,

   Rendering a document in the Xforms or storing it in a database is as you
have suggested
   ok.
   The issue is there when you have xform controls inside a wicket
application
    instead of HTML document(form) and take the imput and stores them into a
database.

    Am I explaining my position clearly ?

Regards


--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Xforms-Controls-within-Wicket-Application-tp3619253p3659485.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to