[Off-topic] Compiling servlets.
It seems that gcj successfully compiled Tomcat 3. You can have a look at: http://sources.redhat.com/rhug/ The maintainer (mailto:green;redhat.com) told me it sounds possible to compile Tomcat4 and Cocoon2 too... Anyone wants to try? ---cut here--- This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: Which way is the best to output blobs from db to user?
-Message d'origine- De: Björn Voigt [mailto:bjoern-voigt;gmx.de] Date: jeudi 24 octobre 2002 22:32 À: cocoon-users Objet: Which way is the best to output blobs from db to user? Hello cocooners, i have a mysql database with a table containing pictures as blob. In an old Version of my Web-Application I used a servlet to output the pictures via http. Now I want to take Cocoon to do this. My question is which way is the best way to solve my problem? A blob can be VERY easily exported from a database via the blob:/ pseudo protocol. YOu can refer to any blob in the database via a simple URL. So to retrieve it via HTTP is as easy as having such a pipeline: map:match pattern=... map:read src=blob:/... mime-type=.../ /mpa:match This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: [Off-topic:XSLT] Passing an XML fragment via a HTML form.
It will work for a textarea if that is an option, but for an input, all the tags get stripped out and just the content gets included. This is a very interesting thread. So with hidden textareas or you custom class, I can pass the XML fragment. But when receiving the request parameter in my XSL, how can I transform it into a XML fragment again and out put it of the transformation? Is the noddeset() function useful in that case? This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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]
[Off-topic:XSLT] Passing an XML fragment via a HTML form.
I have a HTML form, created from a XML file and a XSL Treansformation. I need to pass a subtree of that XML as a parameter, via that form. Is there a way, in XSLT, to transform a XML fragment into a string? So I can have an input in my form that contains the text of this XML fragment. Corrolair when processing parameters sent by the form: is there a way, in XSLT, to transform as string into a XML fragment? ---cut here--- This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: [Off-topic:XSLT] Passing an XML fragment via a HTML form.
I need to pass a subtree of that XML as a parameter, via that form. Is there a way, in XSLT, to transform a XML fragment into a string? So I can have an input in my form that contains the text of this XML fragment. How about parsing the form element value to a DOM object (either client or server side) and extract the DOM node that serves as the root of the fragment you need? You think I should use Java/XSP for such a process? Ok. Let's say I put the subtree to be sent into a DOM object. How do I stringify it? (I presume I cannot pass a Java object via a HTML form :-) This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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]
SunShine InsertTransformer fails with JDK1.4
I am currently using SunShine InsertTransformer with C2.0.3 and C2.0.4-dev. It works fine under JDK1.3. And fails with JDK1.4.1 (Xalan exceptions,see below). Anyone ever had such a failure? Note: will the source:insert be backported to C2.0.X ? Here is the exception cut: ---beginning of exception--- FATAL_E (2002-10-21) 10:58.02:784 [core.xslt-processor] (/cocoon-2.0.3/mount/wikiland_0.7/edit/put(bravo)) Thread-10/TraxErrorHandler: Error in TraxTransformer: javax.xml.transform.TransformerException: java.lang.NullPointerException javax.xml.transform.TransformerException: java.lang.NullPointerException at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava:1226) at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3135) at java.lang.Thread.run(Thread.java:536) Caused by: java.lang.NullPointerException at org.apache.cocoon.sunshine.xml.XMLUtil.getFirstNodeFromPath(XMLUtil.java:801 ) at org.apache.cocoon.sunshine.xml.XMLUtil.getFirstNodeFromPath(XMLUtil.java:748 ) at org.apache.cocoon.sunshine.xml.XMLUtil.getSingleNode(XMLUtil.java:660) at org.apache.cocoon.sunshine.xml.XMLUtil.selectSingleNode(XMLUtil.java:145) at org.apache.cocoon.sunshine.transformation.InsertTransformer.insertFragment(I nsertTransformer.java:386) at org.apache.cocoon.sunshine.transformation.InsertTransformer.endTransformingE lement(InsertTransformer.java:265) at org.apache.cocoon.transformation.AbstractSAXTransformer.endElement(AbstractS AXTransformer.java:351) at org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler. java:307) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 684) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 678) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.templates.ElemChoose.execute(ElemChoose.java:164) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 678) at org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApp lyTemplates.java:423) at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav a:226) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer Impl.java:2008) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava:1171) ... 2 more - java.lang.NullPointerException at org.apache.cocoon.sunshine.xml.XMLUtil.getFirstNodeFromPath(XMLUtil.java:801 ) at org.apache.cocoon.sunshine.xml.XMLUtil.getFirstNodeFromPath(XMLUtil.java:748 ) at org.apache.cocoon.sunshine.xml.XMLUtil.getSingleNode(XMLUtil.java:660) at org.apache.cocoon.sunshine.xml.XMLUtil.selectSingleNode(XMLUtil.java:145) at org.apache.cocoon.sunshine.transformation.InsertTransformer.insertFragment(I nsertTransformer.java:386) at org.apache.cocoon.sunshine.transformation.InsertTransformer.endTransformingE lement(InsertTransformer.java:265) at org.apache.cocoon.transformation.AbstractSAXTransformer.endElement(AbstractS AXTransformer.java:351) at org.apache.xalan.transformer.ResultTreeHandler.endElement(ResultTreeHandler. java:307) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 684) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 678) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.templates.ElemChoose.execute(ElemChoose.java:164) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java: 678) at org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApp lyTemplates.java:423) at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.jav a:226) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(Transform erImpl.java:2182) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(Transformer Impl.java:2008) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.j ava:1171) at
RE: ServerPageAction: XMLFragment reuse in XSL transformer
May be you can try to import a XML fragment via the document() XSL function.
Calling a cocoon:/ URL, you will get the XML fragment in a variable inside
your XSL.
Neat and very efficient !!!
-Message d'origine-
De: Christian Kurz [mailto:crkurz;gmx.de]
Date: vendredi 18 octobre 2002 08:42
À: [EMAIL PROTECTED]
Objet: Re: ServerPageAction: XMLFragment reuse in XSL transformer
Thank you very much for the quick feed-back! The idea sounds great and is a
lot cleaner, than fiddling something in some XSL extension.
I am not sure about the cachaebility: the XMLFragment specifying, which
nodes to filter from the big input document, changes everytime, so Cocoon
would need to parse the source file on every request (, if my understanding
is right).
If I'd slidely change your approach to implementing the same approach into a
transformer component. This transformer component will not be cacheable, but
at least the generator in front of it would be.
Thanks again,
Christian
BTW, thanks also for the code snippet. It helps a lot, as soon as it comes
to thinks like the ObjectModel, I start feeling uncomfortable.
- Original Message -
From: Hunsberger, Peter mailto:Peter.Hunsberger;stjude.org
To: '[EMAIL PROTECTED]' mailto:'[EMAIL PROTECTED]'
Sent: Thursday, October 17, 2002 6:46 PM
Subject: RE: ServerPageAction: XMLFragment reuse in XSL transformer
There's probably about half a dozen ways to do this. Perhaps one of the
simplest is just to create your own caching generator and use aggregation
(with any other XML you may need) in the pipeline.
In the generator you'll need to implement the setup method to see the
objectModel, something like the following:
private gunk mySessionData = null;
public void setup( SourceResolver resolver, Map objectModel, String src,
Parameters parms )
throws ProcessingException, SAXException, IOException
{
if (mySessionData == null ) {
super.setup( resolver, objectModel, src, parms );
Request request =
(Request)ObjectModelHelper.getRequest(objectModel);
Session session = request.getSession(false);
if (session != null) {
// save a pointer to your session data for use in the generate
method
mySessionData =
}
}
}
Now in your generate method just pick up whatever data hangs off of
mySessionData and away you go
-Original Message-
From: Christian Kurz [mailto:crkurz;gmx.de]
Sent: Thursday, October 17, 2002 11:26 AM
To: [EMAIL PROTECTED]
Subject: ServerPageAction: XMLFragment reuse in XSL transformer
Hello cocoon-users,
I need to generate some tiny XML elements (XMLFragment) within a
ServerPageAction and I would like to use this XMLFragment later on in an XSL
transformer, that is fed by an xml generator. The XMLFragment captured in
the ServerPageAction is basically saying, which nodes are to be returned
from the big input document.
From some other message in this group I have understood, that passing
objects is only possible through session or request objects, but not through
sitemap variables. I don't like to use a request generator as the starting
point of the pipeline, as I'd loose cacheability at a very early step in the
pipeline. With a quite big xml input document, this does not seem a good
idea to me.
So I am currently struggling how to get a piece of XML, that is attached to
a session or request object, into the xsl transformer. Has anybody tried
this before e.g. using an XSL extension?
Any help or hints appreciated!
Thank you in advance,
Christian
This e-mail is intended only for the above addressee. It may contain
privileged information. If you are not the addressee you must not copy,
distribute, disclose or use any of the information in it. If you have
received it in error please delete it and immediately notify the sender.
Security Notice: all e-mail, sent to or from this address, may be
accessed by someone other than the recipient, for system management and
security reasons. This access is controlled under Regulation of
Investigatory Powers Act 2000, Lawful Business Practises.
-
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: Adobe new products
I read this morning on Heise (www.heise.de - German) about Adobe introducing a new range of products for big business. Looks like they will be bringing out a Forms Server, an Output Server, a Workflow Server and a Document Server - all designed to make PDF ubiquitous. And each server with a separate price tag I would assume. If I didn't know better - from the limited description - I would say they could be using Cocoon (or a Cocoon based solution) for all that. Does anyone have any additional information - I think the release is next week. I think this is a great news, both for web developpers (1) and for Cocoon developpers (2). (1) One big commercial product is available that shares the philosophy of Cocoon. If your company wants you to devellop web things, you can say Hey, Adobe sells products that sound really great. (2) The fact that a big company chooses such a model for web development will credibilize Cocoon. Chiefs will say Wow, Adobe products sound great but it costs a lot. Open source geeks have made a clone of them? Yes? Cocoon? Well, let's give it a try!. Of course, the ideal scenario is to chain (1) and (2) :-)) This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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]
Request parameters in a cocoon:/
When you call a cocoon:/ from your pipeline, the sitemap calls itself. But inside this new call, you lose the initial request parameters. Is there a way to set new request-parameters for the cocoon:/ call? Or keep the intial request parameters when the sitemap calls itself? This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: Request parameters in a cocoon:/
map:match pattern=*.xsp map:generate type=serverpages src=xsp/(1).xsp/ map:transform src=stylesheets/copySelf.xsl / map:serialize type=xml/ /map:match map:match pattern=bigPage map:aggregate element=page map:part src=cocoon:/data1.xsp/ map:part src=cocoon:/data2.xsp/ map:part src=cocoon:/data3.xsp/ /map:aggregate map:transform src=stylesheets/bigPage.xsl / map:serialize / /map:match My quiestion is that if I send this URl to Cocoon: http://.../bigPage?foo=1bar=0 Will I be able to retrieve those data in the copySelf.xsl? (defining use-stylesheet-parameters for it, of course) This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: Request parameters in a cocoon:/
Good question -- I have not tried that scenario. As a workaround, instead of extracting request parameters from a stylesheet, you could something like this in the xsp fooxsp:exprrequest.getParameter(foo)/xsp:expr/foo barxsp:exprrequest.getParameter(bar)/xsp:expr/bar and use XSLT to get the params during transformation. I think that a cocoon:/ call resets all the requestParameters. It seems that you can retrieve them if you manage to include them as *part of* the URL of the cocoon:/. This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: Request parameters in a cocoon:/
I think that a cocoon:/ call resets all the requestParameters. Maybe, but it should not! Are you sure? Its purpose is to create a new request with old AND new parameters (AFAIU) Well, if you have ideas about how I can pass NEW request parameters for the cocoon:/ call, I am really interested. Using a GET-style URL (cocoon:/toto.xsp?foo=1) fails for me (C2.0.2). This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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: SourceWritingTransformer.
From what I understand, yes. In 2.1 SourceWritingTransformer has been merged with ex-sunrise InsertTransformer. No hope to see this feature in C2.0.4 ? It would be a so neat feature!!! This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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]
InsertTransformer
It seems that the InsertTransformer accepts sunshine:insert subtree as an input. But it provides no XML output so you know if the insertion went ok or not. SWT is much more verbose! You get an XML output that provides a success/failure result. Is it possible to get an XML output from the SunShine InsertTransformer? This e-mail is intended only for the above addressee. It may contain privileged information. If you are not the addressee you must not copy, distribute, disclose or use any of the information in it. If you have received it in error please delete it and immediately notify the sender. Security Notice: all e-mail, sent to or from this address, may be accessed by someone other than the recipient, for system management and security reasons. This access is controlled under Regulation of Investigatory Powers Act 2000, Lawful Business Practises. - 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 hsqldb
There is a JDBC driver for MS SQL Server, available at sourceforge.net: jtds. -Message d'origine- De: Bertrand Delacretaz [mailto:[EMAIL PROTECTED]] Date: lundi 14 octobre 2002 11:26 á: [EMAIL PROTECTED]; [EMAIL PROTECTED] Objet: Re: Cocoon and hsqldb On Monday 14 October 2002 11:18, [EMAIL PROTECTED] wrote: . . . Has someone tried to connect Cocoon to a Microsoft SQL Server database? I'm looking for a database URL connection example. . . . If you're courageous you can use the JDBC-ODBC bridge for this, but last time I checked it was fairly limited and funky (or do they have native JDBC now?). I don't have an URL handy but you should find it in the JDBC-ODBC samples. I've also used www.inetsoftware.de's excellent (commercial) drivers for MS SQL, you'd then use a JDBC URL like: jdbc:inetdae:your_server:1433?database=your_db A nice utility to test these URLs and JDBC drivers is DBVisualizer, http://www.minq.se/products/dbvis/info.html Hope this helps. -Bertrand - 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]
CVS of C2.0.4-dev
I need C2.0.4-dev. I am currently getting the CVS of HEAD. I wonder if HEAD is either C2.0.4-dev? or C2.1-dev? If HEAD is not C2.0.4-dev, what are the instructions to get it? Note: may be this point should be clearly written in the docs or in the wiki. - 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: WebDav, DavFS, Slide and else ....
At the moment, I could get davFS (Linux) to work fine as a local filesystem. I tried cvsfs, but could not make it to work. It's toio bad because it has a natural naming convention - older version of file mapping. Any help is welcome. BTW, I think the newer CVS system made by GNU will have a WebDAV interface. May be it will also implement that naming convention system. -Message d'origine- De: Kjetil Kjernsmo [mailto:[EMAIL PROTECTED]] Date: mercredi 21 août 2002 15:43 À: ROSSEL Olivier Objet: Re: WebDav, DavFS, Slide and else On Wednesday 21 August 2002 15:28, ROSSEL Olivier wrote: Here is a crazy idea I have had. Linux has a WebDav FileSystem. So accessing/updating files via WebDAV is completely transparent to Cocoon. WebDAV servers can have versionning, revision systems. So, without changing the way you work inside Cocoon, you can have WebDAV capabilities. If the WebDAV server allows to access the extra features (older versions, number of the current version,metadata) in a filesystem way, you can have full WebDAV management without doing nothing inside Cocoon. Is it dumb? _I_ really don't think so! It's really good! It is actually how I'd like my content contributors to interact with my server. I don't know how to code it, but I would be _very_ interested if you get it up and running! :-) Have you looked at the webdav example in tomcat4, BTW? Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/ - 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]
WebDav, DavFS, Slide and else ....
Here is a crazy idea I have had. Linux has a WebDav FileSystem. So accessing/updating files via WebDAV is completely transparent to Cocoon. WebDAV servers can have versionning, revision systems. So, without changing the way you work inside Cocoon, you can have WebDAV capabilities. If the WebDAV server allows to access the extra features (older versions, number of the current version,metadata) in a filesystem way, you can have full WebDAV management without doing nothing inside Cocoon. Is it dumb? Note: my initial problem is to have CVS capabilities on my XML data files, that are updated via Cocoon (it's for Wikiland). - 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: WebDav, DavFS, Slide and else ....
Do have run davfs anytime? It's the hell. I never got this to work. I MUST install Slide and test its functionnalities. But I like very much the idea of having no stuff on the client side. Just a filesystem with (for example) naming conventions for accessing older versions or metadata. And all the dirty work is done by the filesystem abstraction and the WebDAV server. So when a user destroys a topic in wikiLand, I go to the (WebDAV) filesystem, make a move of .topic.xml__revisions/topic.xml__last to topic.xml and everything works again. See what I mean? Could Slide be the WebDAV server that does all that? - 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: How to send redirect from an XSP?
You shouldn't do it. Use an action for this. There are already a number of actions that perform this job. Use one of them, modify one of them, write a new one, or write an XSP action that does it. What is an XSP action? Can we now use XSP to write Actions? Is there any documentation on it? You can use the ServerPagesAction. A action written in XSP. It is only documented in the Javadoc. Quite simple, and very nice ! - 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: sexy open source
But if you use schema-based storage, you can have your XML internally stored into SQL tables. And XPath queries are rewritten (yes yes!) into corresponding SQL equivalent. That's on the feature list, but is it implemented yet? If so, where? In XSU? Oracle 9iR2 (yes R2 makes the difference). The only examples I can find on this are ones where the table has already been defined and you're just loading a chunk of XML. That doesn't seem like schema-based storage, as Oracle isn't even touching the DTD or XSD. It's just doing a direct mapping of an XML document into an object. Either the mapping is deduced from the schema. Or you can annotate the schema in order to customize the mapping (providing tables names, column names, SQL types). - 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 2] - Tomcat 4.1.9Beta avaliable
Hi all: I downloaded the last Tomcat beta release and is working fine with Cocoon2. more info at: http://jakarta.apache.com/ download at: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4 .1.9-beta/ This week being the Off-topic week, I will ask something so OT: is Tomcat 4.1 better than 4.0 under heavy loads? - 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: Can cocoon write pdf to a file?
Yes! you want SourceWritingTransformer from Cocoon 2.1 dev. There is a parameter to tell it how to serialize the output. It writes to a file on the local hard drive. SWT can have its own serializer? What a great stuff! Is this feature available in the scratchpad of C2.0.3? - 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: Can cocoon write pdf to a file?
Sure. The main pipeline continues but the portion of XML corresponding to the SWT has been replaced by the result of the SWT step. Input: ... source:write content_to_write ... /content_to_write /source:write ... Output: ... source:result isSuccess='true'/ ... Note: this is not the correct syntax, at all. But this is the idea :-) -Message d'origine- De: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] Date: vendredi 16 août 2002 16:26 À: '[EMAIL PROTECTED]' Objet: RE: Can cocoon write pdf to a file? isn't there to be a serializer after the transformer in the pipeline? -Original Message- From: Geoff Howard [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Friday, August 16, 2002 10:22 AM To: '[EMAIL PROTECTED]' Subject: RE: Can cocoon write pdf to a file? Yes! you want SourceWritingTransformer from Cocoon 2.1 dev. There is a parameter to tell it how to serialize the output. It writes to a file on the local hard drive. SWT can have its own serializer? What a great stuff! Is this feature available in the scratchpad of C2.0.3? Yes, just checked and it's in scratchpad of 2.0.3. From the java docs: This transformer allows you to output to a WritableSource. Definition: map:transformer name=tofile src=org.apache.cocoon.transformation.SourceWritingTransformer map:parameter name=serializer value=xml/ !-- this is the default Serializer (if your Source needs one, like for instance FileSource ) -- /map:transformer/ Invocation: map:transform type=tofile map:parameter name=serializer value=xml/ /map:transform Input XML document example: page xmlns:source= http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 ... source:write src=context://doc/editable/my.xml page XML Object body /page /source:write ... /page Output XML document example: page xmlns:source= http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 ... source:write src=/source/specific/path/to/context/doc/editable/my.xml result=success|failure action=new source specific error message /source:write ... /page Geoff - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html 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: Can cocoon write pdf to a file?
well, the SWT writes to a WritableSource, AFTER being serialized by its OWN serializer. So the main pipeline can be a HTML report of the PDF written to disk. -Message d'origine- De: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] Date: vendredi 16 août 2002 16:40 À: '[EMAIL PROTECTED]' Objet: RE: Can cocoon write pdf to a file? I still don't see how this will work with PDF. PDF comes only from FOPSerializer. the last step in the pipeline. So, if you want to write its result on the disk, how can SWT be useful? I thought, maybe it makes a sense to have a special type of transformer or serializers, which would save output on the hard disk, but pass the URL to the pipeline. so, there'll be uniform way to deal with this sort of situations. on the other hand, having the caching configured properly would probably solve the problem too. -Original Message- From: ROSSEL Olivier [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Friday, August 16, 2002 10:35 AM To: '[EMAIL PROTECTED]' Subject: RE: Can cocoon write pdf to a file? Sure. The main pipeline continues but the portion of XML corresponding to the SWT has been replaced by the result of the SWT step. Input: ... source:write content_to_write ... /content_to_write /source:write ... Output: ... source:result isSuccess='true'/ ... Note: this is not the correct syntax, at all. But this is the idea :-) -Message d'origine- De: Argyn Kuketayev [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Date: vendredi 16 août 2002 16:26 À: '[EMAIL PROTECTED]' Objet: RE: Can cocoon write pdf to a file? isn't there to be a serializer after the transformer in the pipeline? -Original Message- From: Geoff Howard [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Friday, August 16, 2002 10:22 AM To: '[EMAIL PROTECTED]' Subject: RE: Can cocoon write pdf to a file? Yes! you want SourceWritingTransformer from Cocoon 2.1 dev. There is a parameter to tell it how to serialize the output. It writes to a file on the local hard drive. SWT can have its own serializer? What a great stuff! Is this feature available in the scratchpad of C2.0.3? Yes, just checked and it's in scratchpad of 2.0.3. From the java docs: This transformer allows you to output to a WritableSource. Definition: map:transformer name=tofile src=org.apache.cocoon.transformation.SourceWritingTransformer map:parameter name=serializer value=xml/ !-- this is the default Serializer (if your Source needs one, like for instance FileSource ) -- /map:transformer/ Invocation: map:transform type=tofile map:parameter name=serializer value=xml/ /map:transform Input XML document example: page xmlns:source= http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 ... source:write src=context://doc/editable/my.xml page XML Object body /page /source:write ... /page Output XML document example: page xmlns:source= http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 http://apache.org/cocoon/source/1.0 ... source:write src=/source/specific/path/to/context/doc/editable/my.xml result=success|failure action=new source specific error message /source:write ... /page Geoff - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html http://xml.apache.org/cocoon/faq/index.html http://xml.apache.org/cocoon/faq/index.html 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 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: Can cocoon write pdf to a file?
on the other hand, having the caching configured properly would probably solve the problem too. Wait, this last statement makes it sound like you are only interested in keeping the results cached to reduce load. If that is the case, use cocoon caching - it will automatically keep the result in memory and optionally write it out to disk/database as well. Caching will not keep a .pdf file anywhere - it remembers (compiles in docs is misnomer) the byte-stream for reuse if appropriate. I would highly reccomend against attempting to introduce your own file-based caching system when a good one is already in place. Hopefully, that's not what you meant by that. I wonder if Cocoon (2.1?) handles Last-modified management? So when the browser requests something, Cocoon can (automatically or via custom actions) provide a Last-modified, and the client then decides if he can use its cache. I read that Cocoon handles Expires. But Expires and Last-modified are different notions. - 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: Can cocoon write pdf to a file?
I think you can use such a a pipeline: - SWT -- Serializer : PDF - sucessOrFailure2mail.xsl - Sendmail transformer So the first step makes the PDF and provides a report as XML . The second step creates a report mail from the XML output of the SWT. The third step sends the mail (may be with the URL where the PDF can be found). -Message d'origine- De: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] Date: vendredi 16 août 2002 17:05 À: '[EMAIL PROTECTED]' Objet: RE: Can cocoon write pdf to a file? well, I don't remember who started the thread, not me though :) I'll also need some sort of solution with large PDF files. The idea is that you come and launch report, and given a URL to check it later (when PDF is ready). The URL would point to a file on the disk, which will be stored for some time, say one day. Cashing is for a different situation, which you described. -Original Message- From: Geoff Howard [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Sent: Friday, August 16, 2002 10:54 AM To: '[EMAIL PROTECTED]' Subject: RE: Can cocoon write pdf to a file? -Message d'origine- De: Argyn Kuketayev [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] Date: vendredi 16 août 2002 16:40 À: '[EMAIL PROTECTED]' Objet: RE: Can cocoon write pdf to a file? ... on the other hand, having the caching configured properly would probably solve the problem too. Wait, this last statement makes it sound like you are only interested in keeping the results cached to reduce load. If that is the case, use cocoon caching - it will automatically keep the result in memory and optionally write it out to disk/database as well. Caching will not keep a .pdf file anywhere - it remembers (compiles in docs is misnomer) the byte-stream for reuse if appropriate. I would highly reccomend against attempting to introduce your own file-based caching system when a good one is already in place. Hopefully, that's not what you meant by that. Geoff - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html 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: sexy open source
I am currently studying XML DB features of Oracle 9iR2. It is quite impressive. Very very advanced stuff !!! Buy some RAM and let's go :-) PS: BTW? what's the price of Oracle? :-) -Message d'origine- De: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] Date: mercredi 14 août 2002 15:05 À: '[EMAIL PROTECTED]' Objet: RE: sexy open source RDBMS must be Oracle. no other options, imho. cost is not a problem. it's negligeable comparing to the cost of one DBA. while at the same time performance and other features of Oracle are far better than anything. 4) Business Logic Persistence Proposal: Firebird RDBMS as JBoss service jBoss sucks, imho. - 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: sexy open source
8) Web frontend Proposal: Apache Remarks: This is only for security reasons - the task of Apache is just to forward the requests. I think more of you are using it, true? Not needed. Not needed Can somebody explain how to run Tomcat on port 80 under user with no root priviledges? Under Linux, you can use VERY simple iptables rules. And there are free tools to make that too. And patches so you can declare ports under 1024 to be accessible to non-root people. Open source your mind! - 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: sexy open source
I am currently studying XML DB features of Oracle 9iR2. It is quite impressive. Very very advanced stuff !!! How it compares to Tamino and Xindice? What are the cool features (in a nutshell ;)? I dunno Tamino. I hope I will have the time to test Xindice. Oracle 9iR2 has a XML repository accesible vie Webdav, HTTP and FTP. It handles foldering, versionning. It has schema validation system, and (automatic or manual) schema-based XML-SQL mapping. XPath functions are accessible inside SQL queries. And queries can provide XML as output. I am currently investigating mapping SQL queries to HTTP URLs. So we can use a simple Http generator to get XML from Oracle. This is a (very) simplified overview. I have not made stretch test yet. - 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: sexy open source
To add to this. Oracle 9i now has a native XMLType which is really a CLOB. However, it doesn't have the normal limitations of a CLOB -- you can use XPATH for selection and for indexing, a great improvement in my opinion. However, a drawback remains in that you are still unable to select individual nodes and attributes within the CLOB, so your SQL has to return the document as a whole. I disagree. XMLType is a abstraction of how the XML is really stored. XMLType is (by default) CLOB. And XPath are real XPath expressions applied on that CLOB. But if you use schema-based storage, you can have your XML internally stored into SQL tables. And XPath queries are rewritten (yes yes!) into corresponding SQL equivalent. - 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: sexy open source
* XML Editor for Content Editing: Xopus 2 (http://www.xopus.org/) Did they released the beta version of Xopus2 yet? - 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: XPath selector or XPath matcher
Is anybody working on a XPath selector or XPath matcher? I have situations where I would like to select the pipeline or at least the XSLT depending on the value of an attribute within the generated XML. If there is no such mecanism in Cocoon, you can code your XSLT stylesheets so they make the test by themselves. - 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: Redirect/Rewrite Module
I have a situation where I would like to do a lot of URI-redirects/rewrites. I know I can do this via the sitemap, but other people would be doing this. So for the reason of Separation of Concern I would like to separate this from the actual sitemap. My question is what are the possibilties to do something like that? -One way would probably be to have a separate sitemap dedicated to redirects, which is mounted by the actual sitemap. Exactly. I think this is the more robust system. URL patterns will make the redirection via map:redirect, except for special cases where you would need XSP ou may be actions. I think it is the most flexible way to do the trick. - 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: [REVISIT] RE: UTF-8 and HTML Serializer.
Rossel, can you look at the 'source' XML by serializing it with xml serializer, instead of html? what does it show? well i think i got my problem. the request generator accepts a parameter to force the encoding of data retrieved. i misued it by setting the wrong charset. 3 things to know. there is a way to force the charset for the requestGenerator (parameter is called form-encoding or form-charset, i think). Mozilla sends request data using the accept-charset attribute of the form IE sends request data using the encoding of the HTML page where the form is. All can be seen in wikiland 0.5 You will see that the form is in an HTML with a UTF-8 charset. That the form has the attribute accept-charset set to UTF-8. And I think (but not sure) has the form-encoding/charset set to UTF-8. http://lolive.net is the homepage of wikiLand. - 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: xsl and http request header
I think that you can do that using a xsl document() pointing to a cocoon url with http generator and xml serializer. This is a VERY powerful option of Cocoon. -Message d'origine- De: Barbara Post [mailto:[EMAIL PROTECTED]] Date: mercredi 31 juillet 2002 15:51 À: [EMAIL PROTECTED] Objet: xsl and http request header Hello, can an xsl directly access http request header (like http request parameters) or should I use request generator ? I want a text field to have a size specified by the kind of browser... Maybe rather use browser selector to pass a parameter to my xsl...? Babs - 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: using different stylesheets for different xml files
Here is a sitemap for catch-all XML management.
map:match pattern=*.xml
map:generate src={1}.xml/
map:transform src={1}.xsl/
map:serialize/
/map:match
The sitemap resolver receives the URL.
It parses sequentially the sitemap file,
reading only what is inside matching map:match.
The map:match above will be read for any URL that ends with the string
'.xml'.
The sitemap resolver read the map:generate...
It sees that it has to resolve the variable {1}
(which contains the string matched by the first wildcard of pattern=...)
It resolves it either to 'login1' or 'login2' and instanciates
the generator that will generate SAX events by reading the corresponding
file.
Idem for the map:tranform
Then the sitemap resolver reads a (HTML by default) serializer.
It instanciates the HTMLSerializer.
Then it stops reading the file (it ALAYS stops reading the file
as soon as it meets a map:serialize).
The pipeline is ready.
Another approach is this one:
map:match pattern=login1.xml
map:generate src=login1.xml/
map:transform src=login1.xsl/
map:serialize/
/map:match
map:match pattern=login2.xml
map:generate src=login2.xml/
map:transform src=login2.xsl/
map:serialize/
/map:match
How all that works is the same as above.
-Message d'origine-
De: kavitha ramesh [mailto:[EMAIL PROTECTED]]
Date: jeudi 25 juillet 2002 15:02
À: [EMAIL PROTECTED]
Objet: using different stylesheets for different xml files
Hi,
I have two xml files and I would like to use two
different stylesheets for that.How do i do it?
For example I have two xml files inside the folder
name docs:
login1.xml
login2.xml
and I have two stylesheets:
login1.xsl
login2.xsl
and for login1.xml I would like to use the stylesheet
login1.xsl and for login2.xml I would like to use
login2.xsl.How do the sitemap.xmap file look like for
the above?
Please help me,,,
Kavitha
__
__
Want to sell your car? advertise on Yahoo Autos Classifieds.
It's Free!!
visit http://in.autos.yahoo.com
-
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: HTML tree from a Directory generator.
What I want is to get a Windows explorer like view of a directory tree :-) Not a highlighted XML :-) That's clear. You should merge them and not use them consecutively. This means for example to use the collapse/expand code from simple-xml2html.xsl. If you don't want to do it yourself, you must wait a week. I will try to create a Windows explorer like-stylesheet. Ok. I get the idea now. Sorry for being so dumb :-) Well, I think a generic stylesheet could be nice. And visually striking in the samples of (let's say) C2.0.4 :-) - 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: Depth in DirectoryGenerator
-Message d'origine- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Date: mardi 16 juillet 2002 06:21 À: [EMAIL PROTECTED] Objet: Depth in DirectoryGenerator Hi All, I try to use DirectoryGenerator to create dynamic directory list. In documentation said, it's possible to set arbitrary depth of directory recursion. For example, I have set depth to 5: map:pipeline map:match pattern=directory.xml map:generate type=directory src=model depth=5/ map:serialize type=xml/ /map:match /map:pipeline But it does not work, I always receive flat list, even if the subdirectory is not empty: ?xml version=1.0 encoding=UTF-8 ? dir:directory name=model lastModified=1025423302000 date=30.06.02 11:48 requested=true xmlns:dir=http://apache.org/cocoon/directory/2.0; dir:directory name=rdf lastModified=102579130 date=04.07.02 18:01 / dir:file name=entry.xml lastModified=102602808 date=07.07.02 11:48 / dir:file name=map.xml lastModified=1026409374000 date=11.07.02 21:42 / /dir:directory I will appreciate any help. Best Regards, Serge Chernokozinsky I am not sure, but I think I use the depth parameter this way: map:pipeline map:match pattern=directory.xml map:generate type=directory src=model map:parameter name=depth value=5/ /map:generate map:serialize type=xml/ /map:match /map:pipeline And it works. - 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: HTML tree from a Directory generator.
Is there somewhere a XSL that outputs a HTML+javascript tree view of a directory generator output? Why aren't you using the directory2html.xsl merged with the simple-xml2html.xsl? http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/webapp/samples/ common/style/xsl/html/directory2html.xsl http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/src/webapp/samples/ hello-world/style/xsl/simple-xml2html.xsl Joerg What I want is to get a Windows explorer like view of a directory tree :-) Not a highlighted XML :-) - 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: Please help with SourceWritingTransformer
I seem to have done everything right and was testing out the
SourceWritingTransformer and can't get it to write to a file.
I have the
pipeline
map:match pattern=test/*.xsp
map:generate type =serverpages src=test/{1}.xsp/
map:transform type=sql
map:parameter name=use-connection value=dev_database/
/map:transform
map:transform src=test/metadata.xsl/
map:transform type=xslt-with-parameters
src=test/source.xsl
map:parameter name=page-title value={page-title}/
/map:transform
map:transform type=tofile2
map:parameter name=serializer value=xml/
/map:transform
map:serialize type=xml/
/map:match
I know that everything up to the second transformation works
(until the
tofile2 trans which is the SWT). The input to the SWT looks
like this:
?xml version=1.0 encoding=UTF-8 ?
source:write
xmlns:source=http://apache.org/cocoon/source/1.0; src=
context://my.xml
KnowledgeObject xmlns:sql=http://apache.org/cocoon/SQL/2.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
...stuff..
/KnowledgeObject
/source:write
Can you try with a src containing only the path and no context: at all?
I think it may be the problem.
Gurus will confirm, but I think that Writable source are URLs that can
written
to. context:// is a pseudo protocol, that is probably not handled correctly
bu the SWT. Try with a path, I think SWT will be happier.
Note for developpers: may be, the context:// could be considered a Writable
Source.
-
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]
Caching DirectoryGenerator.
I am currently using DirectoryGenerator. My concern is that it is probably a non-cacheable component, so each time a request is made, each time a listing of my directory is made. Of course, files in my directory change once in a century, so the DirectoryGenerator almost always gives the same result. If there is no caching system, I would like to make a kind of home-made caching strategy, using a separate file which timestamp would keep track of the modification in my directories (== I 'touch' this file each time I write something in my directories), so I check this timestamp against the last time the DirectoryGenerator was accessed, make a test and send a cached DirectoryGenerator result instead of launching the component. Is it possible to make that in current architecture? Is it possible to tune the caching strategy (with actions, for example). - 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]
HTML tree from a Directory generator.
Is there somewhere a XSL that outputs a HTML+javascript tree view of a directory generator output? - 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]
UTF-8 and HTML Serializer.
In C2.0.2, I use a pipeline that produce a XML encoded with UTF-8. In this XML, I have one 'é' character that is coded as Ã* ... After the HTML serializer , instead of having the 'é' again, I have two characters coded as: Atilde;copy. It seems that hte serializer realized missed the UTF-8 character and considered it as US-ASCII/ISO-8859-1. Is it a bug in Xalan, or what? - 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: UTF-8 and HTML Serializer.
In this XML, I have one 'é' character that is coded as Ã* ... ^ Outlook ate my copyright sign !!! - 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: UTF-8 and HTML Serializer.
where should i add this? i tried to add it at map:serialize level. but it did nothing: map:serialize type=html encodingutf-8/encoding /map:serialize may be it must be done at declaration time, at map:components level? -Message d'origine- De: Volker Schneider [mailto:[EMAIL PROTECTED]] Date: jeudi 11 juillet 2002 17:08 À: [EMAIL PROTECTED] Objet: RE: UTF-8 and HTML Serializer. Hi, does encodingUTF-8/encoding help with html-serializer? Best regards - Volker - -Original Message- From: ROSSEL Olivier [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 11. Juli 2002 17:00 To: '[EMAIL PROTECTED]' Subject: UTF-8 and HTML Serializer. In C2.0.2, I use a pipeline that produce a XML encoded with UTF-8. In this XML, I have one 'é' character that is coded as Ã* ... After the HTML serializer , instead of having the 'é' again, I have two characters coded as: Atilde;copy. It seems that hte serializer realized missed the UTF-8 character and considered it as US-ASCII/ISO-8859-1. Is it a bug in Xalan, or what? - 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] - 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: UTF-8 and HTML Serializer.
where should i add this? i tried to add it at map:serialize level. but it did nothing: map:serialize type=html encodingutf-8/encoding /map:serialize may be it must be done at declaration time, at map:components level? even at declaration time, it seems not to work. - 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: UTF-8 and HTML Serializer.
can you look at the 'source' XML by serializing it with xml serializer, instead of html? what does it show? well i think i got my problem. the request generator accepts a parameter to force the encoding of data retrieved. i misued it by setting the wrong charset. - 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: xsl vs cocoon
Sure. The sitemap.xmap file makes a mapping between URLs received from client side to a Cocoon pipeline. A pipeline is a chain of java components that create or modify a XML flux. For a given URL, Cocoon parses the sitemap.xmap, gets the corresponding pipeline description, creates the corresponding chain of java components and launches the first components (it is called a generator because it is the one which creates the XML flux, and sends it to the next component). There is no problem if you want to specify several XSLT components inside your pipeline. Advanced feature: When describing a pipeline in sitemap.xmap, you can also make a component conditionnal depending on (for example) a request parameter value in the HTTP request, or may be the speed of the wind (yes Cocoon is marvellous :-) - 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: Réf. : RE: xsl vs cocoon
it's partially true, because right now (which is a pitty) there's no sitemap element that can get a parameter value (which is sometimes very important)... Can't you use an action to set a value for a sitemap variable, then use that variable inside you component description? hi, i agree with olivier,.. , you can also make a component conditionnal depending on (for example) a request parameter value in the HTTP request it's partially true, because right now (which is a pitty) there's no sitemap element that can get a parameter value (which is sometimes very important)... regards othman ---Message original--- De : [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date : mercredi 10 juillet 2002 10:38:03 A : '[EMAIL PROTECTED]' mailto:[EMAIL PROTECTED] Sujet : RE: xsl vs cocoon Sure. The sitemap.xmap file makes a mapping between URLs received from client side to a Cocoon pipeline. A pipeline is a chain of java components that create or modify a XML flux. For a given URL, Cocoon parses the sitemap.xmap, gets the corresponding pipeline description, creates the corresponding chain of java components and launches the first components (it is called a generator because it is the one which creates the XML flux, and sends it to the next component). There is no problem if you want to specify several XSLT components inside your pipeline. Advanced feature: When describing a pipeline in sitemap.xmap, you can also make a component conditionnal depending on (for example) a request parameter value in the HTTP request, or may be the speed of the wind (yes Cocoon is marvellous :-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] . http://www.incredimail.com/redir.asp?ad_id=312lang=12 IncrediMail - La messagerie électronique a enfin évolué - http://www.incredimail.com/redir.asp?ad_id=312lang=12 Cliquer ici ATT574260.gif Description: GIF image - 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: Réf. : RE: xsl vs cocoon
What's a sitemap?
Well, as I said before, it is the file (called sitemap.xmap) which
maps URLs to cocoon behaviour.
Each time a URL request is sent to Cocoon, the sitemap resolver
parses the whole file sitemap.xmap (==the sitemap), tries to
find which map:match elements match the current URL.
It then parses (only) what is inside those map:match,
and for each compoment declaration read, it creates the
java component that corresponds.
For example, for URL:
http://localhost:8080/cocoon/toto.html
the URL that Cocoon receives is toto.html
(the servlet container handled the first part).
So the sitemap resolver will read the sitemap.xmap file
and try to find all goods map:match.
For example map:match pattern=toto.html.../map:match
will be ok for the sitemap resolver, and it will read what's inside this
tag.
Lets' say that:
map:match pattern=toto.html
map:generate type=file src=docs/toto.xml/
map:transform type=xslt src=stylesheets/toto2html.xsl/
map:serialize type=html/
/map:match
The sitemap resolver will read that, and
create a generator, a XSLT transformer and a HTML serializer,
link them one after the other, and launch the pipeline.
The generator make a XML flux from a file which is located at
docs/toto.xml,
then the flux goes through a XML tranformer, which makes a xslt
transformation
using the stylesheet available at stylesheets/toto2html.xsl, then the
resulting
flux is sent to a serializing component, which transforms the input flux
into a html flux.
Then Cocoon send the resulting (html) stream to the client side.
Basically, this is the idea behind a sitemap file.
Why is it so nice? Because the sitemap file can be much more complex.
For example, another possibility could have been:
map:match pattern=toto.*
map:generate type=file src=docs/toto.xml/
map:transform type=xslt src=stylesheets/toto2{1}.xsl/
map:serialize type={1}/
/map:match
Exactly the same but we use a wildcard for URL matching.
So the same sitemap text will handle toto.html, toto.csv ...
Note: The {1} is similar to stuff in regexp, it corresponds to the text
matched by the first wildcard in the matching expression.
Quite nice, isn't it?
And this is only the beginning.
FYI, the sitemap file is parsed linearly, the sitemap resolver
tries to get into _every_ map:match it can (it does only if the matching
pattern
is OK for the current URL), and the sitemap resolving stops
as soon as a map:serialize is met successfully.
May be you do not understand this paragraph now, but keep it in mind for the
future.
Understanding Cocoon means that you understand the process of sitemap
resolution.
The other part of the knowledge is to know what components exist.
Note: I left some specific cases, for comprehension.
Feel free to ask on the list.
We all began wondering what's a sitemap :-)
-
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: Réf. : RE: Réf. : RE: xsl vs cocoon
I am not sure to understand what you want to do exactly. -Message d'origine- De: Othman Haddad [mailto:[EMAIL PROTECTED]] Date: mercredi 10 juillet 2002 11:15 À: [EMAIL PROTECTED] Objet: Réf. : RE: Réf. : RE: xsl vs cocoon With 2.1-dev the RequestParameterInputModule can be used to to get the value of a field in an xsp and select a pipeline in function of it ,but not before!!! do you have any other key to do that? ---Message original--- De : [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date : mercredi 10 juillet 2002 10:52:33 A : '[EMAIL PROTECTED]' mailto:[EMAIL PROTECTED] Sujet : RE: Réf. : RE: xsl vs cocoon it's partially true, because right now (which is a pitty) there's no sitemap element that can get a parameter value (which is sometimes very important)... Can't you use an action to set a value for a sitemap variable, then use that variable inside you component description? hi, i agree with olivier,.. , you can also make a component conditionnal depending on (for example) a request parameter value in the HTTP request it's partially true, because right now (which is a pitty) there's no sitemap element that can get a parameter value (which is sometimes very important)... regards othman ---Message original--- De : [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date : mercredi 10 juillet 2002 10:38:03 A : ' [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ' mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sujet : RE: xsl vs cocoon Sure. The sitemap.xmap file makes a mapping between URLs received from client side to a Cocoon pipeline. A pipeline is a chain of java components that create or modify a XML flux. For a given URL, Cocoon parses the sitemap.xmap, gets the corresponding pipeline description, creates the corresponding chain of java components and launches the first components (it is called a generator because it is the one which creates the XML flux, and sends it to the next component). There is no problem if you want to specify several XSLT components inside your pipeline. Advanced feature: When describing a pipeline in sitemap.xmap, you can also make a component conditionnal depending on (for example) a request parameter value in the HTTP request, or may be the speed of the wind (yes Cocoon is marvellous :-) - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html http://xml.apache.org/cocoon/faq/index.html http://xml.apache.org/cocoon/faq/index.html http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] . http://www.incredimail.com/redir.asp?ad_id=312 http://www.incredimail.com/redir.asp?ad_id=312lang=12 lang=12 IncrediMail - La messagerie électronique a enfin évolué - http://www.incredimail.com/redir.asp?ad_id=312 http://www.incredimail.com/redir.asp?ad_id=312lang=12 lang=12 Cliquer ici http://www.incredimail.com/redir.asp?ad_id=312lang=12 IncrediMail - La messagerie électronique a enfin évolué - http://www.incredimail.com/redir.asp?ad_id=312lang=12 Cliquer ici ATT575595.gif Description: GIF image - 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: Giving up! Cocoon too big, slow and confusing
The documentation should follow the learning curve. May be each doc should have a requirement section, which lists all the notions that must be well known to understand the current topic. And docs should be rated under a system of Beginner, Intermediate and Advanced topics. In fact, i think everybody should use wikiLand : http://www.anyware-tech.com/wikiland I promise that if someone else than me posts something on wikiLand, I code the XSLT to export to xdocs :-) That's a deal, dudes! The second thing that makes Cocoon obscure is the lack of intuitive debugging system. An intuitive debugging system allows the user to _see_ the behaviour of the program. I think that a Cocoon app which could display on the client how the sitemap resolved for a given URI, which could allow to browse between a sitemap resolving report and XML/XSL files involved in the resulting pipeline, all that would make newbies get into Cocoon more easily. The first step should be an easy step. And last thing, error management should be heavily handled in Cocoon. No more strange messages on the client side. My humble 2 cents. - 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: Giving up! Cocoon too big,slow and confusing (Blocks will he lp for sure)
I think the core developers are fully aware of this fact, and the Cocoon Blocks [1] concept will make a big difference here. Trimming down the core and making most or all components pluggable will help a lot in differentiating between stable/well-known and experimental/mysterious components. -Bertrand With dependencies management, administration/upgrading interface, rights management and debugging facilities? And docs? Wow :-) - 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: Giving up! Cocoon too big, slow and confusing
Probably you will appreciate to know that several books will be available VERY soon about Cocoon. BTW, several companies offers trainings about Cocoon. If it sounds too costy to learn it by yourself, you can be helped by professionnals. I agree that the best tool is the one you master. I have a different opinion: To me, the best tool is the one you master and are paid to use. My 2 cents :-) PS: the first time I launched Vim, I could not type anything and couldn't find any way to quit this nasty program. -Message d'origine- De: John Austin [mailto:[EMAIL PROTECTED]] Date: jeudi 27 juin 2002 04:41 À: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Objet: Giving up! Cocoon too big, slow and confusing I'm back from a short vacation in beautiful Chicago (it really is much nicer than Toronto or Montreal) and have waded back in to Cocoon for a couple of days. After just a few hours of poking around I have decided that it will be much simpler for me to simply hand-code a whole hat-full of servlets than to try and pull any meaning out of Cocoon and it's documentation. Fifteen hours on the Interstate wasn't as challenging as trying to figure out how one should check a Web Form this month but I didn't have that feeling of travelling backwards half of the time. I was also able to predict and achieve forward progress (for a change). Thanks guys, but no thanks. Maybe I'm getting old, but I really don't understand the need for all of the complexity and the lack of documentation in this product. On the other hand, I used to feel the same way about the mind-numbing complexity of a certain thirty-year-old mainframe operating system (MVS) produced by IBM back in the sixties and it's patching system (SMP4). So it can't just be my age. Anyway, Cocoon has cost me far morte (a typo that's better than the original word) time than it was worth. The chief problems appear to have been endlessly re-invented terminology for an overwhelming number of 'new concepts' and a complete lack of consistency between different components (i.e. functional code, non-functional examples, unbuildable documentation and a website that doesn't match up with any single released version of the project). I have a lot of respect for the ability of the people who have built this project, but I want them to know that their project appears to be out-of-control and could become very difficult to manage. If experienced developers (like myself) can't figure out how to use enough features in the product to make it worth using, then penetration will be limited and all of your efforts will be wasted. There is more to this business than stuffing in features at the expense of documentation and testing. You have a lot of very good ideas, but the execution of the project as a whole seems to be suffering. I know that I will often look at my JSP and servlet code and think 'XSP and Cocoon were sooo much better!' until I remember that I wasn't ever able to use enough of Cocoon to make a profit. Oh, well, at least all of my test systems have bags of memory now! - 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: What does map:pipeline really do?
I think the only difference is that handle-errors are on per pipeline. so for different error handling, you need separate pipelines. BTW, internal-only=true/false is already a very good reason for having several pipelines. -Message d'origine- De: Per Kreipke [mailto:[EMAIL PROTECTED]] Date: vendredi 14 juin 2002 16:56 À: [EMAIL PROTECTED] Objet: RE: What does map:pipeline really do? John, Volker, I was about to ask the same question. Dear colleagues, does anybody know the difference between: map:pipeline map:match.../map:match map:match.../map:match /map:pipeline and map:pipeline map:match.../map:match /map:pipeline map:pipeline map:match.../map:match /map:pipeline http://xml.apache.org/cocoon/faq/faq-sitemap.html#faq-3 I re-read the entire user doc package last night and came across that section but, with all due respect, that documentation doesn't explain the benefits of one approach or the other. Sure, one pipeline can be hidden but what other reasons exist for separating into multiple pipelines? [Note: Volker's example didn't specify an internal pipeline] - for example, in the default sitemap (which is quite large), why are there so many pipelines? Couldn't it be done with all the matchers inside one pipeline? - in there a performance difference? - in cases where you aggregate XML parts using map:aggregate and the cocoon:/ protocol, are serializers skipped perhaps? Thanks, Per. - 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: how to write a simple Hello World
Hi folks, I'm new in the Cocoon world and I try to test a simple Hello World program. Here my hello.xml document: ?xml version=1.0? ?cocoon-process type=xslt? ?xml-stylesheet href=hello.xsl type=text/xsl ? page titreHello World!/titre content paragraphIt's my first Cocoon page !/paragraph /content /page And here my hello.xsl stylesheet: ?xml version=1.0? xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:template match=page html head title/xsl:value-of select=titre/ /head body xsl:apply-templates/ /body /html /xsl:template /xsl:stylesheet But when I request the hello.xml from my browser, nothing happend! I just see my hello.xml file in the browser. do I have fogotten something? Thank you Sylvain If you use Cocoon2, it does not work the way it used to work in Cocoon1. You have to declare excplicitely which URL pattern will trigger your XML+XSL. In fact, in the file sitemap.xmap, you declare all URL patterns that Cocoon will handle, and associate a data chain (called a pipeline). Have a look at your sitemap.xmap. A piepilne is a chain of Cocoon components that send SAX events to the next component. A pipeline is defined as a XML generator, zero or more XSL transformers and a HTML serializer (: transforms SAX events into a character stream). I think that by studying the sitemap.xmap, you will find a pipeline description that matches your HelloWorld example. Feel free to tell us which difficulties block you. - 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 J2EE
My cocoon.war comes with the binary distribution. I thought that this cocoon.war was necessary to work with Cocoon!?! My question is: What is necessary to work with Coccon and do you have to include it in each Enterprise ARchive you create?? Thank you Sylvain Vadim will tell if I am wrong, but Cocoon is a servlet, ie a Java class. It needs several Java dependencies for XML parsing and other fundamental things to work properly. Additionnal Java libraries can be added to extend its functionnalities (fop for PDF rendering, batik for SVG and graphics management). They are not mandatory. If they are needed in your application, you have to list them in cocoon.xconf and/or sitemap.xmap. For example, for wikiLand, I needed the basic Cocoon stuff and the chaperon parser. So I removed all the .jar uneeded that are usually shipped with Cocoon (big) archive, and added chaperon.jar. If you want, you can take the .war available at the homepahe of wikiLand, and study it. In fact, to remove the dependencies of Chaperon, simply have a look at the beginning the sitemap.xmap and comment everything that talks about chaperon or wiki-parser. Then you will have the skeleton for any Cocoon application. - 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 J2EE
OK, I see. Thank you Olivier. Finally if I want the basic stuff I need cocoon.jar (and others? Do you exist a description list of the additionnal libraries?) in my something.war (or cocoon.war). But do you have to include this cocoon.war in each Enterprise ARchive?? Thank you Sylvain I think that the jars in wikiland.war (minus chaperon.jar) are the basic stuff. I do not know what a Entreprise Archive is, but in any .war you make you need all the .jars of Cocoon. A .war is a hermetic context, with its own classes. If a .ear is (simply) an enhanced .war, then in any .ear that will embed Cocoon, you need to put all the .jar. - 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 installation
Is it easier to install? With Tomcat 4.0.1 or 4.0.4, and with JDK 1.3.X, the installation is straightforward. If you work under Unix, please read the installation section about PJA. Don't use JDK1.4 unless you have time to tune your Tomcat. - 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]
wikiLand Cocoon Application 0.1
Built with Cocoon, the Chaperon parser and the slash-edit system, using the Wiki syntax, here is the announcement of the first Alpha release of wikiLand. Available at http://lolive.net, a .war of C2.0.2+chaperon+wikiLand is available. Please report any bug you can find (there are many, especially in the support of the Wiki syntax). This application is distributed as a fully stand-alone application, or as an add-on for your working C2.0.2 with scratchpad. End-users can follow the mailing-list dedicated to wikiLand (see the web site). lOlive.net PS: greetings go to Jeremy Quinn for slash-edit, Stephan Michels for Chaperon. And to the Cocoon project, of course ;-) - 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]
