July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4078) Jar locking during of component initialization on Windows

by Andrey Lomakin (JIRA)

Jar locking during of component initialization on Windows --------------------------------------------------------- Key: JBSEAM-4078 URL: https://jira.jboss.org/jira/browse/JBSEAM-4078 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: Windows 2000, Java(TM) SE Runtime Environment (build 1.6.0_13-b03), GlassFish v3 Prelude (build b28c) Reporter: Andrey Lomakin JARs that contain components.xml are locked till server shutdown and can not be removed after application undeploy on Windows. As I understend following snippet of code in method org.jboss.seam.init.Initialization#initComponentsFromXmlDocuments: InputStream stream = url.openStream(); log.debug("reading " + url); try { installComponentsFromXmlElements(XML.getRootElement(stream), replacements); } finally { Resources.closeStream(stream); } should be replaced by URLConnection connection = url.openConnection(); connection.setUseCaches(false); InputStream stream = url.openStream(); // and so on... If cashes will not be switched of file will be opened but never closed. Returned instance of InputStream interface is sun.net.www.protocol.jar.JarURLConnection,JarURLInputStream that closes opened jar file only if cashes are not used. class JarURLInputStream extends java.io.FilterInputStream { 103 JarURLInputStream (InputStream src) { 104 super (src); 105 } 106 public void close () throws IOException { 107 try { 108 super.close(); 109 } finally { 110 if (!getUseCaches()) { 111 jarFile.close(); 112 } 113 } 114 } 115 } -- 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, 8 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4028) way to outject someting in to the CURRENT conversation even if a new one is started before the context is flushed

by David Schlotfeldt (JIRA)

way to outject someting in to the CURRENT conversation even if a new one is started before the context is flushed ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4028 URL: https://jira.jboss.org/jira/browse/JBSEAM-4028 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.2.GA Reporter: David Schlotfeldt If you outject and then create a new nested conversation the outjected variable ends up in the nested conversation. This is because ServerConversatoinContext keeps the "additions" to it separate from the actual context variables -- just in the case it needs to "rollback". When the render response phase takes place ServerConversationContext "commits" the new additions. The "key" of each addition is determined at that time. The key of entries is prefixed with the conversation id to allow Seam to determine what conversation it is for. It would be nice if when one could outject the variable into the conversation that was current when it was outjected. This could easily be done by storing the conversation id that was current in the "additions" information and using it instead of the current conversation id when flushed. This of course is a change that could cause many issues for people so I propose an attribute is added to @Out called "conversation-at-flush=[true|false]" with the default value of true. If you want the outject to be in the converation current when outjected you set this attribute to false. Just to point out an issue I could see happen if not kept in mind when implementing: A nested conversation could in theory start, things outjected, and then the nested conversation ended before flush takes place. When flush does happen we need to filter out those outjects from the nested conversation that had conversation-at-flush=false since that conversation was ended. This simply means checking the conversation id is still active before making the addition/removal. -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4319) seam-gen to support wicket

by Rob Shepherd (JIRA)

seam-gen to support wicket -------------------------- Key: JBSEAM-4319 URL: https://jira.jboss.org/jira/browse/JBSEAM-4319 Project: Seam Issue Type: Feature Request Components: Build, Wicket Reporter: Rob Shepherd Priority: Optional It would be lovely if seam-gen supported building seam application templates with wicket instead of, or in addition to JSF. -- 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, 8 months

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4314) Blog example needs additional jars for JBoss 4.x

by Ondrej Skutka (JIRA)

Blog example needs additional jars for JBoss 4.x ------------------------------------------------ Key: JBSEAM-4314 URL: https://jira.jboss.org/jira/browse/JBSEAM-4314 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.GA Environment: JBoss 4.2.3.GA, Sun JDK 5 Reporter: Ondrej Skutka Blog example needs these additional libraries in order to work on JBoss 4.2.3 GA: hibernate-annotations.jar hibernate-entitymanager.jar hibernate-validator.jar slf4j-api.jar slf4j-log4j12.jar This applies only fo JBoss 4.x, it works on JBoss 5.x. -- 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, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4317) Add Support for Wiki-style Table Generation

by John Gilbert (JIRA)

