On Tue, Sep 22, 2009 at 9:58 PM, Steven D. Majewski sd...@virginia.eduwrote:
We've been using Cocoon 2.1.* for some time now, but we haven't really been
doing a proper build.
We've been building the sample app, and using that as a development base,
adding new pipelines
and sitemaps, and
On Wed, Sep 23, 2009 at 8:22 AM, Dominic Mitchell d...@happygiraffe.netwrote:
My first question would have been: are the dependencies correct? What
happens if you run mvn dependency:tree in the webapp? It should include
spring dependencies.
For reference, this is what I get when running
myBlock1 myBlock2 seem to have all the right dependencies (and they
work on their own),
but myCocoonWebapp has only the jars from those two blocks:
[INFO]
[INFO] [dependency:tree {execution: default-cli}]
[INFO]
,
Robby Pelssers
-Original Message-
From: Steven D. Majewski [mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 6:04 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
myBlock1 myBlock2 seem to have all the right
On Wed, Sep 23, 2009 at 5:03 PM, Steven D. Majewski sd...@virginia.eduwrote:
myBlock1 myBlock2 seem to have all the right dependencies (and they work
on their own),
but myCocoonWebapp has only the jars from those two blocks:
[INFO]
On Sep 23, 2009, at 1:45 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 5:03 PM, Steven D. Majewski sd...@virginia.edu
wrote:
myBlock1 myBlock2 seem to have all the right dependencies (and
they work on their own),
but myCocoonWebapp has only the jars from those two blocks:
[INFO]
I can create, 'mvn install' 'mvn jetty:run' both myBlock1 myBlock2.
When I try to connect the two blocks as in http://cocoon.apache.org/2.2/1291_1_1.html
,
I get this error on either a jetty:run or an install:
myBlock1$ mvn jetty:run
[INFO] Scanning for projects...
[INFO]
On Wed, Sep 23, 2009 at 7:22 PM, Steven D. Majewski sd...@virginia.eduwrote:
I can create, 'mvn install' 'mvn jetty:run' both myBlock1 myBlock2.
When I try to connect the two blocks as in
http://cocoon.apache.org/2.2/1291_1_1.html,
I get this error on either a jetty:run or an install:
On Wed, Sep 23, 2009 at 6:50 PM, Steven D. Majewski sd...@virginia.eduwrote:
Thanks. Yes -- I saw that observation in the other message.
However: it wouldn't build doing just a 'mvn install' on the blocks.
Was there a particular reason for the failure when you ran mvn install in
the blocks?
On Sep 23, 2009, at 2:22 PM, Steven D. Majewski wrote:
If I comment out the myBlock2 dependency in myBlock1/pom.xml which I
just added:
!--
dependency
groupIdedu.virginia.lib/groupId
artifactIdmyBlock2/artifactId
version1.0-SNAPSHOT/version
/dependency
--
:23 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
I can create, 'mvn install' 'mvn jetty:run' both myBlock1 myBlock2.
When I try to connect the two blocks as in
http://cocoon.apache.org/2.2/1291_1_1.html
,
I get this error
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml of
myblock1?
Yes. ( And if I take that dependency out, it runs without complaint. )
I guess so...
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski sd...@virginia.eduwrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml of myblock1?
Yes. ( And
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency of myblock2 in the pom.xml
On Sep 23, 2009, at 2:50 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski sd...@virginia.edu
wrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending on the
other?
Did you also add the dependency
On Wed, Sep 23, 2009 at 7:57 PM, Steven D. Majewski sd...@virginia.eduwrote:
On Sep 23, 2009, at 2:50 PM, Dominic Mitchell wrote:
On Wed, Sep 23, 2009 at 7:44 PM, Steven D. Majewski sd...@virginia.edu
wrote:
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you
[mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 8:45 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
On Sep 23, 2009, at 2:36 PM, Robby Pelssers wrote:
So if I understand you correctly you have one block depending
this will not work anymore.
So don't think you're there yet ;-)
Robby
-Original Message-
From: Steven D. Majewski [mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 8:58 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2
]
Sent: Wednesday, September 23, 2009 9:02 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 2:56 PM, Robby Pelssers wrote:
Ok...
Check in eclipse the value of M2_REPO:
Window - Preferences - Java - Build path
Pelssers [mailto:robby.pelss...@ciber.com]
Sent: Wednesday, September 23, 2009 9:10 PM
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
Aha... so that explains why the myBlock2.jar IS still in the
classpath... lol
If you were to do mvn
...@ciber.com]
Sent: Wednesday, September 23, 2009 9:10 PM
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
Aha... so that explains why the myBlock2.jar IS still in the
classpath... lol
If you were to do mvn eclipse:eclipse again
. Majewski [mailto:sd...@virginia.edu]
Sent: Wednesday, September 23, 2009 9:22 PM
To: users@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
On Sep 23, 2009, at 3:14 PM, Robby Pelssers wrote:
Ok...here is what I want you to do in this order
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the minute...
I wouldn't expect maven to complain without
: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the
minute...
I wouldn't expect maven to complain without a good reason. Maybe some
small
To: users@cocoon.apache.org
Subject: RE: problems with Getting Started 2.2 [was: Starting out
with
Cocoon 2.2]
Could you attach both poms to a reply? I'd love to see if I can track
down some mistake there... It's really getting stranger by the
minute...
I wouldn't expect maven to complain
On Wed, Sep 23, 2009 at 9:18 PM, Steven D. Majewski sd...@virginia.eduwrote:
Thank You!!
Both 1.0.0 and 1.0-SNAPSHOT are mismatched in the documentation.
I was following the instructions a little too exactly!
I wondered about this mismatch at the time, but I thought that
perhaps SNAPSHOT
@cocoon.apache.org
Subject: Re: problems with Getting Started 2.2 [was: Starting out with Cocoon
2.2]
On Wed, Sep 23, 2009 at 9:18 PM, Steven D. Majewski sd...@virginia.edu wrote:
Thank You!!
Both 1.0.0 and 1.0-SNAPSHOT are mismatched in the documentation.
I
On Sep 23, 2009, at 4:39 PM, Robby Pelssers wrote:
True… the same here… but if I had no prior maven knowledge this
might be a bit trickier to spot. I guess it’s time to have that
documentation published again… HINT HINT.
Robby
This may also need updating:
We've been using Cocoon 2.1.* for some time now, but we haven't really
been doing a proper build.
We've been building the sample app, and using that as a development
base, adding new pipelines
and sitemaps, and eventually, removing the samples directory before
deploying.
I've started to
PS: That
Could not instantiate listener
org.springframework.web.context.ContextLoaderListener
java.lang.ClassNotFoundException:
org.springframework.web.context.ContextLoaderListener
[ ... stack trace ... ]
warning is the first of several messages. There is also:
2009-09-22
[was: Starting out with
Cocoon 2.2]
PS: That
Could not instantiate listener
org.springframework.web.context.ContextLoaderListener
java.lang.ClassNotFoundException:
org.springframework.web.context.ContextLoaderListener
[ ... stack trace ... ]
warning is the first of several messages
Personally, I would think that Cocoon 2.1 is the most well-developed
and stable of the series. 2.0 is really out-of-date. 2.2 might be worth
tackling if you're prepared to learn the associated frameworks such as
Spring and Hibernate, plus be prepared to do Java coding; but, as many
others have
Thanks for all the further suggestions. I'll use Coccon 2.1. (I dont
know anything about Spring/Maven/Hibernate)
Derek Hohls wrote:
Personally, I would think that Cocoon 2.1 is the most well-developed
and stable of the series. 2.0 is really out-of-date. 2.2 might be worth
tackling if you're
Hello
I wrote two applications using CForms, Spring and Hibernate in Cocoon
2.1. It found it relatively easy to upgrade them to Cocoon 2.2. I
think that CForms, Spring and Hibernate work very well together.
But the same client also has a couple of old applications which still
run in
...which in turn would result in Hippo 7 to get a Cocoon front-end,
right? :-)
Well yes that could indeed happen, but we're not there yet. :-)
Jeroen
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For
I'm looking for help with starting to use Cocoon 2.2. I've looked at the
website (cocoon.apache.org), but havent found very much in terms of
introductory guides, tutorials, etc.
I'm just about to embark on a new project, which will involve handling
SOAP requests, fetching data from an Oracle
Hi David,
I'm just about to embark on a new project... I'd like to use Cocoon
2.2 for this, but I'm concerned about the apparent lack of support for it.
It is true that Cocoon has hit a low point at the moment and I'm sure
many of us wonder if it will ever recover. Many of the original
Lamentable indeed.
Having taken a break from Cocoon 2.1 at work, and returned to 2.2,
after much pain and frustration at recreating what was in cocoon using
'pure' java and spring mvc + freemarker (urgh) + 1000's of lines of
horrible java to do stuff cocoon did for free, I realize how much
On 10/sep/09, at 15:05, Ellis Pritchard wrote:
Lamentable indeed.
Having taken a break from Cocoon 2.1 at work, and returned to 2.2,
after much pain and frustration at recreating what was in cocoon
using 'pure' java and spring mvc + freemarker (urgh) + 1000's of
lines of horrible java to
Francesco Chicchiriccò wrote:
On 10/sep/09, at 15:05, Ellis Pritchard wrote:
Lamentable indeed.
Having taken a break from Cocoon 2.1 at work, and returned to 2.2,
after much pain and frustration at recreating what was in cocoon
using 'pure' java and spring mvc + freemarker (urgh) + 1000's
Well I think that some people have put Cocoon on a low profile. There
were a lot of great frameworks added to the ASF code base lately, which
made people broaden their perspective.
I don't really think that people quit working with/on Cocoon, because
Cocoon 2.1 is stable and a lot of people
On 10/sep/09, at 16:55, Jeroen Reijn wrote
Well I think that some people have put Cocoon on a low profile.
There were a lot of great frameworks added to the ASF code base
lately, which made people broaden their perspective.
I don't really think that people quit working with/on Cocoon,
IMHO, developers tend to mirror the general population in that the majority
follow the herd. The habits of imperative Java programming and the
not-invented-here syndrome meant that Cocoon was only ever going to appeal
to a minority of enlightened developers.
Maven is a head f*ck for the average
Thanks for everyone's responses.
I'm beginning to think that I should use Cocoon 2.0, because at least I
know this is well documented. Which is a shame after people have put a
lot of effort into developing versions 2.1 and 2.2 ...
David Legg wrote:
Most of the useful documentation can be
-
From: David Beasley [mailto:david.beas...@publishingtechnology.com]
Sent: Thursday, September 10, 2009 6:44 PM
To: users@cocoon.apache.org
Subject: Re: Starting out with Cocoon 2.2
Thanks for everyone's responses.
I'm beginning to think that I should use Cocoon 2.0, because at least I
know
David Beasley wrote:
I'm looking for help with starting to use Cocoon 2.2. I've looked at
the website (cocoon.apache.org), but havent found very much in terms
of introductory guides, tutorials, etc.
Tutorials are something that is really lacking. I don't know if it is
me, but I think that
David Beasley wrote:
Thanks for everyone's responses.
I'm beginning to think that I should use Cocoon 2.0, because at least
I know this is well documented. Which is a shame after people have put
a lot of effort into developing versions 2.1 and 2.2 ...
I would recommend Cocoon 2.1. The
Version 2.1 is still king for me!
On 11/09/2009, at 2:44 AM, David Beasley wrote:
Thanks for everyone's responses.
I'm beginning to think that I should use Cocoon 2.0, because at
least I know this is well documented. Which is a shame after people
have put a lot of effort into developing
Hi,
Recognizing the feeling of disconcertation when after having worked with
Cocoon 2.1 one comes back and finds out about Cocoon 2.2.
- many things have changed, (striving towards MVC paradigm)
which is OK, if things are improving
- Cocoon still depends on Avalon (which caused me troubles in
49 matches
Mail list logo
