>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 happe
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
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 f
Jos Snellings wrote:
> You mean this would yield the better versions?
> Yes I have the cocoon trunk from alpha-2 level, and they were converted
> to eclipse projects.
> You mean if I build this together the result might be far better?
It might be that you run into a problem that was solved with on
Are
jnet and
block-deployment
servlet-service
likely to change for 3.0? I think not.
Is cocoon-configuration needed?
Thanks,
Jos
-
To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org
For additional commands, e-mail:
You mean this would yield the better versions?
Yes I have the cocoon trunk from alpha-2 level, and they were converted
to eclipse projects.
You mean if I build this together the result might be far better?
OK, I will do that.
By the way, when is the beta coming about? Now I need it.
Thanks,
Jos
Have you also tried to use Cocoon 3 trunk to build and run your application?
Jos Snellings wrote:
> antlr-2.7.7.jar
> cocoon-configuration-api-1.0.2.jar
> cocoon-servlet-3.0.0-alpha-1.jar
> commons-collections-3.2.jar spring-aop-2.5.5.jar stringtemplate-3.0.jar
>
antlr-2.7.7.jar
cocoon-configuration-api-1.0.2.jar
cocoon-servlet-3.0.0-alpha-1.jar
commons-collections-3.2.jar spring-aop-2.5.5.jarstringtemplate-3.0.jar
aopalliance-1.0.jar
cocoon-controller-3.0.0-alpha-1.jar
cocoon-servlet-service-impl-1.1.0.jar
com
Jos Snellings wrote:
> Thank you for the answer, Rheinhard,
>
> I am afraid it does not. The web.xml I am using is from the cocoon
> sample, and it contains all the necessary listeners. In the log file I
> find startup information, but then it does not find the block.
> By the way, if one expands
Yet something is missing, logging at debuglevel:
At startup, none of the methods in DeploymentUtil is ever called :-(
When a block's url is called it is not found:
2009-11-10 15:37:10,139 DEBUG main org.apache.jasper.servlet.JspServlet
- Scratch dir for the JSP engine
is: /usr/local/apache-tomcat
Thank you for the answer, Rheinhard,
I am afraid it does not. The web.xml I am using is from the cocoon
sample, and it contains all the necessary listeners. In the log file I
find startup information, but then it does not find the block.
By the way, if one expands the block's jar file under WEB-IN
Jos Snellings wrote:
> Hi,
>
> When trying to deploy a cocoon-3 block to Tomcat, it does not seem to
> find it:
> java.lang.RuntimeException: There is no block 'YourBlockName' deployed.
> The available blocks are {}.
>
> I must say that the documentation on this issue is a little bit terse...
>
Hi,
When trying to deploy a cocoon-3 block to Tomcat, it does not seem to
find it:
java.lang.RuntimeException: There is no block 'YourBlockName' deployed.
The available blocks are {}.
I must say that the documentation on this issue is a little bit terse...
(http://cocoon.apache.org/subprojects/b
13 matches
Mail list logo