[JBoss JIRA] Created: (SEAMSECURITY-12) Introduce session management into Seam Security
by Shane Bryzak (JIRA)
Introduce session management into Seam Security
-----------------------------------------------
Key: SEAMSECURITY-12
URL: https://jira.jboss.org/browse/SEAMSECURITY-12
Project: Seam Security
Issue Type: Feature Request
Reporter: Shane Bryzak
Assignee: Shane Bryzak
Fix For: 3.0.0.Beta1
A feature in which many of our users have expressed interest in the past, session management would provide an application-scoped registry of all active user sessions. We should provide features for terminating selected user sessions, setting a policy for multiple user sessions (one/multiple session per user) and provide some kind of formal support for session logging (last login time, ip address, etc). Up till now we've told our users to implement all this stuff manually, but I think it would be cool if we provided support for it out of the box.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBSEAM-4577) Seam Mail looks up template in wrong context on tomcat with shared seam
by Vasilii Lukoyanov (JIRA)
Seam Mail looks up template in wrong context on tomcat with shared seam
------------------------------------------------------------------------
Key: JBSEAM-4577
URL: https://jira.jboss.org/jira/browse/JBSEAM-4577
Project: Seam
Issue Type: Bug
Components: Mail
Affects Versions: 2.2.0.GA
Environment: Tomcat 6.0.18, Seam 2.2.0.GA (shared)
Reporter: Vasilii Lukoyanov
Assignee: Pete Muir
I've got Tomcat with Seam jars shared among all projects (shared.loader=${catalina.base}/shared/seam/*.jar in catalina.properties). Each app has it's own vhost, and deployed to ROOT context.
Layout is the following:
vhosts/siteA.com/ROOT
vhosts/siteB.com/ROOT
Seam application on siteB.com uses seam mail to send confirmation emails. But when it tries to send a message (template is /layout/1email.xhtml)
the following exception is thrown:
javax.servlet.ServletException: #{mailer.sendPreActivationEmail}: java.lang.IllegalArgumentException: resource doesn't exist: /layout/1email.xhtml
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:164)
at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141)
at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90)
at org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:406)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495)
at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60)
at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419)
at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:378)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1509)
at java.lang.Thread.run(Thread.java:619)
Caused by: javax.faces.FacesException: #{mailer.sendPreActivationEmail}: java.lang.IllegalArgumentException: resource doesn't exist: /layout/1email.xhtml
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
at javax.faces.component.UICommand.broadcast(UICommand.java:387)
at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
... 39 more
After some investigation I tried to put message template /layout/1email.xhtml into siteA.com context (vhosts/siteA.com/ROOT). After that I was able to send messages from siteB.com application.
Component that sends code:
@Name("mailer")
@Scope(ScopeType.CONVERSATION)
public class Mailer {
@In("renderer")
private Renderer _renderer;
public void sendPreActivationEmail(Account aUser) {
Contexts.getConversationContext().set("account", aUser);
_renderer.render("/email/eganov_pre_activate.xhtml");
}
}
Important note: when tomcat is starting, siteA.com loads first.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3355) SeamExpressionEvaluator gobbles up exceptions
by Wolfgang Schwendt (JIRA)
SeamExpressionEvaluator gobbles up exceptions
----------------------------------------------
Key: JBSEAM-3355
URL: https://jira.jboss.org/jira/browse/JBSEAM-3355
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.BETA1
Reporter: Wolfgang Schwendt
Priority: Critical
Rev 8710 of org.jboss.seam.bpm.SeamExpressionEvaluator introduced a serious bug. If the invocation of the method expression (me.invoke(...)) throws an exception such as org.jboss.seam.security.AuthorizationException, the SeamExpressionEvaluator afterwards tries to evaluate the EL expression as a value expression. This of course results in a second exception thrown: PropertyNotFoundException. Consequently, the list "exceptions" has size > 2 (rather than just size==1), which results in SeamExpressionEvaluator throwing an ELException that does not wrap the exception which originally caused the method expression invocation to fail.
The bug was introduced because, compared with earlier versions, the try/catch-blocks for the method expression and value expression evaluation were changed and are now wrong. This is serious because it breaks the handling of any application exception thrown while evaluating the EL method expression, such as AuthorizationException.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (SEAMINTL-4) Named parameters in localized messages
by Aslak Knutsen (JIRA)
Named parameters in localized messages
--------------------------------------
Key: SEAMINTL-4
URL: https://jira.jboss.org/browse/SEAMINTL-4
Project: Seam i18n
Issue Type: Feature Request
Components: Messages
Reporter: Aslak Knutsen
Priority: Minor
When coming back to localized message files after being away for a while, it's always a problem to remember what object/value parameter {2} is suppose to be. At this point you have to find the specific message location in the source code and read through the code to figure out what's actually being passed in.
It's also hard to send the file over to someone for translation, because they most likely also need an explanation of what {2} is.
It would be nice to be able to used named parameters, but with Java(< 7) that is a bit of a pain to code.
Would it be possible with some middle ground;
e.g. A name/alias in the message file that is ignored by the parser, but there just for documentation.
(Maybe even function as a named parameter when Java 7 comes out?)
"Welcome {0:firstName} {1:lastName}!"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2403) Cant build Seam from the CR1 download
by Chris Lowe (JIRA)
Cant build Seam from the CR1 download
-------------------------------------
Key: JBSEAM-2403
URL: http://jira.jboss.com/jira/browse/JBSEAM-2403
Project: JBoss Seam
Issue Type: Bug
Environment: Windows XP, Redhat Developer Studio RC1
Reporter: Chris Lowe
Getting the following exception when trying to build Seam 2.0.1 CVS on Win XP
[java] [ERROR] Error on generate component
[java] org.ajax4jsf.builder.config.ParsingException: I/O error on parsing config file
[java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:387)
[java] at org.ajax4jsf.builder.mojo.GenerateMojo.createConfig(GenerateMojo.java:253)
[java] at org.ajax4jsf.builder.mojo.GenerateMojo.execute(GenerateMojo.java:92)
[java] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:4
20)
[java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExe
cutor.java:539)
[java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Default
LifecycleExecutor.java:480)
[java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExec
utor.java:459)
[java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(Def
aultLifecycleExecutor.java:311)
[java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifec
ycleExecutor.java:278)
[java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor
.java:143)
[java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330)
[java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123)
[java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25
)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
[java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
[java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
[java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[java] Caused by: java.net.MalformedURLException: unknown protocol: c
[java] at java.net.URL.<init>(URL.java:574)
[java] at java.net.URL.<init>(URL.java:464)
[java] at java.net.URL.<init>(URL.java:413)
[java] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntit
yManager.java:650)
[java] at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVe
rsionDetector.java:186)
[java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configurati
on.java:771)
[java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configurati
on.java:737)
[java] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107)
[java] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser
.java:1205)
[java] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserI
mpl.java:522)
[java] at org.apache.commons.digester.Digester.parse(Digester.java:1605)
[java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:384)
[java] ... 20 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months