RE: XInclude - optimization/alternatives to

[Axel Honfi]

Hi!

I would first generate the data(featured article) and then format it with
xslt. Another way would be to generate the content-page, then include the
data one time, and then format it with xslt. I have pipelines with up to
four xslt-transformations, because I think that's faster(especially if you
don't use params in the xslt) than multiple queries to a db.

Yes, and you can put xinclude in the content page, take a look at the
Xinclude-transformer.

Best Regards

Axel


-Original Message-
From: Sreedhar Chintalapaty [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 17, 2002 4:07 PM
To: Cocoon Users
Subject: XInclude - optimization/alternatives to


Hi all,

I am using XInclude to process a content page and place the title, author,
and article into different cells in a table.

Content File: featuredArticle.xml

http://apache.org/xsp";
xmlns:xsp-request="http://apache.org/xsp/request/2.0";
xmlns:dbtags=http://gvs/dbtags>

Fall in New Hampshire
The Itinerant Monk

blah-blah-blah
List of Hiking Trails




Style Sheet: formatter.xsl



http://localhost/cocoon/gvs/xsp/{$tab}/{$request-url}#xpointer(//title
)"/>




http://localhost/cocoon/gvs/xsp/{$tab}/{$request-url}#xpointer(//autho
r)"/>




http://localhost/cocoon/gvs/xsp/{$tab}/{$request-url}#xpointer(//artic
le)"/>




This does what I want it to do, but at a cost: The -entire-
featuredArticle.xml is loaded three times, parsed three times and, for the
get-list-of-trails tag, the database is queried three times - you get the
picture.

There must be a better way to do something like this... I would appreciate
any suggestions/advice/pointers...

Thanks, and Best Regards,

Sreedhar Chintalapaty

__
A computer is like an Old Testament god, with a lot of rules and no mercy -
Joseph Campbell


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

RE: XSLT - processing XML from a database field problem

[Axel Honfi]

I have no clue why this happens, but have you tried putting the escaped
stuff into CDATA-braces with the first stylesheet?
I think this should keep the second one from unescaping

Maybe an idea

Axel
-Original Message-
From: Florent Soulière [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 29, 2002 6:03 PM
To: [EMAIL PROTECTED]
Subject: XSLT - processing XML from a database field problem


Hello,

I already passed 2 days trying to solve my problem by myself, but I did not
succeed...
The situation:
I use the SQL Transformer to get data from database. inside this data, there
are fields containing XHTML (e.g. this is bold text). What I want to
do with all the data is to produce a PDF document using FO.
To accomplish such a thing, I use 2 XSL pages: one for "unescaping" the
,  and other XHTML tags into some valid XML-like tags
(, , ...) with . And the
other xsl page does the "big job" by transforming all the document into a FO
document (including the XHTML tags, of course).

The problem:
Even if the unescaping works fine (I checked it by watching the output of
the XSLT transformation of the "unescaping XSL page"), it seems that when I
want to process the ,  & others with a standard
, they automatically come back to a non-escaped form.

What I already tried:
I tried to replace  by a . And I saw
that my XHTML tags were still unescaped, as expected. So I really wonder why
they come back to escaped when applied with apply-templates...
I tried to split the global process into 2 steps: with one pipeline, I get
the unescaped intermediate result, that I store manually into an xml file,
and then with another pipeline I read the intermediate file and push it into
the "big job" XSLT page... And it works!

So, I really would like to know what's wrong with this unescaping and
chained-XSLT stuff... I know that this problems of integrating XML fragments
into Cocoon's pipelines have always been sensitive, although the
documentation have absolutely no care with this.

If anyone can help, thank you in advance.


Florent, Soulière
Stagiaire e-Technologies Lyon
T-Systems Soleri
Groupe Deutsche Telekom
Notre métier: la convergence informatique et télécoms
Convergence is our Business

tél.:+33 4 37 65 24 26
fax:+33 4 37 65 22 31
mail:   [EMAIL PROTECTED]

www.t-systems.fr


-
Please check that your question has not already been answered in the
FAQ before posting. 

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>