Jorg Heymans skrev:
...
yes, the jetty6 plugin insists on target/classes. Cocoon still refuses
to start however, i got exactly the same problem. I then tried to mount
the webapp under jetty6 (not the plugin) and found that cocoon needs a
property set for a temporary webapp dir of some sort.
<Item>
<New id="testWebAppContext"
class="org.mortbay.jetty.webapp.WebAppContext">
<Set name="Server"><Ref id="Server"/></Set>
<Set name="contextPath">/cocoon</Set>
<Set
name="war">/Users/jheymans/src/cocoon-trunk/webapp/src/main/webapp</Set>
<Set name="tempDirectory">./target</Set>
</New>
</Item>
this makes cocoon run under jetty6. I raised the issue on the jetty
support list [1].
If you mount the webapp from jetty4 or 5 it works without problems.
Regards
Jorg
[1] http://thread.gmane.org/gmane.comp.java.jetty.support/7728
So, we have to wait for some more features for the Jetty plugin. I made
./cocoon.sh use the webapp from mvn war:inplace so that we have
something that is easy to use.
/Daniel
