November 2006 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Integration with different JBoss Cache releases

by bstansberry＠jboss.com

JBoss Cache 2.0 is completely API-incompatible with the JBC 1.x series. This thread is to discuss how the JBC/EJB3 integration should deal with that fact. I'm going to assume that EJB3 will want to integrate with different versions of JBC: 1) 2.0 for integration into AS 5. 2) For AS 4.2, 2.0 or 1.4.1, whichever we decide to include with 4.2 3) 1.4.0.SP1 for integration with 4.0.5.GA. (There should be no integration differences between 1.4.0.SP1 and 1.4.1). Carlo has proposed breaking EJB3 into a core and then adapters for integration with different environments. So, the problem with integrating with different JBC releases would be solved by creating different adapters. This should be fairly straightforward, as the JBC integration is encapsulated into just 2 classes: SFSBs: Integration is in the StatefulTreeCache class, which implements ClusteredStatefulClass. I propose changing this class so it implements ClusteredStatefulCache by delegating to a JBC-version-specific adapter. I would add a factory class that is able to load and instantiate the correct adapter by checking the version of JBC available on the classpath. The static org.jboss.cache.Version.getVersionShort() method makes such a version check trivial. Entity Beans: Integration is in the TreeCacheProviderHook class. This class is itself a factory that returns an impl of org.hibernate.cache.Cache. Here I would write implementations of o.h.c.Cache that can integrate with JBC 2.0. If JBC 2.0 was on the classpath, one of those Cache impls would be returned. Otherwise, one of the existing Cache impls that ship with hibernate would be returned. Those impls can integrate with JBC 1.x. Medium term (i.e. after the next couple weeks) I'll want to push the new JBC 2.0 compatible o.h.c.Cache impls into the hibernate code base. But until the AS 5 beta goes out it's logistically easier to do this in EJB3. Biggest hassle to all this is the compile-time incompatibility between JBC releases. So, if we have different JBC adapters in the code base, the EJB3 build is going to need to be segmented to build each one separately. No surprise there. Also, in IDEs it will be a pain to have different sets of adapters on the build path -- would need to do something like have a separate Eclipse project per adapter. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983509#3983509 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983509

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - Re: nothing works in head

by kabir.khan＠jboss.com

Deleting the client-deployer-beans.xml "fixed" it for me this morning View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983497#3983497 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983497

19 years, 5 months

1
0
0 / 0

[Design of POJO Server] - nothing works in head

by bill.burke＠jboss.com

Doesn't seem like deployers are getting deployed in HEAD anymore as nothing seems to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983492#3983492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983492

19 years, 5 months

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Unable to passivate due to ctx lock IS GONE

by Oyabun

So if it's gone, what product has the fix (cache, server)? And what version? -- Alex View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983486#3983486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983486

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Injection of MBeanServer

by scott.stark＠jboss.org

"kabir.khan(a)jboss.com" wrote : I am writing some tests for trying this out in a running jboss instance. I will need to add the jboss-aop-mc-int.jar to the jboss/lib (or server/xxx/lib) folder for this to work, so that either a proxy or a woven class is returned. | | One thing that still is wooly, is where the repository comes from. The repository has not been finalized yet, and there is still some work that needs doing on it: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982960#3982960 | BTW the class to be used is now | | | <bean name="Repository" class="org.jboss.metadata.plugins.repository.basic.BasicMetaDataRepository"/> | | Ok, that was my next question: how does this tie into the current metadata work. We should probably keep the conf/deployer-beans.xml minimal (and rename this to bootstrap-beans.xml) and introduce the aop integration as part of the deployers/* level. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983475#3983475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983475

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Injection of MBeanServer

by scott.stark＠jboss.org

Right, its not. Add it to the server conf/deployer-beans.xml for now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983474#3983474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983474

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Injection of MBeanServer

by kabir.khan＠jboss.com

I am writing some tests for trying this out in a running jboss instance. I will need to add the jboss-aop-mc-int.jar to the jboss/lib (or server/xxx/lib) folder for this to work, so that either a proxy or a woven class is returned. One thing that still is wooly, is where the repository comes from. The repository has not been finalized yet, and there is still some work that needs doing on it: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982960#3982960 BTW the class to be used is now | <bean name="Repository" class="org.jboss.metadata.plugins.repository.basic.BasicMetaDataRepository"/> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983473#3983473 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983473

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Injection of MBeanServer

by bstansberry＠jboss.com

Thanks. I saw the Repository bean in the example, but didn't really think that it was appropriate for the -beans.xml for the Tomcat clustering cache to be deploying what looks to be the singleton AOPKernelRepository for the entire appserver. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983469#3983469 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983469

19 years, 5 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Where can I find a list of what OS tomcat works whit?

by Linuso

I have serache but dont find anything good.. Are there any who knows where I can find a list of what operating systems tomcat 5.0.28 and 4.1.31 works whit? The operating systems I running is AIX 5.2 and 5.3 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983462#3983462 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983462

19 years, 5 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: error loading profiler

by clebert.suconic＠jboss.com

The zip file still opened by the DLL. You have to stop capturing data (after it is started of course). You can use the JMX methods or kill -3 to stop capturing before you open your files. Look at this Link. It has some information on how to proceed: http://labs.jboss.com/portal/jbossprofiler/doc/runtime.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983456#3983456 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983456

19 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2006