You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@commons.apache.org by Bryan Field-Elliot <br...@netmeme.org> on 2004/01/19 05:34:34 UTC
Strugging to grok Jelly
I'm just diving into Jelly from a coding standpoint...
How exactly do I build a script, which processes input files from
another source? A typical use case would be processing SOAP messages.
All the Jelly sample scripts I can find, seem to combine both executable
script, and the "raw materials" to operate upon, in the same script
file. But this doesn't seem very efficient to me from a processing
standpoint, if I want to run one script against any sort of incoming
SOAP message. I don't want to merge them first, then execute. Or is that
the recommended usage pattern?
I hope this question is clear, sorry if I'm missing the obvious.
Thanks,
Bryan
Re: Strugging to grok Jelly
Posted by Bryan Field-Elliot <br...@netmeme.org>.
On Mon, 2004-01-19 at 01:36, Paul Libbrecht wrote:
> Bryan,
>
>
> How about xml:parse ?
>
> paul
>
Thanks Paul,
It was "seeding" the JellyContext with outside variables (such as a
document received via SOAP), before beginning execution of a
Jellyscript, which I didn't grok at first, but now I get it. And once
it's seeded with a raw document String, xml:parse is the right next
step.
Re: Strugging to grok Jelly
Posted by Paul Libbrecht <pa...@activemath.org>.
Bryan,
How about xml:parse ?
paul
On 19-Jan-04, at 05:34 Uhr, Bryan Field-Elliot wrote:
> I'm just diving into Jelly from a coding standpoint...
>
> How exactly do I build a script, which processes input files from
> another source? A typical use case would be processing SOAP messages.
>
> All the Jelly sample scripts I can find, seem to combine both
> executable
> script, and the "raw materials" to operate upon, in the same script
> file. But this doesn't seem very efficient to me from a processing
> standpoint, if I want to run one script against any sort of incoming
> SOAP message. I don't want to merge them first, then execute. Or is
> that
> the recommended usage pattern?
>
> I hope this question is clear, sorry if I'm missing the obvious.
>
> Thanks,
>
> Bryan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org