1 2 Previous Next 21 Replies Latest reply on Oct 22, 2004 6:57 PM by belaban Go to original post
      • 15. Re: JBossCache in production
        aubergine

        Hi Bela

        I've just discovered that with 1.1 you have bundled sleepycats java db. Thi s is a little awkward for us as sleepycats license conflicts with jboss' lgpl.

        is there any chance you could find/use a db that is consistent with lgpl?

        Thanks

        Nick

        • 16. Re: JBossCache in production

          In 1.2 release (scheduled sometime in November), we plan to ship a cache loader that uses JDBC. That may be what you need.

          -Ben

          • 17. Re: JBossCache in production
            aubergine

            Hi Ben

            Thanks for that - yes, that'll do nicely!

            Incidently,just one more question - Bela said some time back that the cache code would be refactored and one of the new features would be the ability to use other transports over jgroups. Is this still the case?

            Thanks
            Nick

            • 18. Re: JBossCache in production
              aubergine

              Hi Ben

              Thanks for that - yes, that'll do nicely!

              Incidently,just one more question - Bela said some time back that the cache code would be refactored and one of the new features would be the ability to use other transports over jgroups. Is this still the case?

              Thanks
              Nick

              • 19. Re: JBossCache in production
                renier

                Hi,

                I've just started using JBossCache now recently so I'm still going through the teehing pains with it...

                We also use JBoss 3.2.3 and I managed to get it working, by recreating the cluster-service as a cluster.sar and moving the jgroups.jar in the lib folder into the sar. And then deploying JBossCache also in a .sar but using the jgroups.jar that comes with JBossCache. The only problem i've experience so far is that JBossCache is not exposing itself in the JNDI tree...

                But I downloaded the source and noticed the bindToJNDI method's contents has been commented out?

                Is this a bug? Or is it intentional and am I just smoking crack?

                Cheers,
                Renier

                • 20. Re: JBossCache in production

                  No, you are not hallucinating. :-) The JNDI exposure has been fixed in the latest source. It was commented out because of the aop. In 3.2, there is no aop, so that will be fine anyway.

                  -Ben

                  • 21. Re: JBossCache in production
                    belaban

                    The bind/unbind code has been uncommented recently. It will be in version 1.2 (already in the CVS).

                    Wrt Sleepycat: we ship it but you don't need to use it if you don't want to. This is all a config issue. Sleepycat is our current default because we like its simplicity and power. lf you don't, all you need to do is change 1 line in an XML file.

                    Bela

                    1 2 Previous Next