November 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMMAIL-21) Port Seam2 Mail suport to Seam3

by hantsy bai (JIRA)

Port Seam2 Mail suport to Seam3 ------------------------------- Key: SEAMMAIL-21 URL: https://issues.jboss.org/browse/SEAMMAIL-21 Project: Seam Mail Issue Type: Feature Request Reporter: hantsy bai Seam2 provied seamless facelets taglib support for mail, port it to Seam 3, please. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-208) Support for resolving no argument methods in an EL value expression

by Dan Allen (JIRA)

Support for resolving no argument methods in an EL value expression ------------------------------------------------------------------- Key: SEAMFACES-208 URL: https://issues.jboss.org/browse/SEAMFACES-208 Project: Seam Faces Issue Type: Feature Request Components: CDI Integration Affects Versions: 3.1.0.Beta2 Reporter: Dan Allen Fix For: 3.1.0.Final The EL specification added support for resolving parameterized methods in value and method expressions, with one exception. It does not support resolving methods with 0 parameters. The reason is that an () used at the end of a property is not acknowledged. As a result, the resolver attempts to resolve the method name as a bean property. For example, assume we have the method: {code} public Integer count() { return 1; } {code} If we attempt to resolve this in a value expression using: {code} #{bean.count()} {code} We can an error message "count property not found on bean" It works as expected if the method has at least one parameter: {code} public Integer count(Integer i) { return i; } {code} The following expression will resolve to a value of 1. {code} #{bean.count(1)} {code} This also breaks resolving the size of a collection: {code} #{employees.size()} {code} In this case, the error is a bit strange because it tries to parse size as an index. The root cause of all this is that the spec does not properly honor 0 parameters as a valid number of parameters for a parameterized methods. Instead, it ignores the () and treats the expression as a property. Method expressions does not have this limitation since both .action and .action() are equivalent expressions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-189) Enhanced EL Support

by Cody Lerum (JIRA)

Enhanced EL Support ------------------- Key: SEAMFACES-189 URL: https://issues.jboss.org/browse/SEAMFACES-189 Project: Seam Faces Issue Type: Feature Request Reporter: Cody Lerum It would be nice to bridge the gap between EE6 and EE7 EL with support for static methods and Enums. Not sure if this should live in Faces, Solder or on it's own. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
6
0 / 0

[JBoss JIRA] (SOLDER-302) @Inject @CookiePram throws NullPointerException if the client browser does not send any cookie.CookieParamProducer implementation broken.

by Assen Todorov (Created) (JIRA)

@Inject @CookiePram throws NullPointerException if the client browser does not send any cookie.CookieParamProducer implementation broken. ----------------------------------------------------------------------------------------------------------------------------------------- Key: SOLDER-302 URL: https://issues.jboss.org/browse/SOLDER-302 Project: Seam Solder Issue Type: Bug Components: Servlet Affects Versions: 3.0.0.Final Environment: CentOS Reporter: Assen Todorov Fix For: 3.1.0.Final The following code snippet throws a NullPointerException if the client does not send any cookie. {code} @Inject @CookieParam("lang") @DefaultValue("en") private Instance<String> languageResolver; {code} The problem is in org.jboss.seam.servlet.http.CookieParamProducer.getCookieValue() {code:title=CookieParamProducer.java} for (Cookie c : request.getCookies()) { {code} The servlet specification says the following about HttpServletRequest.getCookies(): {quote} Returns an array containing all of the Cookie objects the client sent with this request. This method returns null if no cookies were sent. {quote} So CookieParamProducer.java throws NullPointerException when it try to iterate over NULL. org.jboss.seam.servlet.http.CookieParamProducer.getCookie() is also broken because of the same reason. -- 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
6
0 / 0

[JBoss JIRA] (SEAMFACES-217) Seam Faces documentation issues

by Marek Schmidt (Created) (JIRA)

