April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2158) Can't inject a org.hibernate.classic.Session

by Clint Popetz (JIRA)

Can't inject a org.hibernate.classic.Session -------------------------------------------- Key: JBSEAM-2158 URL: http://jira.jboss.com/jira/browse/JBSEAM-2158 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR3 Reporter: Clint Popetz If one does import org.hibernate.classic.Session; @In Session session; the injection throws an IllegalArgumentException, because HibernateSessionProxy doesn't implement the classic Session interface. It seems harmless to do this, and would allow for easier migration of large source bases from loyal hibernate early adoptees that are now transitioning to the next-big-thing. If making HibernateSessionProxy implement the classic interface would be acceptable, please make note of it here and I'll create a patch to that effect. -- 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

17 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2917) Bad cache in getEjbDescriptor

by Clint Popetz (JIRA)

Bad cache in getEjbDescriptor ----------------------------- Key: JBSEAM-2917 URL: http://jira.jboss.com/jira/browse/JBSEAM-2917 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR1 Reporter: Clint Popetz Seam.getEjbDescriptor re-initializes its cache of descriptors every time it fails to find a given class. This method is getting called for every non-injected field of a conversational component, on every invocation field of a component. In my case, this method was eating up an average of 20% of page time. -- 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

17 years, 10 months

5
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2741) "org.jboss.seam.spring.ContextLoader" cannot be resolved to a type

by Kurt Vermeiren (JIRA)

"org.jboss.seam.spring.ContextLoader" cannot be resolved to a type ------------------------------------------------------------------ Key: JBSEAM-2741 URL: http://jira.jboss.com/jira/browse/JBSEAM-2741 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 2.0.1.GA Reporter: Kurt Vermeiren I'm trying to load the Spring application context via the component.xml I followed the instructions in the Seam Reference documentation, the component.xml looks like: <?xml version="1.0" encoding="UTF-8"?> <components xmlns="http://jboss.com/products/seam/components" xmlns:core="http://jboss.com/products/seam/core" xmlns:drools="http://jboss.com/products/seam/drools" xmlns:spring="http://jboss.com/products/seam/spring" xmlns:security="http://jboss.com/products/seam/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.com/products/seam/core http://jboss.com/products/seam/core-2.0.xsd http://jboss.com/products/seam/persistence http://jboss.com/products/seam/persistence-2.0.xsd http://jboss.com/products/seam/drools http://jboss.com/products/seam/drools-2.0.xsd http://jboss.com/products/seam/bpm http://jboss.com/products/seam/bpm-2.0.xsd http://jboss.com/products/seam/security http://jboss.com/products/seam/security-2.0.xsd http://jboss.com/products/seam/mail http://jboss.com/products/seam/mail-2.0.xsd http://jboss.com/products/seam/components http://jboss.com/products/seam/components-2.0.xsd"> ... <spring:context-loader> <spring:config-locations> <value>WEB-INF/SpringContext.xml</value> </spring:config-locations> </spring:context-loader> However I keep getting an error saying that "org.jboss.seam.spring.ContextLoader" cannot be resolved to a type. I checked jboss-seam-ioc.jar (in the classpath), and I see that ContextLoader is not in org.jboss.seam.spring but in the org.jboss.seam.ioc.spring package. I think I can work around it by loading the spring context via web.xml, but I wonder if this is a bug? -- 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

17 years, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2427) Email rendering from async method/event fails to find web resources

by Allon Rauer (JIRA)

Email rendering from async method/event fails to find web resources ------------------------------------------------------------------- Key: JBSEAM-2427 URL: http://jira.jboss.com/jira/browse/JBSEAM-2427 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Allon Rauer Priority: Minor Our system sometimes renders emails (system status, etc.) triggered by a periodic async event. In this context, the email renderer cannot find the xhtml email templates that reside in the web resources directory. Solution: in org.jboss.seam.ui.facelet.FaceletsRenderer modify this block (to propagate the servlet context).... from: // If a FacesContext isn't available, set one up if (FacesContext.getCurrentInstance() == null) { MockFacesContext mockFacesContext = new MockFacesContext(new MockExternalContext()) .setCurrent(); mockFacesContext.createViewRoot(); } to: // If a FacesContext isn't available, set one up if (FacesContext.getCurrentInstance() == null) { MockFacesContext mockFacesContext = new MockFacesContext(new MockExternalContext(ServletLifecycle.getServletContext())) .setCurrent(); mockFacesContext.createViewRoot(); } -- 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

17 years, 10 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2187) E-mail attachment <cid:xxxxxx> problem

by Stefano Zaccaria (JIRA)

E-mail attachment <cid:xxxxxx> problem -------------------------------------- Key: JBSEAM-2187 URL: http://jira.jboss.com/jira/browse/JBSEAM-2187 Project: JBoss Seam Issue Type: Bug Components: Mail Affects Versions: 2.0.0.CR3 Reporter: Stefano Zaccaria Assigned To: Pete Muir Priority: Minor Fix For: 2.0.0.GA When use the cid: tag with seam like the document read <m:attachment value="#{person.photo}" contentType="image/jpeg" fileName="#{person.firstname}_#{person.lastname}.jpg" status="personPhoto" disposition="inline" /> <img src="cid:#{personPhoto.contentId}" /> In my email client (Thunderbird) the image is attachment and not place inline -- 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

