OK,
I gave it a quick try. There is a problem with scenarios which imply a circular dependency between the EJBs and the Spring Deployer.
If the Spring Bean depends on an EJB that needs to be injected with another Spring Bean from the same ApplicationContext, an initialization failure is to be expected, because the EJB cannot be initialized (can't find the ApplicationContext in JNDI, its creation is not finalized yet) which in turns causes the ApplicationContext creation to fail (EJB can't be injected in Spring bean).
However, if the Spring bean depends on an EJB that is not dependent on another Spring bean, then all should work fine.
Hope that helps,
Marius
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242089#4242089
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242089
Also, make sure that you use the <context:annotation-config/> namespace element in your Spring configuration, and make sure you don't have circular dependencies ala EJB->SpringBean->EJB etc, which would make the process of creating the components pretty awkward.
As a note, @Spring is a JBoss-specific annotation used for injecting SpringDeployer-created beans into EJBs but it does not work the other way around.
Cheers,
Marius
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242082#4242082
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242082
I guess it is a bug in JBoss.
When I call
| SecurityAssociation.getSubject().getPrincipals()
|
I get the set of the principals where the first element in this set is the my own implementation of the principal class and that's right, subject gets filled with principals in the LoginModule commit method.
However when I call Sec
| SecurityAssociation.getPrincipal();
| or
| SecurityAssociation.getCallerPrincipal();
| or
| sessionContext.getCallerPrincipal();
|
I always get the instance of the SimplePrincipal.
It seems that my loginModule works well, but during the propagation of the caller principal jboss is ignoring my principal class and sets his default.
Martin
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242075#4242075
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242075
I tried setting SupportsFailOver to true on the Connection. Then, I tried testing failover by taking down node B0, and fail over worked, messages went to B1. After i period of time i brought up B0 and took down B1. Messages never got delievered to B0 and piled up in the message/deliver count queue. I brought up B1, and still nothing happened until i took down B0, then fail over occured and B1 processed the backlog of messages. Next i took down B1 and once again i end up in the messages stuck situation.
It seems to me that FailOver works the first time I take down node B0, but after that FailOver doesn't work properly. Is there anything else i can try?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242073#4242073
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242073