On 06/01/16 17:49, Mark H. Wood wrote:
> When I first looked at Cocoon 3, I thought it was more like a return
> to Cocoon's roots, clearing away a lot of stuff that had accumulated
> and concentrating on the pipeline.
I should have another look
> It's quite true that, without intense study of
Hi,
There is no need to configure it in any special way. All defaults are out
of the box and are mostly sane (what every developer needs).
C3 is considered to be more a RESTful framework not only a simple XML
distribution system.
Most sitemap.xmaps work ok.
We have taken some steps into moving
Peter,
On 1/6/16 11:59 AM, Flynn, Peter wrote:
> On 06/01/16 14:18, Christopher Schultz wrote:
>
>> Moving from Tomcat 5 on (presumably) an older Java to a newer version
>> should not be difficult at all. Is there a reason to move to Tomcat 6
>> and not all the way up to Tomcat 8? Tomcat 6 will
>> If I upgrade manually to Tomcat 8 it's going to break all the directory
>> changes and control software setups that RH-based systems expect, which
>> will create work for my ops and my staff because it will be different
>> from all the other Tomcat servers around here. Unfortunately.
> I
Hi Peter,
I would recommend moving to 2.12 first (and probably staying there).
IMHO 2.2 isn't worth the candle and 3.0 misses the point of using Cocoon in
the first place.
I have a similar set-up as you although I use a blocks based build so that
my 'applications' are seperate from the core.
I
Peter,
On 1/6/16 6:33 AM, Flynn, Peter wrote:
> ...I think.
>
> I have an existing Cocoon service running 2.1.11 under Tomcat5 and
> Apache in CentOS5 on a very old server, and I now have a new server
> running CentOS6, Apache2, and Tomcat6 that I want to migrate to, but I
> am held up by my
On Wed, Jan 06, 2016 at 04:59:23PM +, Flynn, Peter wrote:
[snip]
> It's a pity that Cocoon has strayed so far from its original task of
> serving XML via XSLT. In fact it's not at all clear to me what problem
> Cocoon 3 is intended to solve. At the moment it looks more like a
> development
Hi Peter,
I have been using Cocoon 2.12 (or the 2.13 dev brach) for xslt2
transformation work, and agree with Warrell and Christopher -- you do NOT
need to move to 2.2 or 3.0.
Java 8 works with it, but you may need earlier Java versions to build it
(YMMV).
If you want to lighten your production
Hi Peter,
I completely agree with Christopher!
I got some 2.1.* applications running and kept up with flow of Java /
jBoss versions. Maybe there had been some issues with the XML helper
jars but I don't remember in details.
Try your luck with CentOS 7, Java 8 and Tomcat 8 ... and come back if
On 06/01/16 14:18, Christopher Schultz wrote:
> Moving from Tomcat 5 on (presumably) an older Java to a newer version
> should not be difficult at all. Is there a reason to move to Tomcat 6
> and not all the way up to Tomcat 8? Tomcat 6 will be EOL very soon.[1]
Tomcat 6 is all that CentOS6
10 matches
Mail list logo