October 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] (SEAMSECURITY-121) [Regression] 3.1.0.Beta4 eats exceptions in IdentityImpl + returns RESPONSE_LOGIN_FAILED instead of RESPONSE_LOGIN_EXCEPTION

by Geoffrey De Smet (Created) (JIRA)

[Regression] 3.1.0.Beta4 eats exceptions in IdentityImpl + returns RESPONSE_LOGIN_FAILED instead of RESPONSE_LOGIN_EXCEPTION ---------------------------------------------------------------------------------------------------------------------------- Key: SEAMSECURITY-121 URL: https://issues.jboss.org/browse/SEAMSECURITY-121 Project: Seam Security Issue Type: Bug Affects Versions: 3.1.0.Beta4 Reporter: Geoffrey De Smet Priority: Critical Fix For: 3.1.0.Beta5 org.jboss.seam.security.IdentityImpl#authenticate line 237 eats exceptions: {code} } catch (Exception ex) { authenticating = false; if (ex instanceof AuthenticationException) throw (AuthenticationException) ex; return false; } {code} As a result, my @PostConstruct weld exception isn't show in the log between these 2 lines: {code} INFO 26-10 12:05:00,849 (DemoAuthenticator.java:authenticate:65) Demo login for user (admin) succeeded. INFO 26-10 12:39:19,825 (SecurityServiceImpl.java:login:70) Logging in user [admin] {code} Extra bug: {code} public String login() { try { ... boolean success = authenticate(); ... return RESPONSE_LOGIN_FAILED; } catch (Exception ex) { // Doesn't happen any more because authenticate() eat the exception ... return RESPONSE_LOGIN_EXCEPTION; } } {code} Regression since Beta3 in Beta4. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
9
0 / 0

[JBoss JIRA] (SOLDER-295) Conversions to Collections / Arrays in *ParamProducers

by Jozef Hartinger (Created) (JIRA)

Conversions to Collections / Arrays in *ParamProducers ------------------------------------------------------ Key: SOLDER-295 URL: https://issues.jboss.org/browse/SOLDER-295 Project: Seam Solder Issue Type: Feature Request Components: Servlet Affects Versions: 3.1.0.Beta4 Reporter: Jozef Hartinger Fix For: 3.1.0.Beta5 According to the source code comments, collection and array types are not supported for @RequestParam injection https://github.com/seam/solder/blob/develop/impl/src/main/java/org/jboss/... This works in Seam 2 http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_2/src/main/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] (SEAMPERSIST-70) Seam Persistence documentation issues and comments

by Marek Schmidt (Created) (JIRA)

Seam Persistence documentation issues and comments -------------------------------------------------- Key: SEAMPERSIST-70 URL: https://issues.jboss.org/browse/SEAMPERSIST-70 Project: Seam Persistence Issue Type: Bug Affects Versions: 3.1.0.Beta3 Reporter: Marek Schmidt Fix For: 3.1.0.Final Persistence In general * lots of persistence docs mention seam transactional stuff, while the Seam transactional docs are empty. The documentation should perhaps explain the persistence/transactional split and what modules does what. 1.2. Getting Started * "seam-solder.jar" should be "solder-impl.jar", * "If you are in a java SE environment you will probably also require seam-xml.jar as well for configuration purposes." should be removed * "seam-persistence-impl" should be "seam-persistence" * "org.jboss.seam.solder" should be "org.jboss.solder" * "seam-solder" should be "solder-impl" * "org.jboss.seam.xml:seam-xml-config" dependency should be removed 1.3. Transaction Management * "Seam" should perhaps be "Seam Persistence"? 1.3.1. Configuration * "seam-xml" should be "Solder XML" * "Seam Config XML" should be "Solder Config XML" * typo in the example fragment "</tentityManager>" instead of "</t:entityManager>" * "If you need multiple persistence units in your application then we highly recommend using an EE 6 compatible server, such as JBoss 6." we should probably suggest JBoss AS 7 instead. Missing pieces * FlushModeManager, FlushModeType, ManagedPersistenceContext, PersistenceContexts, are not documented -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (SEAM-115) Release has dependencies on an older release

by Ondrej Skutka (Created) (JIRA)

