January 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBSEAM-46) Understand and document the precise different between component names and ad hoc names

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-46?page=com.atlassian.jira.plug... ] Pete Muir closed JBSEAM-46. --------------------------- Resolution: Out of Date Assignee: Pete Muir No longer relevant in CDI > Understand and document the precise different between component names and ad hoc names > -------------------------------------------------------------------------------------- > > Key: JBSEAM-46 > URL: https://jira.jboss.org/jira/browse/JBSEAM-46 > Project: Seam > Issue Type: Task > Components: Documentation Issues > Reporter: Gavin King > Assignee: Pete Muir > > What exactly works differently when you throw something in a context with an ad hoc name? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBSEAM-29) method-level interceptors

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-29?page=com.atlassian.jira.plug... ] Pete Muir closed JBSEAM-29. --------------------------- Resolution: Out of Date Assignee: Pete Muir Exists in CDI > method-level interceptors > ------------------------- > > Key: JBSEAM-29 > URL: https://jira.jboss.org/jira/browse/JBSEAM-29 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assignee: Pete Muir > Priority: Minor > > Will require hanging onto a lot of state in Component, but it would be *very* useful to be able to specialize interception at the method level. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4482) Sjsxp Maven dependency moved to another location in java.net repository

by Karel Piwko (JIRA)

Sjsxp Maven dependency moved to another location in java.net repository ----------------------------------------------------------------------- Key: JBSEAM-4482 URL: https://jira.jboss.org/jira/browse/JBSEAM-4482 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.2.1.CR1 Reporter: Karel Piwko Fix For: 2.2.1.CR1 Seam cannot be built in CI testing because artifact jjsxp-1.0.1.jar contains message of redirection instead of JAR content. Artifact location as cached in jboss central repository is no longer valid. [artifact:dependencies] Transferring 285K from central [artifact:dependencies] Downloading: com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar from central [artifact:dependencies] Downloading: com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar from repository.jboss.org [artifact:dependencies] Downloading: com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar from snapshots.jboss.org [artifact:dependencies] Downloading: com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar from central [artifact:dependencies] Downloading: com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar from jakarta [artifact:dependencies] Downloading: com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar from jboss [artifact:dependencies] Downloading: com.sun.xml.stream/jars/sjsxp-1.0.1.jar from java.net [artifact:dependencies] Transferring 0K from java.net [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '575ecb7229443ebf248b5f6728e0e50644b0b7ee'; remote = '<!DOCTYPE' - RETRYING [artifact:dependencies] Downloading: com.sun.xml.stream/jars/sjsxp-1.0.1.jar from java.net [artifact:dependencies] Transferring 0K from java.net [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '575ecb7229443ebf248b5f6728e0e50644b0b7ee'; remote = '<!DOCTYPE' - IGNORING [artifact:dependencies] Downloading: org/codehaus/jettison/jettison/1.0.1/jettison-1.0.1.jar from central [artifact:dependencies] Transferring 55K from central [artifact:dependencies] Downloading: org/jboss/resteasy/resteasy-atom-provider/1.1-RC2/resteasy-atom-provider-1.1-RC2.jar from central [artifact:dependencies] Transferring 22K from central compileresteasy: [javac] Compiling 11 source files to /mnt/hudson_workspace/workspace/Seam-2.2.X-nightly/seam/classes/resteasyclasses [javac] error: error reading /mnt/hudson_workspace/workspace/Seam-2.2.X-nightly/m2/repository/com/sun/xml/stream/sjsxp/1.0.1/sjsxp-1.0.1.jar; error in opening zip file [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 1 error -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4527) <redirect> Exception handler with no <message> queues the handled Exception's message

by Chris Bredesen (JIRA)

