anonymous wrote : I'm concerned you're starting to mix requirements. We have splitter and aggregator capabilities elsewhere too.
Yes, so am I. This was more of a desperate solution to get things working for me.
Should I use the Notifiers for this?
In this case I have to add the correlation stuff and that would require some refactoring of NotifyQueue and NotifyTopics. Is this alright?
I'll also check out the wiretap as I havn't done so yet.
thanks,
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064902#4064902
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064902
"tfennelly" wrote : This sounds like wiretap to me.
|
And I'm fairly sure we have that too.
anonymous wrote : I think the whole area of routing messages off the bus (to ESB Message Unaware endpoints) is something that needs attention. We Gateways for getting messages on and the Notifiers and Routers (and possibly more) for getting them off. Grrr!!!
Agreed, but we've already agreed that it's good enough for the 4.2GA release. So let's not go opening that up again ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064900#4064900
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064900
On an initial glance it looks like we've reached the limit what we can do without proper security integration.
The security deployer currently only works with EJB 2 meta data and EJB 3 meta data isn't being augmented with annotations yet. So as a work around the EJB registration deployer tells the security deployer to ignore this deployment.
We need the unified meta model before we can move on.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064862#4064862
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064862
That would be ok if the ServerLoader bootstrap class loader could be an osgi style class loader to have more control over what is exported. There are too many bootstrap jars that should not be visible to other deployments (trove.jar, dom4j.jar, concurrent.jar, log4j.jar, jaxb*, stax*) or we end up with thirdparty code that should only be an implementation detail in the bootstrap classpath.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064836#4064836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064836