October 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4076) Client side state saving CSRF protection

by Stuart Douglas (JIRA)

Client side state saving CSRF protection ---------------------------------------- Key: JBSEAM-4076 URL: https://jira.jboss.org/jira/browse/JBSEAM-4076 Project: Seam Issue Type: Patch Reporter: Stuart Douglas -- 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, 2 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4079) Modularize jBPM integration

by Pete Muir (JIRA)

Modularize jBPM integration --------------------------- Key: JBSEAM-4079 URL: https://jira.jboss.org/jira/browse/JBSEAM-4079 Project: Seam Issue Type: Feature Request Components: BPM, Core Reporter: Pete Muir Assignee: Norman Richards Priority: Blocker Fix For: 2.2.0.CR1 Split jBPM integration out of core - there should be no jBPM integration in core at all. We may have to introduce new hooks for this. -- 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, 2 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4083) Update ICEfaces jars to 1.8.0 on jboss maven repository

by judy guglielmin (JIRA)

Update ICEfaces jars to 1.8.0 on jboss maven repository ------------------------------------------------------- Key: JBSEAM-4083 URL: https://jira.jboss.org/jira/browse/JBSEAM-4083 Project: Seam Issue Type: Task Components: ICE Faces Integration Environment: ICEfaces example and seam-gen option with ICEfaces to be affected Reporter: judy guglielmin Assignee: judy guglielmin Priority: Blocker Fix For: 2.1.2.CR1 Please let me know when this is done and I will update the build scripts. -- 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, 2 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4225) Allow to add eventListeners to WorkingMemory

by Tihomir Surdilovic (JIRA)

Allow to add eventListeners to WorkingMemory -------------------------------------------- Key: JBSEAM-4225 URL: https://jira.jboss.org/jira/browse/JBSEAM-4225 Project: Seam Issue Type: Feature Request Reporter: Tihomir Surdilovic Add support to add eventListeners to WorkingMemory. -- 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, 2 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4236) CLONE -captureCurrentView on redirect should capture all request parameters

by Paul Chan (JIRA)

CLONE -captureCurrentView on redirect should capture all request parameters --------------------------------------------------------------------------- Key: JBSEAM-4236 URL: https://jira.jboss.org/jira/browse/JBSEAM-4236 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Paul Chan Assignee: Dan Allen Fix For: 2.1.2.CR1 When the captureCurrentRequest() method was deprecated and replaced by captureCurrentView(), the behavior changed such that page parameters were being saved instead of request parameters. I'm fine with the idea of preserving page parameters based on how they were bound to the model on the way into the page, but I also think that arbitrary request parameters need to be captured. Otherwise, the redirect back to the current view will in many cases be incomplete and thus fail. The logic I propose is to capture the request parameters and then override the values with the values from the page parameters (giving page parameters the precedence). However, long term, we should also consider the fact that multi-value parameters are not being preserved. Likely they should be captured as well, but there is a lack of infrastructure to support them. -- 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, 2 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4308) Unable to run TestNG tests within JBDS due to missing dependency - slf4j-api

by Karel Piwko (JIRA)

Unable to run TestNG tests within JBDS due to missing dependency - slf4j-api ----------------------------------------------------------------------------- Key: JBSEAM-4308 URL: https://jira.jboss.org/jira/browse/JBSEAM-4308 Project: Seam Issue Type: Bug Components: Build Affects Versions: 2.2.0.GA Reporter: Karel Piwko When running TestNG test suite within JBDS on project generated by seam-gen, there is sl4j-api library missing and tests could not be run. When the same project is run within seam-gen, classpaths are set correctly. Current list of files which must be included in JDBS/Eclipse+TestNG to run tests: /lib/test/jboss-embedded-all.jar /lib/test/hibernate-all.jar /lib/test/thirdparty-all.jar /lib/jboss-embedded-api.jar /lib/jboss-deployers-client-spi.jar /lib/jboss-deployers-core-spi.jar So slf4j-api.jar should go to thirdparty.jar Stacktrace: ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfsfile:/home/kapy/devel/seam-gen/seamEarTest/test-build/ state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/kapy/devel/seam-gen/seamEarTest/test-build/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127) at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289) at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:15) at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024) at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915) at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:278) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823) at org.testng.TestNG.runSuitesLocally(TestNG.java:790) at org.testng.TestNG.run(TestNG.java:708) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) Caused by: java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory at org.hibernate.util.DTDEntityResolver.<clinit>(DTDEntityResolver.java:57) at org.jboss.ejb3.deployers.PersistenceUnitParsingDeployer.parse(PersistenceUnitParsingDeployer.java:113) at org.jboss.ejb3.deployers.PersistenceUnitParsingDeployer.parse(PersistenceUnitParsingDeployer.java:89) at org.jboss.ejb3.deployers.PersistenceUnitParsingDeployer.parse(PersistenceUnitParsingDeployer.java:51) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:223) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:199) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) ... 32 more Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 40 more FAILED CONFIGURATION: @BeforeSuite startSeam -- 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, 2 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4043) seam-gen wrong navigation in icefaces project

