Thanks for the assistance. I'm actually not that concerned about the Spring Bean Demo, I just posted it as a symptom.
Java class reloading is very important to me, I find it really tough to work when I need to start and restart jetty, even when eclipse is checking my compiles. This hasn't been a problem in the past. In any case, I invite you to run: mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org select 2, set a group/artifact and see if the bean is also broken for you "out of the box." I crossposted to dev once I found that my colleague had the same problem. Best regards, -Will On Mon, Oct 4, 2010 at 1:36 PM, Will Heger <will.he...@gmail.com> wrote: > I tried this on a couple of other machines, windows etc. same problem. > > On Mon, Oct 4, 2010 at 4:51 AM, Will Heger <will.he...@gmail.com> wrote: > >> Hi, >> >> After creating a fresh cocoon from the archetype: >> mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org >> >> Using option 2, the block with a sample, I have two problems: >> >> * The Spring Demo Bean does not produces '#message' instead of the bean >> output. >> * RCL will not recompile after altering java files >> >> Is anyone experiencing a similar issue? >> >> Java = sun/oracle 1.6.0_21 >> Ubuntu 10.04 >> >> Thanks, >> -Will >> >> >