for db2 to allow the specification of a
default isolation level so one is not tied to RS for DB2.
On Nov 20, 2006, at 11:02 AM, Udovichenko, Nellya wrote:
> Oh, by the way, doesn't this change address the transaction isolation
> level
> problem in TranQL/OpenEJB (GERONIMO-21
Oh, by the way, doesn't this change address the transaction isolation
level
problem in TranQL/OpenEJB (GERONIMO-2128)?
Thanks,
Nellya Udovichenko.
-Original Message-
From: Matt Hogstrom [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 14, 2006 2:55 AM
To: dev@geronimo.apache.org; opene
o redirect mx4j.log.Logger again as described in
http://mx4j.sourceforge.net/docs/ch04s03.html.
But what do you want to achieve?
Heinz
On 10/24/06, Udovichenko, Nellya <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
>
>
> I noticed that 'mx4j.log.CommonsLogger' is hardcode
Hi,
I noticed that ‘mx4j.log.CommonsLogger’
is hardcoded in org.apache.geronimo.kernel.log.GeronimoLogging class.
Can I use another logger class? If yes then how can I
do this?
Thanks,
Nellya Udovichenko
level in TranQL
I was planning on some changes to TranQL for CMP support but didn't get
them completed on time. I
thought it would be unfair to hold up the release because of my
delinquency so I regressed to 1.3.
The changes should be in 1.1.2 or 1.2.
Udovichenko, Nellya wrote:
>
Hello,
Matt!
I have downloaded Geronimo-1.1.1-rc2 and see TranQL version is 1.3
there instead of 1.3.1
I expected.
Kevan Miller wrote that's due to there haven't been any changes to
TranQL since 1.3
(see topic "TranQL version in Geronimo-1.1.1-rc1"
yesterday).
Does it mean t
I've downloaded the
Geronimo-1.1.1-rc1 and was surprised to see the 1.3 version of TranQL there.
I recall there was a
plan to use TranQL 1.3.1 in G1.1.1, am I wrong, or this is expected to be
corrected in G1.1.1 release?
Nellya Udovichenko,
Intel Middleware Products Division
Hello,
Could you please tell me how can I change keystore
type for Jetty?
I'm trying to replace Jetty SSL keystore type with
PKCS12 by adding the parameter to config.xml:
...
PKCS12
0.0.0.0
8443
...
It works fine for Tomcat, but for Jetty I get the
followi
Hello,
I have launched Geronimo on Sun JDK.
Then I’ve tried to run it with Harmony class library
and IBM VM j9. I’ve got the
error log below. Also I’ve got the same result when launched
Geronimo on Harmony and then - on
Sun JDK.
There is a bug in HOWL repaired in
howl-1.0.1 b
:[EMAIL PROTECTED]
Sent: Wednesday, May 03, 2006 11:46 PM
To: dev@geronimo.apache.org
Subject: Re: New HOWL version in Geronimo
0.1.11 to 1.0.0 appears like a major jump... What else has changed?
--jason
-Original Message-
From: "Udovichenko, Nellya" <[EMAIL PROTECTED]>
Hello!
Now version of HOWL in
Geronimo is 0.1.11. What do you think about its replacing with new one 1.0.0?
Some problems are fixed
in new HOWL version. One of them is of importance for correct Geronimo startup:
class org.objectweb.howl.log.BlockLogBuffer
from howl-logger-0.1
t: Re: Final fields serialization mechanism in Geronimo Corba RMI IIOP
implementation
Udovichenko, Nellya wrote:
>
> Hello!
>
> My JDK version is Sun JDK 1.5. When I use Geronimo Corba RMI IIOP
> implementation
>
> class org.apache.geronimo.interop.rmi.iiop.FinalFieldSetter
Hi,
What JDK do you work on?
It looks like internal Sun class com.sun.security.auth.login.ConfigFile isn’t included
in your JDK
library. This problem could occur if you have used non-Sun JDK. See Geronimo JIRA reference on patch
for org.apache.geronimo.security.network.protocol.S
Hello!
My JDK version is Sun JDK 1.5. When I use Geronimo
Corba RMI IIOP implementation
class
org.apache.geronimo.interop.rmi.iiop.FinalFieldSetter throws RuntimeException
because the implementation of FinalFieldSetter
interface cannot be found
if JDK version differs 1.4.
I ha
14 matches
Mail list logo
