RE: Reference to a servlet in sitemap
I added a HOW-TO about this to the Cocoon Wiki a while back. Here's the reference: http://outerthought.net/wiki/Wiki.jsp?page=IntegrateAServlet It was based on some conversations in this mailing list. Hope it helps, L. -Original Message- From: Mauro Daniel Ardolino [mailto:mauro;altersoft.com.ar] Sent: 07 November 2002 14:59 To: [EMAIL PROTECTED] Subject: Reference to a servlet in sitemap Hi! I have tried to reference a servlet in sitemap without success. I searched in the web and in the mails an haven't found an answer. I have to program a servlet (e.g. a simple servlet that throws a html). So I configured the servlet in the web.xml file. Then, because I'm using cocoon, I have to configure a match in the sitemap. I do not know how to do it. I've tried everything. Help please! Thanks. Mauro -- Ing.Mauro Daniel Ardolino Departamento de Desarrollo y Servicios Altersoft Billinghurst 1599 - Piso 9 C1425DTE - Capital Federal Tel/Fax: 4821-3376 / 4822-8759 mailto: [EMAIL PROTECTED] website: http://www.altersoft.com.ar - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Poor performance of document() in XSL [Was: Re: simpel cocoon question]
A naive implementation of the document() function is likely
to do this. However happily, by implementing the
javax.xml.transform.URIResolver interface [1], and setting
this on the Tranformer using setURIResolver [2] you can easily
plug in a simple cache (e.g. hash of URL versus retrieved content)
that avoid multiple network overheads.
I have a sample implementation and simple test harness
if anyone wants it.
Cheers,
L.
[1]. http://java.sun.com/j2se/1.4/docs/api/javax/xml/transform/URIResolver.html
[2].
http://java.sun.com/j2se/1.4/docs/api/javax/xml/transform/Transformer.html#setURIResolver(javax.xml.
transform.URIResolver)
-Original Message-
From: Ilya A. Kriveshko [mailto:ilya;kaon.com]
Sent: 05 November 2002 14:33
To: [EMAIL PROTECTED]
Subject: Poor performance of document() in XSL [Was: Re: simpel cocoon
question]
SAXESS - Hussayn Dabbous wrote:
snip/
But you also could do it directly within the xslt context:
You can use the document() function in your XSLT-file.
This function allows you to refer to data contained within
another XML-file. This is completely decoupled from cocoon
though. It's more about how to work with XSLT:
snip/
In the past I have encountered a nasty performance problem with document().
For example, when you declare an xsl variable that gets its value from a
document(),
and then use its value several times throughout the stylesheet, the URI
of the document
gets hist as many times as there are references to that variable. I.e.
the xsl variable
does not store the XML fragment it was given at the variable definition
time, but
merely stores the XPath string and then resolves it every time it's
referenced.
This may or may not be true for XPath expressions that do not contain
document()
as well. Does anyone know for sure?
Example:
xsl:variable name=test-me
select=document('cocoon:/gimme-sumthn')/sumthn/in/@there/
xsl:template match=/
this-is-just-a-test
xsl:value-of select=$test-me/
xsl:value-of select=$test-me/
xsl:value-of select=$test-me/
/this-is-just-a-test
/xsl:template
When using Xalan, this example will cause the Cocoon pipeline that
is responsible for gimme-sumthn to be hit three times. I say,
document() is good for rapid prototyping, but is a poor choice for final
deployment for performance reasons. Use aggregation instead.
+2c
--
Ilya
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cocoon and EJB
I'd originally planned to do some work with Cocoon and EJB, but didn't get very far. I was going to use Cocoon as an alternate presentation layer for my J2EE application and was therefore planning to integrate them by writing XSP pages (with helper classes and logicsheets for each EJB) to talk to the bean, and then use pipelines for all the downstream processing. /ducks head back under workload. Cheers, L. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is it a good idea to avoid the use of xsp ?
If you strictly enforce that your XSP pages don't contain Java code, and only use custom tags (Logicsheets) then you don't necessarily have a problem. Your efforts here should focus on creating a useful set of Logicsheets, but ones that have a declarative approach, rather than ending up with a series of procedural statements. The alternative approach is to rely more heavily on your pipeline components (Actions and Transformers). You're unlikely to use XSP pages here, but may have them in limited form, e.g. to parameterise your XML generation to add information from the request/session/etc. Often here the XML you're feeding into the pipeline provides cues to the downstream components. See the SQLTransformer for example. I think the best advice Iwould give at the moment is to choose ONE of these approaches rather than a mix-and-match situation. If you do then your application is partly specified in the sitemap (pipeline structures) and partly in XSP pages (XML + Logicsheets) which isn't nice for maintainance: everything isn't in a single place. The interesting aspect to all this is that if you look a bit closer they're actually equivalent: When an XSP page is transformed into Java code, Cocoon determines the correct logic sheet transform to apply for each of your tags. This is repeated until all thats left are XSP elements. At that point the final transformation is carried out to generate Java code. This is then compiled and execute. So you have a process which: determines the code required for this task, then executes it. When a Pipeline is triggered in the pipeline, Cocoon builds up the Pipeline components (perhaps affected by various Actions along the way). Once the pipeline is built its then executed. So a useful question to ask is: which approach give you the most flexibility? The advantages of putting things in the sitemap is that you're beginning to approach the "Holy Grail" of computing: component based development. Throw together a few pipeline components and you've got an application. Fantastic. But, personally (and this is probably Cocoon heresy!), I think that once you start introducing fairly specific Actions and Transformers -- i.e. ones that have limited reuse, or may be used only in one pipeline -- you're possibly going down the wrong path: there's little value in having these as components other than Java code, particularly because the sitemap gets so complicated that its difficult to see whats going on. So far I've tended to use the sitemap for only doing the association between requests/processing/response rather than defining the processing steps. I'd be interested in what others think. L. -Original Message-From: Gernot Koller [mailto:[EMAIL PROTECTED]]Sent: 12 September 2002 13:49To: [EMAIL PROTECTED]Subject: Is it a good idea to avoid the use of xsp ? Hi! First, thanks for your very quick replies to my last question! After quite some time discussing and evaluating we made a decision in favor of cocoon as presentation framework. One major argument for cocoon and against struts was that in jsp a strict seperation of logic (Java code) and presentation is not always encouraged. Therewas also fear that the same issues might apply to xsp and therefore the decision was made to use cocoon but to avoid the use of xsp. I'm very new to cocoon and by now only have a very vague idea about xsp and issues that might arise using xsp. So what do you think ? Is it a bad idea to use cocoon but not use xsp ? Is it generally possible to compare jsp and xsp in that way? Or are these fears inappropiate? thanks, Gernot --DI Gernot Kollermailto:[EMAIL PROTECTED]phone:+43-676-340 55 52 Do you Yahoo!?Yahoo! News - Today's headlines
RE: Getting started with initial sitemap
http://outerthought.net/wiki/Wiki.jsp?page=MinimalSitemapConfiguration Cheers, L. -Original Message-From: Gernot Koller [mailto:[EMAIL PROTECTED]]Sent: 11 September 2002 16:14To: [EMAIL PROTECTED]Subject: Getting started with initial sitemap Hi! I'm very new to cocoon and this is probably a very "newbie" sort of question.. I installed cocoon as described and have the demo running. Most of the samples work but not all do. I'm not sure, but it seems to me not all samples are supposed to run out of the box as some depend on data sources which definitly don't exist on my system. Anyway, as I'm trying to figure out how all these things are fitting together, I find the demo sitemap containing all these samples way too complicated. I tried to throw out all unnecessary stuff leaving only the most simple hello world sample, but actually failed to do so. So there is my question: How does a minimal sitemap look like ? Or, is there a "empty.war" file which I can import, that only contains the necessary base to begin with ? Also listing the WEB-INF/lib directory of the demo brings millions of jar files wich I can't belive being necessary for a most simple hello world sample. Removing one after each other on a trial and error basis is quite a pain... Can someone of you gurus point my nose to where I can find this sort of info ? thanks! gernot. Yahoo! - We Remember9-11: A tribute to the more than 3,000 lives lost
Problems with my Cocoon database tutorial
Hi all, I'd like to apologise for an error thats crept into my tutorial Cocoon 2: Build database-driven sites on IBM developerWorks thats obviously burnt a number of folks. In the text I've incorrectly shown esql:pool as a child of esql:execute-query rather than esql:connection. The correct structure is, of course: esql:connection esql:pool.../esql:pool esql:execute-query/ esql:query/ esql:connection/ Unfortunately I don't have direct access to the developerWorks website myself, but have contacted them to ask for corrections to be made. Apologies again for causing some of you difficulties and much head scratching. Thanks to Alan Hodgkinson, Wayne Brandes and Pieter Masereeuw for mailing me to point out the problem and suggest fixes. Cheers, L. -- Leigh Dodds Weblog: http://weblogs.userland.com/eclectic Home: http://www.ldodds.com Current Project: http://outerthought.net/wiki/Wiki.jsp Pluralitas non est ponenda sine necessitate -- William of Ockham - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problems with my Cocoon database tutorial
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 06 September 2002 12:42 To: [EMAIL PROTECTED] Subject: Re: Problems with my Cocoon database tutorial ... Apologies again for causing some of you difficulties and much head scratching. To make the punishment fit the crime: how about writing some more tutorials. :) Any suggestions? I've been stuffing bits and pieces into the Cocoon Wiki recently [1] whenever I get time. There's a wishlist there [2] you can put suggestions in. I plan to start doing more stuff on Cocoon -- I'm particularly interested in Cocoon related 'design patterns' or best practices, but would need some help from others to compile this -- a range of experiences is always best for those. L. [1]. http://outerthought.net/wiki/Wiki.jsp [2]. http://outerthought.net/wiki/Wiki.jsp?page=Wishlist - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Relax NG validation for Cocoon
- also relaxng has no way for docs to identify schema, any ideas? In my experiments, Jing is told on the command-line which *.rng to use against a particular doc.xml, i.e. the declaration is external to the xml instance. Thats by design. James Clark purposefully decided that identifying how a schema gets associated with an instance document is outside the scope of RELAX NG. So its up to the implementation. This actually makes a lot of sense, because if you think it through there are many different ways in which one might want to associate a schema with a particular document. Cheers, L. -- Leigh Dodds Weblog: http://weblogs.userland.com/eclectic Home: http://www.ldodds.com Current Project: http://outerthought.net/wiki/Wiki.jsp Pluralitas non est ponenda sine necessitate -- William of Ockham - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XSP Best Practise Question
I've been thinking along the same lines recently, and am still in two minds. I'm intending on writing up an essay on the CocoDocoWiki when I get a few minutes. Current musings: Model-View-Controller is the de facto example of a 'best practice' way of organising your web application code to allow the maximum degree of separation between content/logic/presentation. In servlet/JSP terms this often ends up as a Servlet that does all the work up front (the Model, often called an Action or Handler), and then the JSP just does the job of formatting the content to produce the desired output. Often the Model involves complex business logic, perhaps implemented as EJBs. When looking sat Cocoon I decided that Generators (including XSP pages) were definitely the Model part: they hid the complicated details of the processing, and presented their results to the pipeline for suitable presentation. This is nice and flexible, because you can quickly wrap existing code as a Generator or XSP page, and can then take advantage of Cocoon as a flexible publication tool. Composing pipelines is then often a case of plugging together pre-existing components to create the desired presentation processing. However... As you've noted a lot of examples, and suggested solutions to problems posted to this list, use an alternate approach: the generators present data to the pipeline which uses Transformers and Actions to do often complex operations. The data itself is often wrapped in a page markup language making it easier to transform it to other forms (HTML/PDF/etc). This looks like its breaking MVC, and it probably is. Not sure whether this is good or bad yet, as there are advantages, the main one being that you end up with less logic hidden in Generators and XSP pages and more in custom Transformers/Actions. This can be a good thing if the logic is reusable. If its not, and the various steps in your pipeline are actually tightly coupled then you're going to end up in a mess, IMHO. It's at this point that you're starting to treat the sitemap as a programming language rather than a declarative means of gluing together components. (Aside: anyone notice how close the Sitemap is becoming to a source file? Imports: map:components; Instance Variables: component/global params added in 2.1; Methods: pipelines. There's a danger there in making this environment too programmer oriented). So my general advice is: if the logic is reusable, then make it a transformer/action so you'll have the most reuse. If its not, hide it away. Hope this is useful. I've got a slew more thoughts on page markup languages, templating and separation of concerns, but I'll save that ramble for another time. Cheers, L. -- Leigh Dodds Weblog: http://weblogs.userland.com/eclectic Home: http://www.ldodds.com Current Project: http://outerthought.net/wiki/Wiki.jsp Pluralitas non est ponenda sine necessitate -- William of Ockham -Original Message- From: Michael Edge [mailto:[EMAIL PROTECTED]] Sent: 22 August 2002 10:20 To: [EMAIL PROTECTED] Subject: XSP Best Practise Question Hi All I have a question regarding the use and purpose of XSP. I believe that XSP is an attempt to separate content/logic from presentation, and I believe it's possible to use it in this way. However, in many of the samples (such as results-dept.xsp below, found in the tutorial) XSP is used to retrieve XML from a database and wrap it in some sort of pseudo-html, which is then processed by a logicsheet to produce proper HTML. To me this defeats the whole purpose of XSP. The XSP below mixes content and presentation, and if it contained xsp:logic sections it would be even worse, mixing content, logic and presentation. My thoughts are that, as the XSP is a generator it should generate XML in some suitable form. If logic is needed within the XSP dynamic tags can be used and translated using a logicsheet (or made part of XSP if they are not resuable). However, the actual presentation of this XML should be left to a stylesheet. I would really appreciate your comments and thoughts on this as we are trying to implement multiple projects here using Cocoon and want to use a consistent, best-practise approach. Thanks for your time :-) Michael xsp:page xmlns:xsp=http://apache.org/xsp; xmlns:xsp-request=http://apache.org/xsp/request/2.0; xmlns:esql=http://apache.org/cocoon/SQL/v2; document header titleSearch Results/title /header body s1 title=Department Search Results p You can edit a department by clicking on the edit button, and you can delete a department by clicking on the delete button. /p esql:connection esql:poolpersonnel/esql:pool esql:execute-query esql:query SELECT id, name FROM department WHERE name LIKE esql:parameter%xsp-request:get-parameter name
RE: XSP Best Practise Question
The XSP below mixes content and presentation, and if it contained xsp:logic sections it would be even worse, mixing content, logic and presentation. On this point specifically, I'd consider it a best practice to have *all* logic moved into a logicsheet so that you're left only with your own custom tags in the XSP page. If you do this correctly, and design a recently flexible *declarative* language to wrap you're logic, then you're left with something which isn't wildly different from a JSP page containing custom JSP tags. Cheers, L. - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: cocoon.xconf in subdirectory
I have to admit to not having tried that in detail -- I was going
by what I was seeing in the Cocoon examples.
I'll investigate and confirm that I'm not talking rubbish.
Apologies if I've lead you down the wrong track.
L.
-Original Message-
From: Leszek Gawron [mailto:[EMAIL PROTECTED]]
Sent: 09 August 2002 11:28
To: [EMAIL PROTECTED]
Subject: cocoon.xconf in subdirectory
Following the statement :
!Sub-Sitemaps and Components
Since Cocoon 2.0.X it has been possible to include additional cocoon.xconf
files in sub-directories. These will be automatically processed by Cocoon,
allowing the declaration and use of additional components, JDBC connections,
etc. Again this enables multiple users to more easily share a single
Cocoon instance.
I was trying to put the appropriate datasource definition for my cocoon
application in th application folder (/cocoon/cdn)
The cocoon says that no datasource can be found so my cocoon.xconf is not
being processed. I also tried to put it into /cocoon/cdn/WEB-INF but that gave
no result also
my cocoon.xconf file is simple:
coon version=2.0
datasources
jdbc name=cdn logger=core.datasources.cdn
pool-controoller min=1 max=10/
auto-commitfalse/auto-commit
dburljdbc:izmado:Provider=MSDASQL;Driver={Sql
Server};Server=OUZO\CDN_OPTIMA;Database=CDN_Demo;USER ID=SA;/dburl
usersa/user
password/password
/jdbc
/datasources
/cocoon
Is this all really possible ?
ouzo
--
__
| / \ |Leszek Gawron// \\
\_\\ //_/ [EMAIL PROTECTED] _\\()//_
.'/()\'. Phone: +48(600)341118 / // \\ \
\\ // recursive: adj; see recursive | \__/ |
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
Please check that your question has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
XSP Tutorial
Hi, IBM have posted my second Cocoon tutorial: Working with XML Server Pages in Apache Cocoon 2 http://www-106.ibm.com/developerworks/education/r-xxsp.html?n-x-4252 It covers the basic principles of XSP (code generation using XSLT); the XSP syntax; and of course using and creating logicsheets. I've just finished writing the third tutorial covering the ESQL and Form Validation logicsheets. Not sure when that will be published. Feedback very welcome. L. -- Leigh Dodds, Research Group, Ingenta | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: KrysalIDE for Cocoon2
Personally I think the best IDE for Cocoon wouldn't be one that exposed XSLT, XSP, etc directly. But would allow simple drag and drop creation of pipelines, etc. i.e. a tool targetted to the users of Cocoon, it's adminstrator. Developers of components/stylesheets are well-served by various IDEs already. An XML processing pipeline aware tool could also be used to generate code for other environments, e.g the XML-Pipeline Note that was submitted to the W3C, Ant, etc. Cheers, L. -- Leigh Dodds, Research Group, Ingenta | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Resource Site/Tutorial
Hi, I know a couple of folks have posted a link to my Introduction to Cocoon 2 tutorial [1], I just wondered if it could get added to the Cocoon links on the website? Am writing an XSP tutorial currently. Cheers, L. [1]. http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/83F66813F7FFD61486256B7 4006EB648?OpenDocument -- Leigh Dodds, Research Group, Ingenta | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Oddity with XSP and Namespaces
Thanks Vadim, Hi, can anyone explain the following, or identify that this is a fixed bug? Ok, I can now identify that this is a *fixed* bug. Thanks for finding. Am I right in thinking that this will end up in Cocoon 2.0.2? Thanks, L. - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Automatic FAQ
I wonder if there is a piece of software that accepts mails as input and format them for the web. So I can forward it the best mails of the lists, and browse them, as an FAQ. I agree that this is a good idea, but you can do this in a lot less technical way -- in fact I have been doing it for the XML-DEV mailing list for roughly 2 years now through the eclectic weblog. cocoon-users has a mail archive, so the messages are already formatted for the web and you can point to them. All that's missing is the editorial process to sift through these messages to get the real gems. Why not set up a weblog and start pointing to interesting postings? I've started collecting a list of 'Cocoon tips' based on this process, but haven't published them. I just drop the notes into the Wiki page I run on my laptop. Cheers, L. -- Leigh Dodds, Research Group, Ingenta | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why XSP?
Actually thats not quite what the original poster was asking. You're correct in that XSLT is for transforms, and XSP compares favourably with JSP. However you can extend XSLT using extension functions and elements, thereby adding to its capabilities. So with XSLT alone you *do* have a way to invoke arbitrary code during your transforms (although you should take care not to introduce side-effects). That said, XSP generates compiled classes, whereas most XSLT processors don't do anything similar; although the Sun Translet technology does go someway towards this. The advantage of XSP is mainly its a cleaner form of JSP, the layering seems better defined, and the syntax easier to read. The other advantage of XSP over XSLT is that it exposes the HTTP environment (i.e. the same info as in JSP/servlets), whereas you'd have to produce some custom implementation to achieve that with XSLT alone. HtH, L. -- Leigh Dodds, Systems Architect | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham -Original Message- From: Eduardo Yanez [mailto:[EMAIL PROTECTED]] Sent: 03 July 2001 16:56 To: [EMAIL PROTECTED] Subject: RE: Why XSP? Hi Mikael, XSLT is just a transforming language, you can use it for transform any xml document to any other textual format (html, txt, svg, pdf, etc). On the other side you can compare XSP with JSP, they technologies for dynamic content generation, JSP allow you to create servlets easily for dynamic html generation, with XSP you have dynamic XML generation!. In fact XSP uses XSLT in the transformers (C2) and in the XSP processor (C1). I hope the explanation aids you. Regards, Eduardo Yanez. -Original Message- From: Mikael Steldal [mailto:[EMAIL PROTECTED]] Sent: Viernes, 29 de Junio de 2001 04:51 a.m. To: [EMAIL PROTECTED] Subject: Why XSP? What is the need for XSP? Why not use XSLT with extensions instead? - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XML inside XML, and XSLT inside XSLT
No necessarily. It depends on what you're trying to do. You can go a long way with using entities. e.g: !DOCTYPE book [ !ENTITY chapter1 SYSTEM chapter1.xml !ENTITY chapter2 SYSTEM chapter2.xml !ENTITY chapter3 SYSTEM chapter3.xml ] book chapter1; chapter2; chapter3; /book While you're correct that XInclude appears to be the correct way forward (barring some recent concerns [1]), and offers richer semantics that simple entities. However you'll need an Xinclude processor [2] to use them, while any off-the-shelf XML parser will do entities. [1]. http://www.xmlhack.com/read.php?item=1272 [2]. http://www.ibiblio.org/xml/XInclude/ (although this relies on JDOM) Cheers, L. -- Leigh Dodds, Systems Architect | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham -Original Message- From: Jörn Heid [mailto:[EMAIL PROTECTED]] Sent: 04 July 2001 08:57 To: [EMAIL PROTECTED] Subject: AW: XML inside XML, and XSLT inside XSLT For xml it's XInclude... -Ursprngliche Nachricht- Von: Adrian Geissel [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 4. Juli 2001 09:55 An: [EMAIL PROTECTED] Betreff: Re: XML inside XML, and XSLT inside XSLT For XSLT, use xsl:import href=/ Adrian - Original Message - From: Carloz Alaniz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 03, 2001 9:01 PM Subject: XML inside XML, and XSLT inside XSLT Can someone help me or tell me there is such a thing as including an XML file inside another XML file, or including an XSLT file inside another XSLT file? Does such a thing exist?? ~carloz -- -- - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DTD and XSP..NEED HELP PLZ
I believe your DOCTYPE should be: !DOCTYPE xsp:page [ ... ] xsp isn't enough by itself. The other thing to check is that the 'ens.xml' file is really in/accessible from the same place as the XSP page. If not you'll need a path. Cheers, L. -Original Message- From: Mohamed Ramzy [mailto:[EMAIL PROTECTED]] Sent: 04 July 2001 14:54 To: Cocoon list Subject: DTD and XSP..NEED HELP PLZ hi, i have a problem and i didn't find the answer in the FAQ. my problem is that i have a .xml file which is using a DTD to get external entities, i want to use XSP with this xml file to retrieve some parameters from HTML file, the problem here, i always get a XSP NullPointerException error, here is the code ?xml version=0.1? ?cocoon-process=xsp? ?cocoon-process=xslt? ?xml-stylesheet href=.xsl? !-- xsp is the root element -- !DOCTYPE xsp [ !ENTITY % ens SYSTEM ens.xml %ens;] xsp:page language=java xmlns:xsp=http://www.apache.org/1999/XSP/Core; page parameters fnamexsp:exprrequest.getParameter(fname)/xsp:expr/fname . /parameters /page /xsp:page i don't know if the error in the decleration of the root element in the DOCTYPE, or XSP and DTD can't work together...would any one tell me what to do... i'm using Cocoon 1.8.2 apache JServ/1.1 thanks in advance = Mohamed Ramzy Zakaria, Graduate Research student School of Computer Science Information Technology Jubilee Campus, Nottingham University Nottingham, UK TEL: 00 44 (0)115 84 66529 MOB: 00 44 (0)7947105251 MOB E-MAIL: [EMAIL PROTECTED] __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Stability: Cocoon 1 vs Cocoon 2
Hi, What recommendations would people give to someone looking to start a new Cocoon project. Presumably Cocoon 1 is still the stabler platform at this stage? Has anyone gone through migrating a project from C1 to C2, and if so what problems/difficulties did you encounter? Was it an easy transition. Any comments greatly appreciated. Cheers, L. -- Leigh Dodds, Systems Architect | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Stability: Cocoon 1 vs Cocoon 2
So I think I'd say that a fair assessment is that anyone looking to get to grips with the Cocoon framework would do well to start with C1 (its easier to started), but would do well to switch to C2 due its better speed, but not until the development has progressed much further. Anyone disagree? L. -Original Message- From: Eduardo Yánez [mailto:[EMAIL PROTECTED]] Sent: 28 June 2001 15:25 To: [EMAIL PROTECTED] Subject: RE: Stability: Cocoon 1 vs Cocoon 2 Hi! Cocoon 1.8.2 is a pretty stable version but its foundation is DOM, so if you want to develop a site where the responses can be big the site answers will be slow and the memory requirements can be big also. Cocoon 2 is in alpha version yet (almost a beta), but its foundation is SAX, it is faster (very much faster!) and can handle very large responses with low memory requirements. It manages new technologies like SVG so you can forget about doing images for sites menus (cocoon 2 make them for you!). Cocoon 2 is more dificult to learn, because it has new concepts (they were necesary) that makes it really powerfull. The sitemap and actions for me were issues that makes hard the transition. The Cocoon 1.8.x development is slowed down (if not, it is stoped), Cocoon2 is raising. Regards, Eduardo Ynez. -Original Message- From: Leigh Dodds [mailto:[EMAIL PROTECTED]] Sent: Jueves, 28 de Junio de 2001 08:20 a.m. To: Cocoon-Users Subject: Stability: Cocoon 1 vs Cocoon 2 Hi, What recommendations would people give to someone looking to start a new Cocoon project. Presumably Cocoon 1 is still the stabler platform at this stage? Has anyone gone through migrating a project from C1 to C2, and if so what problems/difficulties did you encounter? Was it an easy transition. Any comments greatly appreciated. Cheers, L. -- Leigh Dodds, Systems Architect | Pluralitas non est ponenda http://weblogs.userland.com/eclectic |sine necessitate http://www.xml.com/pub/xmldeviant| -- William of Ockham - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
