December 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSERVLET-21) Add bean validation to HTTP data producers

by Dan Allen (JIRA)

Add bean validation to HTTP data producers ------------------------------------------ Key: SEAMSERVLET-21 URL: https://issues.jboss.org/browse/SEAMSERVLET-21 Project: Seam Servlet Issue Type: Feature Request Components: Producers Affects Versions: 3.0.0.Alpha2 Reporter: Dan Allen Priority: Minor Like the REST module, allow bean validation to be applied at injection points that use the HTTP data producers. Example: @Inject @Min(5) @RequestParam int pageSize; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-19) Catch integration swallows unhandled runtime exceptions

by Jozef Hartinger (JIRA)

Catch integration swallows unhandled runtime exceptions ------------------------------------------------------- Key: SEAMSERVLET-19 URL: https://issues.jboss.org/browse/SEAMSERVLET-19 Project: Seam Servlet Issue Type: Bug Components: Catch integration Affects Versions: 3.0.0.Alpha2 Reporter: Jozef Hartinger Priority: Critical Fix For: 3.0.0.Alpha3 The spec says: If the servlet that is the target of a request dispatcher throws a runtime exception or a checked exception of type ServletException or IOException, it should be propagated to the calling servlet. All other exceptions should be wrapped as ServletExceptions and the root cause of the exception set to the original exception, as it should not be propagated. CatchExceptionFilter contains this code: if (!catchEvent.isHandled()) { if (e instanceof ServletException) { throw (ServletException) e; } else if (e instanceof IOException) { throw (IOException) e; } } which takes care of ServletExceptions and IOExceptions, however, runtime exceptions are swallowed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Updated: (SOLDER-60) servicehandler package should be serviceHandler for consistency

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-60?page=com.atlassian.jira.plugin.... ] Dan Allen updated SOLDER-60: ---------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] (was: [Documentation (Ref Guide, User Guide, etc.)]) > servicehandler package should be serviceHandler for consistency > --------------------------------------------------------------- > > Key: SOLDER-60 > URL: https://issues.jboss.org/browse/SOLDER-60 > Project: Seam Solder > Issue Type: Bug > Components: Service Handler > Affects Versions: 3.0.0.Beta1 > Reporter: Dan Allen > Fix For: 3.0.0.Beta2 > > > The package name for the service handler feature is inconsistent with other multi-term package names in Solder. > resource loader package: resourceLoader > bean manager package: beanManager > service handler package: servicehandler > the package name should be changed to serviceHandler. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-16) Enable transactions by default on bean that injects EntityManager

by Dan Allen (JIRA)

Enable transactions by default on bean that injects EntityManager ----------------------------------------------------------------- Key: SEAMPERSIST-16 URL: https://issues.jboss.org/browse/SEAMPERSIST-16 Project: Seam Persist Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Priority: Minor A managed bean (non-EJB) that injects an EntityManager is very likely going to use transactions. Thus, as a feature, perhaps optional, we should automatically enable transactions. We proposed this feature to several Seam users and they really likely the convenience, especially for quick start/prototype projects. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMPERSIST-15) Expose TransactionWork as an API

by Dan Allen (JIRA)

Expose TransactionWork as an API -------------------------------- Key: SEAMPERSIST-15 URL: https://issues.jboss.org/browse/SEAMPERSIST-15 Project: Seam Persistence and Transactions Issue Type: Feature Request Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Seam persist provides transaction APIs that are generally useful independent of a transactional bean. However, setting transaction boundaries still requires some work. We see this even inside the persist module, where transactional "work" is wrapped in a helper. I propose exposing this worker as a utility, either for extension writers or for uses in an application. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-14) Contextual injection of Completion Proposals

by Max Andersen (JIRA)

Contextual injection of Completion Proposals -------------------------------------------- Key: SEAMFORGE-14 URL: https://issues.jboss.org/browse/SEAMFORGE-14 Project: Seam Forge Issue Type: Feature Request Components: Shell Reporter: Max Andersen Assignee: Lincoln Baxter III from irc: "just wondering if that shouldn't be something like a @Current CompletionProposals getProposals(String prompt) on Commands ? a producer method for possible completion values." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4748) Mishmash in slf4j-*.jar version in distribution

by Marek Novotny (JIRA)