17 years, 10 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1274) Not able to query FacesMessages to determine if any messages have been added.

by Nathaniel Stoddard (JIRA)

Not able to query FacesMessages to determine if any messages have been added. ----------------------------------------------------------------------------- Key: JBSEAM-1274 URL: http://jira.jboss.com/jira/browse/JBSEAM-1274 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Nathaniel Stoddard It would be helpful to determine if messages have been added to FacesMessages. At this point, it is impossible to determine if messages are present in FacesMessages. -- 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

17 years, 10 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-715) Allow multiple pages.xml files

by Stephan Bublava (JIRA)

Allow multiple pages.xml files ------------------------------ Key: JBSEAM-715 URL: http://jira.jboss.com/jira/browse/JBSEAM-715 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.1.GA Reporter: Stephan Bublava Currently it's possible to use one global pages.xml file or one file per page. I believe that both options are not well-suited for large applications. Consider an application like: /catalog/foo.xhtml /bar.xhtml /... /basket/foo.xhtml /bar.xhtml /... /admin/foo.xhtml /bar.xhtml /... In this case using a global file would be too convoluted, but at the same time one file per page is too fine grained. It would be great to allow one file per directory ("module"), either using a similar naming convention to page.xml or by adding an "import" tag to pages.xml. -- 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

17 years, 10 months

9
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-863) Remember-Me automatic authentication

by H T (JIRA)

Remember-Me automatic authentication ------------------------------------ Key: JBSEAM-863 URL: http://jira.jboss.com/jira/browse/JBSEAM-863 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: H T Fix For: 1.1.7.GA Extend the behaviour of Remember-Me to automatically authenticate the user after they have selected the "Remember Me" service rather than have him or her re-enter their password each time. -- 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

17 years, 10 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2039) selectManyListbox executePhase NullPointerException

by Przemyslaw Rudzki (JIRA)

selectManyListbox executePhase NullPointerException --------------------------------------------------- Key: JBSEAM-2039 URL: http://jira.jboss.com/jira/browse/JBSEAM-2039 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.1.GA Environment: JBoss AS 4.2.1GA, Sun Microsystems JavaServer Faces Implementation 1.2_04-b16-p02, Ubuntu 7.04 Reporter: Przemyslaw Rudzki Fix For: 1.2.1.GA I have simple model: class Book { @ManyToMany //unidirectional private List<DictionaryEntry> dictionaryEntryList; } In the JSF it is presented as: <h:selectManyListbox id="select2Status" value="#{bookHome.instance.dictionaryEntryList}" required="false"> <s:convertEntity /> <s:selectItems value="#{dictionaryEntryList.resultList}" var="item" label="#{item.value}" noSelectionLabel="---------" /> </h:selectManyListbox> 1. When I create entity with some elements selected everything works fine. 2. When I edit the selection and update everything works great. 3. The problem occurs when I deselect all the items and try to do an update. I get then: 00:46:49,840 WARN [lifecycle] executePhase(PROCESS_VALIDATIONS 3,com.sun.faces.context.FacesContextImpl@1625154) threw exception javax.faces.FacesException at com.sun.faces.lifecycle.ProcessValidationsPhase.execute(ProcessValidationsPhase.java:108) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:307) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 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:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NullPointerException at javax.faces.component.UISelectMany.matchValue(UISelectMany.java:496) at javax.faces.component.UISelectMany.validateValue(UISelectMany.java:454) -- 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

17 years, 10 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2226) Need Customer actionOutcome and actionMethod

by Danny Chen (JIRA)

Need Customer actionOutcome and actionMethod -------------------------------------------- Key: JBSEAM-2226 URL: http://jira.jboss.com/jira/browse/JBSEAM-2226 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.GA Reporter: Danny Chen For conversion id, JBoss Seam provide customize method, for example: <core:manager conversation-timeout="300000" conversation-id-parameter="cid" /> But for <s:link>, <s:button>'s actionOutcome and actionMethod, there isn't a way to change these id. I find it is hardcode in: UIAction: public String getName() { return isMethodBinding() ? "actionMethod" : "actionOutcome"; } Pages: private static boolean callAction(FacesContext facesContext) { //TODO: refactor with Pages.instance().callAction()!! boolean result = false; String outcome = facesContext.getExternalContext() .getRequestParameterMap().get("actionOutcome"); String fromAction = outcome; if (outcome==null) { String actionId = facesContext.getExternalContext() .getRequestParameterMap().get("actionMethod"); if (actionId!=null) { if ( !SafeActions.instance().isActionSafe(actionId) ) return result; String expression = SafeActions.toAction(actionId); result = true; MethodExpression actionExpression = Expressions.instance().createMethodExpression(expression); outcome = toString( actionExpression.invoke() ); fromAction = expression; handleOutcome(facesContext, outcome, fromAction); } } else { handleOutcome(facesContext, outcome, fromAction); } return result; } Can let us change them just like conversion id? Thanks -- 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

17 years, 10 months

3
6
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2008