You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Jeff Sexton <js...@odshp.com> on 2003/08/20 01:29:30 UTC

XML-Based Reporting Application, Design?

We'd like to built an application that uses data from a database to create
XML, which can be transformed to various forms.  A significant amount of
coding will be required to create the XML (otherwise I'd just place SQL in
an xsp), so I think a separate servlet will make more sense.  My thought
is to create a servlet that outputs type text/xml, call the servlet from a
sitemap, transform and serialize as needed.

This leads to some specific design questions...

1) Best why to build an XML document in the servlet?  JDOM?

2) Is there a better way to tie together the cocoon pipeline with the
data source than having a URL called in the sitemap?  Afterall it will
all be running under the same Tomcat...

We're very happy with the way Cocoon has worked for other, simpler
applications.  But for this one we perhaps should look at more advanced
features.  And we have not done any significant amout of XML generation
from java, so I'd like to hear some about how others are doing this.

Thanks!

-----
The ODS Companies
Jeff Sexton
Information Services
(503) 228-6554   x1024
http://www.odscompanies.com

This message is intended for the sole use of the individual and entity
to whom it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are
not the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose
or distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email and delete the message.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Jeff,

You might consider writing an avalon component and wrapping it in a 
Generator.  An avalon component is really "plain ol' programming" with 
some restraints, and can be used outside of cocoon.  You could decide 
exactly what functionality you want to be reusable and what you want to 
put in Cocoon, and draw the line there.  For example, your component 
could generate SAX events and the generator could be a thin delegation 
layer.  Or, your component could expose data classes and the Generator 
could do the translation to SAX. (I suggest jakarta commons betwixt for 
that).

I recently did this on a small scale for my first flowscript 
application, and could give more details in response to some specific 
questions :)

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net

Jeff Sexton wrote:

>On Tue, 19 Aug 2003, Geoff Howard wrote:
>  
>
>>Jeff Sexton wrote:
>>    
>>
>>>We'd like to built an application that uses data from a database to create
>>>XML, which can be transformed to various forms.  A significant amount of
>>>coding will be required to create the XML (otherwise I'd just place SQL in
>>>an xsp), so I think a separate servlet will make more sense.  My thought
>>>is to create a servlet that outputs type text/xml, call the servlet from a
>>>sitemap, transform and serialize as needed.
>>>      
>>>
>>I don't quite get why you came to the conclusion that a servlet is
>>better for serious coding than the Cocoon environment.  IMHO you should
>>back up and reconsider that.
>>    
>>
>
>Ok, I will.  And I'll take a look at your tutorial.
>
>There are two reasons that I lean toward a servlet (but I don't feel real
>sure about it, which is why I posted the question).  One is that in
>several of the cases we have to build there will be a fair amount of
>business logic actually coded out.  Others are simpler - just dump the
>data from the database.  But some are going to need plain ol'programming.
>These will be replacing some moderatly complicated C++ programs that
>contain calculations and a lot of condition logic that is not reflected in
>the data source.
>
>The other reason it that if it's all coded in a servlet (or other stand
>alone chunk of java), then it could potentially have a life outside of
>cocoon.  Don't get me wrong, I love Cocoon and plan to use it, but by
>not commiting the XML data source to a cocoon world we might gain some
>handy flexibility, and allow any old java programmer to work on it with
>learning a thing about Cocoon.  Or allowing the code to run in an agent or
>grid environment, as a web service, or as a setand-alone application.
>
>Again I don't feel really strongly about either of these reasons, and
>nothing is cast in stone yet.
>
>Thanks for the helpful feedback!
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Jeff Sexton <js...@odshp.com>.
On Thu, 21 Aug 2003, Andrew Timberlake wrote:
> Just to drop an idea. If you are considering using servlets to abstract
> your business logic from Cocoon, why are you constraining it to servlets.
> Why not create standalone objects which handle the business logic and
> then you can call them from Cocoon, Servlets, Applets, Applications...
> Then you achieve the objectives you're looking for and have to write a
> simple Generator to integrate into Cocoon.

