August 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1365) Make SeamManagedEntityManagerFactory joinTransaction if available

by Michael Youngstrom (JIRA)

Make SeamManagedEntityManagerFactory joinTransaction if available ----------------------------------------------------------------- Key: JBSEAM-1365 URL: http://jira.jboss.com/jira/browse/JBSEAM-1365 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 1.3.0.ALPHA Spring correctly assumes that if EMF.createEntityManager is called while in a transaction that the newly created EntityManager will be joined in with the current transaction. However, in the Seam Spring Integration, when Spring calls EMF.createEntityManager we might return an existing conversation scoped EM instead of a newly created one. In which case we need to join the current transaction if there is one since spring will not. -- 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

18 years

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1439) Seam update broke permission system

by Christian Bauer (JIRA)

Seam update broke permission system ----------------------------------- Key: JBSEAM-1439 URL: http://jira.jboss.com/jira/browse/JBSEAM-1439 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Blocker Fix For: 1.3.0.ALPHA I didn't notice but some seam update in the last 2 weeks broke the permission system. Whenever a node is edited, its permissions are set to exclusive access for the current user. Need to investigate this. -- 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

18 years

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1362) Add validation for page parameters

by Mathew Blackberry (JIRA)

Add validation for page parameters ---------------------------------- Key: JBSEAM-1362 URL: http://jira.jboss.com/jira/browse/JBSEAM-1362 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Mathew Blackberry Currently seam does not validate page parameters when working in restful mode. -- 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

18 years

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1343) Support for Word dash (em-dash) character in s:formattedText (SeamTextLexer)

by Patrick Ruhkopf (JIRA)

Support for Word dash (em-dash) character in s:formattedText (SeamTextLexer) ---------------------------------------------------------------------------- Key: JBSEAM-1343 URL: http://jira.jboss.com/jira/browse/JBSEAM-1343 Project: JBoss Seam Issue Type: Feature Request Components: Core, JSF Affects Versions: 1.2.1.GA Reporter: Patrick Ruhkopf Priority: Trivial <s:formattedText /> currently doesn't support the dash character u0096. That leads to an exception when working with copy n paste from MS Word. I am not able to supply a patch, because I can't find the jboss.text package in the latest HEAD (which causes build errors, by the way). Is it just me? Annyway, just add case '\u0096' to nextToken and mPUNCTUATION. That's it... -- 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

18 years

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1347) Make SeamTest not dependent on TestNG

by Michael Youngstrom (JIRA)

Make SeamTest not dependent on TestNG ------------------------------------- Key: JBSEAM-1347 URL: http://jira.jboss.com/jira/browse/JBSEAM-1347 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 1.3.0.ALPHA It would be nice if it were possible to use SeamTest in a testing framework other than TestNG. I'm not proposing Seam provide support for any other testing frameworks I just think it would be nice if developers could have the option create their own way of using the meat of SeamTest in their own way without having to depend upon TestNG. It would be trivial to move what is currently in SeamTest into an Abstract class (AbstractSeamTest) class and then change SeamTest to extend AbstractSeamTest and specify the testng annotations in that class. That way people who wish to try and make AbstractSeamTest work in another testing framework they can without still having to depend upon TestNG. 100% backwards compatibility, No documentation changes, just a simple refactor. I believe this issue has low risk and I would be more than happy to take on this issue if approved. I would also like this issue to be considered for inclusion in 1.3.0. If you want a patch before approving it I can provide that too. Mike -- 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

18 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1356) Document Groovy support

by Emmanuel Bernard (JIRA)

Document Groovy support ----------------------- Key: JBSEAM-1356 URL: http://jira.jboss.com/jira/browse/JBSEAM-1356 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Fix For: 1.3.0.GA -- 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

18 years

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1307) org.jboss.seam.theme.Theme request

by Tomislav Tkal?evi? (JIRA)

