>It's good to hear but I wonder how this can work for you at all ;-) Well, this is admittedly a bit exceptional. In this forum, mostly people invest efforts to figure out why something does not work, we are about to try to find out why something works ;-) Anyway, where is the code where this happens. blockcontexts are registered via jnet, no? Blockcontexts are mounted in cocoon-block-deployment.
On not using maven: Every single project comes with an eclipse goal, so mvn eclipse:eclipse builds a nice importable project. After import the 'autobuild' is on, so, I just grab COB-INF and META-INF together with 'jar cvf somesample.jar, and the cocoon block is ready. I mainly suppressed maven to replace all internal cocoon dependencies by dependencies on the mutual projects, rather than making them rely on the maven repository. This enables me to 'tweak' the code if necessary. In any case, it allows me to better understand what's happening. One day I must write a 'cocoon for blondes' page. New version: I depart from 'getting started', get the maven archetypes and artefacts: mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create -DarchetypeGroupId=org.apache.cocoon.archetype-sample -DarchetypeArtifactId=cocoon-archetype-sample -DarchetypeVersion=3.0.0-alpha-1 -DgroupId=org.tanteterra -DartifactId=newsample What are the magic words for the alpha2 archetype? I come back with a list of compilation errors. Cheers, Jos On Tue, 2009-11-17 at 15:38 +0100, Reinhard Pötz wrote: > Jos Snellings wrote: > > Please find below the follow up on the tomcat deployment problem. I am sure > > it is of interest > > to a lot of users: > > With the latest sources checked out from svn, built in eclipse the problem > > is solved. > > > > Deployment under tomcat: > > 1. add xercesImpl.jar > > 2. in the local build I have no pom.properties file included in the jar > > (in fact, in my builds there is no META-INF/maven), so > > XMLSitemapServlet.initVersionNumber() will fail, > > I stubbed that method for the time being. > > So you don't use Maven to build Cocoon 3 trunk? > > > 3. An entry Cocoon-Block-Name in the manifest file is not necessary, this > > invalidates: > > http://cocoon.apache.org/subprojects/block-deployment/1.1/1471_1_1.html > > The blockcontext:/ protocol usually used in the Servlet-Service > definition relies on this entry. Without it, the servlet context can't > be resolved correctly. > > > Blocks are neatly deployed under the mount point specified in the > > servlet-service bean declaration. > > It's good to hear but I wonder how this can work for you at all ;-) > > > I had to adapt the samples to the alpha-2 level. Some classes were > > refactored to cocoon-sax, others are obsolete. > > Is the new version available? Care for the adapted code? > > What do you mean by "new version"? > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org