Seam Faces documentation issues ------------------------------- Key: SEAMFACES-217 URL: https://issues.jboss.org/browse/SEAMFACES-217 Project: Seam Faces Issue Type: Bug Components: Documentation Affects Versions: 3.1.0.Beta3 Reporter: Marek Schmidt Faces 1.1 Maven dependency configuration link to "Maven user-defined property" without href in HTML output. (use "url" attribute in docbook instead of "href") 2.1. @RenderScoped link to "Seam Messages API" doesn't work 8. Faces View Configuration "A personal favorite", whose? 8.5 Configuring Transactional Views Docs about Transactional Views should be updated, or perhaps removed if they are not implemented yet. Missing pieces 1. It should be explicitly noted that Seam Faces produces a Conversation under the EL name "conversation" (see impl/src/main/java/org/jboss/seam/faces/context/conversation/NamedConversationAliasProducer.java) 2. injecting @Faces List<Locale>, @Faces @DefaultLocale is not documented 3. conversation boundaries (@Begin, @End, ConversationBoundaryInterceptor), 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] Created: (SEAMFACES-197) Exceptions passed to Catch should have a qualifier

by Jason Porter (JIRA)

Exceptions passed to Catch should have a qualifier -------------------------------------------------- Key: SEAMFACES-197 URL: https://issues.jboss.org/browse/SEAMFACES-197 Project: Seam Faces Issue Type: Feature Request Components: Exception Handling Affects Versions: 3.0.2 Reporter: Jason Porter Priority: Minor It could be possible for an exception to be passed to Catch that is outside of JSF, or is manually fired into Catch. To help the users determine which this is a qualifier should be added to the event fired to Catch. A phase qualifier may also be helpful, but not sure if this is needed as we can get it from the FacesContext easily. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMFACES-152) Create documentation for using Seam Catch in Faces

by Brian Leathem (JIRA)

Create documentation for using Seam Catch in Faces -------------------------------------------------- Key: SEAMFACES-152 URL: https://issues.jboss.org/browse/SEAMFACES-152 Project: Seam Faces Issue Type: Task Components: Documentation Reporter: Brian Leathem Fix For: 3.0.2 Create documentation for using Seam Catch in Faces -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
4
0 / 0

[JBoss JIRA] (SEAM-118) book page in booking example displays warning

by Tomas Remes (Created) (JIRA)

book page in booking example displays warning --------------------------------------------- Key: SEAM-118 URL: https://issues.jboss.org/browse/SEAM-118 Project: Seam 3 Distribution Issue Type: Bug Affects Versions: 3.1.0.Beta4 Environment: seam-3.1.0.Beta4 Reporter: Tomas Remes Priority: Minor Fix For: 3.1.0.Beta5 page "Book hotel" displays following warning message: The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form> -- 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

5
6
0 / 0

[JBoss JIRA] (SEAMSECURITY-124) security-authorization Catch not available

by Marek Schmidt (Created) (JIRA)

security-authorization Catch not available ------------------------------------------ Key: SEAMSECURITY-124 URL: https://issues.jboss.org/browse/SEAMSECURITY-124 Project: Seam Security Issue Type: Bug Affects Versions: 3.1.0.Beta4 Reporter: Marek Schmidt Fix For: 3.1.0.Beta5 Clicking on any unauthorized link will display an HTTP 500 server error page, instead of the expected "You do not have the necessary permissions to perform that operation" error message, as the AuthorizationException is not caught. This is caused by Catch integration not working due to wrong dependency on Faces 3.1.0.Beta3. Overriding faces version to 3.1.0.Beta4 fixes the problem. -- 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
4
0 / 0

[JBoss JIRA] (SOLDER-298) MethodPropertyImpl does not work for primitive boolean

by Lukasz Kaleta (Created) (JIRA)

MethodPropertyImpl does not work for primitive boolean ------------------------------------------------------ Key: SOLDER-298 URL: https://issues.jboss.org/browse/SOLDER-298 Project: Seam Solder Issue Type: Bug Components: Core, Reflections Affects Versions: 3.1.0.Beta4 Environment: AS 7.02, java 1.6.0_25, os: Windows7 Reporter: Lukasz Kaleta Fix For: 3.1.0.Beta5 method.getReturnType() != Boolean.class -> true method.getReturnType().isPrimitive() -> true method.getRetunType = Class("boolean") if (method.getReturnType() != Boolean.class || !method.getReturnType().isPrimitive()) { throw new IllegalArgumentException("Invalid accessor method, must return boolean primitive if starts with 'is'. Method: " + method); } -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2011