December 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-729) support container authorization

by Gavin King (JIRA)

support container authorization ------------------------------- Key: JBSEAM-729 URL: http://jira.jboss.com/jira/browse/JBSEAM-729 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 We should re-authenticate on each request, so that you can use container authorization as well as Seam authorization, -- 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

14 years, 8 months

8
19
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2006) Improve handling of dependencies in examples

by Pete Muir (JIRA)

Improve handling of dependencies in examples -------------------------------------------- Key: JBSEAM-2006 URL: http://jira.jboss.com/jira/browse/JBSEAM-2006 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.0.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical Fix For: 2.0.1.GA Currently dependencies are just handled as before, with all dependencies copied into lib/ I propose to replace lib/ with a local maven repository (just a simple directory structure). This will only be used if present (not present in CVS, created using dependency:copy-dependencies when running dist target). The fileset's used to declare example libraries and inclusion into deployed archives will be altered to use maven ant tasks to pull in these filesets from repositories (using the local repo if present). This requires some extensions to existing ant tasks. A similar scheme can be used for seam-gen -- 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

14 years, 8 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2371) Integration testing Seam components with Maven

by Siarhei Dudzin (JIRA)

Integration testing Seam components with Maven ---------------------------------------------- Key: JBSEAM-2371 URL: http://jira.jboss.com/jira/browse/JBSEAM-2371 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Maven 2.0.7 Reporter: Siarhei Dudzin Various users have reported integration testing with Seam is not working in 'Mavenized' projects. -- 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

14 years, 8 months

14
54
0 / 0

[JBoss JIRA] Created: (JBSEAM-4716) add license to (root) pom

by Michael Brackx (JIRA)

add license to (root) pom ------------------------- Key: JBSEAM-4716 URL: https://jira.jboss.org/browse/JBSEAM-4716 Project: Seam Issue Type: Feature Request Components: Build Affects Versions: 2.2.1.CR2 Reporter: Michael Brackx add license to (root) pom. maven allows adding license information to the poms see http://maven.apache.org/pom.html#Licenses -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-18) Provide exception type mapping (to deal with vendor-specific exception types)

by Dan Allen (JIRA)

Provide exception type mapping (to deal with vendor-specific exception types) ----------------------------------------------------------------------------- Key: SEAMCATCH-18 URL: https://jira.jboss.org/browse/SEAMCATCH-18 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Affects Versions: Alpha2 Reporter: Dan Allen Assignee: Jason Porter There are cases when the useful information about an exception is only available in an implementation-specific exception. It would be useful to provide an exception type mapping infrastructure so that implementation-specific exceptions can be mapped to portable exception types. A classic example is JPA provider exceptions. Hibernate throws a SQLGrammarException in cases where the SQL statement is invalid (has a syntax error or refers to an invalid table/column). However, if you are writing portable JPA code, you cannot catch this exception. Thus, it would be useful to be able to catch an portable exception that represents this vendor-specific exception. Obviously, the actual mapping in this example would be done in the persistence module. Catch needs to provide some mechanism for an integration to register the mappings, which it will honor when notifying handlers. It should be noted that this is a very popular feature from Spring. Refer to SessionFactoryUtils for an example of the exception type mapping. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-47) UIInputContainer keeps invalid state too long

by Nicklas Karlsson (JIRA)

UIInputContainer keeps invalid state too long --------------------------------------------- Key: SEAMFACES-47 URL: https://jira.jboss.org/browse/SEAMFACES-47 Project: Seam Faces Issue Type: Bug Components: UI Components Affects Versions: 3.0.0.Alpha3 Reporter: Nicklas Karlsson Given a <p:input> <h:inputText value="#{credentials.username}" /> </p:input> <p:input> <h:inputText value="#{credentials.password}" /> </p:input> <h:commandButton value="Login" action="#{credentials.login}" /> and a @Model public class Credentials { @NotNull private String username; public String getUsername() { return username; } public void setUsername(String username) { this.username = username; } @NotNull public String getPassword() { return password; } public void setPassword(String password) { this.password = password; } private String password; public void login() { System.out.println(username); System.out.println(password); } } with <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> and a modified input.xhtml that outputs #{cc.attrs.invalid} you submit a blank form and get "true" and correct message for both fields, then you enter a value in the second field and re-submit and the messages are correct but both fields still show true for the invalid attribute output (making it impossible to use the attr for rendered attributes if e.g. an error image) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
4
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-16) Weld in conjunction with Seam 3 Wicket throws java.lang.IllegalStateException: Context is not active during stress testing at higher number of clients

by Martin Gencur (JIRA)

Weld in conjunction with Seam 3 Wicket throws java.lang.IllegalStateException: Context is not active during stress testing at higher number of clients ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: SEAMWICKET-16 URL: https://issues.jboss.org/browse/SEAMWICKET-16 Project: Seam Wicket Issue Type: Bug Environment: Affects version: 3.0.0-SNAPSHOT, Fix version: ? Reporter: Martin Gencur This issue is the same as the linked one (WELD-799), only for Seam Wicket. Read the description there. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-35) Support declarative conversation propagation in individual command components

by Lincoln Baxter III (JIRA)

Support declarative conversation propagation in individual command components ----------------------------------------------------------------------------- Key: SEAMFACES-35 URL: https://jira.jboss.org/browse/SEAMFACES-35 Project: Seam Faces Issue Type: Feature Request Components: Conversations, UI Components Reporter: Lincoln Baxter III http://docs.jboss.com/seam/2.2.0.GA/en-US/html_single/#d0e28286 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3902) Allow disabling of conversation id's on a per-redirect basis

by Preben Ludviksen (JIRA)

Allow disabling of conversation id's on a per-redirect basis ------------------------------------------------------------ Key: JBSEAM-3902 URL: https://jira.jboss.org/jira/browse/JBSEAM-3902 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA Reporter: Preben Ludviksen Some times you have a redirect rule in pages.xml: <page view-id="/login.xhtml"> <navigation> <rule if-outcome="success"> <redirect view-id="/servers.xhtml" /> </rule> </navigation> </page> And you know that you aren't relying on conversation propagation for the given view. It would be nice to have the possibility to disable the automatic propagation to keep the URLs nice in these cases: <redirect view-id="/servers.xhtml" propagation="none" /> -- 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

14 years, 10 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2389) HibernatePersistenceProvider fails with java.lang.Integer version check

by Christian Bauer (JIRA)

HibernatePersistenceProvider fails with java.lang.Integer version check ----------------------------------------------------------------------- Key: JBSEAM-2389 URL: http://jira.jboss.com/jira/browse/JBSEAM-2389 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Priority: Critical My entity had a version property: @Version @Column(name = "OBJ_VERSION", nullable = false) protected Integer version; In a very involved ajax reRender/conversation situation I sometimes got the following exception from HibernatePersistenceProvider: public static void checkVersion(Object value, Session session, Object oldVersion, Object version) { ClassMetadata classMetadata = getClassMetadata(value, session); VersionType versionType = (VersionType) classMetadata.getPropertyTypes()[ classMetadata.getVersionProperty() ]; if ( !versionType.isEqual(oldVersion, version) ) { throw new StaleStateException("current database version number does not match passivated version number"); } } This failed because oldVersion was 'null' and version was '0'. Hibernate returned '0' from ClassMetaData.getVersion(), it looks like it can't return null, from Javadoc: Get the version number (or timestamp) from the object's version property (or return null if not versioned). We should do a null check before asking Hibernate. Workaround: Use primitive for version field in entity or initialize it to '0'. -- 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

14 years, 10 months

3
10
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 December 2010