[JBoss Seam] - Re: JBoss 4.2.0 / 4.2.1 - Seam 2.0.0B1 - Mail Problem
by pete.muir@jboss.org
"bsmithjj" wrote : Here is part of the SLSB that is not deploying - note also that bean is intended to serve as a timer that rereads incoming mail from its mailSession:
|
|
| | @Stateless
| | @Name("mailReader")
| | public class MailReaderBean implements MailReader {
| |
| | @Logger
| | private Log log;
| |
| | @PersistenceContext(unitName = "accessControlDatabase")
| | private EntityManager em;
| |
| | @Resource(mappedName = "java:/Mail")
| | private Session mailSession;
| |
| | @Resource
| | private TimerService timerService;
| |
| | @EJB(beanName="TerminationRequestManagerBean")
| | private TerminationRequestManager terminationRequestManager;
| |
| | @EJB(beanName="ActiveUserReconcilerBean")
| | private ActiveUserReconciler activeUserReconciler;
| |
| | @Timeout
| | public void readEmail(Timer timer) {
| | ... code ...
| | }
| |
| | public void startReading() {
| | ... code ...
| | }
| |
| | public void stopReading() {
| | ... code ...
| | }
| |
| | public boolean isMailReaderTimerRunning() {
| | ... code ...
| | }
| | }
| |
This is just injecting the MailSession using EJB3, not Seam, to inject the Seam managed mail session do:
@In private javax.mail.Session mailSession;
anonymous wrote : I've tried with and without adding mail-ra.rar and got the same problem. I'm also running with a jboss-app.xml that looks like this:
mail-ra.rar is for incoming mail - so you can take that out of the equation.
Sorry, not much help. But I don't think this has much to do with Seam.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085604#4085604
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085604
18 years, 10 months
[JBoss Portal] - "Cannot perform programmatic signout" exception
by tucano
When a user logs out of our JBoss Portal application he is sent to a portal page that contains a logout portlet whose processAction() method calls JBossActionResponse.signout("/home").
This works quite well when our users log in through our normal JSP form mechanism. However, the registration wizard of our website uses the new org.jboss.web.tomcat.security.login.WebAuthentication class to programatically log users in, such that they do not have to re-login once they have created the username and password.
The problem we have is when the programatically signed in members try to log out using the JBossActionResponse.signout() method. In looking at the code for this method, it is checking that the AUTH_TYPE of the portlet request is set to "FORM" and throwing an exception if it is not. When we programatically sign in using the WebAuthentication class, the AUTH_TYPE is set to "PROGRAMMATIC_WEB_LOGIN", and thus we get the exception.
My question is why this AUTH_TYPE check exists in the signout() method, and if anyone knows a way around it using the programmatic login.
Thanks,
Ted
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085597#4085597
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085597
18 years, 10 months