September 2008 - jboss-dev-forums

[Design of POJO Server] - Updated to new AOP deployers in AS trunk

by kabir.khan＠jboss.com

Moved from http://www.jboss.com/index.html?module=bb&op=viewtopic&t=139015 "kabir.khan(a)jboss.com" wrote : I have almost completed the new AOP deployers. The aim was to install the AOP artifacts via MC beans rather than directly into the aspect manager as was the case previously. Locally, with my changes here I am able to get the full AOP testsuite passing. I have yet to try out ejb3-interceptors-aop.xml, which I will look at on Monday. | | Before I can upgrade AS trunk I need to do another AOP release, then we need a release of MC (aop-mc-int). Once upgraded in AS, and switched over to use the new deployers the following two things apply to all jboss-aop.xml files used in AS | | 1) The aop namespace must be defined, so the contents of the file must be as follows: | | | <?xml version="1.0" encoding="UTF-8"?> | | <aop xmlns="urn:jboss:aop-beans:1.0"> | | ... | | </aop> | | | | 2) interceptors can only be defined at the top level. We don't support: | | | <?xml version="1.0" encoding="UTF-8"?> | | <aop xmlns="urn:jboss:aop-beans:1.0"> | | <bind pointcut="all(@Test1)"> | | <interceptor class="MyInterceptor"/> | | </bind> | | <bind pointcut="all(@Test2)"> | | <interceptor class="MyInterceptor"/> | | </bind> | | </aop> | | | | instead you must use the alternative syntax (which is similar to how aspects/advice-bindings work) | | | <?xml version="1.0" encoding="UTF-8"?> | | <aop xmlns="urn:jboss:aop-beans:1.0"> | | <interceptor class="MyInterceptor"/> | | <bind pointcut="all(@Test1)"> | | <interceptor-ref name="MyInterceptor"/> | | </bind> | | <bind pointcut="all(@Test2)"> | | <interceptor-ref name="MyInterceptor"/> | | </bind> | | </aop> | | | I have updated AS trunk to use this now. An additional constraint is now is that since everything maps onto MC beans in the background, names must be unique within a classloader domain. So, the following is not allowed | <?xml version="1.0" encoding="UTF-8"?> | <aop xmlns="urn:jboss:aop-beans:1.0"> | <interceptor name="Blah" class="x"/> | <bind name="Blah" pointcut="..."> | <interceptor-ref name="Blah"/> | </bind> | </aop> | Since both the interceptor and the binding result in an underlying MCBean called "Blah". Duplicate bean names are not allowed within a controller. Rather you need to do | <?xml version="1.0" encoding="UTF-8"?> | <aop xmlns="urn:jboss:aop-beans:1.0"> | <interceptor name="Blah" class="x"/> | <bind name="BlahBind" pointcut="..."> | <interceptor-ref name="Blah"/> | </bind> | </aop> | I ran the smoke and some other tests, but in case this breaks something unforeseen for somebody while I am out this evening, you can undo the changes by reverting https://svn.jboss.org/repos/jbossas/trunk/server/src/etc/conf/default/dep... to revision 78640. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178608#4178608 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178608

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why do messages destined for paging not get assigned mes

by timfox

Yes we could do something like that (that's what we do in JBM 1.4 with the null persistence). We don't need the node id though - the id only needs to be unique on that node, not globally unique. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178607#4178607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178607

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Optional injection with @Inject

by alesj

Resolved: https://jira.jboss.org/jira/browse/JBMICROCONT-356 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178582#4178582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178582

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why do messages destined for paging not get assigned mes

by clebert.suconic＠jboss.com

Can't we make the IDs based on the Node_ID & current_time + extraSequence somehow, in such way we don't need to look at the latestID when we restart? If we do that, we won't need to read the pages when restarting, and we could assign IDs before paging. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178573#4178573 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178573

17 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Re: Common marshalling infrastructure

by david.lloyd＠jboss.com

Well, I'm still working on the finishing bits and unit tests, so for now I'll just say, "42". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178571#4178571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178571

17 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5895; Processing too many classes

by alesj

"wolfc" wrote : I'm having the same problem here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178209#4178209. Same in what way? I don't see them excluding lib directory. It seems their problem is that they actually have lib directory, which includes some ejb3 annotated classes, which then get picked up by OptAMDD. Looks like ear's lib (or whatever user defines as 'lib') should be always strictly excluded in annotation scanning visitor? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178546#4178546 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178546

17 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5895; Processing too many classes

by wolfc

I'm having the same problem here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178209#4178209. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178540#4178540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178540

17 years, 6 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1454 Encapsulate Container infomation in TO/VO

by ALRubinger

"jaikiran" wrote : I just noticed that there is a StatefulSessionInvokableContext (in proxy) which currently implements the InvokableContext. I guess, this should now implement the new InvokableSessionContext. Do you recommend that i change this too? Yep. These look good to the naked eye, and I have all Unit Tests passing. If you can verify the clusteredsession tests in TestSuite are OK, than this is good for commit. There is one issue that we should probably break off from this work: "getDispatcherRegistrationName()" is being used throughout ProxyFactory code where perhaps "getName()" would be more appropriate. public ProxyFactoryBase(final String proxyFactoryName, InvokableContext container) | { | // Set properties | this.setName(proxyFactoryName); | this.setContainerName(container.getDispatcherRegistrationName()); | this.setContainerGuid(container.getGuid()); | this.setClassLoader(container.getClassloader()); | this.setAdvisor(container.getAdvisor()); | } Part of my initial design of the proxy component was based on the assumption that'd we'd be referring to the Container by one name, and this is not necessarily the case (there's a name used to register it in MC/Ejb3Registrar, and another used to register w/ AOP Dispatcher, and these are not guaranteed to be equal). So the solution there would involve adding something to ProxyFactory classes to support each property in the correct place. Let's open up a JIRA to address that differentiation (and clear up the code so future maintainers don't get confused). S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178512#4178512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178512

17 years, 6 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: Russian doll packaging in arbitrary directories - JBAS-5

by alesj

I'll port this DirectoryStructure to deployers project, to simplify the work needed to test this: --> sar with lib --> sar with top/snd/third (multiple dirs) --> sar inside ear with lib --> sar inside ear with top/snd/third (multiple dirs) Then if someone wants to use this, (s)he can enable it in AS - in some xyz-dpeloyers-jboss-beans.xml View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178510#4178510 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178510

17 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: gwt-console in distribution

by heiko.braun＠jboss.com

Sure, I will take a look at it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178486#4178486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178486

17 years, 6 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 September 2008