Re: HTML5 doctype from Cocoon 2.1?

[Martin Holmes]

Thanks Alec -- I think I might be able to manage an HTML5 serializer if 
I have a good example to work from. I'm puzzled about why you needed 
your custom serializer, though -- I've been able to serialize XHTML 1.1 
without problems, using the regular serializer configured just like 
yours below. What does your dynamic serializer do that can't be done 
with a regular one?


Cheers,
Martin

On 10-11-16 01:05 AM, Alec Bickerton wrote:

The code below is part of a seperate serialiizer class that extands 
HTMLSerializer and implements SitemapModelComponent.
It's configered in the sitemap as shown.


yes
-//W3C//DTD XHTML 1.1//EN

http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd
UTF-8


Regards,
Alec

On 15/11/10 17:09, Martin Holmes wrote:

Hi there,

Where exactly did you put this code? Did you implement your serializer
as a separate class file, or have you modified the core Cocoon code?

(I have no experience of customizing Cocoon itself, although I've
written the odd class to implement custom sorting collations and to add
functionality to XQuery code.)

Cheers,
Martin

On 10-11-15 01:08 AM, Alec Bickerton wrote:

Hi,

Just to throw in my 0.02c. At my current workplace we solved this
issue by implementing both a dynamic XML Serializer
and an HTML Serializer. We found that reconfiguring a the serializer
for each use while risky does work.

Caveat: While this approach has been tested under light load. I cannot
say how it'll behave under heavy load, we're
still checking. YMMV.


 public void setup(SourceResolver resolver, Map objectModel,
String src, Parameters par) {
 String configxml = "";
 String[] parameterNames = par.getNames();
 for (int i = 0; i<   parameterNames.length; i++) {
 String paramName = parameterNames[i];
 String paramValue = par.getParameter(paramName, null);
 if (!paramName.isEmpty()&&   paramValue != null)
 configxml += "<" + paramName +">" + paramValue +"";
 }
 if (configxml.length()>   0) {
 configxml = "" + configxml +""; //
put settings around to make an 'xml'
 try {
 DefaultConfigurationBuilder confBuilder = new
DefaultConfigurationBuilder();
 ByteArrayInputStream stream = new
ByteArrayInputStream(configxml.getBytes());
 Configuration conf = confBuilder.build(stream);
 /
  * all these values are supported - see
AbstractTextSerializer cdata-section-elements doctype-public
  * doctype-system encoding indent media-type method
omit-xml-declaration standalone version
  ***/
 super.configure(conf);
 } catch (ConfigurationException e) {
 log.error("ConfigurationException: " +
e.getLocalizedMessage(), e);
 } catch (SAXException e) {
 log.error("SAXException: " + e.getLocalizedMessage(),
e);
 } catch (IOException e) {
 log.error("IOException: " + e.getLocalizedMessage(), e);
 }
 }
 }



On 15/11/10 05:31, Jos Snellings wrote:

Hi Martin,

Do not know details, but it might help if you use the xsl:output element
in your transformation.
There is hope that it would not be overridden by the serializer.



Cheers,
Jos


On 11/12/2010 05:17 PM, Martin Holmes wrote:

Hi there,

Does anyone know how to configure a serializer for Cocoon 2.1 that
will output an HTML5 document? That means a minimal doctype that looks
like this:



served as text/html.

Cheers,
Ma



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






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

Re: HTML5 doctype from Cocoon 2.1?

[Martin Holmes]

Hi there,

Where exactly did you put this code? Did you implement your serializer 
as a separate class file, or have you modified the core Cocoon code?


(I have no experience of customizing Cocoon itself, although I've 
written the odd class to implement custom sorting collations and to add 
functionality to XQuery code.)


Cheers,
Martin

On 10-11-15 01:08 AM, Alec Bickerton wrote:

Hi,

Just to throw in my 0.02c. At my current workplace we solved this issue by 
implementing both a dynamic XML Serializer
and an HTML Serializer. We found that reconfiguring a the serializer for each 
use while risky does work.

Caveat: While this approach has been tested under light load. I cannot say how 
it'll behave under heavy load, we're
still checking. YMMV.


public void setup(SourceResolver resolver, Map objectModel, String src, 
Parameters par) {
String configxml = "";
String[] parameterNames = par.getNames();
for (int i = 0; i<  parameterNames.length; i++) {
String paramName = parameterNames[i];
String paramValue = par.getParameter(paramName, null);
if (!paramName.isEmpty()&&  paramValue != null)
configxml += "<" + paramName +">" + paramValue +"";
}
if (configxml.length()>  0) {
configxml = "" + configxml +""; // 
put settings around to make an 'xml'
try {
DefaultConfigurationBuilder confBuilder = new 
DefaultConfigurationBuilder();
ByteArrayInputStream stream = new 
ByteArrayInputStream(configxml.getBytes());
Configuration conf = confBuilder.build(stream);
/
 * all these values are supported - see 
AbstractTextSerializer cdata-section-elements doctype-public
 * doctype-system encoding indent media-type 
method omit-xml-declaration standalone version
 ***/
super.configure(conf);
} catch (ConfigurationException e) {
log.error("ConfigurationException: " + 
e.getLocalizedMessage(), e);
} catch (SAXException e) {
log.error("SAXException: " + 
e.getLocalizedMessage(), e);
} catch (IOException e) {
log.error("IOException: " + 
e.getLocalizedMessage(), e);
}
}
}