org.jboss.seam.theme.Theme request ---------------------------------- Key: JBSEAM-1307 URL: http://jira.jboss.com/jira/browse/JBSEAM-1307 Project: JBoss Seam Issue Type: Feature Request Reporter: Tomislav Tkal?evi? I was trying to set a value for context param named <context-param> <param-name>org.ajax4jsf.SKIN</param-name> <param-value>#{theme.theme}</param-value> </context-param> in the web.xml of my apllication through the seam theme component which seams to be null, even if there is a theme which i have selected. #{theme.theme} in this case is a value which is located in my defeault.properties file, and has a value if I set it in the outputtext or anything else to log the value of the #{theme.theme}. I get the next exception, here is the stack trace: 13:47:32,446 ERROR [InternetResourceService] Error on send resource org.ajax4jsf.framework.skin.SkinNotFoundException: Name for current Skin calculated as null at org.ajax4jsf.framework.skin.SkinFactoryImpl.getSkin(SkinFactoryImpl.java:92) at org.ajax4jsf.framework.renderer.compiler.ElementBase$4.getValue(ElementBase.java:302) at org.ajax4jsf.framework.renderer.compiler.ElementBase$ValueGetter.getStringOrDefault(ElementBase.java:426) at org.ajax4jsf.framework.renderer.compiler.ClassElement.getString(ClassElement.java:88) at org.ajax4jsf.framework.renderer.compiler.ClassElement.encode(ClassElement.java:60) at org.ajax4jsf.framework.renderer.compiler.ElementBase.encode(ElementBase.java:104) at org.ajax4jsf.framework.renderer.compiler.ElementBase.encode(ElementBase.java:104) at org.ajax4jsf.framework.renderer.compiler.RootElement.encode(RootElement.java:64) at org.ajax4jsf.framework.renderer.compiler.ElementBase.encode(ElementBase.java:72) at org.ajax4jsf.framework.resource.TemplateCSSRenderer.send(TemplateCSSRenderer.java:79) at org.ajax4jsf.framework.resource.InternetResourceBase.send(InternetResourceBase.java:369) at org.ajax4jsf.framework.resource.ResourceLifecycle.send(ResourceLifecycle.java:86) at org.ajax4jsf.framework.resource.InternetResourceService.sendResource(InternetResourceService.java:213) at org.ajax4jsf.framework.resource.InternetResourceService.serviceResource(InternetResourceService.java:183) at org.ajax4jsf.framework.resource.InternetResourceService.serviceResource(InternetResourceService.java:118) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:207) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 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.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) 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.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) -- 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

18 years

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1331) Groovy Seam example needs to include jboss-el

by Emmanuel Bernard (JIRA)

Groovy Seam example needs to include jboss-el --------------------------------------------- Key: JBSEAM-1331 URL: http://jira.jboss.com/jira/browse/JBSEAM-1331 Project: JBoss Seam Issue Type: Bug Reporter: Emmanuel Bernard Assigned To: Emmanuel Bernard Fix For: 1.3.0.BETA1 To get the example working, I had to edit the build.xml, to include the jboss-el jars; otherwise I get a NoClassDefFound - Exception. I think that 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1335) Update XML version numbers for seam 1.3

by Norman Richards (JIRA)

Update XML version numbers for seam 1.3 --------------------------------------- Key: JBSEAM-1335 URL: http://jira.jboss.com/jira/browse/JBSEAM-1335 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards Assigned To: Norman Richards Fix For: 1.3.0.BETA1 -- 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

18 years

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1216) Can't use equals symbol in wiki text

by Christian Bauer (JIRA)

Can't use equals symbol in wiki text ------------------------------------ Key: JBSEAM-1216 URL: http://jira.jboss.com/jira/browse/JBSEAM-1216 Project: JBoss Seam Issue Type: Bug Components: Wiki Affects Versions: 1.2.1.GA Reporter: Christian Bauer Assigned To: Christian Bauer We really shouldn't use the EQ symbol for unordered lists. Folks want to write text that includes an = symbol. -- 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

18 years

3
6
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 August 2007