gmane.text.xml.cocoon.user

CocoonJAXRSServlet

Jos Snellings — 2012-05-18T06:01:49

Dear all,

Cocoon-3 ordinary pipeline components offer a flexible way to organise
REST-full calls between services.
(REST, after all is a principle, not a framework).
However, curiosity drove me into setting up a small example of a JAX-RS
webservice.
1. with mvn jetty:run : works perfectly
2. as a block in a standalone war context, deployed to tomcat :
      java.lang.NoClassDefFoundError:
com/sun/jersey/spi/container/servlet/ServletContainer
This is configured in cocoon-rest. Does it need the jersey container or can
we get rid of it?

Kind regards,
Jos

Re: Cocoon 2.1 sitemap broken in Tomcat 6

Thorsten Scherler — 2012-05-17T18:56:30

yes

salu2

Cocoon 2.1 sitemap broken in Tomcat 6

Bob Harrod — 2012-05-17T17:32:05

We've recently upgraded our Cocoon 2.1 based web app from Tomcat 4 to
Tomcat 6.  Our sitemaps were written with a somewhat invalid matchers which
worked in Tomcat 4:

For example:

<map:match pattern="/basicthing">
...
</map:match>


Tomcat 6 more adequately adheres to the HTTP URL spec and appends a
trailing slash.  Of course, the trailing slash breaks the matcher above.
The following matcher would work in Tomcat 6 but breaks all of the matchers
for Tomcat 4:

<map:match pattern="/basicthing/">
...
</map:match>


To avoid duplication, I've written a matcher to catch this case to avoid
duplicating matchers:

<map:match pattern="*/">
    <map:redirect-to uri="cocoon:/{1}"/>
</map:match>


While this works for the basic case, it is not recursive, and as soon as a
url pattern goes past basic thing (/basicthing/morethings/), I need another
matcher to catch this case ("*/*/").

Is there a way to create a recursive matcher in cocoon to catch multiple
slashes and end at a trailing slash?  I'm thinking something lik

Re: Cocoon 2.1 web application base path

Christopher Schultz — 2012-05-17T16:02:30

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andy,

On 5/16/12 12:36 PM, Andy Stevens wrote:

+1

IMO this is the right way to do things.

If you want a completely, fully-absolute URL, you might want to:

 <map:parameter name="requestScheme" value="{request:scheme}" />
 <map:parameter name="requestServerName" value="{request:serverName}" />
 <map:parameter name="requestServerPort" value="{request:serverPort}" />

 <map:parameter name="context-path" value="{request:contextPath}" />
 <map:parameter name="request-uri" value="{request:requestURI}" />
 <map:parameter name="query-string" value="{request:queryString}" />

We have a bunch of XSL templates that produce XHTML and need to
provide references back to themselves in certain circumstances. So, we
pass everything and the template can build as much of the URL as it
chooses in a case-by-case basis.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http:/

Re: Cocoon 2.1 web application base path

Bob Harrod — 2012-05-17T14:01:19

Including {request.contextPath} as a transform param did the trick, thanks!

Is there any way to do this globally for all matches in the sitemap or does
it have to be passed to each transform?

- Bob
On May 16, 2012 12:53 PM, "Bob Harrod" <rjharrod< at >gmail.com> wrote:

Re: Cocoon 2.1 web application base path

Javier Puerto — 2012-05-16T19:44:33

2012/5/16 Bob Harrod <rjharrod< at >gmail.com>


It's included as a block for cocoon-2.1 and it's builded with cocoon-2.1 by
default but I've used it for Cocoon 2.2 & 3 so I'm not sure how to
configure it. I remember that you have to declare the component at the
beginning of the sitemap before use it. You can browse the block code and
samples for linkrewritter here

http://svn.apache.org/viewvc/cocoon/tags/cocoon-2.1/RELEASE_2_1_11/src/blocks/linkrewriter/

Or even better, download the sources and play a bit with the samples :)

http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.1/RELEASE_2_1_11



The LinkRewriterTransformer is a transformer component for pipeline process
and must be used from a sitemap context. You should place the transformer
in the pipeline so the links get transformed to the right location, usually
at the end of the pipeline before the serializer.

<map:pipeline>
...

  <map:match pattern="welcome">
    <map:generate src="welcome.xml">
    <map:transform src="xslt/xml2page.xsl"/> <!-- your

Re: Cocoon 2.1 web application base path

Bob Harrod — 2012-05-16T16:53:40