Yes, this is what I realized yesterday after reading the various posts
here and looking into the various tools.  In all reality, I would have
done it that way anyway, when it came down to specific coding.  But I
quickly realized that the various APIs and tools can all easily use
general objects.  We could easily construct everything from simple
servlets to web services to grids.

What a wonderful world!


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Andrew Timberlake <an...@ddd.co.za>.
Jeff

Just to drop an idea. If you are considering using servlets to abstract
your business logic from Cocoon, why are you constraining it to servlets.
Why not create standalone objects which handle the business logic and
then you can call them from Cocoon, Servlets, Applets, Applications...
Then you achieve the objectives you're looking for and have to write a
simple Generator to integrate into Cocoon.

Andrew

Jeff Sexton wrote:
> On Tue, 19 Aug 2003, Geoff Howard wrote:
> 
>>Jeff Sexton wrote:
>>
>>>We'd like to built an application that uses data from a database to create
>>>XML, which can be transformed to various forms.  A significant amount of
>>>coding will be required to create the XML (otherwise I'd just place SQL in
>>>an xsp), so I think a separate servlet will make more sense.  My thought
>>>is to create a servlet that outputs type text/xml, call the servlet from a
>>>sitemap, transform and serialize as needed.
>>
>>I don't quite get why you came to the conclusion that a servlet is
>>better for serious coding than the Cocoon environment.  IMHO you should
>>back up and reconsider that.
> 
> 
> Ok, I will.  And I'll take a look at your tutorial.
> 
> There are two reasons that I lean toward a servlet (but I don't feel real
> sure about it, which is why I posted the question).  One is that in
> several of the cases we have to build there will be a fair amount of
> business logic actually coded out.  Others are simpler - just dump the
> data from the database.  But some are going to need plain ol'programming.
> These will be replacing some moderatly complicated C++ programs that
> contain calculations and a lot of condition logic that is not reflected in
> the data source.
> 
> The other reason it that if it's all coded in a servlet (or other stand
> alone chunk of java), then it could potentially have a life outside of
> cocoon.  Don't get me wrong, I love Cocoon and plan to use it, but by
> not commiting the XML data source to a cocoon world we might gain some
> handy flexibility, and allow any old java programmer to work on it with
> learning a thing about Cocoon.  Or allowing the code to run in an agent or
> grid environment, as a web service, or as a setand-alone application.
> 
> Again I don't feel really strongly about either of these reasons, and
> nothing is cast in stone yet.
> 
> Thanks for the helpful feedback!
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Geoff Howard <co...@leverageweb.com>.
Jeff Sexton wrote:
> On Tue, 19 Aug 2003, Geoff Howard wrote:
> 
>>Jeff Sexton wrote:
>>
>>>We'd like to built an application that uses data from a database to create
>>>XML, which can be transformed to various forms.  A significant amount of
>>>coding will be required to create the XML (otherwise I'd just place SQL in
>>>an xsp), so I think a separate servlet will make more sense.  My thought
>>>is to create a servlet that outputs type text/xml, call the servlet from a
>>>sitemap, transform and serialize as needed.
>>
>>I don't quite get why you came to the conclusion that a servlet is
>>better for serious coding than the Cocoon environment.  IMHO you should
>>back up and reconsider that.
> 
> 
> Ok, I will.  And I'll take a look at your tutorial.
> 
> There are two reasons that I lean toward a servlet (but I don't feel real
> sure about it, which is why I posted the question).  One is that in
> several of the cases we have to build there will be a fair amount of
> business logic actually coded out.  Others are simpler - just dump the
> data from the database.  But some are going to need plain ol'programming.
> These will be replacing some moderatly complicated C++ programs that
> contain calculations and a lot of condition logic that is not reflected in
> the data source.
> 
> The other reason it that if it's all coded in a servlet (or other stand
> alone chunk of java), then it could potentially have a life outside of
> cocoon.  Don't get me wrong, I love Cocoon and plan to use it, but by
> not commiting the XML data source to a cocoon world we might gain some
> handy flexibility, and allow any old java programmer to work on it with
> learning a thing about Cocoon.  Or allowing the code to run in an agent or
> grid environment, as a web service, or as a setand-alone application.
> 
> Again I don't feel really strongly about either of these reasons, and
> nothing is cast in stone yet.

