[Security & JAAS/JBoss] - Re: retry fails with form based authentication woth custom l
by j2ee_junkie
ppradhan,
One thing that is not completely clear from your description is wether or not the user has actually authenticated to servlet container. Just because the login form is returned does not neccessarily mean authentication did not happen. To be more specific...
Consider the case when a request is made to login form page direclty. The user fills out the form and submits. If the user authenticated correctly, then the container will redirect user back to originally requested page. Which in this case happens to be the login form.
So I suggest trying one of two things. Either add some temporary code to your login form (jsp) to display something if user is authenticated (i.e. request.getUserPrincipal()). Or create and secure another page (well call it main). Then request main. If user has not authenticated, they should be forwarded to login form. Once authenticated, user should be forwarded back to main.
cgriffith
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964032#3964032
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964032
19 years, 9 months
[EJB 3.0] - Re: ClassCastException with ActiveMQ RA
by jc7442
issue 1: ClassCastException is due to the fact that MDB EJB3 RC8 implementation is not able to create topic/queue with another implementation than JBossMQ.
isue 2: If you create topic/queue using XML, you can go one step further. But now the problem is that MDB EJB3 use a createConnectionConsummer method that is optional in JMS 1.1 spec.
Consequently, MDB EJB3 + activeMQ does not works.
You can unse JBoss Messaging. You will not be able to create topic/queue dynamically (issue 1) but you will be able to use MDB EJB3 when queue is already created (there is a demo with EJB3 in the downloaf of messaging).
If you really wants to use activeMQ, you can write your MDB in EJB2 style. It works fine.
In SVN, it looks like a lot of works have been done to improve in class MDB.java, I first wanted to patch it but there is so many differences between EJB3 RC8 branch and the main branch ... that now I prefer the solution of writting MDB in EJB2 style.
Question is while the issue be corrected in a further rcx release of EJB3 or should we wait till a JBoss 5 release ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964030#3964030
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964030
19 years, 9 months