Ok, thank you!  I can look at the LinkRewriterTransformer.  Since I'm new
to this, I have some follow up questions:

1. Is this a "plugin" that I have to install or does it exist in the stock
version of cocoon 2.1?

2. The examples reference the transformer from a sitemap context.  Is there
a way to use the LinkRewriterTranformer directly from another transform (as
this transform is actually creating the anchor)?

Thanks so much for your help.

- Bob


On Wed, May 16, 2012 at 10:24 AM, Bob Harrod <rjharrod< at >gmail.com> wrote:

Re: Cocoon 2.1 web application base path

Andy Stevens — 2012-05-16T16:36:25

Hi Bob,

Assuming you have the request input module in your cocoon.xconf, then you
can pass the context path into an xsl:param (or otherwise use in the
sitemap) with e.g.
<map:transform src="mytransform.xslt">
<map:parameter="xslParamName" ="{request:contextPath}"/>
</map:transform>

Regards,

Andy
 On 16 May 2012 06:02, "Bob Harrod" <rjharrod< at >gmail.com> wrote:

Re: Cocoon 2.1 web application base path

Javier Puerto — 2012-05-16T14:45:33

Hi Bob

2012/5/16 Bob Harrod <rjharrod< at >gmail.com>


I think that you want to use the LinkRewriterTransformer

http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/transformation/LinkRewriterTransformer.html

I hope that it's helps.

Salu2.

Re: Cocoon 2.1 web application base path

Bob Harrod — 2012-05-16T14:24:29

I'm rending html in a transform, and would like to render an anchor who's
href is absolute, not relative.  For example, instead of this:

<a href="../home">...</a>

I would like to be able to provide a full url in the href:

<a href="http://mysite/application1/home">...</a>

Thank you for your assistance with this!


On Wed, May 16, 2012 at 12:52 AM, Bob Harrod <rjharrod< at >gmail.com> wrote:

Re: Cocoon 2.1 web application base path

Jos Snellings — 2012-05-16T05:03:50

Hi !

What are you trying to achieve?

Jos

On Wed, May 16, 2012 at 6:52 AM, Bob Harrod <rjharrod< at >gmail.com> wrote:

Cocoon 2.1 web application base path

Bob Harrod — 2012-05-16T04:52:24

I'm quite new to cocoon, and supporting an older version (2.1).  Does
anyone know how I can gain access the web application base path inside of a
transform?  Of course, it can be passed by the sitemap...  Any help would
be appreciated!

Thanks!

RE: Bug in servlet service framework C2.2?? [SOLVED]

Robby Pelssers — 2012-05-15T13:24:24

Just wanted to reply on my own question.  I did a bit of out-of-the-box thinking and came up with a even nicer solution for my particular use case.

Basically all that servlet service does is exposing that XSLT to all cocoon blocks using that have a dependency on this shared module.  And I might add it's doing this in a tedious way.

Remember my original service pattern?  It was first of all tedious to pass on parameters to it and secondly it just doesn't work if the serializer is not of < at >type XML.

            <map:match pattern="csv-transformation-service/*">
              <map:generate src="service-consumer:"/>
              <map:transform src="xslt/csv_transformer.xslt" type="saxon">
                <map:parameter name="separator" value="{1}"/>
              </map:transform>
              <map:serialize type="text"/>
            </map:match>

Invocation from this service looked like this:

      <map:match pattern="test-csv-transformer-service">
          <map:generate src="data/csv_generator_testdata.xm

Bug in servlet service framework C2.2??

Robby Pelssers — 2012-05-15T10:35:47

Hi all,

As an important side note.  I've run into a serious limitation a few times already.

Let me explain shortly what I try to do.

I want to e.g. generate an XML representation of CSV data from an XQuery generator.  I borrowed the schema from the CSV generator and dropped some attributes which are not useful.

<?xml version="1.0" encoding="ISO-8859-1"?>
<csv:document xmlns:csv="http://apache.org/cocoon/csv/1.0">
    <csv:header>
        <csv:column>Column A</csv:column>
        <csv:column>Column B</csv:column>
        <csv:column>Column C</csv:column>
    </csv:header>
    <csv:record>
        <csv:field>Field A1</csv:field>
        <csv:field>Field B1</csv:field>
        <csv:field>Field C1</csv:field>
    </csv:record>
    <csv:record>
        <csv:field>Field A2</csv:field>
        <csv:field>Field B2</csv:field>
        <csv:field>Field C2</csv:field>
    </csv:record>
