headers
Jos Snellings | 1 Dec 07:22
Picon

Re: Cocoon documentation

The documentation of cocoon-3 can be checked out as:
svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs

The cocoon community will be delighted at some good documentation.
Talking about community I fear such as an active community is to be
reestablished, so I think we'd better provide some sweet stuff.

What would Reinhard think of starting with as a table of contents?
I will be glad to write some documentation as well. I have some goose
feathers available after Christmas, when I will be through the
experience of creating a first app.

How about you? 
Jos

On Mon, 2009-11-30 at 08:07 -0500, Matt Whipple wrote:
> I'm a recent transplant to Cocoon (and Java), in particular because
> Cocoon 3 appears as though it is/will be closely in line with my own
> perspective on web application development.  I'm interested in
> contributing to the development of the framework itself, but likely
> won't be able to produce anything remotely useful  for a couple months
> as I familiarize myself with all of the related technologies. 
> 
> I've just read some of the attacks on the poor documentation of the
> project and the resulting difficult entry for those unfamiliar.  This
> is, of course, easily confirmed by the combination of woefully out of
> date references and dead links on the Web site (i.e. to the Daisy
> site).  As I am (obviously) hopeful to see Cocoon succeed, I certainly
> don't want it to become mired in isolation like so many good projects. 
>
(Continue reading)

Permalink | Reply | 11 comments |
headers
David Legg | 1 Dec 10:16
Picon

Re: [OT] [Job] Cocoon developer required (London)

in the HTML
Robby Pelssers wrote:
> What did you do to make it crash? ;-)  I can open the home page without
> any issues.
>   

I've tried it on another XP machine and an Ubuntu system and... Doh! 
both work fine.

I suspect my machine doesn't like the video object in the HTML for some 
reason.  I have performed video editing on it before so maybe I have an 
errant codec installed somewhere.

As you were! ;-)

Regards,
David Legg
Permalink | Reply | 0 comments |
headers
Matt Whipple | 1 Dec 12:23
Favicon

Re: Cocoon documentation


Jos Snellings wrote:
> The documentation of cocoon-3 can be checked out as:
> svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
>   
I stumbled upon the HTML deliverable of that on
http://people.apache.org/~reinhard/c3-ref/html/ after sending my email. 
I'd think it would be best if the official documentation focused on
being primarily a comprehensive reference with a quick bootstrap guide. 
A community documentation site could then supplement that with all the
typical tutorials/how-to's and tips & tricks which gets the reader where
he wants to be with a straightforward, minimalist approach which then
references the official docs and other more enlightening sources. 
Regular articles/blog entries could then highlight the activity in the
community, and the possibilities of various Cocoon components could be
showcased.  Guides to all of the overlapping processes which can be
[easily] extrapolated from existing material can be given a home so that
a potential new developer with a specific need is provided with an
apparent foot in the door.  Basically a site which presents a welcoming,
active community rather than seemingly a group of scattered people
developing in Cocoons and enabling me to make bad wordplay (such is the
price).  To that end, an agreed upon forum would be ideal. 
> The cocoon community will be delighted at some good documentation.
> Talking about community I fear such as an active community is to be
> reestablished, so I think we'd better provide some sweet stuff.
>
> What would Reinhard think of starting with as a table of contents?
> I will be glad to write some documentation as well. I have some goose
> feathers available after Christmas, when I will be through the
> experience of creating a first
(Continue reading)

Permalink | Reply | 10 comments |
headers
Steven Dolg | 1 Dec 16:55

Re: StringTemplateGenerator

Jos Snellings schrieb:
> Dear,
>
> Just a small question, testing:
> When I get:
> java.lang.NullPointerException
> 	at
> org.apache.cocoon.stringtemplate.StringTemplateGenerator.constructCacheKey(StringTemplateGenerator.java:75)
>
> I notice that StringTemplateGenerator has two constructors: one with a
> 'source' argument, and one without.
> The one without source argument is called.
> Does this make sense? Am I making a mistake in the sitemap?
> Here's the code:
>   <map:match pattern="testcases/{name}.st">
>       <map:generate src="testcases/{map:name}.st"
> type="string-template"/>
>        <map:serialize type="xhtml"/>
>   </map:match>
>   

Hi,

the two constructors serve two different purposes:
* the default contructor is used by the sitemap to assemble pipelines in 
the way described by the sitemap definition (so that one being called is 
expected in your case)
* the constructor with the source parameter is intended for the 
programmatic use (pure convenience)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Steven Dolg | 1 Dec 17:14