<redirect> Exception handler with no <message> queues the handled Exception's message ------------------------------------------------------------------------------------- Key: JBSEAM-4527 URL: https://jira.jboss.org/jira/browse/JBSEAM-4527 Project: Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.1.2.GA Reporter: Chris Bredesen Priority: Minor Given the following simple exception handler... <exception> <redirect view-id="/error.xhtml" /> </exception> ... one might expect that, based on the lack of a <message/> element within, no FacesMessage would get enqueued when an Exception is handled. However, this is not the case. Navigator.getDisplayMessage() falls back to e.getMessage() when the literal message is null which is in fact the case when there is no <message/> element. Since Seam provides for syntax such as this... <exception> <redirect view-id="/error.xhtml"> <message severity="WARN">#{org.jboss.seam.handledException.message}</message> </redirect> </exception> ... it is this user's belief that the default behavior should be to omit any message when the configuration specifies a <redirect> with no <message>. -- 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, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1849) Exception handling broken

by Christian Bauer (JIRA)

Exception handling broken ------------------------- Key: JBSEAM-1849 URL: http://jira.jboss.com/jira/browse/JBSEAM-1849 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Looks like some work on the namespaces confused the exception handling: <exception> <redirect view-id="/message.xhtml"> <message severity="ERROR">Exception: #{org.jboss.seam.handledException.message}</message> </redirect> </exception> or <exception> <redirect view-id="/message.xhtml"> <message severity="ERROR">Exception: #{org.jboss.seam.exception.message}</message> </redirect> </exception> or (on message.xhtml): Exception: #{org.jboss.seam.handledException} produce: (http-127.0.0.1-8080-2hread) 07:29:27,035 DEBUG [Exceptions] reading exception mappings from /WEB-INF/pages.xml (http-127.0.0.1-8080-2hread) 07:29:27,039 DEBUG [Navigator] redirecting to: /message.xhtml (http-127.0.0.1-8080-2hread) 07:29:27,041 DEBUG [FacesManager] redirecting to: /wiki/message.seam?cid=7 (http-127.0.0.1-8080-2hread) 07:29:27,043 ERROR [CachedConnectionValve] Application error: Faces Servlet did not complete its transaction (http-127.0.0.1-8080-1hread) 07:29:27,046 TRACE [SeamPhaseListener] before phase: RESTORE_VIEW 1 (http-127.0.0.1-8080-1hread) 07:29:27,046 DEBUG [FacesLifecycle] >>> Begin JSF request (http-127.0.0.1-8080-1hread) 07:29:27,047 DEBUG [SeamPhaseListener] beginning transaction prior to phase: RESTORE_VIEW 1 (http-127.0.0.1-8080-1hread) 07:29:27,047 DEBUG [UTTransaction] beginning JTA transaction (http-127.0.0.1-8080-1hread) 07:29:27,048 TRACE [SeamPhaseListener] after phase: RESTORE_VIEW 1 (http-127.0.0.1-8080-1hread) 07:29:27,048 DEBUG [ConversationPropagation] Found conversation id in request parameter: 7 (http-127.0.0.1-8080-1hread) 07:29:29,048 DEBUG [Manager] No stored conversation, or concurrent call to the stored conversation (http-127.0.0.1-8080-1hread) 07:29:29,049 DEBUG [SeamPhaseListener] committing transaction after phase: RESTORE_VIEW 1 (http-127.0.0.1-8080-1hread) 07:29:29,049 DEBUG [UTTransaction] committing JTA transaction (http-127.0.0.1-8080-1hread) 07:29:29,050 TRACE [SeamPhaseListener] before phase: RENDER_RESPONSE 6 (http-127.0.0.1-8080-1hread) 07:29:29,050 DEBUG [SeamPhaseListener] beginning transaction prior to phase: RENDER_RESPONSE 6 (http-127.0.0.1-8080-1hread) 07:29:29,050 DEBUG [UTTransaction] beginning JTA transaction (http-127.0.0.1-8080-1hread) 07:29:29,066 ERROR [STDERR] Aug 23, 2007 7:29:29 AM com.sun.facelets.FaceletViewHandler handleRenderException SEVERE: Error Rendering View[/message.xhtml] javax.el.ELException: /message.xhtml: Property 'handledException' not found on type org.jboss.seam.Namespace at com.sun.facelets.compiler.TextInstruction.write(TextInstruction.java:48) at com.sun.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:39) at com.sun.facelets.compiler.UILeaf.encodeAll(UILeaf.java:149) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:577) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandler.java:233) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:106) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) 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:82) 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:395) at org.jboss.seam.wiki.core.ui.WikiUrlRewriteFilter.doFilter(WikiUrlRewriteFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:72) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:44) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:149) 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) -- 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, 2 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4474) Hibernate class org.hibernate.lob.ReaderInputStream is now org.hibernate.engine.jdbc.ReaderInputStream and that breaks Seam