On 15/11/10 05:31, Jos Snellings wrote:

Hi Martin,

Do not know details, but it might help if you use the xsl:output element
in your transformation.
There is hope that it would not be overridden by the serializer.



Cheers,
Jos


On 11/12/2010 05:17 PM, Martin Holmes wrote:

Hi there,

Does anyone know how to configure a serializer for Cocoon 2.1 that
will output an HTML5 document? That means a minimal doctype that looks
like this:



served as text/html.

Cheers,
Ma



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

HTML5 doctype from Cocoon 2.1?

[Martin Holmes]

Hi there,

Does anyone know how to configure a serializer for Cocoon 2.1 that will 
output an HTML5 document? That means a minimal doctype that looks like this:




served as text/html.

Cheers,
Martin


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

Re: Determining the host OS

[Martin Holmes]

That does help, for sure; it's quicker to know which slash to add when I 
need to add one. I'd love to be sure that the absence of the trailing 
slash was reliable on Windows, and its presence reliable on *nix, but it 
seems better to check.


Cheers,
Martin

Robin Rigby wrote:

Martin

Does this help you?



Look at

blocks/cocoon-core-sample/cocoon-core-main-sample/src/main/resources/COB-INF
/modules/sitemap.xmap 



 
Robin 
 


-Original Message-
From: news [mailto:n...@ger.gmane.org] On Behalf Of Martin Holmes
Sent: 20 January 2009 16:49
To: users@cocoon.apache.org
Subject: Re: Determining the host OS

HI Steve,

Do you know how to call this in a sitemap? If I pass this into an XSLT 
transformation:




the parameter is empty.

Cheers,
Martin

Stephen Winnall wrote:
There is a module called SystemPropertyModule which appears to do what 
you want. Just ask it for "os.name".


Steve

On 20 Jan 2009, at 01:09, Martin Holmes wrote:


HI folks,

