On Thu, 30 Aug 2001, Ignacio J. Ortega wrote:
> I think we are facing some kind of "sealing violation bug" here.., some
> comments point out that Sun JCE cannot be used with unsigned providers
That was my second bet, and testing without ReloadInterceptor in 3.3
should clear this out.
However,
ss(Handler.java:160)
> at org.apache.cocoon.sitemap.Manager.invoke(Manager.java:103)
> at org.apache.cocoon.Cocoon.process(Cocoon.java:423)
> at
> org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:507)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java)
>
>
&g
BRAHMANYAM,VEENA (HP-MountainView,ex1)
> [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 30 de agosto de 2001 20:14
> Para: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Asunto: RE: Cannot set up certs for trusted CAs exception ( JCE and
> tomcat an d cocoon2.0)
>
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 29, 2001 10:15 PM
To: '[EMAIL PROTECTED]'
Cc: '[EMAIL PROTECTED]'
Subject: Re: Cannot set up certs for trusted CAs exception ( JCE and
tomcat an d cocoon2.0)
Hi,
Try to place JCE/JSSE in tomcat.home/lib, or even better in
Hi there. I frequently do crypto in servlets, and I have not personally run
into any problems. The only relevant difference between your environment and
some of mine, as far as I can tell, is that while I have heard of Cocoon, I
have no idea what it is =)
Also, I'm a little confused as to why
