August 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3227) Update to Hibernate Tools 3.2.3.GA

by Pete Muir (JIRA)

Update to Hibernate Tools 3.2.3.GA ---------------------------------- Key: JBSEAM-3227 URL: https://jira.jboss.org/jira/browse/JBSEAM-3227 Project: Seam Issue Type: Task Components: Tools Reporter: Pete Muir Assignee: Pete Muir Fix For: 2.1.0.BETA1 -- 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

16 years, 5 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3052) Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle

by Peter Maedel (JIRA)

Catch & Print (RunTime)Exceptions that get produced within Seam LifeCycle ------------------------------------------------------------------------- Key: JBSEAM-3052 URL: http://jira.jboss.com/jira/browse/JBSEAM-3052 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.2.GA Environment: JBoss AS 4.2.2 Seam 2.0.2 Reporter: Peter Maedel Lots of people have been dealing with the issue of overwritten exceptions: http://www.seamframework.org/Community/ConnectionProblem http://www.seamframework.org/Community/TransactionIsNotActiveWithCreateAn... Although in some cases this behaviour is part of EJB specification (EJB Container overwriting Exception) I am unsure if there isnt a possibility within Seam to print exceptions when they occure rather than have them overwritten with useless junk (cannot open connection, transaction is abort_only) later on. If you want to reproduce try opening a page that references a bean with this @create method: @Create public void iCrash(){ new File("nonExistentDirectory").listFiles(); } Honestly this behaviour has been a horrible waste of time so far! -- 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

16 years, 5 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3221) seam-gen build failing on deployment due to missing jboss-seam-excel dependency

by Jacob Orshalick (JIRA)

seam-gen build failing on deployment due to missing jboss-seam-excel dependency ------------------------------------------------------------------------------- Key: JBSEAM-3221 URL: https://jira.jboss.org/jira/browse/JBSEAM-3221 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Assignee: Jacob Orshalick Fix For: 2.1.0.BETA1 juxl.jar needs to be added to deployment lists for both war and ear seam-gen'd projects -- 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

16 years, 5 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2972) Unit test fails because of wicket unavailabity

by Joshua Partogi (JIRA)

Unit test fails because of wicket unavailabity ---------------------------------------------- Key: JBSEAM-2972 URL: http://jira.jboss.com/jira/browse/JBSEAM-2972 Project: Seam Issue Type: Task Components: Wicket Affects Versions: 2.1.0.A1 Reporter: Joshua Partogi Unit test fails because wicket component is not installed. Here are the message: java.lang.IllegalStateException: Must set application-class in <web:wicket-filter /> in components.xml at org.jboss.seam.web.WicketFilter.init(WicketFilter.java:80) at org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:97) at org.jboss.seam.mock.AbstractSeamTest.createSeamFilter(AbstractSeamTest.java:942) at org.jboss.seam.mock.AbstractSeamTest.setupClass(AbstractSeamTest.java:921) at org.jboss.seam.mock.SeamTest.setupClass(SeamTest.java:44) Developers shouldn't be forced to use wicket. It should be left optional. -- 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

16 years, 5 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3201) Update readme.txt, and other locations for JBoss 4.2.3 as needed

by Jay Balunas (JIRA)

Update readme.txt, and other locations for JBoss 4.2.3 as needed ---------------------------------------------------------------- Key: JBSEAM-3201 URL: https://jira.jboss.org/jira/browse/JBSEAM-3201 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.0.3.CR2, 2.1.0.BETA1 Update the readme.txt for seam, and search for other locations such as example readme files, reference guide, etc... Must test functionality first as well. -- 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

16 years, 5 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3177) update release-process.txt with JDK6 testing steps

by Jay Balunas (JIRA)

update release-process.txt with JDK6 testing steps -------------------------------------------------- Key: JBSEAM-3177 URL: https://jira.jboss.org/jira/browse/JBSEAM-3177 Project: Seam Issue Type: Task Components: Build, Test Harness Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Priority: Critical Fix For: 2.0.3.CR2, 2.1.0.BETA1 We need to add JDK6 specific tests to the release process testing. This includes seam-gen, example testing, and others as needed. Should not be a full retest - pick risk areas. -- 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

16 years, 5 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3200) Upgrade release-process.txt to use JBoss AS 4.2.3

by Jay Balunas (JIRA)

Upgrade release-process.txt to use JBoss AS 4.2.3 ------------------------------------------------- Key: JBSEAM-3200 URL: https://jira.jboss.org/jira/browse/JBSEAM-3200 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.0.3.CR2, 2.1.0.BETA1 Upgrade release-process.txt to use JBoss AS 4.2.3. -- 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

16 years, 5 months

1
2
0 / 0

[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

16 years, 5 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

16 years, 5 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

16 years, 5 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2008