I'm trying to write a Cocoon-2.1-based application which I want to be 
completely portable between Tomcats running on Linux, OSX and Windows. 
I'm having a problem with the use of slashes and backslashes, 
especially on Windows, where I've found that some relative paths are 
expressed with backslashes and some with forward slashes, and the 
{realpath:/} constant returns a value without a trailing slash 
(whereas on *nix there seems to always be a trailing slash.


I could solve these problems using Flowscript and XSLT if I could 
determine what host OS Cocoon is running on. However, I can't find a 
way to do that in the sitemap. There's the HostSelector, which tells 
me the domain of the host; and there's the BrowserSelector, which 
tells me the connecting client's browser; but there's no way I can 
find to discover what operating system Cocoon is running on.


Does anyone know a way to do this, preferably directly in the sitemap?

All help appreciated,
Martin


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




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



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

Re: Determining the host OS

[Martin Holmes]

My mistake here: I'd added it to one matcher, but I was looking for it 
in the output of another one. It works just fine!


Thanks indeed.

Cheers,
Martin

Andy Stevens wrote:

2009/1/20 Martin Holmes :

HI Steve,

Do you know how to call this in a sitemap? If I pass this into an XSLT
transformation:



the parameter is empty.


That looks reasonable to me.  I assume you've got the input module
defined somewhere? (either in the components section of the sitemap
or, more likely, the default

entry in cocoon.xconf)
Chances are it would throw an error anyway if it wasn't.

What if you try

?  Is the parameter still empty in your XSL?  If so, it's not the
input module bit that's the problem.  What does the start of your XSL
file (especially the xsl:param) look like?

The system-property module is a jxpath-based one; I know the example
on http://cocoon.apache.org/2.1/userdocs/concepts/modules.html uses
{system-property:substring-before(user.home, user.name)}
but I'd have thought it should still be okay with no functions.  Do
any other system properties work?  Perhaps the app server hides some
of them - if you write a JSP that loops over them all and prints them
out, is os.name included in the list?  Are you getting any
securitymanager errors appearing in the logs?

Some more ideas at least.


Andy



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

Re: Determining the host OS

[Martin Holmes]

HI Steve,

Do you know how to call this in a sitemap? If I pass this into an XSLT 
transformation:




the parameter is empty.

Cheers,
Martin

Stephen Winnall wrote:
There is a module called SystemPropertyModule which appears to do what 
you want. Just ask it for "os.name".


Steve

On 20 Jan 2009, at 01:09, Martin Holmes wrote:


HI folks,

I'm trying to write a Cocoon-2.1-based application which I want to be 
completely portable between Tomcats running on Linux, OSX and Windows. 
I'm having a problem with the use of slashes and backslashes, 
especially on Windows, where I've found that some relative paths are 
expressed with backslashes and some with forward slashes, and the 
{realpath:/} constant returns a value without a trailing slash 
(whereas on *nix there seems to always be a trailing slash.


I could solve these problems using Flowscript and XSLT if I could 
determine what host OS Cocoon is running on. However, I can't find a 
way to do that in the sitemap. There's the HostSelector, which tells 
me the domain of the host; and there's the BrowserSelector, which 
tells me the connecting client's browser; but there's no way I can 
find to discover what operating system Cocoon is running on.


Does anyone know a way to do this, preferably directly in the sitemap?

All help appreciated,
Martin


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




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

Determining the host OS

[Martin Holmes]

HI folks,

I'm trying to write a Cocoon-2.1-based application which I want to be 
completely portable between Tomcats running on Linux, OSX and Windows. 
I'm having a problem with the use of slashes and backslashes, especially 
on Windows, where I've found that some relative paths are expressed with 
backslashes and some with forward slashes, and the {realpath:/} constant 
returns a value without a trailing slash (whereas on *nix there seems to 
always be a trailing slash.


I could solve these problems using Flowscript and XSLT if I could 
determine what host OS Cocoon is running on. However, I can't find a way 
to do that in the sitemap. There's the HostSelector, which tells me the 
domain of the host; and there's the BrowserSelector, which tells me the 
connecting client's browser; but there's no way I can find to discover 
what operating system Cocoon is running on.


Does anyone know a way to do this, preferably directly in the sitemap?

All help appreciated,
Martin


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

Re: mkdir in flowscript fails

[Martin Holmes]

Hi Steven,

I think you nailed it -- I'd omitted the folder prefix. It's set to 
{realpath:/} in the sitemap.


A fresh pair of eyes is a wonderful thing. Thanks indeed!

Cheers,
Martin

Steven D. Majewski wrote:





On Jan 9, 2009, at 5:36 PM, Martin Holmes wrote:


Hi there,

I'm trying to write flowscript which saves the output of a pipeline 
onto the file system. I've successfully done this for several 
pipelines, following the instructions on the WIKI. Up to now, I've 
been saving all the output files in an existing directory. Now I want 
to save one pipeline into a subdirectory, which I create on the fly 
based on the document id:





Using relative pathnames is kind of iffy:

var xhtml_folder = new Packages.java.io.File("teiJournal/backups/" + 
styleGuide + "/" +  docId);


if (!xhtml_folder.exists()){

  xhtml_folder.mkdir();

}




If you're running cocoon in tomcat, the current working directory will 
likely be the directory you
were in when you ran startup.sh -- not necessarily tomcat or cocoons 
home directory. ( I'm guessing

that other servlet containers do the same thing. )




The new folder is named with the string in docId, and its parent 
folder already exists. The parent folder is writable by the user under 
which Cocoon is running (in fact, it's owned by that user), and other 
pipelines can already save files into it; however, I just can't get 
Cocoon to create the subfolder. This is running on a RedHat server. If 
I modify the function to write the file directly to the existing 
directory, it works fine.


Does anyone have any idea why this might fail? This is the error, 
followed by the complete flowscript function:


ERROR (2009-01-09) 14:30.51:770 [flow] 
(/ialltjournal/teiJournal/backups/apa/doc.xhtml?id=iallt_40_01_sawhill) 
http-8081-7/MemberBox: JavaException: java.io.FileNotFoundException: 
/usr/local/apache-tomcat-dev/webapps/ialltjournal/teiJournal/backups/apa/iallt_40_01_sawhill/iallt_40_01_sawhill.xhtml 
(No such file or directory)


(In other words, the output file is not saved, because the new 
directory has not been successfully created.)


function makeBackupXHTML() {
  var xml_file;
  var xhtml_folder;
  var xhtml_file;
  var outstreamXHTML;

  try {

// Get required variables.

var folder = Packages.java.lang.String(cocoon.parameters["folder"]);
var styleGuide = 
Packages.java.lang.String(cocoon.parameters["styleGuide"]);
var qParams = 
Packages.java.lang.String(cocoon.parameters["urlQueryString"]);

var arrTemp = qParams.split("&");
var docId = arrTemp[0].split("=")[1];

//Create a directory to dump the files to

xhtml_folder = new Packages.java.io.File("teiJournal/backups/" + 
styleGuide + "/" +  docId);

if (!xhtml_folder.exists()){
  xhtml_folder.mkdir();
}



And here you're prefixing teiJournal with parameter "folder" ,
so the path printed in the error message for the file may not match the 
relative directory path name
for the directory you created.  ( What is being passed as parameter 
"folder" ? )


Rather than concatenating the pathnames twice, you might use the

File(File parent, String child)

constructor for the second instance, using File xhtml_folder as the 
parent File.

This will guarantee that they are both on the same path.



// Create link to file


xhtml_file = Packages.java.io.File(folder + "teiJournal/backups/" 
+ styleGuide + "/" + docId + "/" + docId + ".xhtml");


// Create outputstream to dump the results of conversion to the file

outstreamXHTML = new Packages.java.io.FileOutputStream( xhtml_file );

// Call cocoon pipeline and save the results to the outputstream
var pipePath = styleGuide + "/doc.xhtml?id=" + docId;
cocoon.processPipelineTo(pipePath, null, outstreamXHTML);

outstreamXHTML.close();

// Bounce back to the backups list page.
cocoon.redirectTo("../../backups.xhtml?styleGuide=" + styleGuide + 
"#" + docId, true);


  } catch( ex ) {
 cocoon.log.error(ex);
// Smth. went wrong. Sending a error.txt file to the browser
 cocoon.sendPage("backups/save_file_error.txt", null);
  }
}





-- Steve Majewski / UVA Alderman Library



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

Re: mkdir in flowscript fails

[Martin Holmes]

This is Cocoon 2.1, by the way -- forgot to mention that.

Martin Holmes wrote:

Hi there,

I'm trying to write flowscript ...



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

mkdir in flowscript fails

[Martin Holmes]

Hi there,

I'm trying to write flowscript which saves the output of a pipeline onto 
the file system. I've successfully done this for several pipelines, 
following the instructions on the WIKI. Up to now, I've been saving all 
the output files in an existing directory. Now I want to save one 
pipeline into a subdirectory, which I create on the fly based on the 
document id:


var xhtml_folder = new Packages.java.io.File("teiJournal/backups/" + 
styleGuide + "/" +  docId);


 if (!xhtml_folder.exists()){

   xhtml_folder.mkdir();

 }

The new folder is named with the string in docId, and its parent folder 
already exists. The parent folder is writable by the user under which 
Cocoon is running (in fact, it's owned by that user), and other 
pipelines can already save files into it; however, I just can't get 
Cocoon to create the subfolder. This is running on a RedHat server. If I 
modify the function to write the file directly to the existing 
directory, it works fine.


Does anyone have any idea why this might fail? This is the error, 
followed by the complete flowscript function:


ERROR (2009-01-09) 14:30.51:770 [flow] 
(/ialltjournal/teiJournal/backups/apa/doc.xhtml?id=iallt_40_01_sawhill) 
http-8081-7/MemberBox: JavaException: java.io.FileNotFoundException: 
/usr/local/apache-tomcat-dev/webapps/ialltjournal/teiJournal/backups/apa/iallt_40_01_sawhill/iallt_40_01_sawhill.xhtml 
(No such file or directory)


(In other words, the output file is not saved, because the new directory 
has not been successfully created.)


function makeBackupXHTML() {
   var xml_file;
   var xhtml_folder;
   var xhtml_file;
   var outstreamXHTML;

   try {

// Get required variables.

 var folder = Packages.java.lang.String(cocoon.parameters["folder"]);
 var styleGuide = 
Packages.java.lang.String(cocoon.parameters["styleGuide"]);
 var qParams = 
Packages.java.lang.String(cocoon.parameters["urlQueryString"]);

 var arrTemp = qParams.split("&");
 var docId = arrTemp[0].split("=")[1];

//Create a directory to dump the files to

 xhtml_folder = new Packages.java.io.File("teiJournal/backups/" + 
styleGuide + "/" +  docId);

 if (!xhtml_folder.exists()){
   xhtml_folder.mkdir();
 }

// Create link to file

 xhtml_file = Packages.java.io.File(folder + "teiJournal/backups/" 
+ styleGuide + "/" + docId + "/" + docId + ".xhtml");


// Create outputstream to dump the results of conversion to the file

 outstreamXHTML = new Packages.java.io.FileOutputStream( xhtml_file );

// Call cocoon pipeline and save the results to the outputstream
 var pipePath = styleGuide + "/doc.xhtml?id=" + docId;
 cocoon.processPipelineTo(pipePath, null, outstreamXHTML);

 outstreamXHTML.close();

// Bounce back to the backups list page.
 cocoon.redirectTo("../../backups.xhtml?styleGuide=" + styleGuide + 
"#" + docId, true);


   } catch( ex ) {
  cocoon.log.error(ex);
// Smth. went wrong. Sending a error.txt file to the browser
  cocoon.sendPage("backups/save_file_error.txt", null);
   }
}

All help appreciated,
Martin



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

Passing parameters into XQuery

[Martin Holmes]

HI there,

Using Cocoon 2.1.10:

I'm trying to pass the value of the original URI requested by the 
browser into an XQuery generator, and I have two problems. First, I 
can't seem to pass any parameter value into the XQuery at all:






The parameter doesn't make it into the XQuery, for some reason. (GET 
values from the URI are all available, though.)


Secondly, I'm not sure how to get the full URI of the page. With a match 
pattern like this:






[...]


where the URL might have a long search string:

http://...stuff/contents.xml?sort=date_asc&author=smith&vol=39

what would I use to retrieve the full URL?

All help appreciated,
Martin


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

Odd image problem

[Martin Holmes]

Hi folks,

Using Cocoon 2.1.10, with this matcher in my sitemap:


  


When I access the URL of one of the images in Firefox, it downloads the 
image to my temp directory and opens it from there (so the URL bar shows 
file:///[temp_folder]...). When I access it through IE7, it shows me the 
image directly from the server (so the address bar shows http://...).


Can anyone suggest why this might be happening? It's as if the server 
isn't telling the browser what the mime type is properly, so Firefox is 
downloading the file and opening it locally.


Cheers,
Martin


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

Re: map:match question

[Martin Holmes]

Dominic Mitchell wrote:

Your URLs are constructed incorrectly.  Everything after the hash should 
never get sent to the server.  It's purely for use by the browser.  You 
need to set them up like this:


   .../article.htm?id=EMLS3-2FITTNOCT&searchString=nocturne#hit10


Doh! That's it. Works a treat now.

Thanks,
Martin


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

map:match question

[Martin Holmes]

I'm having trouble getting a match to trigger when the URL has a hash 
followed by a query string. This is my match pattern:




It works fine when the url is something like this:

...article.htm?id=EMLS3-2FITTNOCT&searchString=nocturne

but not if the URL is like this:

...article.htm#hit10?id=EMLS3-2FITTNOCT&searchString=nocturne

In other words, the presence of the #hit10 hash component in the url 
causes the match to fail. I've tried variations such as


article.htm | article.htm#*

but I can't get any of them to match.

What's the right way to do this?

All help appreciated,
Martin


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

Re: Sitemap problem with 2.1.7

[Martin Holmes]

Lars Huttar wrote:

Martin Holmes wrote:

...
However, if I comment out the matcher in the root sitemap, then my 
matcher works, and the resource is correctly retrieved from 
.../katakana/css/style.css.


Does anyone know what could be causing this? I thought sitemaps always 
cascaded downwards, with subfolder sitemaps overriding any similar 
settings in sitemaps further up the tree.
I would expect that to depend on whether the super-sitemap's  
for the subsitemap occurs before or after its .
Is the relative order of those two different, between Cocoon 2.1.7 and 
your older version?


That was it! The old Cocoon was auto-mounting all sitemaps after its own 
match elements, but the new one had the default mount catch-all before 
these matches, for some reason.


Cheers,
Martin


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

Sitemap problem with 2.1.7

[Martin Holmes]

Hi there,

I'm moving a project from an old version of Cocoon to Cocoon 2.1.7, and 
I've hit a very odd sitemap problem. The root sitemap for Cocoon has 
this matcher:



  


My project resides in a subfolder called "katakana", and it has this 
matcher:



  


In the old version of Cocoon, the matcher in my sitemap was happily 
overriding the matcher in the root sitemap, so any call for this file:


.../katakana/style.css

would result in the resource being retrieved from:

.../katakana/css/style.css


In 2.1.7, though, it appears that the root sitemap is overriding my 
project sitemap. Any call for


.../katakana/style.css

tries to retrieve the resource from .../katakana/style.css, and fails.

However, if I comment out the matcher in the root sitemap, then my 
matcher works, and the resource is correctly retrieved from 
.../katakana/css/style.css.


Does anyone know what could be causing this? I thought sitemaps always 
cascaded downwards, with subfolder sitemaps overriding any similar 
settings in sitemaps further up the tree.


All help appreciated,
Martin


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

Re: Cocoon XSLT and schema documents

[Martin Holmes]

Doh!

Thanks for this. I guess I have a long job trawling through my 
stylesheets to add the namespace prefix.


Cheers,
Martin

Andrew Stevens wrote:

From: Martin Holmes <[EMAIL PROTECTED]>
Date: Thu, 26 Jan 2006 10:54:16 -0800

Hi there,

I have some XML documents (TEI P5) that start like this:

http://www.tei-c.org/ns/1.0";


setting the element's namespace to http://www.tei-c.org/ns/1.0, I notice

...
When XSLT transformations are run against them, no templates are 
applied, so plain text is all that shows up. However, when I remove 
all the attributes from the root element:




the transformations work fine.


My guess is your XSL tempates don't include the namespaces, so are 
looking to match elements in the default (i.e. no) namespace?




Oops, hit the wrong key.  Should have been

http://www.w3.org/1999/XSL/Transform";
xmlns:tei="http://www.tei-c.org/ns/1.0";>

Matches.


Doesn't match.


Doesn't match either.



or something along those lines.  Also keep in mind the actual prefixes 
used don't matter, it's the namespace URIs that need to match.



Andrew.



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

Cocoon XSLT and schema documents

[Martin Holmes]

Hi there,

I have some XML documents (TEI P5) that start like this:

http://www.tei-c.org/ns/1.0"; version="5.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 imt_p5.xsd" 
xmlns:svg="http://www.w3.org/2000/svg";>


When XSLT transformations are run against them, no templates are 
applied, so plain text is all that shows up. However, when I remove all 
the attributes from the root element:




the transformations work fine. Does anyone know why this might be? I see 
the same behaviour in oXygen, so it's most likely something I'm doing 
wrong rather than a Cocoon problem, but the documents validate just fine.


All help appreciated,
Martin


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

Re: Generating plain text on Cocoon 2.1.6

[Martin Holmes]

I now have a working system, and in case anyone else has the same 
problem, this is what I had to do:

1. Use an absolutely minimal xsl:output element in the stylesheet:

2. Create my own serializer based on the standard text serializer, but 
with a new name and an explicit encoding parameter:

	
	name="utf8text" 	
		src="org.apache.cocoon.serialization.TextSerializer">

UTF-8

3. Use that serializer in my map:match:
 
No other combination (and I tried virtually everything!) would work 
properly; some caused the null pointer exception in Xalan, some resulted 
in empty XML documents, and some tripped up when encountering a 
character with a codepoint above 255.

This was Cocoon 2.1.6 running on Tomcat 5.5, with Java 1.5.
Hope this helps someone!
Martin
Martin Holmes wrote:
Hi there,
When I switch to the XML serializer, I get an empty XML document:

with no root element, and the wrong encoding.
This is strange; something must be throwing the Xalan parser for a loop, 
but there's nothing weird at all in the XSL as far as I can see; it's 
adapted from another file which works fine on a different installation 
of Cocoon (2.1.5). I've copied the XSLT below -- can anyone see anything 
wrong here?


http://www.w3.org/1999/XSL/Transform";
  version="1.0">

   












  

  []
  


  












  



  
•
  
  
.
  




  

 
   
 
   [Note : ]
 
 
   
 
   
 
  "" ()
  

  


  
  
  


    
  

  
    


  



Cheers,
Martin

Upayavira wrote:
Martin Holmes wrote:
I'm having problems generating plain text output (utf-8) on Cocoon 
2.1.6. I get a NullPointerException. The scenario is:

  




  
The XML files are UTF-8 and the XSL file starts out like this:


 type="text/plain"
 



The XSL works fine running locally in oXygen with Saxon 6.5.3. I've 
tried removing the processing instruction, but it makes no 
difference. I've also tried adding a UTF-8 text serializer to the 
sitemap like this:


name="text" 
src="org.apache.cocoon.serialization.TextSerializer">
UTF-8
  

but no joy.
I've included the top few lines of the stack trace below. Can anyone 
suggest what the problem might be?

Thanks for the other stack trace. Unfortunately, those ones are 
usually very difficult to debug, as the error shows up in Xalan as a 
null pointer exception, which was actually triggered by something much 
further back in the pipeline.

Now, have you tried replacing  with 


What do you see? Does it produce your text content, but wrapped in XML?
Also, the processing instruction, to my knowledge, won't make any 
difference. It looks like a Cocoon 1.x instruction, that Cocoon 2 
doesn't know about. Configuration like that happens in the sitemap, 
not in processing instructions.

Regards, Upayavira

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

Re: Generating plain text on Cocoon 2.1.6

[Martin Holmes]

Nailed it!
I had this in my stylesheet:

Changing it to

("type" instead of "method") solves the problem!
But that shouldn't be, should it? According to XSLT 1.0 and 2.0, the 
attribute should be "method". Am I missing something here?

Cheers,
Martin
Upayavira wrote:
Martin Holmes wrote:
I'm having problems generating plain text output (utf-8) on Cocoon 
2.1.6. I get a NullPointerException. The scenario is:

  




  
The XML files are UTF-8 and the XSL file starts out like this:


 type="text/plain"
 



The XSL works fine running locally in oXygen with Saxon 6.5.3. I've 
tried removing the processing instruction, but it makes no difference. 
I've also tried adding a UTF-8 text serializer to the sitemap like this:


UTF-8
  
but no joy.
I've included the top few lines of the stack trace below. Can anyone 
suggest what the problem might be?

Thanks for the other stack trace. Unfortunately, those ones are usually 
very difficult to debug, as the error shows up in Xalan as a null 
pointer exception, which was actually triggered by something much 
further back in the pipeline.

Now, have you tried replacing  with 


What do you see? Does it produce your text content, but wrapped in XML?
Also, the processing instruction, to my knowledge, won't make any 
difference. It looks like a Cocoon 1.x instruction, that Cocoon 2 
doesn't know about. Configuration like that happens in the sitemap, not 
in processing instructions.

Regards, Upayavira

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

Re: Generating plain text on Cocoon 2.1.6

[Martin Holmes]

Hi there,
When I switch to the XML serializer, I get an empty XML document:

with no root element, and the wrong encoding.
This is strange; something must be throwing the Xalan parser for a loop, 
but there's nothing weird at all in the XSL as far as I can see; it's 
adapted from another file which works fine on a different installation 
of Cocoon (2.1.5). I've copied the XSLT below -- can anyone see anything 
wrong here?


http://www.w3.org/1999/XSL/Transform";
  version="1.0">













  

  []
  


  
	

	









  



  
•
  
  
.
  




  

 
   
 
   [Note : ]
 
 
   
 
   
 
  "" ()
  

  


  
  
  



  

  



  

    

Cheers,
Martin

Upayavira wrote:
Martin Holmes wrote:
I'm having problems generating plain text output (utf-8) on Cocoon 
2.1.6. I get a NullPointerException. The scenario is:

  




  
The XML files are UTF-8 and the XSL file starts out like this:


 type="text/plain"
 



The XSL works fine running locally in oXygen with Saxon 6.5.3. I've 
tried removing the processing instruction, but it makes no difference. 
I've also tried adding a UTF-8 text serializer to the sitemap like this:


UTF-8
  
but no joy.
I've included the top few lines of the stack trace below. Can anyone 
suggest what the problem might be?

Thanks for the other stack trace. Unfortunately, those ones are usually 
very difficult to debug, as the error shows up in Xalan as a null 
pointer exception, which was actually triggered by something much 
further back in the pipeline.

Now, have you tried replacing  with 


What do you see? Does it produce your text content, but wrapped in XML?
Also, the processing instruction, to my knowledge, won't make any 
difference. It looks like a Cocoon 1.x instruction, that Cocoon 2 
doesn't know about. Configuration like that happens in the sitemap, not 
in processing instructions.

Regards, Upayavira

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

Re: Generating plain text on Cocoon 2.1.6

[Martin Holmes]

Upayavira wrote:
you need to show more of the exception stack trace. the bit you showed 
wasn't the bit that actually held the error.
Sorry -- here's the full thing:
org.apache.cocoon.ProcessingException: Error executing pipeline.: 
java.lang.RuntimeException: java.lang.NullPointerException

cause: java.lang.RuntimeException: java.lang.NullPointerException
full exception chain stacktrace[hide]
org.apache.cocoon.ProcessingException: Error executing pipeline.: 
java.lang.RuntimeException: java.lang.NullPointerException
	at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.handleException(AbstractProcessingPipeline.java:825)
	at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:270)
	at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:468)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:120)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:138)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:89)
	at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:240)
	at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:180)
	at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:243)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:138)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:89)
	at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:240)
	at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:180)
	at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:243)
	at org.apache.cocoon.Cocoon.process(Cocoon.java:606)
	at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1119)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
	at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
	at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
	at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
	at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
	at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
	at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
	at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
	at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
	at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:825)
	at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:738)
	at 
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:526)
	at 
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
	at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
	at 
