October 2010 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1250) Socket write error with Seam JMS Remoting

by Scott McNab (JIRA)

Socket write error with Seam JMS Remoting ----------------------------------------- Key: JBSEAM-1250 URL: http://jira.jboss.com/jira/browse/JBSEAM-1250 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.2.1.GA, 1.2.0.GA Environment: WindowsXP, JBossAS 4.2.0.CR1 Reporter: Scott McNab Assigned To: Shane Bryzak Full details are given in the corresponding forum topic, however a summary is: * Client-side javascript subscribes to a JMS topic by calling Seam.Remoting.subscribe(). * The client then navigates to a new page. * Approximately 30 seconds later, a SocketException (socket write error) occurs on the server within Seam Remoting (presumably because my Seam poll-timeout is set to 30 seconds). This occurs consistently with JBoss running under Windows, but does not seem to occur when the server is run on Linux. It is also not affected by browser type (i.e. it happens when using Firefox or IE). This bug did not occur previously when the same code was running with Seam 1.0.1.GA. -- 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

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2935) Seam Remoting/GWT1.5M2, change to 'Long' behavior (impacts Date?)

by darren hartford (JIRA)

Seam Remoting/GWT1.5M2, change to 'Long' behavior (impacts Date?) ----------------------------------------------------------------- Key: JBSEAM-2935 URL: http://jira.jboss.com/jira/browse/JBSEAM-2935 Project: Seam Issue Type: Bug Components: GWT Affects Versions: 2.1.x Reporter: darren hartford From: 1.5M2 announcement post -- http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thr... " - "long" emulation. The Java language defines "long" types to be 64-bit signed integers, whereas JavaScript only supports 64-bit floating point numbers, which cannot accurately represent the same whole-number range as a true "long" type. GWT 1.5 M2 transparently emulates long types properly to more faithfully maintain Java semantics in web mode. " Although this is from GWT 1.5M2, the risk/return of them changing this is unlikely. It appears that this also impacts Dates. This has been tested against Seam 2.1-snapshot (4/25/2008) and GWT 1.5M2 on jboss 4.2. Other datatypes are working correctly, Long and Dates are not. This seems to only impact the RPC mechanism. symptoms (on client side) for Long. Same symptoms for java.util.Date: ============== getLong had a failure: com.google.gwt.core.client.JavaScriptException: (TypeError): orig has no properties message: orig has no properties fileName: http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRe... lineNumber: 7172 stack: java_lang_Long_parseLong__Ljava_lang_String_2I(undefined,16)@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:7172 com_google_gwt_user_client_rpc_core_java_lang_Long_1CustomFieldSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2([object Object])@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:4258 com_domain_app_gwt_client_SeamGwtStandardDataService_1TypeSerializer_instantiate__Lcom_google_gwt_user_client_rpc_SerializationStreamReader_2Ljava_lang_String_2([object Object],"java.lang.Long/4227064769")@http://dhartford:8080/sample-ejb3-gwt-client/com.domain.app.gwt.SeamEjbRemote/0838C54E584391EEA8D10F2AD23CB3D5.cache.html:2102 -- 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

4
6
0 / 0

[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: (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: (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 October 2010