cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luke Studley <Luke.Stud...@cerillion.com>
Subject RE: Inserting / Comining XML data
Date Thu, 06 Dec 2001 08:51:00 GMT
True enough. Concede the point.

But my original stylesheets and logic ran in a standalone application and
didn't need to call a servlet via http. Also you might struggle to access
local beans, files etc using http unless your servlet container is running
in process.

I guess we agree that this is possible - whether through your http/servlet
requests or my own fantastical made up uris - but the question I am
interested in is whether you think this is a good way of structuring things,
i.e. "style your page (or result fragment) and pull in the pieces" you need
as opposed to the more traditional cocoon way of "assemble all the things
you need and then style it"

I've only been using C2 for a few days - but this is the biggest hurdle I've
had to overcome in porting my original stylesheets. Just trying to figure
out if there is a more "Cocoon Way" for doing what I'm trying to do or
whether I spend the effort to delve into C2 and get my method working within
cocoon.

Thanks for response though.

Luke


-----Original Message-----
From: Kirk Woerner [mailto:kirk@stoneseeker.com] 
Sent: 06 December 2001 02:22
To: cocoon-users@xml.apache.org
Subject: RE: Inserting / Comining XML data 

<<>>

Hey,

I've been following this discussion.  This is not rambling, the concept
works.  I've done it before using http:  That is, created a URIHandler or
something similar, but then wrapped it in a servlet and made sort of an XML
XPath requester that loads stuff from a database.  However, I think Robs
point is that pretty most anything you'd want to do with a URIResolver
class, you could also do with http: (i.e. a servlet)  So the calls might be

http://localhost:8082/serve/catalog/cars/*
http://localhost:8082/serve/sales/invoices/0002332

(I think you could probably even get the "http:localhost/serv" put somewhere
else so they would have to know that, but I'm not sure how...)

The XSL processor would then go get it if you used "document()".  And that's
a problem with the way you're viewing it I think.  The "document()" function
is part of the XSL processing (Xalan), not part of cocoon as far as I can
tell.  Now, you might be able to add stuff to Xalan, but then your XSL would
be tied to it.

Unless you're talking about in the sitemap.xmap file.  This get XSLTed down
to java, compiled, and run so presumedly it's handled a different way.


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Mime
View raw message