Release has dependencies on an older release -------------------------------------------- Key: SEAM-115 URL: https://issues.jboss.org/browse/SEAM-115 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.1.0.Beta4 Reporter: Ondrej Skutka Assignee: Shane Bryzak Priority: Blocker Fix For: 3.1.0.CR1 In Seam 3.1.0.Beta4 there are following dependencies/references on 3.1.0-Beta3: security/pom.xml persistence/pom.xml jcr/pom.xml on 3.1.0-Beta2: seam-3.1.0.Beta4-build/faces/examples/viewconfig/pom.xml on 3.1.0-SNAPSHOT: security/examples/saml-sp/pom.xml security/examples/saml-idp/pom.xml security/examples/openid-op/pom.xml persistence/tests/jetty-hibernate/pom.xml persistence/tests/jetty-openjpa/pom.xml persistence/tests/jbossas-hibernate/pom.xml faces/examples/viewaction/pom.xml jms/testsuite/pom.xml solder/examples/princess-rescue/pom.xml solder/examples/quiz/pom.xml on 3.0.0-SNAPSHOT: jms/modules/activemq/pom.xml jms/modules/hornetq/pom.xml jms/modules/openmq/pom.xml on 3.0.0-CR1: remoting/pom.xml (should be 3.0.0.CR2?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

9
14
0 / 0

[JBoss JIRA] (SEAM-114) The seam reference manual documentation should clearly state it's version

by Geoffrey De Smet (Created) (JIRA)

The seam reference manual documentation should clearly state it's version ------------------------------------------------------------------------- Key: SEAM-114 URL: https://issues.jboss.org/browse/SEAM-114 Project: Seam 3 Distribution Issue Type: Task Components: Build Infrastructure Reporter: Geoffrey De Smet When I go here http://docs.jboss.org/seam/3/latest/reference/en-US/html_single I can't figure out what version it's talking about easily. It's pretty easy to automate this so it's automatically correct: https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/blob/master/pom.... {code} <plugin> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-jdocbook-plugin</artifactId> <version>2.3.6</version> <extensions>true</extensions> <dependencies> <dependency> <groupId>org.jboss.pressgang</groupId> <artifactId>pressgang-xslt-ns</artifactId> <version>2.0.1</version> </dependency> <dependency> <groupId>org.jboss.pressgang</groupId> <artifactId>pressgang-jdocbook-style</artifactId> <type>jdocbook-style</type> <version>2.0.1</version> </dependency> </dependencies> <configuration> ... <injections> <injection> <name>project.version</name> <value>${project.version}</value> </injection> </injections> ... </configuration> </plugin> {code} https://github.com/droolsjbpm/drools-planner/blob/master/drools-planner-d... {code} <info> <title>Drools Planner User Guide</title> <releaseinfo>Version &project.version;</releaseinfo> ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
5
0 / 0

[JBoss JIRA] Created: (SEAM-48) Missing conversation sources

by Ondrej Skutka (JIRA)

Missing conversation sources ---------------------------- Key: SEAM-48 URL: https://issues.jboss.org/browse/SEAM-48 Project: Seam 3 Issue Type: Bug Components: Build Infrastructure Affects Versions: 3.0.0.CR3 Reporter: Ondrej Skutka There are missing sources of the Conversation module from the 3.0.0.CR3 Seam release. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
10
0 / 0

[JBoss JIRA] (SEAM-116) Make version of depencies consistent across modules for a release

by Ondrej Skutka (Created) (JIRA)

Make version of depencies consistent across modules for a release ----------------------------------------------------------------- Key: SEAM-116 URL: https://issues.jboss.org/browse/SEAM-116 Project: Seam 3 Distribution Issue Type: Task Components: Common Dependencies Affects Versions: 3.1.0.Beta4 Reporter: Ondrej Skutka Fix For: 3.1.0.CR1 Attachments: index.html For a Seam release make sure that when two modules have a common dependency, these are of the same version (if possible). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

6
6
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-17) Utility for resolving Servlet for path

by Dan Allen (JIRA)

Utility for resolving Servlet for path -------------------------------------- Key: SEAMSERVLET-17 URL: https://jira.jboss.org/browse/SEAMSERVLET-17 Project: Seam Servlet Issue Type: Feature Request Components: Utilities Affects Versions: 3.0.0.Alpha1 Reporter: Dan Allen Priority: Minor One area where the Servlet API is very stingy about information is determining which Servlet is going to handle a servlet path. This mapping is calculated countless times inside of Servlet containers, yet the utility is not exposed. Let's expose the logic of mapping requests to Servlets. See chapter 12 of the Servlet specification (http://jcp.org/aboutJava/communityprocess/final/jsr315/index.html) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (SEAMFACES-114) DeploymentException: WELD-001408

