August 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-6) s:debug

by Nicklas Karlsson (JIRA)

s:debug ------- Key: SEAMFACES-6 URL: https://jira.jboss.org/jira/browse/SEAMFACES-6 Project: Seam Faces Issue Type: Feature Request Reporter: Nicklas Karlsson Assignee: Lincoln Baxter III The return of the s:debug that never really got completed in Seam 2 ;-) A <s:debug/> tag that can be dropped in a page and you can bring up a display of what's in the context, the active Seam config, perhaps even some performance numbers for the page, security stuff, persistence stuff. The ability to add custom facets in this for displaying own data is nice, too. -- 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, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (SEAMFACES-60) Cannot deploy a Weld ear application which uses Weld Extensions

by Adam Warski (JIRA)

Cannot deploy a Weld ear application which uses Weld Extensions --------------------------------------------------------------- Key: SEAMFACES-60 URL: https://jira.jboss.org/browse/SEAMFACES-60 Project: Seam Faces Issue Type: Bug Affects Versions: 3.0.0.Beta1 Reporter: Adam Warski Stack trace: http://pastie.org/1320406 See also: https://jira.jboss.org/browse/JBAS-8660 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
8
0 / 0

[JBoss JIRA] Created: (SEAMFACES-50) Extra BeanManagerProviders in service file results in no BM found on beta-1

by Nicklas Karlsson (JIRA)

Extra BeanManagerProviders in service file results in no BM found on beta-1 --------------------------------------------------------------------------- Key: SEAMFACES-50 URL: https://jira.jboss.org/browse/SEAMFACES-50 Project: Seam Faces Issue Type: Bug Components: Build & Distribution Affects Versions: 3.0.0.Alpha3 Reporter: Nicklas Karlsson The faces modules contains the service file for BeanManagerProvider that has org.jboss.weld.extensions.beanManager.DefaultJndiBeanManagerProvider org.jboss.weld.extensions.beanManager.JBossJndiBeanManagerProvider in addition to it's own org.jboss.seam.faces.beanManager.FacesServletContextBeanManagerProvider Since the weld extensions also carry the Default/JBoss JNDI providers we end up with 5 providers for that dependency combination. For some reason (classloading?), in the beta1-AS Pete provided this is a problem - resulting in *no* BeanManagers being found (which results in a crash when the faces module SeamExternalContext is set up for the first time) Removing the JNDI based BeanManagerProviders from faces appears to help the issue itself but it leaves the faces module completely dependent on other modules for BM access -- 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, 1 month

5
5
0 / 0

[JBoss JIRA] Created: (SEAMFACES-48) UIInputContainer doesn't fetch messages for valuebindings against ISO-8859-1 fields

by Nicklas Karlsson (JIRA)

UIInputContainer doesn't fetch messages for valuebindings against ISO-8859-1 fields ----------------------------------------------------------------------------------- Key: SEAMFACES-48 URL: https://jira.jboss.org/browse/SEAMFACES-48 Project: Seam Faces Issue Type: Bug Components: UI Components Affects Versions: 3.0.0.Alpha3 Reporter: Nicklas Karlsson Priority: Minor iso-8859-1 field names don't have their messages displayed (M4). Could also be something with the general JSF config, though. -- 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, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-188) CatchExceptionHandler ignores JSF AbortProcessingException

by George Gastaldi (JIRA)

CatchExceptionHandler ignores JSF AbortProcessingException ---------------------------------------------------------- Key: SEAMFACES-188 URL: https://issues.jboss.org/browse/SEAMFACES-188 Project: Seam Faces Issue Type: Bug Reporter: George Gastaldi When an exception is thrown on an actionListener (clicking a link for example), an AbortProcessingException is thrown. However, this exception is ignored on org.jboss.seam.faces.exception.CatchExceptionHandler. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-196) Support for FacesManager

by George Gastaldi (JIRA)

Support for FacesManager ------------------------ Key: SEAMFACES-196 URL: https://issues.jboss.org/browse/SEAMFACES-196 Project: Seam Faces Issue Type: Feature Request Reporter: George Gastaldi It would be nice to have a FacesManager class just like we had in Seam 2, to - allow redirects to another view; - pass parameters as a Map - encode the conversation ID -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (SEAMFACES-195) Removed combined maven module

by Brian Leathem (JIRA)

Removed combined maven module ----------------------------- Key: SEAMFACES-195 URL: https://issues.jboss.org/browse/SEAMFACES-195 Project: Seam Faces Issue Type: Task Components: Build & Distribution Affects Versions: 3.0.2 Reporter: Brian Leathem Fix For: 3.1.0.Beta1 Removed combined maven module, and change the impl artifact to drop the impl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3592) Security concerns regarding Seam.Remoting.eval()

by Drew Kutchar (JIRA)

Security concerns regarding Seam.Remoting.eval() ------------------------------------------------ Key: JBSEAM-3592 URL: https://jira.jboss.org/jira/browse/JBSEAM-3592 Project: Seam Issue Type: Task Components: Remoting Reporter: Drew Kutchar Assignee: Shane Bryzak A malicious user can import the seam/remoting/resource/remote.js and use Seam.Remoting.eval() to bypass @WebRemote restrictions and call any arbitrary method? This can be a very serious security hole, even if Seam Remoting is not enabled (by marking any components using @WebRemote). Shane Bryzak stated that he is aware of this issue and has disabled Seam.Remoting.eval() functionality until he finds a way for expression evaluations to honor the @WebRemote annotation. This JIRA is created to track Shane's work. -- 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, 1 month

2
3
0 / 0

[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, 1 month

2
4
0 / 0

[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, 1 month

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2011