Gotcha.  Ok, then my advice stands: I'd suggest writing some supporting 
classes which contain most of your heavy lifting, and call those from a 
Generator which handles the mandatory Cocoon-specific methods.  Cocoon 
generators are very simple if you already know java and SAX, especially 
if you have the critical logic factored out into your supporting classes.

Geoff



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Geoff Howard <co...@leverageweb.com>.
Jeff Sexton wrote:
>>On Tue, 19 Aug 2003, Geoff Howard wrote:
>>
>>>I don't quite get why you came to the conclusion that a servlet is
>>>better for serious coding than the Cocoon environment.  IMHO you should
>>>back up and reconsider that.
> 
> Oh, and a third reason is that we plan to create the XML off-line as a
> batch operation with pre-defined parameters, in addition to on-demand with
> ad-hoc parameters.

Except that this ties you more to Cocoon, you may want to look into the 
command line mode of Cocoon for this.  There are some improvements in 
2.1 to this that I think would make this a piece of cake to implement no 
matter how you structure your code.

Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Jeff Sexton <js...@odshp.com>.
> On Tue, 19 Aug 2003, Geoff Howard wrote:
> > I don't quite get why you came to the conclusion that a servlet is
> > better for serious coding than the Cocoon environment.  IMHO you should
> > back up and reconsider that.

Oh, and a third reason is that we plan to create the XML off-line as a
batch operation with pre-defined parameters, in addition to on-demand with
ad-hoc parameters.

Thanks!



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Jeff Sexton <js...@odshp.com>.
On Tue, 19 Aug 2003, Geoff Howard wrote:
> Jeff Sexton wrote:
> > We'd like to built an application that uses data from a database to create
> > XML, which can be transformed to various forms.  A significant amount of
> > coding will be required to create the XML (otherwise I'd just place SQL in
> > an xsp), so I think a separate servlet will make more sense.  My thought
> > is to create a servlet that outputs type text/xml, call the servlet from a
> > sitemap, transform and serialize as needed.
>
> I don't quite get why you came to the conclusion that a servlet is
> better for serious coding than the Cocoon environment.  IMHO you should
> back up and reconsider that.

Ok, I will.  And I'll take a look at your tutorial.

There are two reasons that I lean toward a servlet (but I don't feel real
sure about it, which is why I posted the question).  One is that in
several of the cases we have to build there will be a fair amount of
business logic actually coded out.  Others are simpler - just dump the
data from the database.  But some are going to need plain ol'programming.
These will be replacing some moderatly complicated C++ programs that
contain calculations and a lot of condition logic that is not reflected in
the data source.

The other reason it that if it's all coded in a servlet (or other stand
alone chunk of java), then it could potentially have a life outside of
cocoon.  Don't get me wrong, I love Cocoon and plan to use it, but by
not commiting the XML data source to a cocoon world we might gain some
handy flexibility, and allow any old java programmer to work on it with
learning a thing about Cocoon.  Or allowing the code to run in an agent or
grid environment, as a web service, or as a setand-alone application.

Again I don't feel really strongly about either of these reasons, and
nothing is cast in stone yet.

Thanks for the helpful feedback!



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Geoff Howard <co...@leverageweb.com>.
Jeff Sexton wrote:
> We'd like to built an application that uses data from a database to create
> XML, which can be transformed to various forms.  A significant amount of
> coding will be required to create the XML (otherwise I'd just place SQL in
> an xsp), so I think a separate servlet will make more sense.  My thought
> is to create a servlet that outputs type text/xml, call the servlet from a
> sitemap, transform and serialize as needed.

I don't quite get why you came to the conclusion that a servlet is 
better for serious coding than the Cocoon environment.  IMHO you should 
back up and reconsider that.  If the xml is going to go through Cocoon, 
I really don't think you have a better option than writing your own 
Generator, whether you do that through XSP or directly as a Generator 
doesn't matter.  Programming in raw SAX is not as simple as JDOM but if 
you have a large dataset or are otherwise performance sensitive, you 
want to go straight to SAX, not JDOM/DOM and not string (which is 
probably your only option with Servlet apart from sticking a DOM in the 
session).  I wrote a tutorial on custom Generators for the Cocoon docs 
that is still fairly recent and should be a good head start though it's 
not perfect.

