May 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2965) Glassfish JPA example readme.txt says that it does not work on glassfish - it did.

by Jay Balunas (JIRA)

Glassfish JPA example readme.txt says that it does not work on glassfish - it did. ---------------------------------------------------------------------------------- Key: JBSEAM-2965 URL: http://jira.jboss.com/jira/browse/JBSEAM-2965 Project: Seam Issue Type: Task Components: Documentation Issues, Platform interoperability Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas The readme.txt for the JPA example says that glassfish support is currently not working, but it seemed to function and deploy just fine. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2966) Glassfish hibernate example readme.txt update

by Jay Balunas (JIRA)

Glassfish hibernate example readme.txt update --------------------------------------------- Key: JBSEAM-2966 URL: http://jira.jboss.com/jira/browse/JBSEAM-2966 Project: Seam Issue Type: Task Components: Documentation Issues, Examples, Platform interoperability Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Minor readme.txt says glassfish V1, but it worked great on V2. Should update just to be current. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2948) Update readme.txt testng commands to include testteport

by Jay Balunas (JIRA)

Update readme.txt testng commands to include testteport ------------------------------------------------------- Key: JBSEAM-2948 URL: http://jira.jboss.com/jira/browse/JBSEAM-2948 Project: Seam Issue Type: Task Components: Documentation Issues Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Priority: Trivial Update "and testall" to "ant testall testreport" in readme.txt Could also say "Then checkout the report in the /test-report directory. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Deleted: (JBSEAM-2968) Fix deadlock bug in the Seam performance test.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2968?page=all ] Pete Muir deleted JBSEAM-2968: ------------------------------ > Fix deadlock bug in the Seam performance test. > ---------------------------------------------- > > Key: JBSEAM-2968 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2968 > Project: Seam > Issue Type: Task > Reporter: Phillip Thurmond > > Running the Seam performance test against MySQL usually results in a deadlock when the cluster size reaches 6 nodes. I haven't tried it against other databases. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2968) Fix deadlock bug in the Seam performance test.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-2968?page=comments#action_12411953 ] Pete Muir commented on JBSEAM-2968: ----------------------------------- I will delete the issue > Fix deadlock bug in the Seam performance test. > ---------------------------------------------- > > Key: JBSEAM-2968 > URL: http://jira.jboss.com/jira/browse/JBSEAM-2968 > Project: Seam > Issue Type: Task > Reporter: Phillip Thurmond > > Running the Seam performance test against MySQL usually results in a deadlock when the cluster size reaches 6 nodes. I haven't tried it against other databases. -- 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, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2968) Fix deadlock bug in the Seam performance test.

by Phillip Thurmond (JIRA)

Fix deadlock bug in the Seam performance test. ---------------------------------------------- Key: JBSEAM-2968 URL: http://jira.jboss.com/jira/browse/JBSEAM-2968 Project: Seam Issue Type: Task Reporter: Phillip Thurmond Running the Seam performance test against MySQL usually results in a deadlock when the cluster size reaches 6 nodes. I haven't tried it against other databases. -- 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, 8 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2932) update build scripts for ICEfaces1.7.0 release for seam-gen and seam-icefaces example

by judy guglielmin (JIRA)

update build scripts for ICEfaces1.7.0 release for seam-gen and seam-icefaces example ------------------------------------------------------------------------------------- Key: JBSEAM-2932 URL: http://jira.jboss.com/jira/browse/JBSEAM-2932 Project: Seam Issue Type: Task Components: ICE Faces Integration Affects Versions: 2.0.2.CR2 Reporter: judy guglielmin Assigned To: judy guglielmin Priority: Optional Fix For: 2.0.2.CR2 update of build scripts for 1.7.0 release to become default for builds. -- 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, 8 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2939) Seam Remoting Problem - Cannot pass HashMap

by P C (JIRA)

Seam Remoting Problem - Cannot pass HashMap ------------------------------------------- Key: JBSEAM-2939 URL: http://jira.jboss.com/jira/browse/JBSEAM-2939 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.GA Environment: Windows XP Reporter: P C Assigned To: Shane Bryzak I have a problem where when I pass a HashMap parameter from client js to the server, the server (SEAM) doesn't seem to be able to convert/decode the HashMap properly. I have the following exception in seam: Caused by: org.jboss.seam.remoting.wrapper.ConversionException: Could not create value of type [java.util.HashMap<java.lang.String, java.lang.String>] at org.jboss.seam.remoting.wrapper.MapWrapper.convert(MapWrapper.java:101) ..... Here what I have done to pass the HashMap in javascript: var testM = new Seam.Remoting.Map() testM.put("0","0"); testM.put("1","1"); Seam.Component.getInstance("event").testMap(testM,callback); Someone mentioned a bug like that in the past, but doesn't look like it is resolved (JBSEAM-1202) -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2937) If "/lib/gen" is populated testng tests fail with configuration errors