org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3418)
	at 
org.apache.xalan.transformer.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:389)
	at 
org.apache.cocoon.xml.AbstractXMLPipe.endDocument(AbstractXMLPipe.java:55)
	at 
org.apache.cocoon.transformation.TraxTransformer.endDocument(TraxTransformer.java:562)
	at 
org.apache.cocoon.xml.AbstractXMLPipe.e

Generating plain text on Cocoon 2.1.6

[Martin Holmes]

I'm having problems generating plain text output (utf-8) on Cocoon 
2.1.6. I get a NullPointerException. The scenario is:

  




  
The XML files are UTF-8 and the XSL file starts out like this:


type="text/plain"




The XSL works fine running locally in oXygen with Saxon 6.5.3. I've 
tried removing the processing instruction, but it makes no difference. 
I've also tried adding a UTF-8 text serializer to the sitemap like this:


UTF-8
  
but no joy.
I've included the top few lines of the stack trace below. Can anyone 
suggest what the problem might be?

org.apache.cocoon.ProcessingException: Error executing pipeline.: 
java.lang.RuntimeException: java.lang.NullPointerException
	at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.handleException(AbstractProcessingPipeline.java:825)
	at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:270)
	at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:468)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:120)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:138)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:89)
	at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:240)
	at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:180)
	at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:243)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:117)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:138)
	at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68)
	at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:89)

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