Can you explain by the way why so much coding is required to get from 
the ResultSet(s) to xml?

Geoff Howard


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Jeff Sexton <js...@odshp.com>.
On Wed, 20 Aug 2003, Steven Noels wrote:
> Pardon my ignorance for your particular use case, but did you look at
> xReporter?

Nope, but I will now.  Thanks, this is all good information!

> It's available from http://xreporter.cocoondev.org/, and it
> seems like it addresses most of the things you are looking after.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Steven Noels <st...@outerthought.org>.
Jeff Sexton wrote:

> We'd like to built an application that uses data from a database to create
> XML, which can be transformed to various forms.  A significant amount of
> coding will be required to create the XML (otherwise I'd just place SQL in
> an xsp), so I think a separate servlet will make more sense.  My thought
> is to create a servlet that outputs type text/xml, call the servlet from a
> sitemap, transform and serialize as needed.

Pardon my ignorance for your particular use case, but did you look at 
xReporter? It's available from http://xreporter.cocoondev.org/, and it 
seems like it addresses most of the things you are looking after.

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Steven Noels <st...@outerthought.org>.
Michael Vennera wrote:

> - If your report includes any grouping, order your SQL
> query by those fields. That way you can use an
> <xsl:for-each> and compare each row to the previous
> one to determine when you have a new value. (Much
> simpler than the Meunch method)

Some time ago, we isolated the functionality of the grouping support in 
xReporter in a separate component: 
http://xreporter.cocoondev.org/subprojects/groupingtransformer.html

HTH,

</Steven>
-- 
Steven Noels                            http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at            http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org                stevenn at apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Re: XML-Based Reporting Application, Design?

Posted by Geoff Howard <co...@leverageweb.com>.
Michael Vennera wrote:
> I've also built a reporting app using Cocoon, using
> XSP to pull back the data from Oracle and then
> transforming it into either a PDF report or a CSV
> file. A couple of tips from my experience:
> 
> - If your report includes any grouping, order your SQL
> query by those fields. That way you can use an
> <xsl:for-each> and compare each row to the previous
> one to determine when you have a new value. (Much
> simpler than the Meunch method)

I agree that you'll probably want to avoid Meunchian
grouping but I'd go a step further and suggest doing
your grouping in the generator if at all possible.
That may sound like heresy to some, but it depends
how you look at your problem, and what changes in
grouping need to happen.

The esql grouping logic (should be in ESQLHelper.java
or something) would be a great place to start.  I've
felt that would be great to refactor out into a more
usable library, which would allow a simple SQLGenerator
with grouping for cases where you don't need to manipulate
the data very much and just want to mimic relational data
in xml.

If someone provided a patch along those lines it'd be well
received (at least by me!).

Geoff


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


RE: XML-Based Reporting Application, Design?

Posted by Michael Vennera <mi...@yahoo.com>.
I've also built a reporting app using Cocoon, using
XSP to pull back the data from Oracle and then
transforming it into either a PDF report or a CSV
file. A couple of tips from my experience:

- If your report includes any grouping, order your SQL
query by those fields. That way you can use an
<xsl:for-each> and compare each row to the previous
one to determine when you have a new value. (Much
simpler than the Meunch method)

- Rather than using svg, you can create a simple
histogram by setting the height attribute of a series
of bar images imported via <fo:external-graphic>

- If your reports are large, there are a couple of
things you can do to improve efficiency: (1) use
XSLTC, (2) keep the XML generated by the XSP as lean
as possible, (3) keep your XSL-FO as small as possible
by placing formatting attributes as "high-up" in the
element hierarchy as possible.

Hope this helps,

Mike
mike_vennera@yahoo.com

