cocoon lib searchpath
I want to put some application specific jar files in the application's WEB-INF/lib directory. So I've created the following structure: cocoon_dir/WEB_INF/lib [1] /myapplication/WEB-INF/lib [2] [1] this is cocoon's default lib dir [2] this is where my jar are when using the default build from cocoon-2.1.5.1 src my files will only be found when I put them to [1], but not in [2]. Can anyone tell me what I'm missing here? Is there an extra config option that remained hidden from me so far? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: cocoon restart after changing java files
Hi, I made some JAVA files and put thme on$COCOON/webapp/WEB-INF/classes/whatever/... Then, I must restart Cocoon each time I change a file if I want to have my changes handled (compile my java files and then restart cocoon) But, now I wouldn't like to restart Cocoon no more as some parts of my website are used in production environment but, on the other hand, still continue to develop my java files. Is there a way to do this ? How about a second instance of cocoon(+jetty) that listens for connections on a different port (let's say instead of the default ). The combination of production environment and development is definitely nothing you want to have at the same time. HTH - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
woody: 1 form, multipe pages
I could need some insights on the following problem: I've got one xml file to store user data (one for each user). The user should be able to edit the data with forms (woody aka cforms). As the information is too complex for a single page I want to split the input process to several pages. The user should move from one page to the next and at the end the changes are saved in the xml file again. This seems to be easy, as long as I don't split the page, i.e. a single form for all, but does not work as expected (at least for me) when I try to use multiple forms and save (bind) all to one xml file. As I cannot imagine that I'm the first one to try something like this, I would like to hear some experiences of people who've solved this. Any pointers are welcome... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: woody: 1 form, multipe pages
Gunter D'Hondt wrote: Have you tried using multiple binding definitions (and multiple Binding instances)? You might also use 1 form and 1 binding but multiple form templates (this might make it easier) The disadvantage of using 1 binding is that you'll have to add and hide all fd:fields in every page you don't want to use them. Otherwise, they won't be in the binding and their values would be set to null. So the way to go seems to be multiple bindings? I've not tried this and, as the newbie I obviously am, would be glad to find an example for multiple bindings. Is there anything in the samples I've missed up to now? thanks for the really fast response on the original question. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: woody: 1 form, multipe pages
Here is how I did : - 1 physical persistence file (ie where to bind data), but this could be a bean - as many definition, binding and template files as the number of pages of the form. Each definition/binding/template batch maps only a portion of the persistence file. - a flow script that manages the flow between pages, with buttons like next, back. Ok, I think I've got the idea now. ;) I'll try if this works for my application, too. thanks Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
