I've worked with the Cocoon XSP before and now I'm trying out AxKit. I've also had these same problems. The syntax is bulky and very verbose(in a bad way), debugging is a pain because I have no idea what exactly I'll be getting in turms of produced code, and a minor one is that I need to look at the error_log of my apache process to figure out what went wrong (seeing just a Error 500, or whatever isn't very useful). The thing that I noticed about XSP in both of the evironments is that it just throws out a lot of what I knew about programming, because I'm not writing code anymore, I'm writing structure and output(or so it seems).
Anyway, on to what I wanted to mention. Another thing that I've seen(and used) is enhydra xmlc. I think that that was a pretty good solution, not perfect, but better than XSP. Create a template of what a page will look like and mark the dynamic tags with IDs. XMLC converts the entire thing into an object with methods for the various tags. The document is presented to you as a DOM where you can manipulate the tree with the (pretty much) normal DOM interface. I found it really nice to work with and all of the normal programming tools and techniques still worked just fine (no special markup to get in the way). You still can produce valid XML, just have xmlc validate when it compiles the template and then all access it through the DOM interface so you can't change it to be invalid (at least I don't think you can). I think something like that would work great in a system like AxKit. Andrew Parker Fisher, James wrote: > > With respect to goal #2 ... Hmmm. Would a business really use this. Lets > see if I can come up with an example. I am a business who sells some type > of app server that will live on your servers. I decide to use XSP so (at > least today) I can port it to and from AxKit and Cocoon. So I can tell my > clients they can house my app server on a java app server or apache > mod/perl. Is this realistic?! We could still port our app regardless. > Granted, the XSP would save some work. But, does that advantage outweigh > the disadvantages.... > > - More typing > - Harder to debug > - Semi-dynamic pipeline. With one of the perl based method I can write out > at the top of the file whatever pipeline I want. > - Probably slower than one of the perl based methods. (More text to process > eq slower?!) > - Not an official spec so it could change any day?! > > That's all I can think of right now. I am also interested in other > opinions. > > Note: I like everything about AxKit except XSP > > JF > > > > > > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > This footnote also confirms that this email message has been swept by > MIMEsweeper for the presence of computer viruses. > > www.mimesweeper.com > ********************************************************************** > > > --------------------------------------------------------------------- > 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]
