April 2011 - 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

13 years, 5 months

8
19
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

13 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4800) s:link does not work on failover in a clustered environment

by Samuel Mendenhall (JIRA)

s:link does not work on failover in a clustered environment ----------------------------------------------------------- Key: JBSEAM-4800 URL: https://issues.jboss.org/browse/JBSEAM-4800 Project: Seam 2 Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.Final Environment: EAP 5.1 Seam 2.2.2.EAP5 Reporter: Samuel Mendenhall Fix For: 2.3.0.BETA1 When clicking on an s:link after a node has been taken down, the exception below is thrown. Method of reproducing: * Two EAP 5.1 nodes fronted with mod_jk. No firewall, sticky sessions + session replication definitely enabled. * JBDS Seam generated ear + a simple @Clustered EJB3 which has a method that takes a parameter and prints the EL parametrized text (I don't think EL parametrization is relevant here) * Click on the s:link on the page, it invokes fine, go back in the browser. Shutdown the active JBoss instance. Click the s:link again which is redirected to the 2nd JBoss now and receive: 14:17:42,995 ERROR [Exceptions] handled and logged exception java.lang.IllegalStateException: Unable to read view /home.xhtml to execute action "#{someComponent.printText('Hello World')}" at org.jboss.seam.navigation.SafeActions.isActionSafe(SafeActions.java:67) at org.jboss.seam.navigation.Pages.callAction(Pages.java:699) at org.jboss.seam.navigation.Pages.preRender(Pages.java:331) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:561) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:472) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:148) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:118) SafeActions.java:67 isn't so telling: =================== String viewId = id.substring(0, loc); String action = "\"#{" + id.substring(loc+1) + "}\""; InputStream is = FacesContext.getCurrentInstance().getExternalContext().getResourceAsStream(viewId); if (is==null) throw new IllegalStateException("Unable to read view " + "/" + viewId + " to execute action " + action); =================== The code says the InputStream is null on failover, so the getResourceAsStream(viewId) failed to return anything. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMJCR-4) OCM Bindings

by John Ament (JIRA)

OCM Bindings ------------ Key: SEAMJCR-4 URL: https://issues.jboss.org/browse/SEAMJCR-4 Project: Seam JCR Issue Type: Feature Request Components: OCM Reporter: John Ament Fix For: 3.0.0.Alpha2 OCM Bindings should support either Seam JCR created annotations denoting node types as well as field level annotations denoting the properties. The bindings should happen once on startup, not at runtime, so doing this in the JcrExtension makes sense. The alternative would be to use JAX-B bindings. I think either would work, and if we can we should support JAX-B. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

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

13 years, 5 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

13 years, 5 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

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-55) Use catalog for XMLSchema hosted on w3.org in the external/ xjc goal

by Marek Schmidt (JIRA)

Use catalog for XMLSchema hosted on w3.org in the external/ xjc goal -------------------------------------------------------------------- Key: SEAMSECURITY-55 URL: https://issues.jboss.org/browse/SEAMSECURITY-55 Project: Seam Security Issue Type: Task Affects Versions: 3.0.0.Final Reporter: Marek Schmidt Priority: Minor The current xjc task downloads the http://www.w3.org/2001/XMLSchema from the w3.org, which is commonly serving only HTTP 503 responses. The build should use a local copy of the schema (catalog). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (SOLDER-93) Add more thorough tests for @Requires

by Dan Allen (JIRA)

Add more thorough tests for @Requires ------------------------------------- Key: SOLDER-93 URL: https://issues.jboss.org/browse/SOLDER-93 Project: Seam Solder Issue Type: Enhancement Components: Core Affects Versions: 3.0.0.CR4 Reporter: Dan Allen Add more thorough tests for @Requires for scenarios in which the required class is referenced in the bean that relies on that class. Currently, the only reference to the required class is in the @Requires annotation as a string. Test scenarios: - @Requires on package-info.java references class on classpath - inject required class into bean in package - use required class as return value of method on bean in package - use required class a super class of bean in package - do not include injected class in shrinkwrap archive - make sure deployment succeeds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 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

13 years, 5 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011