Add Support for Wiki-style Table Generation ------------------------------------------- Key: JBSEAM-4317 URL: https://jira.jboss.org/jira/browse/JBSEAM-4317 Project: Seam Issue Type: Feature Request Components: Seam Text Reporter: John Gilbert Currently Seam Text supports html tables. But wiki style tables would be much easier for yours. For example: ||H1||H2|| |c1|c2| |c3|c4| -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3849) ClassLoader cannot find xhtml files when scanning page.xml files in an EAR with Multiple WARs

by Reind D (JIRA)

ClassLoader cannot find xhtml files when scanning page.xml files in an EAR with Multiple WARs --------------------------------------------------------------------------------------------- Key: JBSEAM-3849 URL: https://jira.jboss.org/jira/browse/JBSEAM-3849 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.CR2 Environment: JBoss AS 5.0.0.GA, JDK6, Seam 2.1.1.CR2 Reporter: Reind D I have an EAR that contains multiple WAR files. The ear deploys correctly, but on the first web request, during a scan of all *.page.xml files, I get the following output to the log for each page.xml file: WARN [VFSScanner] Error handling item 'login/index.page.xml': java.lang.NullPointerException: Cannot find URL from classLoader for login/index.page.xml, loading from org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader@1ed964f The NPE occurs in this code: org.jboss.seam.deployment.FileDescriptor.java this.url = classLoader.getResource(name); if (this.url == null) { throw new NullPointerException("Cannot find URL from classLoader for " + name + ", loading from " + classLoader); } As a result, none of the page.xml files work. Note that the second WAR works as expected, with all the page.xml files loaded correctly. The same project worked in Seam 2.0.2.SP1 and JBoss AS 4.2.3.GA -- 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, 8 months

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4219) Allow use of RuleFlow in Seam RuleBase

by Tihomir Surdilovic (JIRA)

Allow use of RuleFlow in Seam RuleBase -------------------------------------- Key: JBSEAM-4219 URL: https://jira.jboss.org/jira/browse/JBSEAM-4219 Project: Seam Issue Type: Feature Request Reporter: Tihomir Surdilovic Allow passing of RuleFlow .rf files through components.xml to RuleBase as well as the the process name to be started. -- 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, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4245) Disinjection in Seam-Guice

by Pawel Wrzeszcz (JIRA)

Disinjection in Seam-Guice -------------------------- Key: JBSEAM-4245 URL: https://jira.jboss.org/jira/browse/JBSEAM-4245 Project: Seam Issue Type: Patch Affects Versions: 2.1.2.CR2 Reporter: Pawel Wrzeszcz Assignee: Dan Allen Currently, the implementation of Seam and Guice integration injects the values into the fields annotated with the @Inject annotation, but it doesn't disinject. The patch includes: * implementation of disinjection in the GuiceInterceptor * updated example together with tests (including a test for disinjection) * minor documentation changes Patch for revision 11153 in the community/Seam_2_2 branch. -- 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, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4315) I would like to begin the process of translating Seam into Portuguese. (pt-BR)

by lyndon tavares (JIRA)

I would like to begin the process of translating Seam into Portuguese. (pt-BR) ------------------------------------------------------------------------------- Key: JBSEAM-4315 URL: https://jira.jboss.org/jira/browse/JBSEAM-4315 Project: Seam Issue Type: Feature Request Components: Documentation Translation Reporter: lyndon tavares Translating Seam into Portuguese. (pt-BR) -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4241) Add ability to retract facts from workingmemory in pageflow

by Tihomir Surdilovic (JIRA)

Add ability to retract facts from workingmemory in pageflow ----------------------------------------------------------- Key: JBSEAM-4241 URL: https://jira.jboss.org/jira/browse/JBSEAM-4241 Project: Seam Issue Type: Feature Request Reporter: Tihomir Surdilovic Currently you can only insert/update facts to WM in pageflow, for example: <handler class="org.jboss.seam.drools.DroolsDecisionHandler"> <workingMemoryName>workingMemory</workingMemoryName> <assertObjects> <element>#{game}</element> <element>#{guess}</element> </assertObjects> </handler> Add ability to also specify a list of facts for retraction -- 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, 8 months

2
5
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 July 2009