headers
Robby Pelssers | 3 Feb 10:16
Favicon

question regarding Apache infrastructure

Hi all,

 

I know in the past there was a Cocoon demo app running showing most features of Cocoon.  Is it still possible to host a demo app on Apache infrastructure? And if so, are there any docs out there explaining the conditions and how-to’s?

 

Kind regards,

Robby

Permalink | Reply | 1 comment |
headers
Thorsten Scherler | 19 Jan 10:56
Picon

[c3] XincludeTransformer.java weirdness

Hi all,

in
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/component/XIncludeTransformer.java

we do

import org.apache.cocoon.sax.xpointer.ParseException;
...
import org.apache.cocoon.sax.xpointer.XPointerFrameworkParser;

but in
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/xpointer/

There is no such classes.

I do not understand since we can build with cli without problems. In 
eclipse I can fix the project setup by adding the cocoon-sax beta jar to 
the classpath. However that is the same jar as the project, which does 
not make sense at all.

Somebody has an idea?

salu2

--

-- 
Thorsten Scherler<scherler.at.gmail.com>
codeBusters S.L. - web based systems
<consulting, training and solutions>

http://www.codebusters.es/
Permalink | Reply | 3 comments |
headers
Reinhard Pötz | 19 Jan 09:09
Picon
Favicon

[c3] Pipeline API refactoring


As I mentioned several times I think we should polish the pipeline API 
before we do our first beta release of Cocoon 3. Especially the enforced 
resutl type "OutputStream" and the exception handling need some 
improvements.

