April 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1052) seam-dev.properties, seam-prod.properties

by Pete Muir (JIRA)

seam-dev.properties, seam-prod.properties ----------------------------------------- Key: JBSEAM-1052 URL: http://jira.jboss.com/jira/browse/JBSEAM-1052 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Optional In the same way you have persistence-dev.xml, there should be seam-dev.properties to allow you to configure your application differently when in dev/prod (e.g. disable random password generation). AFAICS seam.properties must be in WEB-INF/classes/seam.properties for it to be read (it isn't read in ejb-jar/seam.properties as it's not in the classloader) -- 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, 9 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2662) Map Spring transaction status codes back to JTA status codes in SpringTransaction.JtaSpringSynchronizationAdapter

by Michael Youngstrom (JIRA)

Map Spring transaction status codes back to JTA status codes in SpringTransaction.JtaSpringSynchronizationAdapter ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2662 URL: http://jira.jboss.com/jira/browse/JBSEAM-2662 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 2.1.0.A1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.1.x SpringTransaction.JtaSpringSynchronizationAdapter doesn't map SpringTransaction status codes back to JTA codes when adapting Spring synchronization to JTA Synchornization -- 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, 9 months

2
6
0 / 0

[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

17 years, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2887) Create WikiUploadImage thumbnail data in different image sizes on upload, not on view

by Christian Bauer (JIRA)

Create WikiUploadImage thumbnail data in different image sizes on upload, not on view ------------------------------------------------------------------------------------- Key: JBSEAM-2887 URL: http://jira.jboss.com/jira/browse/JBSEAM-2887 Project: Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Blocker -- 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, 9 months

1
1
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

17 years, 9 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

17 years, 9 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

17 years, 9 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2825) mail example - attachment email - inline image is broken

by Jay Balunas (JIRA)

mail example - attachment email - inline image is broken -------------------------------------------------------- Key: JBSEAM-2825 URL: http://jira.jboss.com/jira/browse/JBSEAM-2825 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Minor Fix For: 2.0.2.GA The email that the attachment example sends contains an example of an inline image - but the image is not found. -- 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, 9 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2861) 'IllegalStateException: No application context active' when rendering email after application redeployment and action method invoked over WebService

by Kurt Edegger (JIRA)

'IllegalStateException: No application context active' when rendering email after application redeployment and action method invoked over WebService ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2861 URL: http://jira.jboss.com/jira/browse/JBSEAM-2861 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Environment: WindowsXP; JBoss 4.2.0.GA; JDK1.5.0_10 Reporter: Kurt Edegger I do get an 'IllegalStateException: No application context active' error, if my Seam application tries to render an email after a WebService call as described in greater detail in the forum thread http://www.seamframework.org/Community/ApplicationContextConfusion. The exception only occurs if the application is redeployed, not if the application is deployed at server startup. -- 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, 9 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2874) Update Preview without the incremental update

by Max Andersen (JIRA)

Update Preview without the incremental update --------------------------------------------- Key: JBSEAM-2874 URL: http://jira.jboss.com/jira/browse/JBSEAM-2874 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Max Andersen Assigned To: Christian Bauer I'm being sent back to the front page constantly when typing blogs, apparently because the asynchronous updating of the preview causes something to break. Switching back to the workspace seem to work though.. Could we have the "Update preview" button always be shown and only have the incremental update running when I click the checkbox ? Then I could explictly ask about the update and avoid the redirecting. -- 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, 9 months

2
1
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 April 2008