I'm thinking of introducing something like this
| public class ControllerStates
| {
| public static ControllerState previousState(List<ControllerState> states, ControllerState state);
|
| public static int currentStateIndex(List<ControllerState> states, ControllerState state);
|
| public static ControllerState nextState(List<ControllerState> states, ControllerState state);
|
| ...
| }
|
to handle this previous/next state lookup in a singe place.
Currently there is a bunch of code that does this, mostly w/o any constraints check, e.g. no such state in states.
I'll push it in org.jboss.dependency.spi.helpers package.
Or should/could this be on the ControllerState already?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142290#4142290
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142290
"jesper.pedersen" wrote : We need to target the adaptor implementation towards JBM 1.4 as it is deployed in AS 5.0 and EAP 4.3.
|
My comments about a JBM specific RA were referring to JBM 2.0 only. There's no way we're going to do this on the EAP 4.3 / AS 5 timescale. (EAP 4.3 code freeze has already started!).
To fix the EAP 4.3 bug, the current generic JMS RA needs to be patched so it doesn't make erroneous assumptions of XA capability based on instanceof.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142286#4142286
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142286
We need to target the adaptor implementation towards JBM 1.4 as it is deployed in AS 5.0 and EAP 4.3.
An implementation for JBM 2.0 would happen at a later point.
Looking at other projects - ActiveMQ and JORAM - they include an adaptor in their distribution so I think we should go this way also - e.g. as a sub-project in JBM.
Then we can remove the existing JCA/JMS code in AS/trunk as JBossMQ isn't used anymore.
There are properly some code that can be shared, but lets look at that at a later point when the implementation is more or less complete.
I'll get something up and running and we can look into importing it into JBM SVN.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142274#4142274
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142274