Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

Nicola Ken Barozzi wrote: Of course, slide + Wyona + etc is the final goal Please let's not jump to conclusions ;-) -- Steven Noelshttp://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog athttp://blogs.co

Re: [Q]Non-cacheable Generator

I just notice that the deprecated folder from cvs contains XMLDBGenerator and XMLDBCollectionGenerator. But I never tried out. Anyway, would you suggest how I could fix my generator to non-cached? Thanks. --- Ken C <[EMAIL PROTECTED]> wrote: > Hi, > Having read the "write a custom generator"

[Q]Non-cacheable Generator

Hi, Having read the "write a custom generator" tutorial, I am trying to write one that hooks up a connection to an xmldb -- eXist; and then get an xml back based on a request parameter. Everything seems to work fine for the first time the request is made. Different request parameters on subsequ

Re: XMLForm/Flow Integration

Stefano Mazzocchi wrote: Ugo, "awful" means 'very bad'. I think you meant "awesome" which means "very good". :) Oops ;-). Ugo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

Re: alternative to tomcat?

"Leo Simons" <[EMAIL PROTECTED]> wrote: > http://wiki.cocoondev.org/Wiki.jsp?page=ApacheModProxy > > have got to love you Pier :D Took 2 hours to transfer some of our more > heavily used mod_jk+tomcat servlet apps over to mod_proxy+jetty, and now > processor load dropped from 15% to 2%. It's not

Re: Command line in binary distribution

> >At present, the command line interface is only supported within the > >source distribution. Is there a reason why it is not supported within > >the binary distribution? > > > >If thought useful, I would be willing to have a go at > >creating/porting the scripts across to work with the binary > >

Re: alternative to tomcat?

http://wiki.cocoondev.org/Wiki.jsp?page=ApacheModProxy have got to love you Pier :D Took 2 hours to transfer some of our more heavily used mod_jk+tomcat servlet apps over to mod_proxy+jetty, and now processor load dropped from 15% to 2%. cheers, - Leo Pier Fumagalli wrote: http://www.apache.o

Re: [Flow Samples] Broken Images

"Tony Collen" <[EMAIL PROTECTED]> wrote: > Anyone else seeing broken images for > http://localhost:8080/cocoon/samples/flow/index.html on CVS HEAD? I am... Pier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional co

[Flow Samples] Broken Images

Anyone else seeing broken images for http://localhost:8080/cocoon/samples/flow/index.html on CVS HEAD? Tony - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

Re: Command line in binary distribution

Upayavira wrote: Dear All, At present, the command line interface is only supported within the source distribution. Is there a reason why it is not supported within the binary distribution? If thought useful, I would be willing to have a go at creating/porting the scripts across to work with

Re: SourceFactory instantiated twice

Charles Yates wrote: Hello, I've been working on a custom SourceFactory and was getting some odd behavior suggesting that it was not a singleton (SourceFactory extends ThreadSafe) as expected. I investigated a bit and discovered that 2 were being instantiated. You can see this behavior in

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

Jeff Turner wrote, On 19/02/2003 15.49: ... So there's a half-formed plan over in Forrest-land to migrate to XHTML 2 as an intermediate format, and make it one of the frontend formats too: http://marc.theaimsgroup.com/?l=forrest-dev&m=104351979527689&w=2 Then why not use html (ihtml), there ar

Re: alternative to tomcat?

"Ignacio J. Ortega" <[EMAIL PROTECTED]> wrote: > Pier, > >> >> Actually, on this topic, I have some _shocking_ results after a major >> benchmark session, and a comparison between Tomcat 4.1.18 and >> Jetty 4.2.7... >> I am now rewriting my presentation for NordU >> due >

RE: alternative to tomcat?

Pier, > > Actually, on this topic, I have some _shocking_ results after a major > benchmark session, and a comparison between Tomcat 4.1.18 and > Jetty 4.2.7... > I am now rewriting my presentation for NordU > due > tomorrow. > >

Re: Getting closer to XForms (was: extending XMLForms for different kinds of models...opinions?)

Hello, Konstantin. > ... > Having the model declaration in the sitemap is not a very good idea IMHO. In > a real application there are a lot of forms and each one has its own model. > Having all these declared in the sitemap would make a hybrid monster from > it. > ... I agree. The solution propos

Re: XMLForm/Flow Integration

On Mittwoch, Februar 19, 2003, at 12:12 Uhr, Stefano Mazzocchi wrote: ivelin wrote: Thanks for the good work Chris. I will try to review the code soon. -=Ivelin=- [snipping 72Kb! of stuff] Thank you for taking your time to edit emails to avoid wasting bandwidth. -- Stefano Mazzocchi

Re: xdoc -> wiki documentation (Re: documentation in separate cvs module or block)

