August 2013 - seam-issues - Jboss List Archives

[Community] Announcement: Planed outage: 2013-08-24 5:00 PM UTC

by Libor Krzyžanek

Libor Krzyžanek [https://community.jboss.org/people/lkrzyzanek] posted the announcement <b>Announcement</b>: "Planed outage: 2013-08-24 5:00 PM UTC" To view the announcement, visit: https://community.jboss.org/index.jspa -------------------------------------------------------------- Forums/Wiki/Blogs at community.jboss.org will be unavailable for about 4 hours due to upgrade. -------------------------------------------------------------- Announcement expires on August 28, 2013

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4939) pages.xml does not support "virtual" view-id without file on disk

by Georgi Gyurchev (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4939?page=com.atlassian.jira.plugi... ] Georgi Gyurchev commented on JBSEAM-4939: ----------------------------------------- Is there any progress on this? The workaround gives problems with secured directories. > pages.xml does not support "virtual" view-id without file on disk > ----------------------------------------------------------------- > > Key: JBSEAM-4939 > URL: https://issues.jboss.org/browse/JBSEAM-4939 > Project: Seam 2 > Issue Type: Bug > Components: Core, Framework > Affects Versions: 2.3.0.BETA1 > Environment: JBOSS 7.1 AS + JSF2.1 + Richfaces 4.2.0.Final > Reporter: Andrea Martino > Labels: navigation > Fix For: The future > > > In Seam 2.2.x, it is possible to define a "virtual" view in pages.xml without any related file on disk. > For example, in Seam 2.2.x it is possible to define a redirect as following without having any "home.xhtml" file on disk: > <page view-id="/home.xhtml"> > <navigation> > <redirect view-id="/welcome.xhtml"/> > </navigation> > </page> > In Seam 2.2.x, when entering "/myapp/home.seam" the browser is correctly redirected to "/myapp/welcome.seam". In Seam 2.3.0.Beta1 in JBOSS 7.1 AS, a FacesFileNotFoundException is thrown. This issue is similar to JBSEAM-4926. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5122) @Factory return value lost

by superanna li (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5122?page=com.atlassian.jira.plugi... ] superanna li commented on JBSEAM-5122: -------------------------------------- Hi Marek, Finally, figured out it's em.clear() that causing currentUser value lost. but I am wondering, even "currentUser" in the session has been detached, but why not calling @Factory getUser() method again to gain value again? Why just create a new empty User? Best regards, Anna > @Factory return value lost > -------------------------- > > Key: JBSEAM-5122 > URL: https://issues.jboss.org/browse/JBSEAM-5122 > Project: Seam 2 > Issue Type: Bug > Reporter: superanna li > > Dear team, > In the booking search page, click 'search' button, reRender the bookingList in the same page, once click one of the booking for the detail information, the currentUser will changed(the currentUser become the newly created user with no value). it seems "currentUser" context value has been changed. > CurrentUserFactory where @Factory is used > {code} > @Name(CurrentUserFactory.FACTORY_COMPONENT_NAME) > @Scope(ScopeType.CONVERSATION) > public class CurrentUserFactory extends UserHome { > private static final long serialVersionUID = 1L; > public static final String COMPONENT_NAME = "currentUser"; > @In(value = ID_COMPONENT_NAME, scope = ScopeType.SESSION, required = false) > @Out(value = ID_COMPONENT_NAME, scope = ScopeType.SESSION, required = false) > private Integer id; > @Factory(value = COMPONENT_NAME, scope = ScopeType.CONVERSATION, autoCreate = true) > public User getUser() { > return getInstance(); > } > ... > } > {code} > SearchAction: > {code} > @Name(MyProjectsSearchAction.COMPONENT_NAME) > @Scope(ScopeType.CONVERSATION) > @Restrict("#{identity.loggedIn}") > public class MyProjectsSearchAction implements Serializable { > private static final long serialVersionUID = 1L; > public static final String COMPONENT_NAME = "myProjectsSearch"; > > @In(value = "currentUser", required = true) > private User currentUser; > public void find() { > .... > } > } > {code} > DetailAction: > {code} > @Name(MyProjectsDetailsAction.COMPONENT_NAME) > @Scope(ScopeType.CONVERSATION) > @Restrict("#{identity.loggedIn}") > public class MyProjectsDetailsAction implements Serializable { > private static final long serialVersionUID = 1153512259556496433L; > public static final String COMPONENT_NAME = "myProjectsDetails"; > @Begin(join = true) > public void showDetails() { > ... > } > {code} > Best regards, > Anna -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Krzysztof Borgul (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Krzysztof Borgul commented on JBSEAM-4822: ------------------------------------------ It is possible to upload file with semicolon - I've uploaded test file to this issue. If I can remember the issue was that regexp splits header on semicolon, but it shouldn't if semicolon is part of quoted string. > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > Attachments: a;a.txt > > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Krzysztof Borgul (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Krzysztof Borgul updated JBSEAM-4822: ------------------------------------- Attachment: a;a.txt > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > Attachments: a;a.txt > > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Krzysztof Borgul (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Krzysztof Borgul commented on JBSEAM-4822: ------------------------------------------ No "x;a.txt" (x-semicolon-a-dot-txt) > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4822: --------------------------------------- never mind, I haven't think of somebody can name a file with semicolon :(, while it is reserved special character in HTTP, they need to be encoded. > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-4822: --------------------------------------- just to be sure, the filename in description is "x a.txt", right? > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Martin Gainty (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Martin Gainty commented on JBSEAM-4822: --------------------------------------- every RE parser I have used expects RE reserved characters to be escaped otherwise the parser will try to perform some action such as replacing the token with a new token escape the character ; to \; and retry > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-4822) MultipartRequestImpl incorrect parse filename with semicolon

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-4822?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-4822: ---------------------------------- Environment: (was: Windows XP) > MultipartRequestImpl incorrect parse filename with semicolon > ------------------------------------------------------------ > > Key: JBSEAM-4822 > URL: https://issues.jboss.org/browse/JBSEAM-4822 > Project: Seam 2 > Issue Type: Bug > Affects Versions: 2.2.0.GA > Reporter: Krzysztof Borgul > Priority: Minor > > When I uploaded file with semicolon in name, org.jboss.seam.web.MultipartRequestImpl.parseParams incorrect parse header line: > Content-Disposition: form-data; name="form:fileUpload"; filename="x;a.txt" > It was split on four parts: > Content-Disposition: form-data > name="form:fileUpload" > filename="x > a.txt" > ,but should be > Content-Disposition: form-data > name="form:fileUpload" > filename="x;a.txt" > The problem is in the regular expression used as split method parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2013