I have just tried to build the microcontainer from source and had a few issues.
There appears to be a missing dependency in deployers/pom.xml as it requires jboss-dependency (BeanMetaDataDeployer used it).
The second issue is the javacc configuraiton in osgi-int/pom.xml. It currently includes the package name as part of the outputDirectory instead of using the packageName. This has an impact on classpath/project generation using eclipse:eclipse.
The third issue is the location of the test resources in aop-mc-int. If you generate classpath/project files then eclipse will complain about one resource directory being included in another.
I would like to fix the two issue, any objections?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033273#4033273
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033273
Ok, this is clearer. I thought you were talking about A being notified of B's failure.
Ok, makes sense, but still not something I'd like to have in the CacheListener since this should not be the way to deal with exceptional circumstances.
Perhaps another listener to deal with such asynchronous exceptional cases? Still ugly, but at least we don't clutter the "regular use" listener, listening for normal events.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033237#4033237
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033237
"bill.burke(a)jboss.com" wrote : What code is forked?
I didn't mention forked code?
anonymous wrote : Are you still living in 2006?
I will admit that I stopped looking at the EJB3 code a while ago, but that was mainly
because trying to get anything done about what I see as the problems
wasn't getting anywhere, so it was a waste of energy.
I just left you guys to come to the correct conclusions yourselves
as you realize what the problems are and how unsupportable a component
doing its own integration with n platforms for m different versions
(n * m == large number) is.
EJBTHREE-932 tells me you haven't got there yet. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033196#4033196
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033196
I'm "ranting" at Carlo wanting to do JBoss Messaging integration in the EJB3 project.
The JIRA task he just raised.
I still don't see a "ActivationFactory" interface defined in either the appserver
or JBoss Embeded for EJB3 to inject that can be implemented as
1) An invocation on the JMX bus in JBoss4
2) A facade on the RAR metadata repository in JBoss5
3) Whatever mechanism other environments have for this integration.
I'll be able to sleep a lot easier when this (and many other properly defined and stable
integration points) exists and EJB3 uses it. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033190#4033190
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033190