by Jay Balunas (JIRA)

If "/lib/gen" is populated testng tests fail with configuration errors ---------------------------------------------------------------------- Key: JBSEAM-2937 URL: http://jira.jboss.com/jira/browse/JBSEAM-2937 Project: Seam Issue Type: Bug Components: Test Harness Affects Versions: 2.0.2.CR2 Reporter: Jay Balunas Attachments: ant-testcore-config-error.txt If you run "ant testcore", "ant testall", or "ant test" (with the examples) the tests will fail if the "$SEAM/lib/gen" directory is there. The "gen" directory gets populated while using seam-gen. If I remove the "gen" directory all tests are fine. If I put it back they fail with errors like below. I will attach a more complete log. The jars in that directory are also listed below. ant.jar ant.jar dom4j.jar hibernate-tools.jar jboss-el.jar runtime.jar bsh.jar el-api.jar hsqldb.jar jboss-seam.jar text.jar common.jar freemarker.jar javassist.jar jtidy.jar An example of the error: [testng] FAILED CONFIGURATION: @BeforeClass init [testng] java.lang.RuntimeException: Unable to bootstrap: [testng] at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:147) [testng] at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:183) [testng] at org.jboss.embedded.Bootstrap.bootstrap(Bootstrap.java:195) [testng] at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:11) [testng] at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1041) [testng] at org.jboss.seam.mock.BaseSeamTest.startSeam(BaseSeamTest.java:935) [testng] at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:923) [testng] at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) [testng] Caused by: java.lang.IllegalStateException: ServerConfig is already installed. [testng] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:525) [testng] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:398) [testng] at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(AbstractKernelController.java:96) [testng] at org.jboss.embedded.Bootstrap.bootstrapURL(Bootstrap.java:141) [testng] ... 29 more [testng] ... Removed 22 stack frames [testng] SKIPPED CONFIGURATION: @BeforeMethod begin [testng] SKIPPED CONFIGURATION: @AfterMethod end [testng] SKIPPED CONFIGURATION: @BeforeMethod begin [testng] SKIPPED CONFIGURATION: @AfterMethod end [testng] SKIPPED CONFIGURATION: @AfterClass cleanup [testng] SKIPPED: testRequiredPageParameter [testng] SKIPPED: testPageParameter [testng] [testng] =============================================== [testng] Seam Core - Integration: Pages.xml [testng] Tests run: 2, Failures: 0, Skips: 2 [testng] Configuration Failures: 1, Skips: 5 [testng] =============================================== [testng] -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2923) Performance: Events need not be fired for seam-internal context variable manipulation

by Clint Popetz (JIRA)

Performance: Events need not be fired for seam-internal context variable manipulation ------------------------------------------------------------------------------------- Key: JBSEAM-2923 URL: http://jira.jboss.com/jira/browse/JBSEAM-2923 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1 Reporter: Clint Popetz This isn't a "bug" but I wasn't sure what to use for "proposed performance enhancement." While profiling, I noticed that the work which ManagedEntityIdentityInterceptor does results in a lot of [pre|post][Set|Remove]Variable events for the swizzled fields that are being placed in the conversation context, though those variables aren't documented and wouldn't therefore have listeners (presumably.) In general, a lot of internal seam code does things like this, and "Events.instance().raiseEvent" x 2 for each .set() or .remove() is not trivial, according to my profiling, even when no one is listening, mainly because each Events.instance() results in a call to Component.getInstance(). That leads me to believe the Context interface should a form of set() and remove() that takes a boolean "silent" paremeter, and if it is true, they raise no events. The old methods call into the new ones with that parameter set to false. Things like ManagedEntityIdentityInterceptor pass true for efficiency. The idea would be that set/removes which result from outjections and factories would fire events, but sets/removes from internal seam manipulations wouldn't. Another example are the five sets that MethodContextInterceptor does to the method context. That's ten events fired for no reason on every invocation of a non-entity seam component method. I have a local patch to do this, and can clean it up and attach it here if the seam developers feel its an acceptable approach. -- 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, 8 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2008