Re: REST / Can't find URLResponseBuilder

Johannes Lichtenberger schrieb:
> On Sun, 2009-11-29 at 07:32 +0100, Jos Snellings wrote:
>   
>> In the samples, a typical use of StringTemplate is shown: a page is to
>> be interpreted by the StringTemplate engine, and a number of properties
>> are passed via the hashtable.
>> The idea is that you would open a view on the object.
>> So, 
>> - the query points to a resource
>> - the controller decodes what the resource is and what you want (view
>> it, update it?)
>> - the way to view it could be: pass my resource to a StringTemplate
>> invocation:  new Page('stringtemplateinvocation',resource);
>>  
>> However, I have not tried to elaborate this so far. Shall I post it when
>> i have a useable example?
>>     
>
> Yes it would be great. My concern is that I don't want to display a
> template page. I want to process the request (the parameters Google
> Earth sends when zooming in) and within my Generator query a native XML
> database system and built the algorithmic logic inside the generator
> (what data out of the shreddered xml file is needed and has to be
> transformed with an XSLT stylesheet). So I basically know how RESTful
> webservices work, but I don't know how to use cocoon3 in this case (I
> assume new Page(...) isn't the right thing to return when I just want to
> pass the request params to my generator. So I don't want to use
> StringTemplate in this case (but it's nontheless a great thing). So the
> query points to a controller, which decides that it's a GET request
> (view) and passes the parameters on to my generator (which I still have
(Continue reading)

Permalink | Reply | 1 comment |
headers
Steven Dolg | 1 Dec 17:20

Re: REST / Can't find URLResponseBuilder

Steven Dolg schrieb:
> Johannes Lichtenberger schrieb:
>> On Sun, 2009-11-29 at 07:32 +0100, Jos Snellings wrote:
>>  
>>> In the samples, a typical use of StringTemplate is shown: a page is to
>>> be interpreted by the StringTemplate engine, and a number of properties
>>> are passed via the hashtable.
>>> The idea is that you would open a view on the object.
>>> So, - the query points to a resource
>>> - the controller decodes what the resource is and what you want (view
>>> it, update it?)
>>> - the way to view it could be: pass my resource to a StringTemplate
>>> invocation:  new Page('stringtemplateinvocation',resource);
>>>  
>>> However, I have not tried to elaborate this so far. Shall I post it 
>>> when
>>> i have a useable example?
>>>     
>>
>> Yes it would be great. My concern is that I don't want to display a
>> template page. I want to process the request (the parameters Google
>> Earth sends when zooming in) and within my Generator query a native XML
>> database system and built the algorithmic logic inside the generator
>> (what data out of the shreddered xml file is needed and has to be
>> transformed with an XSLT stylesheet). So I basically know how RESTful
>> webservices work, but I don't know how to use cocoon3 in this case (I
>> assume new Page(...) isn't the right thing to return when I just want to
>> pass the request params to my generator. So I don't want to use
>> StringTemplate in this case (but it's nontheless a great thing). So the
>> query points to a controller, which decides that it's a GET request
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jos Snellings | 1 Dec 17:31
Picon

Re: Cocoon documentation

Yes, that would be it...
agreed.
On Tue, 2009-12-01 at 06:23 -0500, Matt Whipple wrote:
> Jos Snellings wrote:
> > The documentation of cocoon-3 can be checked out as:
> > svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
> >   
> I stumbled upon the HTML deliverable of that on
> http://people.apache.org/~reinhard/c3-ref/html/ after sending my email. 
> I'd think it would be best if the official documentation focused on
> being primarily a comprehensive reference with a quick bootstrap guide. 
> A community documentation site could then supplement that with all the
> typical tutorials/how-to's and tips & tricks which gets the reader where
> he wants to be with a straightforward, minimalist approach which then
> references the official docs and other more enlightening sources. 
> Regular articles/blog entries could then highlight the activity in the
> community, and the possibilities of various Cocoon components could be
> showcased.  Guides to all of the overlapping processes which can be
> [easily] extrapolated from existing material can be given a home so that
> a potential new developer with a specific need is provided with an
> apparent foot in the door.  Basically a site which presents a welcoming,
> active community rather than seemingly a group of scattered people
> developing in Cocoons and enabling me to make bad wordplay (such is the
> price).  To that end, an agreed upon forum would be ideal. 
> > The cocoon community will be delighted at some good documentation.
> > Talking about community I fear such as an active community is to be
> > reestablished, so I think we'd better provide some sweet stuff.
> >
> > What would Reinhard think of starting with as a table of contents?
> > I will be glad to write some documentation as well. I have some goose
(Continue reading)

Permalink | Reply | 0 comments |
headers
Simone Tripodi (JIRA | 1 Dec 21:19
Picon
Favicon

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent


     [
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simone Tripodi updated COCOON3-3:
---------------------------------

    Attachment: XIncludeTransformer.patch

Last uploaded patch (XIncludeTransformer.patch ~92K) contains a new implementation of the XInclude
processor based strictly only on SAX APIs, no more DOM to extract elements by ids or by xpath expressions.

Like always, don't hesitate to contact me if some help or extra work is needed to apply the patch.

> Provide an XInclude transformer as a PipelineComponent
> ------------------------------------------------------
>
>                 Key: COCOON3-3
>                 URL: https://issues.apache.org/jira/browse/COCOON3-3
>             Project: Cocoon 3
>          Issue Type: Improvement
>          Components: cocoon-sax
>    Affects Versions: 3.0.0-alpha-1
>            Reporter: Simone Tripodi
>            Assignee: Cocoon Developers Team
>            Priority: Minor
>             Fix For: 3.0.0-alpha-3
>
>         Attachments: XInclude.patch, XIncludeTransformer.patch, XIncludeTransformerFixedAndApacheHeaders.patch
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Reinhard Pötz | 1 Dec 21:42
Picon
Favicon

Re: Cocoon documentation

Matt Whipple wrote:
> Jos Snellings wrote:
>> The documentation of cocoon-3 can be checked out as:
>> svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
>>   
> I stumbled upon the HTML deliverable of that on
> http://people.apache.org/~reinhard/c3-ref/html/ after sending my email. 
> I'd think it would be best if the official documentation focused on
> being primarily a comprehensive reference with a quick bootstrap guide. 
> A community documentation site could then supplement that with all the
> typical tutorials/how-to's and tips & tricks which gets the reader where
> he wants to be with a straightforward, minimalist approach which then
> references the official docs and other more enlightening sources. 
> Regular articles/blog entries could then highlight the activity in the
> community, and the possibilities of various Cocoon components could be
> showcased.  Guides to all of the overlapping processes which can be
> [easily] extrapolated from existing material can be given a home so that
> a potential new developer with a specific need is provided with an
> apparent foot in the door.  Basically a site which presents a welcoming,
> active community rather than seemingly a group of scattered people
> developing in Cocoons and enabling me to make bad wordplay (such is the
> price).  To that end, an agreed upon forum would be ideal. 

Agreed. When I started to write the C3 documentation, I had the Spring
reference documentation in mind. I think it's one of the best examples
because it focuses on describing the technology and the concepts.

As a forum for everything beyond reference docs we could either use
Daisy or the Apache Wiki. (http://wiki.apache.org/cocoon)
(Continue reading)

Permalink | Reply | 8 comments |
headers
Matt Whipple | 1 Dec 17:54
Favicon

Re: Cocoon documentation

Reinhard Pötz wrote:
> Matt Whipple wrote:
>   
>> Jos Snellings wrote:
>>     
>>> The documentation of cocoon-3 can be checked out as:
>>> svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
>>>   
>>>       
>> I stumbled upon the HTML deliverable of that on
>> http://people.apache.org/~reinhard/c3-ref/html/ after sending my email. 
>> I'd think it would be best if the official documentation focused on
>> being primarily a comprehensive reference with a quick bootstrap guide. 
>> A community documentation site could then supplement that with all the
>> typical tutorials/how-to's and tips & tricks which gets the reader where
>> he wants to be with a straightforward, minimalist approach which then
>> references the official docs and other more enlightening sources. 
>> Regular articles/blog entries could then highlight the activity in the
>> community, and the possibilities of various Cocoon components could be
>> showcased.  Guides to all of the overlapping processes which can be
>> [easily] extrapolated from existing material can be given a home so that
>> a potential new developer with a specific need is provided with an
>> apparent foot in the door.  Basically a site which presents a welcoming,
>> active community rather than seemingly a group of scattered people
>> developing in Cocoons and enabling me to make bad wordplay (such is the
>> price).  To that end, an agreed upon forum would be ideal. 
>>     
>
> Agreed. When I started to write the C3 documentation, I had the Spring
> reference documentation in mind. I think it's one of the best examples
(Continue reading)

Permalink | Reply | 7 comments |

Gmane