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

[Design of Messaging on JBoss (Messaging/JBoss)] - Refactoring on delegates

by clebert.suconic＠jboss.com

I just created a wiki page (1st draft) to support a discussion on the refactoring of our current client delegates into an agnostic model: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingDelegateRefactoring My goal is to make this refactoring in 3 or 4 steps, to make the process easier. 1st - Get rid os aspects (but keep any aspect acting as a generic interceptor such as Failover/Exception/Close) 2nd - Introduce proxies finally replacing the AOP pointcuts. 3rd - Rename packages & classes to what we are targeting as the final model. (for example, instead of ConnectionDelegate, rename it to just Connection... also rename the package to something reflecting the agnostic idea) 4th - Remove the DelegateSupport and place IOSession (mina objects) into Connection For the 1st iteration there is little or no discussions at all. We can just proceed on removing those aspects as this is a just refactoring. The wiki page will have more details and lets kick the discussion here now. I wanted to reuse what was already discussed on our previous meetings and on forums. Please let me know if you remember of any point previously discussed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108266#4108266 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108266

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: aop-mc-int tests take too long

by pgier

I changed the aop tests back to off by default and I updated the usage comments in the pom. I guess I could turn just one of the configurations on by default. And then that would run during a release. For now, I'll turn all the tests on in hudson, and then leave the other tests activatable using profiles. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108259#4108259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108259

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to update PoolClass usage

by ALRubinger

"scott.stark(a)jboss.org" wrote : Since I was in there I have replaced all PoolClass usage with Pool in the ejb3 subproject. Ah, looks like I did miss the @PoolClass > @Pool changes in some of the EJB3 testsuite configs. Was confused as to why you were seeing this problem in TCK. :) Thanks for switching those over. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108234#4108234 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108234

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Security annotation usage need refactoring

by anil.saldhana＠jboss.com

http://jira.jboss.com/jira/browse/JBAS-4858 The JACC layer for EJB3 should get into a security deployer for the ejb3 metadata. I have not yet got to doing this task. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108233#4108233 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108233

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Security annotation usage need refactoring

by scott.stark＠jboss.org

The security related annotations are some of the least authoritative and simply need to be dropped in favor of the new metadata. The org.jboss.ejb3.security.JaccHelper and org.jboss.ejb3.Ejb3DescriptorHandler.addSecurityAnnotations are duplicating much of the metadata processing. I'm focusing on updating these two pieces of code to validate the AnnotationMetaDataDeployer behavior. Initially I'm going to try to leave the aspect alone in terms of letting them continue to lookup the annotations and integrate the AnnotationMetaDataDeployer output via the MetaData repository. In the future I believe the security related metadata should be used instead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108229#4108229 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108229

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to update PoolClass usage

by scott.stark＠jboss.org

Since I was in there I have replaced all PoolClass usage with Pool in the ejb3 subproject. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108225#4108225 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108225

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to update PoolClass usage

by scott.stark＠jboss.org

So it just was that my cts workspace was out of date. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108220#4108220 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108220

18 years, 4 months

1
0
0 / 0

[Design of JBoss IIOP on JBoss] - Re: tomcat deployer dependency on jboss-iiop.jar

by reverbel

See my comment at http://jira.jboss.com/jira/browse/JBAS-4927. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108219#4108219 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108219

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to update PoolClass usage

by scott.stark＠jboss.org

Note that was the cts config I was testing against. There is a separate ejb3-interceptors-aop.xml for that setup. The current trunk version is using the Pool annotation: | <annotation expr="!class((a)org.jboss.annotation.ejb.Pool)"> | @org.jboss.annotation.ejb.Pool (value="ThreadlocalPool", maxSize=30, timeout=10000) | </annotation> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108217#4108217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108217

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to update PoolClass usage

by scott.stark＠jboss.org

It is the deploy/ejb3-interceptors-aop.xml default annotation that is causing the problem. It should be replaced with @org.jboss.annotation.ejb.Pool("..."), however, I don't see a DefaultPool type of entry in the ejb3.deployer/META-INF/ejb3-deployers-beans.xml EJB3PoolFactoryRegistry that can be used. I'll set it to StrictMaxPoolFactory for now. |  | <bean name="EJB3PoolFactoryRegistry" class="org.jboss.ejb3.pool.PoolFactoryRegistry"> | <property name="factories"> |  | <map class="java.util.HashMap" keyClass="java.lang.String" | valueClass="java.lang.Class"> |  | <entry> | <key>ThreadlocalPool</key> | <value>org.jboss.ejb3.pool.ThreadlocalPoolFactory</value> | </entry> |  | <entry> | <key>StrictMaxPool</key> | <value>org.jboss.ejb3.pool.StrictMaxPoolFactory</value> | </entry> | </map> | </property> | </bean> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108216#4108216 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108216

18 years, 4 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 2007