Reinhard Pötz wrote:
Kamal Bhatt wrote:
Those anyone have any thoughts? There is nothing overly unusual
about my applications, it is just a standard application with single
block and no extra code. The only thing unusual about it is I am
using map:mount at the sitemap level.
Cheers.
This is partially fixed. On the latest version of Glassfish I got it
to work, but with new issues. That problem was that there must be a
'/' after the context-path. Eg:
<bean id="au.com.tt.ccm.cocoon-ccm.service"
class="org.apache.cocoon.sitemap.SitemapServlet">
<servlet:context mount-path="/cocoon-ccm"
context-path="blockcontext:/cocoon-ccm/">
</servlet:context> </bean>
Will work.
This:
<bean id="au.com.tt.ccm.cocoon-ccm.service"
class="org.apache.cocoon.sitemap.SitemapServlet">
<servlet:context mount-path="/cocoon-ccm"
context-path="blockcontext:/cocoon-ccm">
</servlet:context> </bean>
Will not.
Is this a bug or a very stupid error.
The context path has to be a directory which means that a trailing
slash is correct. Did you get a helpful error message?
Anyway, the latest version of the servlet-service framework in SVN
(not released yet!) was enhanced by a check that adds a trailing slash
in the case it is missing.
Thanks for sharing your findings!
Yes and no. It was really strange. When I deployed the application, I
would get this strange error which seemed to suggested file corruption.
That wasn't helpful. I will try to replicate it and post it. When I
restarted the server, it was a completely different error. The error on
restart was semi reasonable (for a Java exception, which are rarely
useful), but someone else had got the error in the past and posted on
the mailing list and I was able to decipher it that way.
I might add that I tried it on SJSAS 8.2 and got another error (even
with the context-path fix). If I can't work it out, I will post it on
the mailing list (I may post it just for the sake of someone's sanity).
Also, a couple of questions:
1. What is the context-path? I cannot work out what it means.
2. Anyone tried to use Cocoon 2.2 in a clustered environment? If so, any
caveats?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]