July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3188) ConcurrentModificationException on flush of ServerConversationContext

by Sanne Grinovero (JIRA)

ConcurrentModificationException on flush of ServerConversationContext --------------------------------------------------------------------- Key: JBSEAM-3188 URL: https://jira.jboss.org/jira/browse/JBSEAM-3188 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Environment: 2.0.3.CR1, JBoss 4.2.2, JDK 5 Reporter: Sanne Grinovero As confirmed by other people on the forum at http://seamframework.org/Community/ConcurrentModificationExceptionAfterPr... It is possible for ServerConversationContext to iterate on an EntrySet which is modified in the iteration block. I couldn't understand exactly in which scenarios it happens, but it's easy to patch the code to iterate on a copy instead (I'll attach the patch). I can't say if it's correct to make a copy, or if you should actually avoid the changes. -- 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

12 years, 7 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2092) Nothing mentioned about dependency on commons-* libraries

by Jacek Zebrowski (JIRA)

Nothing mentioned about dependency on commons-* libraries --------------------------------------------------------- Key: JBSEAM-2092 URL: http://jira.jboss.com/jira/browse/JBSEAM-2092 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 2.0.0.CR2, 2.0.0.CR1 Reporter: Jacek Zebrowski As in the title. -- 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

12 years, 9 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2403) Cant build Seam from the CR1 download

by Chris Lowe (JIRA)

Cant build Seam from the CR1 download ------------------------------------- Key: JBSEAM-2403 URL: http://jira.jboss.com/jira/browse/JBSEAM-2403 Project: JBoss Seam Issue Type: Bug Environment: Windows XP, Redhat Developer Studio RC1 Reporter: Chris Lowe Getting the following exception when trying to build Seam 2.0.1 CVS on Win XP [java] [ERROR] Error on generate component [java] org.ajax4jsf.builder.config.ParsingException: I/O error on parsing config file [java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:387) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.createConfig(GenerateMojo.java:253) [java] at org.ajax4jsf.builder.mojo.GenerateMojo.execute(GenerateMojo.java:92) [java] at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:4 20) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExe cutor.java:539) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(Default LifecycleExecutor.java:480) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExec utor.java:459) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(Def aultLifecycleExecutor.java:311) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifec ycleExecutor.java:278) [java] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor .java:143) [java] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) [java] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) [java] at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25 ) [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) [java] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) [java] at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) [java] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [java] Caused by: java.net.MalformedURLException: unknown protocol: c [java] at java.net.URL.<init>(URL.java:574) [java] at java.net.URL.<init>(URL.java:464) [java] at java.net.URL.<init>(URL.java:413) [java] at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntit yManager.java:650) [java] at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVe rsionDetector.java:186) [java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configurati on.java:771) [java] at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configurati on.java:737) [java] at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) [java] at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser .java:1205) [java] at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserI mpl.java:522) [java] at org.apache.commons.digester.Digester.parse(Digester.java:1605) [java] at org.ajax4jsf.builder.config.BuilderConfig.parseConfig(BuilderConfig.java:384) [java] ... 20 more -- 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

12 years, 9 months

5
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1957) Improve handling of JBoss Embedded in Seam

by Pete Muir (JIRA)

Improve handling of JBoss Embedded in Seam ------------------------------------------ Key: JBSEAM-1957 URL: http://jira.jboss.com/jira/browse/JBSEAM-1957 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: 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

12 years, 9 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2355) Move Seam onto vanilla build of JBoss Embedded

by Pete Muir (JIRA)

Move Seam onto vanilla build of JBoss Embedded ---------------------------------------------- Key: JBSEAM-2355 URL: http://jira.jboss.com/jira/browse/JBSEAM-2355 Project: JBoss Seam Issue Type: Task Components: Test Harness Affects Versions: 2.0.0.GA Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical -- 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

12 years, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-855) Client-API for Monitoring Download Progress of large amounts of data

by Stefan Frank (JIRA)

