You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Xephyrus <xe...@xephyrus.com> on 2003/05/01 21:06:54 UTC
XML as script -or- XML processing engine
Greetings,
Last week I suddenly had a project foisted on me to build a template
engine for munging flat-files of various formats. Oh, and I had 3
days to do it in.
I knew exactly what we needed: something that worked like JSP's in
that we could write beans to perform our custom, proprietary (or
maybe not so much) data-munging tasks and bind them to tags through
configuration.
I thought that must be what XSLT is all about. So I spent half a day
or so trying to figure out how to get XSLT to work with flat files.
I finally decided that you just can't get there from here and went
looking for some other tool to do what I needed.
I did find XML For All (XFA) and XMLScript, but those seem to be
one-off projects rather than community- and standards-oriented
project.
So: Did I miss something? Is there something already in existence or
even in planning that would provide a flexible and definable XML tag
processing engine? If so, details please. If not, is there some
reason not to do that? Is there any interest in doing it?
I apologize if this has already been discussed. The archives have
been down so I wasn't able to troll them before posting this.
Oh, and BTW: I ended up writing my own engine to get by. I used SAX
to do the parsing, implemented a stack for parent-child
relationships, and a history list with replayability for iteration.
It's not the most elegant design, but I was able to get it in place
with the needed tag code to meet the deadline.
. Topher
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: XML as script -or- XML processing engine
Posted by David Crossley <cr...@indexgeo.com.au>.
Another possibility is "Chaperon". We are using that with
Apache Forrest and Apache Cocoon to handle such situations.
http://chaperon.sourceforge.net/
--David
Xephyrus wrote:
>
> Last week I suddenly had a project foisted on me to build a template
> engine for munging flat-files of various formats. Oh, and I had 3
> days to do it in.
<snip/>
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: XML as script -or- XML processing engine
Posted by Xephyrus <xe...@xephyrus.com>.
Jelly jelly.
At a glance that looks exactly like what I'm looking for. Thanks. *(`:
. Topher
> i think that you need some jelly :)
>
> http://jakarta.apache.org/commons/jelly/index.html
>
> - robert
>
> On Thursday, May 1, 2003, at 08:06 PM, Xephyrus wrote:
>
>> Greetings,
>>
>>
>> Last week I suddenly had a project foisted on me to build a template
>> engine for munging flat-files of various formats. Oh, and I had 3
>> days to do it in.
>>
>>
>> I knew exactly what we needed: something that worked like JSP's in
>> that we could write beans to perform our custom, proprietary (or maybe
>> not so much) data-munging tasks and bind them to tags through
>> configuration.
>>
>>
>> I thought that must be what XSLT is all about. So I spent half a day
>> or so trying to figure out how to get XSLT to work with flat files. I
>> finally decided that you just can't get there from here and went
>> looking for some other tool to do what I needed.
>>
>>
>> I did find XML For All (XFA) and XMLScript, but those seem to be
>> one-off projects rather than community- and standards-oriented
>> project.
>>
>>
>> So: Did I miss something? Is there something already in existence or
>> even in planning that would provide a flexible and definable XML tag
>> processing engine? If so, details please. If not, is there some
>> reason not to do that? Is there any interest in doing it?
>>
>>
>> I apologize if this has already been discussed. The archives have
>> been down so I wasn't able to troll them before posting this.
>>
>>
>> Oh, and BTW: I ended up writing my own engine to get by. I used SAX
>> to do the parsing, implemented a stack for parent-child
>> relationships, and a history list with replayability for iteration.
>> It's not the most elegant design, but I was able to get it in place
>> with the needed tag code to meet the deadline.
>>
>>
>> . Topher
>>
>>
>>
>> ---------------------------------------------------------------------
>> In case of troubles, e-mail: webmaster@xml.apache.org
>> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
>> For additional commands, e-mail: general-help@xml.apache.org
>>
>
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail: webmaster@xml.apache.org
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For
> additional commands, e-mail: general-help@xml.apache.org
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: XML as script -or- XML processing engine
Posted by robert burrell donkin <ro...@blueyonder.co.uk>.
i think that you need some jelly :)
http://jakarta.apache.org/commons/jelly/index.html
- robert
On Thursday, May 1, 2003, at 08:06 PM, Xephyrus wrote:
> Greetings,
>
>
> Last week I suddenly had a project foisted on me to build a template
> engine for munging flat-files of various formats. Oh, and I had 3
> days to do it in.
>
>
> I knew exactly what we needed: something that worked like JSP's in
> that we could write beans to perform our custom, proprietary (or
> maybe not so much) data-munging tasks and bind them to tags through
> configuration.
>
>
> I thought that must be what XSLT is all about. So I spent half a day
> or so trying to figure out how to get XSLT to work with flat files.
> I finally decided that you just can't get there from here and went
> looking for some other tool to do what I needed.
>
>
> I did find XML For All (XFA) and XMLScript, but those seem to be
> one-off projects rather than community- and standards-oriented
> project.
>
>
> So: Did I miss something? Is there something already in existence or
> even in planning that would provide a flexible and definable XML tag
> processing engine? If so, details please. If not, is there some
> reason not to do that? Is there any interest in doing it?
>
>
> I apologize if this has already been discussed. The archives have
> been down so I wasn't able to troll them before posting this.
>
>
> Oh, and BTW: I ended up writing my own engine to get by. I used SAX
> to do the parsing, implemented a stack for parent-child
> relationships, and a history list with replayability for iteration.
> It's not the most elegant design, but I was able to get it in place
> with the needed tag code to meet the deadline.
>
>
> . Topher
>
>
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail: webmaster@xml.apache.org
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org