--- Scott Warren <sc...@ocom.com.au> wrote:
> I have done something very similar. I used XSP to
> generate a "document"
> then used various stylesheets to output html, xls
> etc. This worked very
> well. I didn't use anything other than Cocoon to get
> the data. It's fast
> and the very flexiable. A PDF output would be great
> but time/money
> stopped us from doing that. Also there is talk in
> the future of having
> Graphs in the reports later on.
> 
> Regards
>  
>  
> Scott Warren
> Ocom Software
> ... Exceeding Quality.....
> email | mailto:scottw@ocom.com.au
> web | ocom.com.au
>  
> 
> -----Original Message-----
> From: Jeff Sexton [mailto:jsexton@odshp.com] 
> Sent: Wednesday, 20 August 2003 9:30 AM
> To: users@cocoon.apache.org
> Subject: XML-Based Reporting Application, Design?
> 
> 
> We'd like to built an application that uses data
> from a database to
> create
> XML, which can be transformed to various forms.  A
> significant amount of
> coding will be required to create the XML (otherwise
> I'd just place SQL
> in
> an xsp), so I think a separate servlet will make
> more sense.  My thought
> is to create a servlet that outputs type text/xml,
> call the servlet from
> a
> sitemap, transform and serialize as needed.
> 
> This leads to some specific design questions...
> 
> 1) Best why to build an XML document in the servlet?
>  JDOM?
> 
> 2) Is there a better way to tie together the cocoon
> pipeline with the
> data source than having a URL called in the sitemap?
>  Afterall it will
> all be running under the same Tomcat...
> 
> We're very happy with the way Cocoon has worked for
> other, simpler
> applications.  But for this one we perhaps should
> look at more advanced
> features.  And we have not done any significant
> amout of XML generation
> from java, so I'd like to hear some about how others
> are doing this.
> 
> Thanks!
> 
> -----
> The ODS Companies
> Jeff Sexton
> Information Services
> (503) 228-6554   x1024
> http://www.odscompanies.com
> 
> This message is intended for the sole use of the
> individual and entity
> to whom it is addressed, and may contain information
> that is privileged,
> confidential and exempt from disclosure under
> applicable law. If you are
> not the intended addressee, nor authorized to
> receive for the intended
> addressee, you are hereby notified that you may not
> use, copy, disclose
> or distribute to anyone the message or any
> information contained in the
> message. If you have received this message in error,
> please immediately
> advise the sender by reply email and delete the
> message.
> 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
> 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


RE: XML-Based Reporting Application, Design?

Posted by Scott Warren <sc...@ocom.com.au>.
I have done something very similar. I used XSP to generate a "document"
then used various stylesheets to output html, xls etc. This worked very
well. I didn't use anything other than Cocoon to get the data. It's fast
and the very flexiable. A PDF output would be great but time/money
stopped us from doing that. Also there is talk in the future of having
Graphs in the reports later on.

Regards
 
 
Scott Warren
Ocom Software
... Exceeding Quality.....
email | mailto:scottw@ocom.com.au
web | ocom.com.au
 

-----Original Message-----
From: Jeff Sexton [mailto:jsexton@odshp.com] 
Sent: Wednesday, 20 August 2003 9:30 AM
To: users@cocoon.apache.org
Subject: XML-Based Reporting Application, Design?


We'd like to built an application that uses data from a database to
create
XML, which can be transformed to various forms.  A significant amount of
coding will be required to create the XML (otherwise I'd just place SQL
in
an xsp), so I think a separate servlet will make more sense.  My thought
is to create a servlet that outputs type text/xml, call the servlet from
a
sitemap, transform and serialize as needed.

This leads to some specific design questions...

1) Best why to build an XML document in the servlet?  JDOM?

2) Is there a better way to tie together the cocoon pipeline with the
data source than having a URL called in the sitemap?  Afterall it will
all be running under the same Tomcat...

We're very happy with the way Cocoon has worked for other, simpler
applications.  But for this one we perhaps should look at more advanced
features.  And we have not done any significant amout of XML generation
from java, so I'd like to hear some about how others are doing this.

Thanks!

-----
The ODS Companies
Jeff Sexton
Information Services
(503) 228-6554   x1024
http://www.odscompanies.com

This message is intended for the sole use of the individual and entity
to whom it is addressed, and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If you are
not the intended addressee, nor authorized to receive for the intended
addressee, you are hereby notified that you may not use, copy, disclose
or distribute to anyone the message or any information contained in the
message. If you have received this message in error, please immediately
advise the sender by reply email and delete the message.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org