Re: Missing xml declaration and doctype when using XQuery

[Martin Holmes]

Answering my own question, in case anyone else has the same problem:
My XQuery was returning this:


{f:GetDoc()}

If I make it return this:



{f:GetDoc()}


Then it works. Apparently the container tag is required before the 
doctype headers will be generated.

Cheers,
Martin
Martin Holmes wrote:
Hi there,
I have the following two matches in my pipeline:

  




  

  






  
In the case of the first, I get this at the top of my XHTML output 
document:


http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml";>
In the case of the second, I get nothing before the HTML tag:
http://www.w3.org/1999/xhtml";>
Can anyone suggest why this might be the case? In the first case, the 
XML input to the transformation is taken from a file, and in the second, 
it's taken from the an eXist database via XQuery, but there's no other 
difference in the pipelines -- same transformation, same serialization. 
The second has an "encodeURL" transform, but even if I remove that, it 
makes no difference. I'd really like to be producing good XHTML from 
this application. Any ideas?

All help appreciated.
Cheers,
Martin

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

Missing xml declaration and doctype when using XQuery

[Martin Holmes]

Hi there,
I have the following two matches in my pipeline:

  




  

  






  
In the case of the first, I get this at the top of my XHTML output document:

http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml";>
In the case of the second, I get nothing before the HTML tag:
http://www.w3.org/1999/xhtml";>
Can anyone suggest why this might be the case? In the first case, the 
XML input to the transformation is taken from a file, and in the second, 
it's taken from the an eXist database via XQuery, but there's no other 
difference in the pipelines -- same transformation, same serialization. 
The second has an "encodeURL" transform, but even if I remove that, it 
makes no difference. I'd really like to be producing good XHTML from 
this application. Any ideas?