Mishmash in slf4j-*.jar version in distribution ----------------------------------------------- Key: JBSEAM-4748 URL: https://issues.jboss.org/browse/JBSEAM-4748 Project: Seam Issue Type: Task Components: Build Affects Versions: 2.2.1.CR3 Reporter: Marek Novotny Assignee: Marek Novotny There is transitive dependecy in wicket module for slf4j-*.jar and this conflicts with global setting of slf4j-api version (1.5.8 instead of 1.4.2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSEAM-4663) backbuttoningAfterLogoutWithAjaxTest fails in Booking example ( with JBossAS M3 )

by Martin Gencur (JIRA)

backbuttoningAfterLogoutWithAjaxTest fails in Booking example ( with JBossAS M3 ) --------------------------------------------------------------------------------- Key: JBSEAM-4663 URL: https://jira.jboss.org/browse/JBSEAM-4663 Project: Seam Issue Type: Bug Environment: JBossAS: jboss-6.0.0.20100429-M3 Reporter: Martin Gencur Fix For: The future Error message: Backbuttoning failed. expected:<JBoss Suites: Seam Framework> but was:<JBoss Seam Debug Page> Stacktrace: java.lang.AssertionError: Backbuttoning failed. expected:<JBoss Suites: Seam Framework> but was:<JBoss Seam Debug Page> at org.jboss.seam.example.common.test.booking.selenium.BackButtonTest.backbuttoningAfterLogoutWithAjaxTest(BackButtonTest.java:75) ... Removed 23 stack frames The test is located here: ${SEAM_HOME}/src/test/ftest/src/main/org/jboss/seam/example/common/test/booking/selenium/BackButtonTest.java Steps to reproduce the bug (according to the backbuttoningAfterLogoutWithAjaxTest ): 1) login 2) enter "Mar" into Search field 3) click Logout 4) click Go Back (browser button) 5) click Search button on the search page 6) now a wrong page is displayed (Seam Debug Page instead of Booking home page) and browser show the following error: Caused by java.lang.IllegalArgumentException with message: "null source" java.util.EventObject.<init>(EventObject.java:38) javax.faces.event.SystemEvent.<init>(SystemEvent.java:67) javax.faces.event.ComponentSystemEvent.<init>(ComponentSystemEvent.java:69) javax.faces.event.PostRestoreStateEvent.<init>(PostRestoreStateEvent.java:69) com.sun.faces.lifecycle.RestoreViewPhase.deliverPostRestoreStateEvent(RestoreViewPhase.java:256) com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:245) com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:107) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114) javax.faces.webapp.FacesServlet.service(FacesServlet.java:308) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.HotDeployFilter.doFilter(HotDeployFilter.java:53) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:293) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) java.lang.Thread.run(Thread.java:619) Nothing is shown on jbossAS console. Everything works fine when trying with JBoss 5.1.0.GA. Furthermore, the test passed for the last time with seam build from 2010/05/26. -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Updated: (SOLDER-28) Add logging to AnnotatedTypeBuilder

by Dan Allen (JIRA)

[ https://issues.jboss.org/browse/SOLDER-28?page=com.atlassian.jira.plugin.... ] Dan Allen updated SOLDER-28: ---------------------------- Fix Version/s: 3.0.0.CR1 Affects Version/s: 3.0.0.Beta1 Component/s: Logging > Add logging to AnnotatedTypeBuilder > ----------------------------------- > > Key: SOLDER-28 > URL: https://issues.jboss.org/browse/SOLDER-28 > Project: Seam Solder > Issue Type: Feature Request > Components: Logging > Affects Versions: 3.0.0.Beta1 > Reporter: Pete Muir > Fix For: 3.0.0.CR1 > > > We could do with some good trace logging to identify when annotations are added or removed, and also in create to show decisions made. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (SOLDER-56) Create a distribution build

by Dan Allen (JIRA)

Create a distribution build --------------------------- Key: SOLDER-56 URL: https://issues.jboss.org/browse/SOLDER-56 Project: Seam Solder Issue Type: Feature Request Components: Build infrastructure Affects Versions: 3.0.0.Beta1 Reporter: Dan Allen Assignee: Dan Allen Fix For: 3.0.0.Final Create a distribution build. Consult the other Seam modules (namely Servlet and Catch) as a reference. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
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 December 2010