by Juergen Zimmermann (JIRA)

DeploymentException: WELD-001408 -------------------------------- Key: SEAMFACES-114 URL: https://issues.jboss.org/browse/SEAMFACES-114 Project: Seam Faces Issue Type: Bug Components: CDI Integration Affects Versions: 3.0.0.CR2 Environment: Windows VISTA SP 2, JDK 6u24, JBoss 6 Hudson build 2356 Reporter: Juergen Zimmermann When I try to use SEAM Faces I get a stacktrace (see below). I'm using JBoss 6 Hudson build 2356 so that I can use Weld 1.1. I'll attach a testcase: * source code for EAR, EJB module, and Web module * executable .ear * FacesContext is injected in KundenverwaltungController within the Web module and results in the stacktrace. Stacktrace: 14:33:27,384 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///C:/Software/jboss-6.1.0-H2356/server/default/deploy/swe2.ear_WeldBootstrapBean state=Create: org.jboss.weld.exceptions. DeploymentException: WELD-001408 Unsatisfied dependencies for type [FormValidationTypeOverrideExtension] with qualifiers [@Default] at injection point [[field] @Inject private org.jboss.seam.faces.util.BeanManagerUtils.classExtension] at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:305) [:6.1.0-SNAPSHOT] at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:139) [:6.1.0-SNAPSHOT] at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:162) [:6.1.0-SNAPSHOT] at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:385) [:6.1.0-SNAPSHOT] at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:371) [:6.1.0-SNAPSHOT] at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:390) [:6.1.0-SNAPSHOT] at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:92) [:6.1.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.1.SP1] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.1.SP1] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.1.SP1] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.1.GA] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.1.GA] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.1.GA] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.1.0-SNAPSHOT] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.deploy(ProfileDeployAction.java:151) [:0.2.2] at org.jboss.profileservice.dependency.ProfileDeployAction.installActionInternal(ProfileDeployAction.java:94) [:0.2.2] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.SP1] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.SP1] at org.jboss.profileservice.dependency.ProfileActivationWrapper$BasicProfileActivation.start(ProfileActivationWrapper.java:190) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationWrapper.start(ProfileActivationWrapper.java:87) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.activateProfile(ProfileActivationService.java:215) [:0.2.2] at org.jboss.profileservice.dependency.ProfileActivationService.activate(ProfileActivationService.java:159) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.activate(AbstractProfileServiceBootstrap.java:112) [:0.2.2] at org.jboss.profileservice.resolver.BasicResolverFactory$ProfileResolverFacade.deploy(BasicResolverFactory.java:87) [:0.2.2] at org.jboss.profileservice.bootstrap.AbstractProfileServiceBootstrap.start(AbstractProfileServiceBootstrap.java:91) [:0.2.2] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:132) [:6.1.0-SNAPSHOT] at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.1.0-SNAPSHOT] at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

9
13
0 / 0

[JBoss JIRA] Created: (SEAMCONFIG-51) Using seam-config-xml 3.1.0.Beta2 fails with NoClassDefFoundError: org/jboss/seam/logging/Logger

by Geoffrey De Smet (JIRA)

Using seam-config-xml 3.1.0.Beta2 fails with NoClassDefFoundError: org/jboss/seam/logging/Logger ------------------------------------------------------------------------------------------------ Key: SEAMCONFIG-51 URL: https://issues.jboss.org/browse/SEAMCONFIG-51 Project: Seam Config Issue Type: Bug Components: Build Infrastructure Reporter: Geoffrey De Smet Assignee: Stuart Douglas 3.0.0.Final doesn't have this problem. It even looks like seam-config-xml 3.1.0.Beta2 is borked because adding the logging dependency explicitly {code} <dependency> <groupId>org.jboss.logging</groupId> <artifactId>jboss-logging</artifactId> <version>3.0.0.Beta5</version> </dependency> {code} results in java.lang.ClassNotFoundException: org.drools.guvnor.server.repository.RepositoryShutdownService something that works by using 3.0.1-SNAPSHOT instead -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

3
4
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 2011