On Wed, Feb 19, 2003 at 01:39:56PM +, Pier Fumagalli wrote: > "Jeff Turner" <[EMAIL PROTECTED]> wrote: > > > So I agree with Diana about moving all docs to the Wiki. It seems the > > best long-term solution, avoiding all the problems that a dual wiki/xdoc > > system would cause. > > I disagr

RE: Streaming Transformations for XML (STX) and Cocoon

> [Daniel Fagerstrom] > I have done some initial experiments using STX > (Streaming Transformations for XML see: > http://stx.sourceforge.net/ ) together with > Cocoon and this far it seem to work well. I hope that people interested in STX have a good chance to experiment with it. Hopefully,

Streaming Transformations for XML (STX) and Cocoon

I have done some initial experiments using STX (Streaming Transformations for XML see: http://stx.sourceforge.net/ ) together with Cocoon and this far it seem to work well. STX is similar to XSLT but the transformation rules reacts on events (SAX) instead of matching on a tree model as XSLT. Th

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

"Jeff Turner" <[EMAIL PROTECTED]> wrote: > So I agree with Diana about moving all docs to the Wiki. It seems the > best long-term solution, avoiding all the problems that a dual wiki/xdoc > system would cause. I disagree on that. IMO the "Wiki" syntax doesn't have the capability to contextualize

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

On Wed, 19 Feb 2003, Jeff Turner wrote: > On Wed, Feb 19, 2003 at 03:11:44PM +1100, David Crossley wrote: > > Diana Shannon wrote: > > > > Will people be able to do both ways - traditional patch/create > > xdocs in cvs, or via the Wiki? > > With Chaperon integration, the next version of Forrest s

Re: Chaperon samples in Cocoon

Stephan Michels wrote: > David Crossley wrote: > > On a related issue ... you will notice in the > > chaperon/samples/sitemap.xmap that i needed to use > > the previously generated quote.xlex and quote.xgrm > > I tried to instead use the "cocoon:" protocol for these, > > but this results in a usel

Re: Go with the flow!

Ugo Cei wrote: "The Model-View-Controller 2 (MVC2) pattern is the foundation of Webflow's architecture. Webflow functions mostly as a controller, but it also provides basic model support and includes tag libraries for the view. Unlike most other controller systems, Webflow is more like a workf

Re: XMLForm/Flow Integration

ivelin wrote: Thanks for the good work Chris. I will try to review the code soon. -=Ivelin=- [snipping 72Kb! of stuff] Thank you for taking your time to edit emails to avoid wasting bandwidth. -- Stefano Mazzocchi <[EMAIL PROTECTED]> Pluralitas non est ponenda

Re: XMLForm/Flow Integration

Ugo Cei wrote: Apart from these two minor points, it seems like you've done an awful job! Ugo, "awful" means 'very bad'. I think you meant "awesome" which means "very good". :) I can say this since Ugo and I spent last morning talking IRL exactly about this (what a timing, BTW!) This is go

Re: Writing docs... Where shall I put that?

Pier Fumagalli wrote: I need to write some docs for the HttpProxyGenerator, and was wondering on where I shall put those files... As Stefano is remodeling the build system, would it be better to have it in src/blocks/proxy/doc or in src/documentation/... I tend to believe that it might be b

sporadic occurance of an EmptyStackException ...

Hy, Sometimes i get following exception, when i call my cocoon-app. When i recall the very same URL in general everything is OK. In rare cases the problem vanishes after two retries, but sporadically returns. Did anyone encounter similar problems and possibly has an idea, what i might do wrong ?

DO NOT REPLY [Bug 17127] - [PATCH] I18nTransformer support for multiple catalogues

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

XML Document Editor freely available

Interesting :-): http://www.econtentmag.com/ecxtra/2003/2003_0218/2003_0218_3.html Matthew -- Open Source Group Cocoon { Consulting, Training, Projects } = Matthew Langham, S&N AG, Klingenderstrasse 5, D-33100 Paderborn Tel:+4

Re: XMLForm/Flow Integration

looks very interesting. Once I have time again, hopefully soon ;-), I am looking forward to playing with it. thanks -- Jakob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]

Re: xdoc -> wiki documentation (Re: documentation in separate cvs module or block)

On Wed, Feb 19, 2003 at 09:02:42AM +0100, SAXESS - Hussayn Dabbous wrote: > Hy; Let's move this thread over to cocoon-docs.. --Jeff ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECT

Go with the flow!

"The Model-View-Controller 2 (MVC2) pattern is the foundation of Webflow's architecture. Webflow functions mostly as a controller, but it also provides basic model support and includes tag libraries for the view. Unlike most other controller systems, Webflow is more like a workflow system. It p

Re: xdoc -> wiki documentation (Re: documentation in separate cvsmodule or block)

Hy; The mentioning of "Wiki" triggered my curiousity: If we move all docs to Wiki, then how can we maintain different release versions of the docs ? Or will there be only one single document version, that fits for all released cocoon versions ? Or do you propose to connect Wiki with an underlyi