On 07/24/2013 05:30 PM, Piratenvisier wrote: ... >> Because I am not able to install the whole application because of >> this error. >>> >>>> But I see a strong tendenca to a programmed pipeline and I found >>>> myself even without cocoon on this way. >>> >>> see the pipeline example you can use cocoon-pipeline in you normal >>> spring webapp (without cocoon servlet). >>> > I got a programmed fop-pipeline running. Under wicket you have to > grant access to the stylesheets > und let wicket give you the full href.
Actually you can call a java cocoon pipeline from wicket to do the job for you. ;) ...but seriously there are many fish in the sea and I myself ATM are experiencing node.js which is really rapid in terms of development especially if your gui is using json. Our company has create a framework called rapidMobile where I am ATM testing to serve the static html5 part with creating a node.js server around it, instead of using c3 as we did before. While playing around I found it pretty easy to create basic REST services for node and do some REST services that prior had been in cocoon (maybe re-factored to go into node). What I am trying to say is that cocoon is the best in what it is designed for: being a lib capable of use x input formats and serialize to n output formats. The whole idea for myself is best expressed in Apache Forrest and they concept of input, internal and output modules. Where everything is drilled down to an internal language so it easy to create various input and output formats. >>>>> >>>>> However that seems pretty much as the sample block. >>>>> Try just to start cocoon-rest-optional and do mvn clean install >>>>> jetty:run >>>>> >>>>> I just added a small sample (I consider it quite clean) to use a >>>>> pipeline in your java code. >>>> How should i call the Restcontroller from the browser and what >>>> result should I see ? >>> >>> cd ../cocoon-rest-optional #assuming you were in samples before >>> mvn clean install jetty:run >>> http://localhost:8888/ >>> >>> There are three different showcases, the last two ones are mail >>> samples. Where "Here comes the response from server..." stands we >>> will wait the response. I implement the whole thing with html5 and a >>> bit of javascript to post to the server and update the response div >>> with the server response. In case you have success it will read: >>> "Result: true" while the request is processed you see "Processing >>> request...". In case of result: false check the logs in >>> ./target/work/cocoon.log >>> >>> salu2 > I got your example running, thank you > I aknowledge that cocoon is again getting interesting. yeah :) salu2 -- Thorsten Scherler <scherler.at.gmail.com> codeBusters S.L. - web based systems <consulting, training and solutions> http://www.codebusters.es/
