June 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3011) s:graphicImage throws NullPointerException GraphicImageResource.doWork when el expression for value is null

by Coral Featherstone (JIRA)

s:graphicImage throws NullPointerException GraphicImageResource.doWork when el expression for value is null ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3011 URL: http://jira.jboss.com/jira/browse/JBSEAM-3011 Project: Seam Issue Type: Bug Affects Versions: 2.0.1.GA Environment: all Reporter: Coral Featherstone An exception is thrown when s:graphicImage value is given an EL expression, part or all of which is null. . We are using s:graphicImage in a rich:modalPanel as the edit part of the crud and it relies on the selected row of a rich:datatable to get the image bytes. When no row is selected the following stack is thrown. 16:21:56,818 ERROR [ContextualHttpServletRequest] ended request due to exception java.lang.NullPointerException at org.jboss.seam.ui.graphicImage.GraphicImageResource.doWork(GraphicImageResource.java:69) at org.jboss.seam.ui.graphicImage.GraphicImageResource.access$000(GraphicImageResource.java:30) at org.jboss.seam.ui.graphicImage.GraphicImageResource$1.process(GraphicImageResource.java:53) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:53) at org.jboss.seam.ui.graphicImage.GraphicImageResource.getResource(GraphicImageResource.java:48) at org.jboss.seam.servlet.SeamResourceServlet.doGet(SeamResourceServlet.java:69) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 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.MultipartFilter.doFilter(MultipartFilter.java:85) 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:44) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:147) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:276) at org.ajax4jsf.Filter.doFilter(Filter.java:175) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) 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.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:432) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 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:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:619) -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2983) Unknown Entity when persisting seam managed JPA entity

by Guillaume Jeudy (JIRA)

Unknown Entity when persisting seam managed JPA entity ------------------------------------------------------ Key: JBSEAM-2983 URL: http://jira.jboss.com/jira/browse/JBSEAM-2983 Project: Seam Issue Type: Bug Affects Versions: 2.0.1.GA Reporter: Guillaume Jeudy Priority: Minor Caused by: java.lang.IllegalArgumentException: Unknown entity: com.archinsurance.rdm.entity.packages.impl.RefReleasePackageImpl_$$_javassist_4 at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:215) when attempting to persist a seam managed JPA entity. Seam instantiates a javassist proxy and this is what the user app is trying to persist. The exception is not thrown when the entity is marked with @Entity annotation, if it is mapped with XML hibernate mapping definition it will fail with the above exception. Implement a consistent behavior to handle the seam managed JPA entity usecase regardless of the mapping technique being used. As recommended by Pete Muir this use case should not be utilized. Suggested behavior should be to throw a more explicit exception on startup whenever this invalid usecase is detected. More details in the below forum thread: http://seamframework.org/Community/UnknownEntityWhenPersistingSeamManaged... -- 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, 8 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3001) core:filters element doesnt exist as outlined in seam doc

by Guillaume Jeudy (JIRA)

core:filters element doesnt exist as outlined in seam doc --------------------------------------------------------- Key: JBSEAM-3001 URL: http://jira.jboss.com/jira/browse/JBSEAM-3001 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.0.1.GA Reporter: Guillaume Jeudy Priority: Minor The documentation issue is right at the bottom of this page in the example on how to use persistence:filter with a seam managed persistence context. http://docs.jboss.com/seam/2.0.1.GA/reference/en/html/persistence.html#pe... I believe persistence:filters should replace core:filters in the doc. -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3097) Modify Filter to allow Collection Values

by Craig Savolainen (JIRA)

Modify Filter to allow Collection Values ---------------------------------------- Key: JBSEAM-3097 URL: http://jira.jboss.com/jira/browse/JBSEAM-3097 Project: Seam Issue Type: Feature Request Components: Core Reporter: Craig Savolainen Priority: Minor The current HibernatePersistenceProvider/ManagedHibernateSession implementations will not correctly pass a collection of values to the underlying filter. -- 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, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3118) Unclear ItemValidator example in reference (31.2)

by Richard Richter (JIRA)

Unclear ItemValidator example in reference (31.2) ------------------------------------------------- Key: JBSEAM-3118 URL: http://jira.jboss.com/jira/browse/JBSEAM-3118 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.0.A1 Reporter: Richard Richter In section 31.2 of Seam reference (2.1 version) there is an example which is not very clear: @Name("itemValidator") @BypassInterceptors @Validator public class ItemValidator implements Validator { public void validate(FacesContext context, UIComponent cmp, Object value) throws ValidatorException { ItemController ItemController = (ItemController) Component.getInstance("itemController"); return itemController.validate(value); } } First thing is that if you accept one import for Validator, the other usage of that type is broken - there are both Hibernate Validator annotation and JSF Validator interface used (I'd use FQN for this one probably). Other thing is that there is return of something for void method. Example is rather confusing as it is now. -- 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, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3014) Email / PDF rendering ignores custom taglibs defined with facelets.LIBRARIES in web.xml