by Jozef Hartinger (JIRA)

seam-gen wrong navigation in icefaces project --------------------------------------------- Key: JBSEAM-4043 URL: https://jira.jboss.org/jira/browse/JBSEAM-4043 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.GA Reporter: Jozef Hartinger Assignee: Dan Allen Priority: Minor Fix For: 2.1.2.CR1 1.) Create new ear project and generate entities using database tables from release-process.txt (or any other tables, does not really matter) 2.) Deploy, create some entity and go to the listing page 3.) In the listing page there are two links in the last column of every row - View and Edit The problem is that both these links will get you to the "view entity" page, however Edit link should get you to the edit page (PersonEdit.seam for example) as it does in RichFaces case. -- 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, 2 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4065) Dynamic Web Project with Seam in Eclipse defaults to old version rather than newer version

by Jeff Wexler (JIRA)

Dynamic Web Project with Seam in Eclipse defaults to old version rather than newer version ------------------------------------------------------------------------------------------ Key: JBSEAM-4065 URL: https://jira.jboss.org/jira/browse/JBSEAM-4065 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.GA Environment: Windows 2003 server, 4GB memory, eclipse-jee-ganymede-SR2-win32.zip, JBossTools-ALL-win32-3.0.0.GA-R200903141626-H5.zip, PostgreSQL 8.3.7 JDBC Driver 8.3-604.jdbc4 Reporter: Jeff Wexler Priority: Minor Created a new project with configuration of Dynamic Web Project with Seam 2.1 (technology preview). Then select New project again to create another seam project. Configuration defaults to Dynamic Web Project with Seam 1.2 rather than 2.0 or 2.1. I would assume that the default should be to either the previously selected one (2.1) or to one of the later versions (2.0 or 2.1). -- 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, 2 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4066) captureCurrentView on redirect should capture all request parameters

by Dan Allen (JIRA)

captureCurrentView on redirect should capture all request parameters -------------------------------------------------------------------- Key: JBSEAM-4066 URL: https://jira.jboss.org/jira/browse/JBSEAM-4066 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.2.0.CR1 Attachments: JBSEAM-4066-trunk-v1.txt When the captureCurrentRequest() method was deprecated and replaced by captureCurrentView(), the behavior changed such that page parameters were being saved instead of request parameters. I'm fine with the idea of preserving page parameters based on how they were bound to the model on the way into the page, but I also think that arbitrary request parameters need to be captured. Otherwise, the redirect back to the current view will in many cases be incomplete and thus fail. The logic I propose is to capture the request parameters and then override the values with the values from the page parameters (giving page parameters the precedence). However, long term, we should also consider the fact that multi-value parameters are not being preserved. Likely they should be captured as well, but there is a lack of infrastructure to support them. -- 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, 2 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4051) Add metawidget examples

by Dan Allen (JIRA)

Add metawidget examples ----------------------- Key: JBSEAM-4051 URL: https://jira.jboss.org/jira/browse/JBSEAM-4051 Project: Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.1.2.CR1 Adopt the Seam metawidget examples from the metawidget examples distribution into the examples directory (booking, groovybooking, dvdstore). Use the same build strategy by copying the source from original example into a staging directory and then overwriting the files that differ. That way, maintenance is kept to a minimum. -- 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, 2 months

2
3
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 October 2009