xls and/or zip examples? (multiple xml docs)

Are there any examples of outputting multiple xml documents out of exist
into one row per doc in an xls spreadsheets and vice versa importing
same?  Or is that handled automagically?

Has anyone made a processor to collect multiple xml transformations of
exist xml docs into a zipfile?

--



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

HI Mike,

On 2/26/07, Mike Leary <[hidden email]> wrote:
> Are there any examples of outputting multiple xml documents out of exist
> into one row per doc in an xls spreadsheets and vice versa importing
> same?  Or is that handled automagically?

How are you generating the XLS file? Are you thinking here about using
the Excel processors?

> Has anyone made a processor to collect multiple xml transformations of
> exist xml docs into a zipfile?

XML transformations? Are you talking about the eXist database? Could
you please elaborate?

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On Mon, Feb 26, 2007 at 06:11:55PM -0800, Alessandro Vernet wrote:
> How are you generating the XLS file? Are you thinking here about using
> the Excel processors?

Yes, thinking about using the excel processors, but even if it came to
routing through a CSV file with one doc per row, I'm a bit unclear on
the structure of the for-each construct needed to make it happen -- the
examples I've seen seem a bit counter-intuitive.

> XML transformations? Are you talking about the eXist database? Could
> you please elaborate?

I want to output data from the exist database via my oxf app's web
interface.  Data will be in multiple documents (and collections,
probably), but all instances of the same schema.  Getting the docs is
just xquery fun.  One doc per row into an xls/csv file may (or may not)
be relatively neat and tidy.  If, rather, those docs are each being
transformed into other xml documents, I'd want to bundle them up somehow
for a single download of some kind of archive file.



--



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

On 2/26/07, Mike Leary <[hidden email]> wrote:
> Yes, thinking about using the excel processors, but even if it came to
> routing through a CSV file with one doc per row, I'm a bit unclear on
> the structure of the for-each construct needed to make it happen -- the
> examples I've seen seem a bit counter-intuitive.

I would try to generate a CSV first, instead of using the Excel
processors. There are many ways to do this, one being to write a
pipeline that:

1. Runs your query on eXist using the XForms submission processor.
More at http://www.orbeon.com/ops/doc/processors-submission

2. Pipe the output of the XForms submission processor into a
stylesheet that generates the CSV file. The stylesheet will generate a
document with just one root element <document xsi:type="xs:string"
content-type="text/plain"> that contains text.

3. Use the HTTP serializer in text mode to send back the data. More at
http://www.orbeon.com/ops/doc/processors-serializers-http#text-mode

> I want to output data from the exist database via my oxf app's web
> interface.  Data will be in multiple documents (and collections,
> probably), but all instances of the same schema.  Getting the docs is
> just xquery fun.  One doc per row into an xls/csv file may (or may not)
> be relatively neat and tidy.  If, rather, those docs are each being
> transformed into other xml documents, I'd want to bundle them up somehow
> for a single download of some kind of archive file.

You could do this is a pipeline: iterate over the queries with
p:for-each and in each iteration save a file in a temporary directory
with the file serializer. Then you will need to write your own
processor or use the Java processor to zip up the content of that
directory.

This is fairly high level, but I hope it helps,

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws