February 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1844) @Raise event does not work with @Observer in the same bean

by Ilya Doe (JIRA)

@Raise event does not work with @Observer in the same bean ---------------------------------------------------------- Key: JBSEAM-1844 URL: http://jira.jboss.com/jira/browse/JBSEAM-1844 Project: JBoss Seam Issue Type: Bug Reporter: Ilya Doe If the method that is annotated with @RaiseEvent is in the same stateful bean (conversation scoped) with the method annotated @Observer; when the observer method is called all to-be injected fields are null. See details in the forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074789 -- 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, 6 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2148) Support for SelectItemGroup

by Pete Muir (JIRA)

Support for SelectItemGroup --------------------------- Key: JBSEAM-2148 URL: http://jira.jboss.com/jira/browse/JBSEAM-2148 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.0.CR2 Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.0.2.GA We can do something like <s:selectItemGroup label="#{foo.bar}"> <s:selectItems .../> <s:selectItems .../> </s:selectItemGroup> and, as a shorthand to put each list in a distinct group <s:selectItems group="Foo"/> I don't understand why this isn't in JSF core. -- 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, 6 months

3
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1696) EmptyStackException in Transaction.java

by Matt Drees (JIRA)

EmptyStackException in Transaction.java --------------------------------------- Key: JBSEAM-1696 URL: http://jira.jboss.com/jira/browse/JBSEAM-1696 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: Seam cvs 20070717.1711 Reporter: Matt Drees Priority: Minor I occasionally get the following stacktrace. I believe it happens when the SeamPhaseListener tries to begin a transaction, but an exception is thrown, so the stack is never pushed. Later, when it tries to commitOrRollback, the following happens. 2007-07-18 15:29:55,229 ERROR () SeamPhaseListener: uncaught exception java.lang.IllegalStateException: Could not commit transaction at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:589) at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:325) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:226) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) 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:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:82) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:68) 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:61) 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:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.util.EmptyStackException at java.util.Stack.peek(Stack.java:79) at org.jboss.seam.transaction.Transaction.beforeCommit(Transaction.java:64) at org.jboss.seam.transaction.UTTransaction.commit(UTTransaction.java:44) at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:579) You'd probably just need a simple "if (!synchronizations.isEmpty())" check before peek()ing or pop()ing. -- 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, 6 months

3
7
0 / 0

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

by Eugene Kisly (JIRA)

CLONE -Remember-Me automatic authentication ------------------------------------------- Key: JBSEAM-2079 URL: http://jira.jboss.com/jira/browse/JBSEAM-2079 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Eugene Kisly Fix For: 1.1.7.CR1 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

16 years, 6 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-979) Seam scan's for pageflows on startup

by Pete Muir (JIRA)

Seam scan's for pageflows on startup ------------------------------------ Key: JBSEAM-979 URL: http://jira.jboss.com/jira/browse/JBSEAM-979 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Core Affects Versions: 1.2.0.GA Reporter: Pete Muir -- 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, 7 months

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2660) Rename exception context variables

by Gavin King (JIRA)

Rename exception context variables ---------------------------------- Key: JBSEAM-2660 URL: http://jira.jboss.com/jira/browse/JBSEAM-2660 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.1.GA, 2.0.0.GA Reporter: Gavin King Priority: Blocker Fix For: 2.0.2.GA, 2.1.0.GA We have a name collision on the name "org.jboss.seam.exception", we need to use the names: org.jboss.seam.exception.caughtException org.jboss.seam.exception.handledException in the Exceptions component and the debug page. -- 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, 7 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2657) Seam-mail fails when invoked from custom servlet bound with web:context-filter

by Przemyslaw Jaskierski (JIRA)

Seam-mail fails when invoked from custom servlet bound with web:context-filter ------------------------------------------------------------------------------ Key: JBSEAM-2657 URL: http://jira.jboss.com/jira/browse/JBSEAM-2657 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.0.1.GA Environment: Seam 2.0.1 and 2.0.2-SNAPSHOT from 13 feb 2008, plain Tomcat 6.0, JSF RI 1.2_07. Reporter: Przemyslaw Jaskierski (Reporting as FR as requested by Pete. Please, read linked thread for the full context). I try to send an email from one of services. The same code: renderer.render(/WEB-INF/emailTemplates/test.xhtml); invoked from application-scoped component with method annotated as @Observer(foo) 1. works when a synchronous event is invoked in JSF action using Events.instance().raiseEvent(foo) 2. fails when invoked using Events.instance().raiseAsynchronousEvent(foo) from the same JSF action 3. fails when invoked as both synchronous and asynchronous events from custom servlet bound with web:context-filter. Case 2. and 3. both lead to this exception: java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:267) at org.jboss.seam.mock.MockFacesContext.<init>(MockFacesContext.java:60) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.init(FaceletsRenderer.java:95) at org.jboss.seam.ui.facelet.FaceletsRenderer$RenderingContext.run(FaceletsRenderer.java:77) at org.jboss.seam.ui.facelet.FaceletsRenderer.render(FaceletsRenderer.java:169) Pete's response: (2) is untested and I wouldn't necessarily expect (3) to work. File a JIRA feature request for (3) please - but it will require some redesign on how we render mails (hopefully make it much more robust) -- 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, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2491) Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released

by Marcus Adair (JIRA)

Seam is still using Groovy 1.1 beta, Groovy 1.5 has been released ----------------------------------------------------------------- Key: JBSEAM-2491 URL: http://jira.jboss.com/jira/browse/JBSEAM-2491 Project: JBoss Seam Issue Type: Bug Components: Build Affects Versions: 2.0.1.CR1 Reporter: Marcus Adair According to the groovy-all.jar/META-INF/MANIFEST.MF file, Groovy 1.1 beta is still be used. 1.5 was released in 12/2007 and appears to solve some gotchas related to its use with Seam. See: http://docs.codehaus.org/display/GROOVY/2007/12/07/Groovy+1.5+released -- 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, 7 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2482) Possible work around for Weblogic "varargs" EJB issue

by Jay Balunas (JIRA)

Possible work around for Weblogic "varargs" EJB issue ----------------------------------------------------- Key: JBSEAM-2482 URL: http://jira.jboss.com/jira/browse/JBSEAM-2482 Project: JBoss Seam Issue Type: Task Components: Documentation, Examples Affects Versions: 2.0.1.CR1 Reporter: Jay Balunas Priority: Minor Attachments: full-stack-of-ejb-transient-error.txt There is a know issue with weblogic and support for EJBs that use variable arguments. This is documented in the reference guide for more details. I've attached the full stack trace from the console. The main errors revolve around EJB3 timers - there may be a way to disable timers through the weblogic.xml deployment descriptor, or perhaps a different file. There are other warnings around EJB synchronization, but they may still function. If solved the reference docs should be updated. -- 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, 7 months

3
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2319) searchparents="true" required to properly detect Groovy in build

by Dan Allen (JIRA)

searchparents="true" required to properly detect Groovy in build ---------------------------------------------------------------- Key: JBSEAM-2319 URL: http://jira.jboss.com/jira/browse/JBSEAM-2319 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.GA Reporter: Dan Allen Priority: Minor Fix For: 2.0.x Attachments: JBSEAM-2319-v1.txt If you are using Ant >= 1.7.0, the check to determine if there are Groovy files present on the classpath will not work unless the attribute searchparents="true" is added to the <available> element that performs the check. This is an API change in Ant. Unfortunately, this attribute is not present in earlier versions of Ant and therefore throws an error. Can we just require Ant 1.7.0 or is there some way to work around an attribute that an older version of Ant does not recognize? Here is the check:  <available property="groovy.present" value="true" file="" searchparents="true"> <filepath> <fileset dir="${src.action.dir}"> <include name="**/*.groovy"/> </fileset> </filepath> </available> -- 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, 7 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2008