Hi Uwe,
Geronimo ships a default self-signed certificate in the distributions. You
should replace this default certificate after installing Geronimo. You will
have to designate the certificate used by Geronimo as a trusted certificate
in OpenLaszlo to get past the error you are encountering.
I also have been getting these errors. I have been unable to figure
out the exact reason. But I am guessing that the common factor here
seems to be Windows XP SP2. The openejb build itself fails on my
Lenovo T60p with Windows XP SP2 with the same error that you get. I
also tried with many parallel
djencks wrote:
I'm having trouble distinguishing between this and the previous
error. Are you sure this isn't leftover in the log from a previous
failed run? You might want to start with a fresh copy of geronimo
just to be certain you are seeing only the most up to date problems
djencks wrote:
Out of curiousity, what does your app do if there is no transaction
manager available in the tomcat environment?
Ok :)
I use Spring + Hibernate 3 on my app and these frameworks that use the class
TransactionManager.
Complete trace in the tomcat 6 (without
Hello,
how can I do this? Is there any HowTo´s? OpenLaszlo (OL) is only a framework
(Flash) without a section where I can manipulate the keystore. OL used it from
Java (Sun, IBM,...- 'C:\JAVA\JRE\jre1.6.0_06\lib\security\cacerts')...so
Geronimo need to interact with Sun´s Java JRE...possible?
I have a question about deploying JAX-WS webservices. I generated and deployed
the simple sample jax-ws calculator and looked at what it had generated and
what was deployed and in the simple case this will work fine. In my case I
have a JAX-WS webservice for which I am supplying a web.xml
On Apr 19, 2008, at 3:05 PM, newbie-gero wrote:
Hi,
i'm using geronimo 2.1. I did try deploying the directory(without
compressing into .war format), but it gives errors. However i can
deploy in
Tomcat. Since tomcat and geronimo are from apache family, i will
like to
know if whether i can