All help appreciated.
Cheers,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Authentication and sessions

[Martin Holmes]

Hi there,
I'm working on a simple authentication system based on the 
authentication-fw example, and everything is working fine as long as 
cookies are turned on in the browser. As soon as cookies are turned off, 
authentication becomes lost. I'm using the following elements in each of 
my sitemap pipelines:

  
  
but nothing is being encoded in the URL for some reason. Is there 
anything else I need to do to get the session id to be carried by the 
URL instead of in cookies?

All help appreciated,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Authentication map problem

[Martin Holmes]

That did it! Many thanks indeed. Now I'll have to figure out what it 
means to put a path statement inside the parentheses -- I've never seen 
that before.

Cheers,
Martin
Ralph Goers wrote:
Replace {1} with {../1}. The way you have it the sitemap is attempting to
locate the file name in the map returned from the auth-protect action
instead of from the * in the map:match.
Ralph
Martin Holmes said:
Hi there,
I'm trying to adapt the authentication-fw example for my own use, and
I'm hitting a problem. The example uses only one file ("protected.xml"),
which is defined explicitly in the sitemap match element. I'm trying to
protect all the documents in a folder, like this:


  
  
  
  
  
  



  
This code is adapted directly from the example match element, with just
a few changes to accommodate my document type. When I try this, browsing
to the url  after being authenticated,
I get the following error:
org.apache.cocoon.ResourceNotFoundException: Resource not found.:
org.apache.excalibur.source.SourceNotFoundException:
file:/usr/local/jakarta-tomcat-5/webapps/cocoon/authentication-fw/test/.xml
doesn't exist.
However, if I replace the "*" and {1} parameters with actual file names
from the folder, everything works fine. Can anyone see why the wildcard
matching would fail in this match element?
Cheers,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


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

