On Thu, Jan 13, 2011 at 8:00 AM, jowi <[email protected]> wrote: > hhm, I am still confused but at least on a higher level... > >> I can only think of two possibilities, both remote. One is that for >> some reason java is not using the cacerts file you think it's using. > How can I check this?
Do a "find / -name cacerts" and see how what turns up. It's possible that OpenJDK uses a different location. >> The other is that for some reason the WiaB/Java Cert code doesn't like >> your root ca cert. > Hhm, until Rev "82c0fdac92" from 21.11.2010 (Author: Lennard de Rijk) > anything worked fine. Do you mean that (using your current environment) you have verified that the commit just after "82c0fdac92" exhibits the problem? > I did not change my certificates since that time. So, if you do not > change anything in the WiaB/Java Cert code I would assume, that my > certificates should be still acceptable. The only change that I did in > the meantime is to switch from sundjdk to openjdk because this was the > only way to get a "Build successful" when using a newer revision > (don't know what has changed since revison "a0bb2b9998" from > 21.11.2010 (Author: Alex North)...see also my previous comments/ > questions here: > http://groups.google.com/group/wave-protocol/browse_thread/thread/22991eb120d686ea > ) The problem building using SunJDK is fixed. I do all my development using the SunJDK and my server (and the demo server) use the SunJDK. So any problem that would cause WiaB to not compile/run under the SunJDk will get fixed shortly after being discovered. -Tad -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