by Gena Batalski (JIRA)

Email / PDF rendering ignores custom taglibs defined with facelets.LIBRARIES in web.xml --------------------------------------------------------------------------------------- Key: JBSEAM-3014 URL: http://jira.jboss.com/jira/browse/JBSEAM-3014 Project: Seam Issue Type: Bug Components: Mail, PDF Affects Versions: 2.1.0.A1, 2.0.2.GA Environment: 2.1.0.A1, Facelets shipped with Seam-gen, trinidad latest Reporter: Gena Batalski Assigned To: Pete Muir During the rendering of email/pdf occurs an exception, if the email or pdf uses custom facelets taglibs defined with context parameter facelets.LIBRARIES . -- 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, 8 months

2
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3137) Numberguess example throws NoClassDefFoundError: org/richfaces/webapp/taglib/UIComponentELTagBase

by Stan Silvert (JIRA)

Numberguess example throws NoClassDefFoundError: org/richfaces/webapp/taglib/UIComponentELTagBase ------------------------------------------------------------------------------------------------- Key: JBSEAM-3137 URL: http://jira.jboss.com/jira/browse/JBSEAM-3137 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.BETA1 Reporter: Stan Silvert If I run the trunk version of numberguess, I get: javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/richfaces/webapp/taglib/UIComponentELTagBase org.apache.jasper.servlet.JspServlet.service(JspServlet.java:273) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) I'm looking through the code and I noticed that org.jboss.seam.ui.util.cdk.UIComponentTagBase extends the RichFaces UIComponentELTagBase. I assume that is the problem? I assume you don't want Seam to be dependent on RichFaces? Also, Seam's UIComponentTagBase is marked as @deprecated. So I'm not sure how to proceed. I could add the RichFaces jar to numberguess, but that's probably not the correct fix. -- 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, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3031) components.properties not being used in seam-gen EAR

by Dan Allen (JIRA)

components.properties not being used in seam-gen EAR ---------------------------------------------------- Key: JBSEAM-3031 URL: http://jira.jboss.com/jira/browse/JBSEAM-3031 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.2.SP1, 2.1.0.BETA1 In the EAR build produced by seam-gen, the components.properties never gets a chance to do its job because the replacement tokens in components.xml are being filled in by the Ant build instead. -- 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, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2860) Allow subclass of BaseSeamTest to provide an alternate MockServletContext implementation

by Clint Popetz (JIRA)

Allow subclass of BaseSeamTest to provide an alternate MockServletContext implementation ---------------------------------------------------------------------------------------- Key: JBSEAM-2860 URL: http://jira.jboss.com/jira/browse/JBSEAM-2860 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.1.0.A1 Reporter: Clint Popetz Attachments: ExtendedServletContext.java, mockServletContext.diff I'm integrating seam into an environment which has a mock servlet context based on servletunit...but BaseSeamTest doesn't provide a hook for using that. This patch provides identical behavior by default, but allows subclasses to provide an alternate servletContext implementation. Note that BaseSeamTest wants to be able to call getInitParameters, so I've provided a subinterface "ExtendedServletContext," made BaseSeamTest use that interface, and made MockServletContext implement that interface. -- 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, 8 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3125) seam conversation and session.disconnect()

by Florian Keusch (JIRA)

seam conversation and session.disconnect() ------------------------------------------ Key: JBSEAM-3125 URL: http://jira.jboss.com/jira/browse/JBSEAM-3125 Project: Seam Issue Type: Bug Components: Spring Environment: Seam 2.0.2.SP1 Spring 2.5.4 Reporter: Florian Keusch hi, we use seam/spring/hibernate in our application. We detected a problem that database connections are not released after each request during seam conversations. Then if we have many conversations we can run out of connections. Let me explain this issue a little bit more: If a conversation starts a session is opened. This session is bound to the conversation and borrows a database connection from the pool. After the request the session doesn't have to be closed necessarily, but the session should be disconnected (to release the connection). What happens in the code (org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean) is that the session only is 'marked' as closed. Later seam recognizes that the conversation is still opened and the session will not be closed at the end of the request. The connection is therefore not returned to the pool for many requests until the conversation ends. For our case we fixed this problem by slightly changing the code of org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean (see the patch). We added code to disconnect the session greetings fke patch: --- SeamManagedSessionFactoryBean.java 2008-06-19 09:17:09.152049800 +0200 +++ SeamManagedSessionFactoryBeanPatched.java 2008-05-27 20:16:46.000000000 +0200 @@ -165,8 +165,6 @@ } if (method.getName().equals("close")) { - Session session = getSession(); - session.disconnect(); isClosed = true; return null; } @@ -290,7 +288,6 @@ if (method.getName().equals("close")) { log.debug("Closing Session Proxy."); - delegate.disconnect(); closed = true; return null; } -- 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, 8 months

3
5
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 June 2008