Authentication map problem

[Martin Holmes]

Hi there,
I'm trying to adapt the authentication-fw example for my own use, and 
I'm hitting a problem. The example uses only one file ("protected.xml"), 
which is defined explicitly in the sitemap match element. I'm trying to 
protect all the documents in a folder, like this:



  
  
  
  
  
  



  
This code is adapted directly from the example match element, with just 
a few changes to accommodate my document type. When I try this, browsing 
to the url  after being authenticated, 
I get the following error:

org.apache.cocoon.ResourceNotFoundException: Resource not found.: 
org.apache.excalibur.source.SourceNotFoundException: 
file:/usr/local/jakarta-tomcat-5/webapps/cocoon/authentication-fw/test/.xml 
doesn't exist.

However, if I replace the "*" and {1} parameters with actual file names 
from the folder, everything works fine. Can anyone see why the wildcard 
matching would fail in this match element?

Cheers,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Simple authentication example?

[Martin Holmes]

Hi there,
I'm just getting started with Cocoon and trying to figure out how to 
protect a pipeline with a very basic authentication method. The 
authentication-fw example is confusing me a bit -- I'm not sure what the 
relationship is between flow and authentication. Does anyone know of a 
very simple example or explanation somewhere? I just want to get a 
username and pw from a login form, check it against hardcoded strings, 
and protect a pipeline with it. I've read the doc here:


but I get lost around the point of "authentication-resource", which 
seems to assume I'll be using a Java class or an external resource for 
authentication.

Cheers,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]