Jon Scott Stevens wrote: >on 7/17/02 4:33 PM, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > > > >>+1 - I can't wait to convert my site from JSP (just on principle). >>Though it will be to XML, I'd never lower myself to using just >>PHP of course. And anyhow my objective is to only update data when I >>want to change something. :-) >> >> > >Right now, the site is in XML, but since XML isn't dynamically generated >without using some beast like Cocoon, I'm not even going to bother with >that. > > You do have some options there. You could just println in a servlet. Nasty but hey, PHP and JSPs are basically inverted servlets, which is why they are so ugly. Think what would happen if you turned a dog inside out, it would allow you to modify its inner workings more easily and the changes would take place instantaneously, but the structure and form would look much like a JSP or PHP page. (mmm and I forgot my spoon)
You could cut Cocoon down, Cocoon is only a hog when you load all the stuff that is typically in it. Now the catch is that the Cocoon developers love to talk about tools for documenting things but they don't actually produce any documentation worth speaking of. I assume its because they're all un/secretly writing books. But if you slimmed that down it would probably be quite lean. I may soon generate the documentation on how to do this right after I figure it out. You could use something like velocity and/or turbine, but I hear they're kind of weird and that mostly weird people use them. Then again the installation process for an app based on those is so derned intollerable that upgrading would take longer than developing it from scratch anyhow. You could do a quicky servlet that transformed your XML and served it out, implemented basically the Cocoon sitemap leanly using a property file. There is even an Avalon component that implements an XML property file reader. I hear tomcat has one of those embeded somewhere too. As I'm sure does every other apache framework down deep. Of course, you know all serious web applications are implemented in PERL anyhow. Which is why if one could get close enough to the iternet backbone to smell it, I imagine it would smell like burnt camel hair. (burnt from the dot-bomb) And well Pier's tagline explains perl better than I. ;-) Lastly, you could launch ant on the fly and probably have it do everything for you via an ant build script. In conclusion, except for POI and HTTPD, there really is only one Apache project, its just impelemnted in different ways. :-) -Andy >-jon > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
