November 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

12 years, 6 months

6
9
0 / 0

[JBoss JIRA] (SEAMSECURITY-130) Usage and implementation of equals/hashcode

by bram meijboom (Created) (JIRA)

Usage and implementation of equals/hashcode -------------------------------------------- Key: SEAMSECURITY-130 URL: https://issues.jboss.org/browse/SEAMSECURITY-130 Project: Seam Security Issue Type: Bug Affects Versions: 3.1.0.Beta4 Environment: PICKETLINK-LDAP 1.5.0.ALPHA02, PICKETLINK 1.5.0.ALPHA02 Reporter: bram meijboom Priority: Critical Implementations of equals and hashcode are not consistent for the implemented org.picketlink.idm.spi.model.* classes, so a SimpleIdentityObject is not found in a hashset with IdentityObjectImpl's if there is a entry in the set that has the same name/type as the ldap one. Due to the usage of hashsets in FallbackIdentityStoreRepository you end up with double entries when query-ing for objects. i think this is also a issue in the implementation of the FallbackIdentityStoreRepository (wich should use the interface only and not the equals/hashcode) or the api wich should provide consistent way of determining the hashcode and equals. affected class:org.jboss.seam.security.management.IdentityObjectImpl suggestions: - use the provided org.picketlink.idm.impl.types.SimpleIdentityObject in the org.jboss.seam.security.management.picketlink.JpaIdentityStore - make IdentityObjectImpl a subclass of SimpleIdentityObject PS: the implementation of LDAPIdentityObjectImpl is not consistent to, it uses the id.hashCode() in calculating the hashcode and not the name -- 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

12 years, 6 months

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

12 years, 6 months

2
2
0 / 0

[JBoss JIRA] (SOLDER-300) Document @System Properties injection

by Marek Schmidt (Created) (JIRA)

Document @System Properties injection ------------------------------------- Key: SOLDER-300 URL: https://issues.jboss.org/browse/SOLDER-300 Project: Seam Solder Issue Type: Bug Components: Documentation Reporter: Marek Schmidt Fix For: 3.1.0.Beta5 Provide documentation for SOLDER-48 injectable system properties ( https://github.com/seam/solder/commit/7dbbfb9fdc1d9a874cb356880556f43eece... ) -- 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

12 years, 6 months

3
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

12 years, 6 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

12 years, 6 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

12 years, 6 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

12 years, 6 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

12 years, 6 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

12 years, 6 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2011