Client-API for Monitoring Download Progress of large amounts of data --------------------------------------------------------------------- Key: JBSEAM-855 URL: http://jira.jboss.com/jira/browse/JBSEAM-855 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Reporter: Stefan Frank Assigned To: Shane Bryzak Priority: Optional If you transport larger chunks of data via remoting, it is currently not possible to monitor the download progress. The effect is, that you can only display an unqualified busy-animation to the user. We implement this manually right now, by breaking down the date into smaller chunks and then reporting back the progress based on the downloaded chunks vs. the total number. of chunks. An enhancement would be to have: - a possibility to register a callback for progres on the client - a feature to have the data(especially collections) chopped up automatically and sent in smaller chunks (maybe some annotations as hint?!) This would make it possible to display a proper progress-bar on the client and report back, that the download is still running. -- 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

12 years, 9 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-731) <restrict> in components.xml

by Gavin King (JIRA)

<restrict> in components.xml ---------------------------- Key: JBSEAM-731 URL: http://jira.jboss.com/jira/browse/JBSEAM-731 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.0.BETA1 I guess we should allow you to restrict access to a component or method via a declaration in components.xml -- 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

12 years, 9 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3145) Support conversation restoring in GWT remoting service

by Anahide Tchertchian (JIRA)

Support conversation restoring in GWT remoting service ------------------------------------------------------ Key: JBSEAM-3145 URL: http://jira.jboss.com/jira/browse/JBSEAM-3145 Project: Seam Issue Type: Feature Request Components: Remoting Affects Versions: 2.1.0.A1 Reporter: Anahide Tchertchian Assigned To: Shane Bryzak Current implementation does not make it possible to restore conversation when calling a remote seam component from a GWT module. -- 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

12 years, 9 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-986) Seam Remoting - support subscribing to a JMS Queue

by Shane Bryzak (JIRA)

Seam Remoting - support subscribing to a JMS Queue -------------------------------------------------- Key: JBSEAM-986 URL: http://jira.jboss.com/jira/browse/JBSEAM-986 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 1.2.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Seam Remoting currently supports subscribing to a JMS topic, however doesn't support subscribing to a queue. This would be useful for things such as progress updates, etc. -- 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

12 years, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1229) Remoting exception with JMS subscription

by Alex Mateescu (JIRA)

Remoting exception with JMS subscription ---------------------------------------- Key: JBSEAM-1229 URL: http://jira.jboss.com/jira/browse/JBSEAM-1229 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA Environment: JEMS Installer 1.2 ejb3 profile, JBoss Portal 2.6.0ALPHA1, JBoss Seam 1.2.1GA running on Fedora Core 6, Firefox 1.5 Reporter: Alex Mateescu Assigned To: Shane Bryzak Priority: Minor I am deploying an EAR with multiple (the number is probably irrelevant) JARs and WARs that use Seam Remoting and subscribe to a JMS topic. The subscribe calls work fine, they send the correct topic name and receive a token. On the first poll, though, there is an exception: 2007-04-23 14:08:29,602 ERROR [org.jboss.seam.remoting.Remoting] Error java.lang.IllegalArgumentException: Invalid token argument - token not found in Session Context. [undefined] at org.jboss.seam.remoting.messaging.SubscriptionRegistry.getSubscription(SubscriptionRegistry.java:179) at org.jboss.seam.remoting.messaging.PollRequest.poll(PollRequest.java:45) at org.jboss.seam.remoting.PollHandler.handle(PollHandler.java:83) at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:110) at org.jboss.seam.servlet.ResourceServlet.doGet(ResourceServlet.java:68) at org.jboss.seam.servlet.ResourceServlet.doPost(ResourceServlet.java:77) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) Upon closer inspection, the polling request looks like this: <envelope><body><poll token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll token="undefined" timeout="10"/></body></envelope> which is the cause of the exception. Subsequent calls look fine: <envelope><body><poll token="c312b1bb-d996-46e4-a8d7-6f35caa99d73" timeout="10"/><poll token="3922899d-1e6b-4bc1-96ab-3713f4460446" timeout="10"/></body></envelope> I think the error was there before, when using Seam 1.1.0GA, but it was random. I may be wrong, but now it is always there. Of course, remoting works fine after the initial call. -- 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

12 years, 9 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008