</csv:document>

Next I wrote a XSLT that transforms this into a CSV file.

<?xml version="1.0" encoding="UTF-8"?>
<!--
Author: Rob

how to pass parameters to a service transformer

Robby Pelssers — 2012-05-15T10:15:26

Hi all,

I've got a question regarding the service transformer.  How do I pass any parameters to the service?  The demo from get-started page is not clear on this topic.


<map:match pattern="custom-transformation-service/*">
  <map:generate src="service-consumer:"/>
  <map:transform src="xslt/custom_transformer.xslt" type="saxon">
    <map:parameter name="separator" value="{1}"/>
  </map:transform>
  <map:serialize type="xml"/>
</map:match>

<!--
Currently I pass on the parameter by extracting the separator from the match pattern
but is there another way?  First of all i'm asking because i foresee issues in doing it this way.
 Secondly I see use cases where I need to pass a bunch of parameters and i don't want ugly match patterns.
Suppose I want to pass on two URL's as parameters, I'm already blocked  with this approach.
-->
<map:match pattern="test-csv-transformer-service">
  <map:generate src="data/testdata.xml"/>
  <map:transform type="servletService">
    <map:parameter name="service" value="servlet:sha

Re: mount named blocks inconvenience

Jos Snellings — 2012-05-11T11:50:20

O yes, Francesco, that is in every way a good workaround.
Thanks,
Jos

On Fri, May 11, 2012 at 12:43 PM, Francesco Chicchiriccò <
ilgrosso< at >apache.org> wrote:

Re: mount named blocks inconvenience

Francesco Chicchiriccò — 2012-05-11T10:43:19

I've seen this since my first experiments with Cocoon 2.0 (and I am sure 
that if you search archives you would also get some better reply than 
this...): basically,

http://localhost/mywebapp/foo

and

http://localhost/mywebapp/foo/

are two different HTTP resources; the root of matching for a given block 
(i.e. "<map:match pattern="">) will always get not more than "foo/".

If you want to match http://localhost/mywebapp/foo, I think you'll have 
to mount something at root (say a 'bar' block)

<servlet:context mount-path="" context-path="blockcontext:/bar"/>

then inside this bar block have

<map:match pattern="foo">
...


I hope all this is "formally" correct: if not, it's the way I've been 
following so far ;-)
Regards.

mount named blocks inconvenience

Jos Snellings — 2012-05-10T11:05:05

Dear cocooners,

Problem:
1. In the definition of a named block, for:
    <servlet:context mount-path="/foo" context-path="blockcontext:/foo/"/>

This tells the cocoon servlet that a block "foo" is mounted on "foo" in the
webapp.

2. sitemap.xmap
  An empty matcher like in the cocoon sample:
 <map:match pattern="">
            <map:read src="welcome.html" mime-type="text/html"/>
  </map:match>

3. call
    localhost/mywebapp/foo

   or, the root of the block. (it is configured correctly, all the rest
works).

EVENT:  exception:

For named blocks
java.lang.StringIndexOutOfBoundsException: String index out of range: 0 at
java.lang.String.charAt(String.java:687) at
org.apache.cocoon.sitemap.node.MatchNode.invoke(MatchNode.java:89)

Without having it investigated in extenso, it seems that when blocks are
named, so not mounted as 'root block', that there is a problem with
<excerpt>
String testValue = resolvedValue == null
                ? null : resolvedValue.toString();
        if (testValue == null) {

fop fonts

Jos Snellings — 2012-05-07T08:04:16

Dear group,

In C3,
I need to load extra fonts for FOP. The default set cannot display cyrillic
characters,
and greek characters with diacritics.
Where would one put them best?
What is best to configure the fopFactory? Where should the configuration
file be?

Just before I experiment a bit to find it out, probably somebody out there
knows the answer.

Thank you !
Jos

Re: log levels

Jos Snellings — 2012-05-02T15:06:17

OK, that is good news.
Thank you, Thorsten.
Jos


On Wed, May 2, 2012 at 3:27 PM, Thorsten Scherler <scherler< at >gmail.com>wrote:

Re: log levels

Thorsten Scherler — 2012-05-02T13:27:25

If you talk about current beta log4j has been droped. Create a 
src/main/resources/logback.xml (when target is war deploy) or 
cl-config/WEB-INF/classes/logback.xml (when you use jetty:run) in your 
project and c3 will use that.

HTH

salu2