[JBoss AOP] - Re: Different jboss-aop.xml files for unit testing
by nizzy
Hi Flavia,
Can I just confirm a few things about my setup;
1. I would have thought the following pointcut would have worked
| <aspect class="com.ecebs.unittest.aop.aspect.ExceptionInjector" scope="PER_CLASS" />
|
| <bind pointcut="call(public void com.ecebs.unittest.aop.ExampleManagerBean->createObject(..))
| AND withincode(public void com.ecebs.unittest.aop.ExampleManagerBeanTest->testCreateObject_MultefileException())">
| <advice name="throwMultefileException" aspect="com.ecebs.unittest.aop.aspect.ExceptionInjector" />
| </bind>
Just to explain what I have done
ExampleManagerBean - session bean under test
ExampleManagerBeanTest - junit test
So pointcut is saying "if createObject method in session bean is called from within the junit test then execute aspect - ExceptionInjector"
Is my understanding correct?
I still can't get the aspect to be executed!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225870#4225870
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225870
17 years
[JBoss Messaging] - Exciting times for JBoss Messaging
by timfox
As many of you will be aware, for some time now Red Hat has had more than one messaging system implementation in house:
JBoss Messaging - the project based at JBoss, (currently available in the JBoss EAP and JBoss SOA-P products), and Red Hat Messaging, based on the Apache Qpid project (currently available in the Red Hat Enterprise MRG product).
For a while now we've recognised that we need to present a single consistent messaging offering across the whole of JBoss / Red Hat, so the projects are coming together to deliver a unified cross-company messaging solution in the future.
To reach that goal, JBoss Messaging 2.x will implement AMQP, as we consider this to be of strategic importance, along with JMS, and of course the full set of enterprise messaging functionality that you'd expect in any serious messaging broker.
JBoss Messaging will also be relicensing it's code under the ASL 2.0 licence (moving away from LGPL) in order to be usable by the widest range of interested parties.
The JBoss Messaging team will work with the Apache QPid community to ensure the QPid AMQP clients work seamless with both the QPid and JBoss Messaging brokers.
The JBoss Messaging project will remain as a community project at jboss.org.
I think you'll agree this is great news and will signal the start of a new era of unified messaging at Red Hat. :)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225860#4225860
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225860
17 years