by Scott Marlow (JIRA)

Hibernate class org.hibernate.lob.ReaderInputStream is now org.hibernate.engine.jdbc.ReaderInputStream and that breaks Seam --------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4474 URL: https://jira.jboss.org/jira/browse/JBSEAM-4474 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Scott Marlow Priority: Blocker Jira JBAS-7440 is about a JBoss app server 6.0.0.M1 unit test failure. The failure is showing that the Seam and Hibernate integration is broken. This problem occurred when we upgraded AS (5_x branch) to the recent Hibernate 3.5.0-Beta-2. Hibernate 3.5.0-Beta-2 contains a fix for HHH-2412 (Support for JDBC4), which involved repackaging org.hibernate.lob.ReaderInputStream to now be org.hibernate.engine.jdbc.ReaderInputStream. However, Seam has a dependency on the old package name org.hibernate.lob.ReaderInputStream. This package name change results in an app server integration test for Seam failure (error = java.lang.NoClassDefFoundError: org/hibernate/lob/ReaderInputStream). -- 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, 2 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4037) Define required SPI for RESTEasy integration

by Christian Bauer (JIRA)

Define required SPI for RESTEasy integration -------------------------------------------- Key: JBSEAM-4037 URL: https://jira.jboss.org/jira/browse/JBSEAM-4037 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer Priority: Critical This issue is a compilation of other issues that help us summarize and define the SPI we need from RESTEasy for Seam integration. -- 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, 2 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4191) TransactionsAttribute.SUPPORTS in EjbSynchronisations

by Wolfgang Schwach (JIRA)

TransactionsAttribute.SUPPORTS in EjbSynchronisations ----------------------------------------------------- Key: JBSEAM-4191 URL: https://jira.jboss.org/jira/browse/JBSEAM-4191 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.CR2 Environment: Affects all versions. Reporter: Wolfgang Schwach The class org.jboss.seam.transaction.EjbSynchronizations violates the Java-Specs. As stated in http://java.sun.com/blueprints/guidelines/designing_enterprise_applicatio... classes that implement SessionSynchronization may not have the TransactionsAttribute TransactionAttributeType.SUPPORTS. -- 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, 2 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1206) improve i18n in seam-gen

by Pierre Raoul (JIRA)

improve i18n in seam-gen ------------------------ Key: JBSEAM-1206 URL: http://jira.jboss.com/jira/browse/JBSEAM-1206 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.1.GA Reporter: Pierre Raoul It would be great that seam-gen will generate crud pages and classes for an existing Entity class: - with all the literals replaced with #{messages['key']} - and i18n default messages generated Herewith files of a draft version. I used the jpaconfiguration propositions from JBSEAM-843. It works under Eclipse: the target "updatecrud" in the project build.xml can be run from Eclipse. Nota: to translated Enum type, test of this type had to be added. I did it through file inclusion. So it can be used with any other project specific types, e.g. in the attached zip with joda-time type. -- 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, 2 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4165) Document includePageParams attribute

by Samuel Mendenhall (JIRA)

Document includePageParams attribute ------------------------------------ Key: JBSEAM-4165 URL: https://jira.jboss.org/jira/browse/JBSEAM-4165 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Samuel Mendenhall Assignee: Shane Bryzak Priority: Minor Per subject, the includePageParams should be documented, not currently in there that I see. -- 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, 2 months

3
4
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 January 2010