Moving simple Rest-Submission to XPL

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

Moving simple Rest-Submission to XPL

Marcus-2
Hi,
ok, while i have to find a solution for saving my mixed-content documents and transfer all the embedded html to normal xhtml, rather than lexical html i have to make some disicions and wanna ask for help with this one!
 
At the moment i'm doing my saving like at gov-forms. I have a save-submission and for the right paths i use some addition instances with my exist-paths, and the documents-paramters and than there is the docuemnts-instance as well.
If i now have to serialze the embedded html in my documents-instance that i was getting from the FCKeditor right before saving to eXist i see two ways:
1# to run additional submissions when i push the save-trigger
2# to use only one xpl and to do all the stuff there
 
1: Would be the easier working thing now
2: Here i have the problem to get all the infos i nee to the XPL when i normaly only can overgive one instance as input :-(
And than there is still the question about the custom error management with all the xforms-submit-events! I don't know how i could use them with an xpl???
 
Normaly i think it would be better to prefer the xpl version, but for now addistion submissions are the easier way!
What do you think about that? Do you have simple answer on my problems with way 2#???
 
Thanks for every thoughts on this.
Marcus
 
 
Just to give the sample of my actual submission i copied it:
-------------------------------------------------------------------------------------
<xforms:submission id="save-submission" ref="xxforms:instance('document-instance')"
action="{xxforms:instance('exist-instance')//main2}/{xxforms:instance('parameters-instance')/form-id}/{xxforms:instance('parameters-instance')/document-id}"
method="put" replace="none" f:url-type="resource" xxforms:username="kkbib01" xxforms:password="kkbib">
<xforms:setvalue ev:event="xforms-submit-serialize" ref="instance('persistence-admin-instance')/save-status">validated</xforms:setvalue>
<xforms:action ev:event="xforms-submit-done">
<xforms:setvalue ref="instance('persistence-admin-instance')/message" value="xxforms:instance('resources-instance')/forms/detail/messages/save-success"/>
<xforms:setvalue ref="xxforms:instance('control-instance')/data-status"/>
<xforms:setvalue ref="instance('persistence-admin-instance')/save-status"/>
<xforms:toggle case="ok-message"/>
<xforms:toggle case="ok-message2"/>
</xforms:action>
<xforms:action ev:event="xforms-submit-error">
<xforms:action if="not(instance('persistence-admin-instance')/save-status = 'validated')">
<xforms:setvalue ref="instance('persistence-admin-instance')/message"
value="xxforms:instance('resources-instance')/forms//detail/messages/save-error-form"/>
<xforms:toggle case="validation-error-message"/>
<xforms:toggle case="validation-error-message2"/>
</xforms:action>
<xforms:action if="instance('persistence-admin-instance')/save-status = 'validated'">
<xforms:setvalue ref="instance('persistence-admin-instance')/message"
value="xxforms:instance('resources-instance')/forms//detail/messages/save-error-submission"/>
<xforms:toggle case="fatal-error-message"/>
<xforms:toggle case="fatal-error-message2"/>
</xforms:action>
<xforms:setvalue ref="instance('persistence-admin-instance')/save-status"/>
</xforms:action>
</xforms:submission>
 


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

Re: Moving simple Rest-Submission to XPL

Alessandro Vernet
Administrator
Marcus,

On 6/21/07, Marcus <[hidden email]> wrote:
> If i now have to serialze the embedded html in my documents-instance that i
> was getting from the FCKeditor right before saving to eXist i see two ways:
> 1# to run additional submissions when i push the save-trigger
> 2# to use only one xpl and to do all the stuff there

Unless you would be reusing the service that does the HTML to XHTML
processing and returns the instance (case #1 above), I would go with a
simple pipeline which is called with 1 submission. This way you have
less files, the XForms code is simpler (only 1 submission), and you
have only one service in the page flow. There are also arguments going
the other way, so this somewhat a matter or personal preference :).

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
http://www.orbeon.com/



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