For that purpose I created a branch "c3-pipeline-api-refactoring" in our 
whiteboard 
(https://svn.apache.org/repos/asf/cocoon/whiteboard/c3-pipeline-api-refactoring/) 
so that our discussions don't become too theoretical ;-)

That branch only contains a minimum set of classes so that we see the 
effects of a proposed change on real code but don't have to change the 
whole codebase just for some examples that might be thrown away.

Steven and I plan to continue our work some time next week. We will 
commit our changes then and explain them on the mailing list for further 
discussions.

--

-- 
Reinhard Pötz         Founder & Managing Director, Indoqa and Deepsearch
                         http://www.indoqa.com/people/reinhard-poetz.html

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
________________________________________________________________________

       Furthermore, I think Oracle has to honor the JSPA agreement.
     http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap
Permalink | Reply | 1 comment |
headers
David Crossley | 16 Jan 14:21
Picon
Favicon

resurrect the Cocoon documentation

TL;DNR
Use the Apache CMS for at least our top-level docs
and the stalled 2.1 and 2.2 docs.

However, i cannot actually do this work, just explain and guide.

I have done some background research to try to gather the
various past threads and docs. Perhaps this will help us to
bring the Cocoon documentation back to life.

In the past we had the sources for the docs in xml format
and then processed by Apache Forrest to generate the html pages.

A few years ago we moved to using the Daisy CMS to store/edit
all content for 2.1 and 2.2 versions, as well as the top-level
project non-version-specific stuff.

For Cocoon-2.2, and the top-level stuff, the Maven site plugin
extracted the content from Daisy and generated the html pages. [4]

For Cocoon-2.1, the Forrest plugin "Daisy input plugin" extracted
the content from Daisy and generated the html pages. [5]

For Cocoon-3, the source content is stored in xml files
and the Maven site plugin generates the html pages.

All generated html was (and still is) committed to the
Cocoon "site" SVN [1].

Then 'svn up' on the people.apache.org machine does the
publishing step. (Later that step could move to using svnpubsub.)

The Daisy server operated on our Zones machine cocoon.zones.apache.org
(which also housed the demonstrations for Cocoon 2.1 and 2.2).
The Zones server is managed by the Cocoon project. See [2].

However, the machine that provided the zones for a set of
projects needed to be upgraded. The Cocoon project did not
move our services in time.
IIRC we do now have a "freebsd jail" which is basically configured,
but not yet re-installed Daisy or Cocoon demo examples,
nor the web server.
IIRC we did get a backup of the Daisy data [3] if that helps.

The Forrest forrestbot neededi to be turned off, as it could not
access the source content for the 2.1 documentation.

For the 2.2 documentation, i presume that Maven also has troubles.

So unless someone can re-instate the new cocoon.zones.apache.org
and the Daisy server, then we need some other solution.

Suggestion to use the Apache CMS:

One other solution would be to use the new Apache CMS. [7]

It can have source content in either Markdown format
or in HTML format and perhaps others.

To resurrect the content, we might be able to use the
last published "generated" set of html documents, strip off
the outer headers and menu stuff, replace with basic header,
and use that set of content to seed the CMS.

--------------------
(Some of these resources are only available to Cocoon PMC members.)

[1] http://svn.apache.org/repos/asf/cocoon/site/site/

[2] http://svn.apache.org/repos/private/pmc/cocoon/cocoon.zones.apache.org/

[3] Search the PMC archive for various email from Bertrand

[4] http://cocoon.apache.org/1418_1_1.html
How to publish docs to cocoon.apache.org
(i.e. for Cocoon-2.2 and the top-level of c.a.o)

[5] http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
How to publish Cocoon-2.1 docs

[7] Apache CMS
http://wiki.apache.org/general/ApacheCms2010
http://wiki.apache.org/general/ApacheCMSFAQ
http://www.apache.org/dev/cmsref.html
Permalink | Reply | 0 comments |
headers
Wolfram Eisert | 16 Jan 12:51
Favicon

Porting to current cocoon version

Dear List,


we are currently using Cocoon 2.0.4 and plan to update to a newer version during this year.

For that I have a few questions:
  • Does it make sense to wait for Cocoon 3.0?
  • Is the configuration compatible between Cocoon 2.2 and Cocoon 3.0?
  • Is there a "howto" for moving from Cocoon 2.0.4 to a current Version?
Thank you for your answers.

Wolfram
Permalink | Reply | 8 comments |
headers
Simone Tripodi | 10 Jan 11:17
Picon
Favicon

[JIRA] add more karma to Cedric and Robby

Good morning all,

I'm here to kindly ask if some of us has enough powers to give more
karma on JIRA to our new PMC members Cedric (cedric) and Robby
(robbypelssers).

I cc-ed Reinhard because he added Francesco and I so at 90% he can
help us (sorry for the noise Reinhard!)

Many thanks in advance, all the best!
-Simo

http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
Permalink | Reply | 2 comments |
headers
Robby Pelssers (Created) (JIRA | 6 Jan 16:26
Picon
Favicon

[jira] [Created] (COCOON3-88) Add JavaWrapper for JsLint to the project

Add JavaWrapper for JsLint to the project
-----------------------------------------

                 Key: COCOON3-88
                 URL: https://issues.apache.org/jira/browse/COCOON3-88
             Project: Cocoon 3
          Issue Type: Improvement
          Components: cocoon-optional
    Affects Versions: 3.0.0-alpha-3
            Reporter: Robby Pelssers
            Priority: Minor

It might be useful to add validation for Javascript files to Cocoon3. 
http://code.google.com/p/jslint4java/

If there is a similar outstanding validator for CSS (csslint) ?? we could also consider to add this as well

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 0 comments |
headers
Robby Pelssers | 6 Jan 15:48
Favicon

HTML5 serializer

Hi all,

 

I’ve been looking at how to add a HTML5 serializer to the project.

 

So far my investigations have led to add following code to org.apache.cocoon.sax.component.XMLSerializer

 

    public static XMLSerializer createHTML5Serializer() {

        XMLSerializer serializer = new XMLSerializer();

 

        serializer.setContentType(TEXT_HTML_UTF_8);

        serializer.setDoctypePublic("XSLT-compat");

        serializer.setEncoding(UTF_8);

        serializer.setMethod(HTML);

 

        return serializer;

    }

 

 

Using the HTML5 serializer in a test to print the output:

 

    <at> Test

    public void testHTML5Serializer() throws Exception {

        ByteArrayOutputStream baos = new ByteArrayOutputStream();

 

        newNonCachingPipeline()

        .setStarter(

           new XMLGenerator("<html><head><title>serializer test</title></head><body><p>test</p></body></html>")

        )

        .setFinisher(XMLSerializer.createHTML5Serializer())

        .withEmptyConfiguration()

        .setup(baos)

        .execute();

 

        String data = new String(baos.toByteArray());

        System.out.println(data);

}

 

Would print

 

<!DOCTYPE html PUBLIC "XSLT-compat">

<html>

<head>

<META http-equiv="Content-Type" content="text/html; charset=UTF-8">

<title>serializer test</title>

</head>

<body>

<p>test</p>

</body>

</html>

 

 

I read a number of articles describing the issues with serializing html5 and so far this was the best I could come up with which is not 100% conforming due to

·         Non matching doctype although it will not break in the browser  à should be <!DOCTYPE html>

·         The charset should be <meta charset=”UTF-8”/> according to html5 spec

 

 

http://www.contentwithstyle.co.uk/content/xslt-and-html-5-problems/

http://www.w3schools.com/html5/tag_meta.asp

 

 

Does anyone have more knowledge on this subject?

 

Robby   

 

 

Permalink | Reply | 11 comments |
headers
Jean-Baptiste Onofré (Created) (JIRA | 6 Jan 14:53
Picon
Favicon

[jira] [Created] (COCOON3-87) Update Cocoon to be OSGi compliant

Update Cocoon to be OSGi compliant
----------------------------------

                 Key: COCOON3-87
                 URL: https://issues.apache.org/jira/browse/COCOON3-87
             Project: Cocoon 3
          Issue Type: Improvement
          Components: cocoon-controller, cocoon-databases, cocoon-monitoring, cocoon-pipeline,
cocoon-profiling, cocoon-rest, cocoon-sax, cocoon-servlet, cocoon-shiro, cocoon-sitemap,
cocoon-stax, cocoon-stringtemplate, cocoon-util, cocoon-webapp, cocoon-wicket
            Reporter: Jean-Baptiste Onofré
            Assignee: Jean-Baptiste Onofré

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Permalink | Reply | 2 comments |
headers
Robby Pelssers | 6 Jan 11:41
Favicon

cocoon-parent pom breaking build

Hi guys,

 

I think the cocoon-parent pom is causing issues.  But as I am using maven3 it might be wise that I don’t touch that file as it might break with others still using maven 2.

 

Can someone using maven 2 take a look if he finds errors in that pom?

 

Thx in advance,

Robby

Permalink | Reply | 5 comments |
headers
Jos Snellings | 6 Jan 08:43

revoke "where is org.apache.cocoon.components"

Dear Cocooners,

Sorry, sent message in title in haste;
answering my own question:

/org/apache/cocoon/cocoon-serializers-charsets/1.0.0

As "side module" it does not come with the distribution when getting the source code, that is why I did not see it.

Cheers,
Jos

Permalink | Reply | 0 comments |

Gmane