No... Not yet anyway! Ideally, barebones, I'm just looking for a way to instantiate the rendering engine in a main method. I know there's infinite flexibility when the http client/container are included, but I'd rather leave them out of it.
I know this isn't a practical application for Tapestry, but it does have the capability... -----Original Message----- From: Fernando Padilla [mailto:[EMAIL PROTECTED] Sent: Friday, February 29, 2008 11:56 AM To: Tapestry users Subject: Re: T5: File generation The question I have is on what could you mean by "generate files". If you can just have an job to hit a particular url, then you can use tapestry to generate that url. If you want tapestry to programmatically generate a page, that is conceptually possible, and I think I saw some code floating around, but I've not done it, and it's not generally used. You can also have a component capture the output of it's rendering and have it do whatever it wants with that. For example, I have a Buffer component that caches the output and puts it in memcached. You could have a component that dumps its output to a file (but it would still require an outside process to hit a url to generate the page to have the component generate itself).. Have I confused you enough yet? Joel Wiegman wrote: > Hello all, > > Our application has the need to generate files. > > I'm interested in trying to use Tapestry to do this since we're > already using T5 on the presentation layer. > > Has anyone extracted the Tapestry templating engine to do other > processing? Something like the pseudo-code below: > > // BEGIN > > @Inject > ComponentRenderer cr; > > MyComponent component = new MyComponent(); component.setName("Test"); > > OutputStream os = cr.render(component); > > // END > > Can anyone point me to the right package/class to look at for > something like this? > > Thanks! > > Joel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
