Le mardi 03 avril 2007 à 12:35 +0300, Dumitru CIUBENCO a écrit : > Thanks a lot Tiry, > > I looked over your solution, it seems that it will be helpful in my > case. Great. > > Maybe you can point some documentation about basics steps in order to > build new wizard from scratch. Well the page flow is a standard Seam Pageflow => cf Seam documentation :) Is is executed in a nested sub conversation. The display occurs in a a4j:include => the navigation between sceens is done in ajax depending on the JSF output (here the pageFlow).
Here are the problems we have now : - In Seam 1.1.5 a4j:include and PageFlow do not fit well when it coms to ending both the PageFlow and the ajax navigation. => The solution for now uses a dedicated page for ending the pageFlow that generates a client side GET request to exit the ajax navigation ==> This problem is supposed to be fixed in latest Seam version (did not test it for now) - the triniad fileUpload does not work in a ajaxRequest (hope to fix this soon) If you want to take a closer look, source is quite simple : - wizards XHTML screens are in web/wizards/createWorkspace - page flow is at root of webapp source directory - the workspaceActionBean is the ActionListener tied to this wizard > > > > About background upload, you are right it’s not easy, but I am sure > it’s possible. Agreed, it should be. Good luck :) > > It’s all about workaround, when you are using AJAX J > > > > -----Original Message----- > From: Tiry [mailto:[EMAIL PROTECTED] > Sent: Monday, April 02, 2007 7:36 PM > To: Dumitru CIUBENCO > Cc: [email protected] > Subject: Re: [Ecm] Smart wizard > > > > Hi, > > > > I added a basic wizard for creating workspace some days ago in the > > trunk. > > The wizard system uses : > > - JBPM/Seam PageFlow to define the navigation rules and logic > > - a4J:include to have the wizard completly rendered in ajax > > - the action system to create the button to start the wizard > > - a nested conversation to handle the state of the wizard > > > > It might be worth looking if it works for your use case. > > Anyway, I think that you won't be able to process the upload in > > background easily without relying on a client plugin. > > > > > > Tiry > > > > Le lundi 02 avril 2007 à 18:05 +0300, Dumitru CIUBENCO a écrit : > > > Hi, > > > > > > > > > > > > I’m looking over process of creating documents, I think there is > > > possibility to improve/organize this process. > > > > > > Usually our end-user will have to do the same process in order to > > > create some document. So, let say our end-user have to do, a New > > > Document, which will have several children with attached files(pdf, > > > doc,etc). The process at this point will be : > > > > > > E.g. > > > > > > Submit New Document Name ---> Add Meta data --->Add > Info--->...--->Add > > > Child 1&Upload file--->Add info & Upload file --->...--->Add Child > > > 2&Upload file …. Add Child n &Upload file … > > > > > > We can split these processes of creating such documents in different > > > transaction, with different steps. For each transaction we can > define > > > one first step, several intermediate steps, and one ending step. > > > > > > We can define concrete sequence of steps in a transaction. > > > > > > I had started to build new component-‘smart wizard’. Basically I > want > > > to create base structure for “Directed acyclic graph”, on top of > which > > > can be implemented more complex custom wizards. > > > > > > I would like to remove as much is possible inefficient steps(like > > > premature submit) in transactions in order to implement batch > > > processes. > > > > > > E.g: if my end-user want to build 10 file with attachment, he will > > > spend a lot of time waiting for upload, but in case of > wizard(because > > > it is a single transaction) you can put this step at the end, and at > > > least upload step will be processed at the end, possible in > > > background. > > > > > > > > > > > > Any comments on this? > > > > > > > > > > > > I hope this is not a crazy idea J, or it is? > > > > > > > > > > > > > > > > > > Regards, Dima. > > > > > > > > > > > > > > > _______________________________________________ > > > ECM mailing list > > > [email protected] > > > http://lists.nuxeo.com/mailman/listinfo/ecm > > > > _______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
