Re: Editing existing instance documents as well as new

hello,

Phillip Rhodes wrote:
> A couple of points:
>
> Is there a way within the xform document to specify the URL where the 
> instance document can be obtained?  Perhaps if you created the xform 
> document dynamically, you can include the href to a servlet that would 
> return you instance data (in xml of course, since that is the spec).  
> You would have to implement the servlet.
yes. you can use setInstanceURI to pass a URI to the processor before 
init. this URI will then be used to load the instance.
before you ask: this is not part of 0.9.2 yet but of next release (in a 
few days)
> quoting:
> <<
> you've to do some data management beyond XForms (e.g. associating 
> instances with forms)
>  >>
>
> I do not understand this!
> "instances" in this case is the xml template data, that is, the xml 
> document that represents the document that needs to be populated by the 
> xform implementation (e.g. a PO)
> It appears that xforms (and this implementation) of it allows you to 
> bind the instance data to the form controls.  Since you have this 
> binding defined in your xform document, I do not understand why it in 
> the quote above "you've to do some data management beyond XForms"
this was maybe badly explained:
this has nothing to do with internal association of UI/bind to 
instances; but if you want to load a form with a special instance to 
edit you have to tell the xforms processor which instance URI you want 
(see above).
if your application stores instance data separate from the forms working 
with them (as will most likely be the case) your application has to know 
which instance data belong to which form (there's nothing inside the 
instance telling you this by spec) - this is a matter of data management 
and is application specific and not handled by the XForms spec. (beyond 
its scope).
the spec says: there's a src attribute which points to the instance-data 
and this will be used by the processor - it doesn't say how the value of 
this attribute will be set by an application (cause you hardly will be 
happy with a static one). Chiba allows you to do that by the use of 
setInstanceURI. Chiba additionally offers to import an instance which 
you already have as DOM (importInstance method). in that case your 
instance DOM is imported directly into the XForms DOM without using any 
resolver.
i hope this clarified things.

best,

Joern





> At 01:21 AM 10/10/03 +0200, you wrote:
>
> > - you've to do some data management beyond XForms (e.g. associating 
> > instances with forms)
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Chiba-developer mailing list
> Chiba-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/chiba-developer


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php