October 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3044) Seam and Google Guice Integration

by Pawel Wrzeszcz (JIRA)

Seam and Google Guice Integration --------------------------------- Key: JBSEAM-3044 URL: http://jira.jboss.com/jira/browse/JBSEAM-3044 Project: Seam Issue Type: Patch Affects Versions: 2.1.0.A1 Reporter: Pawel Wrzeszcz A patch contains implementation of Guice support for Seam. Basically, it allows use of Guice injection for all Seam components annotated with the @Guice annotation. I expect Guice may be useful to tie non-Seam parts of large or legacy applications together with Seam. Implementation is located in the src/guice directory and packaged as jboss-seam-guice.jar. I've provided an XML Schema for configuration and a really simple example application, together with a test case. Usage and documentation: http://wiki.jboss.org/wiki/LabsSeamGuice -- 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

16 years, 11 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3412) .page.xml are only loaded for pages with .xhtml extesnion.

by Prashant Kadam (JIRA)

.page.xml are only loaded for pages with .xhtml extesnion. ---------------------------------------------------------- Key: JBSEAM-3412 URL: https://jira.jboss.org/jira/browse/JBSEAM-3412 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.BETA1 Environment: JBoss Reporter: Prashant Kadam I have a facelete pages with '.jspx' extension. It seems that pages with only .xhtml extensions are mapped for page orchestration. Here's the code from org.jboss.seam.navigation.Pages.java file : private void parsePages(Set<String> ...fileNames) { Set<String> mergedFileNames = new HashSet<String>(); for (Set<String> f : fileNames) { mergedFileNames.addAll(f); } for (String fileName: mergedFileNames) { String viewId = "/" + fileName.substring(0,fileName.length()-".page.xml".length()) + ".xhtml"; // needs more here InputStream stream = ResourceLoader.instance().getResourceAsStream(fileName); if (stream==null) { log.info("no pages.xml file found: " + fileName); } else { log.debug("reading pages.xml file: " + fileName); parse(stream,viewId); } } } -- 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

16 years, 11 months

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3449) Upgrade to latest RestEasy beta

by Scott Olcott (JIRA)

Upgrade to latest RestEasy beta ------------------------------- Key: JBSEAM-3449 URL: https://jira.jboss.org/jira/browse/JBSEAM-3449 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.0.BETA1 Reporter: Scott Olcott The latest beta os beta-8 -- 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

16 years, 11 months

10
29
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3300) ICEfaces <ice:dataTable> should use <ice:dataPaginator>

by Valerie Griffin (JIRA)

ICEfaces <ice:dataTable> should use <ice:dataPaginator> ------------------------------------------------------- Key: JBSEAM-3300 URL: https://jira.jboss.org/jira/browse/JBSEAM-3300 Project: Seam Issue Type: Bug Components: ICE Faces Integration, Tools Affects Versions: 2.0.3.CR1 Environment: ICEfaces Reporter: Valerie Griffin Assignee: Gregory Dick The ICEfaces integration creates an <ice:dataTable> component for data display but does not create <ice:dataPaginator> components to control that display. Note that <ice:dataPaginator> components must be inside a form. Note, also, that the paginator won't work if the generated TblList.java code contains the override of maxResults. -- 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

16 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3599) Seam-gen : Icefaces war project throws IllegalStateException

by Jozef Hartinger (JIRA)

Seam-gen : Icefaces war project throws IllegalStateException ------------------------------------------------------------ Key: JBSEAM-3599 URL: https://jira.jboss.org/jira/browse/JBSEAM-3599 Project: Seam Issue Type: Bug Components: ICE Faces Integration, Tools Affects Versions: 2.1.0.GA Environment: JDK 5 JBoss AS 4.2.3 Reporter: Jozef Hartinger Assignee: judy guglielmin Attachments: seam-gen-ice-ear-edit.txt 1.) Create new Icefaces EAR project 2.) Generate entities from database using standard vehicle and person tables (release-process.txt) 3.) Deploy project 4.) Create person 5.) After new person is created, click to view user details 6.) Click edit button - after this I am getting the attached exception -- 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

16 years, 11 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3299) use ice:selectInputDate to edit Timestamp data

by Valerie Griffin (JIRA)

use ice:selectInputDate to edit Timestamp data ---------------------------------------------- Key: JBSEAM-3299 URL: https://jira.jboss.org/jira/browse/JBSEAM-3299 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.3.CR1 Environment: ICEfaces Reporter: Valerie Griffin It's very useful to get a date popup to edit timestamp data, even though the date is only part of the input. It w9ould be even more useful to allow the user to specify a standard date format. -- 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

16 years, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3146) Allow Object... args in the hasPermission EL function

by Samuel Mendenhall (JIRA)

Allow Object... args in the hasPermission EL function ----------------------------------------------------- Key: JBSEAM-3146 URL: http://jira.jboss.com/jira/browse/JBSEAM-3146 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Samuel Mendenhall Priority: Minor So the following is possible #{identity.hasPermission('blog', 'create', arg1, arg2)} and the args can be accessed in the drl file, so we should also allow #{s:hasPermission('blog', 'create', arg1, arg2)} -- 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

16 years, 12 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3652) Major reentrancy problem with "Page Scope" components and injection/disinjection

by Denis Forveille (JIRA)

Major reentrancy problem with "Page Scope" components and injection/disinjection -------------------------------------------------------------------------------- Key: JBSEAM-3652 URL: https://jira.jboss.org/jira/browse/JBSEAM-3652 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.GA, 2.0.3.CR1, 2.0.2.SP1 Environment: WebSphere v6.1.0.17 in POJO Mode Reporter: Denis Forveille Priority: Blocker This bug is very similar to the JBSEAM-3295 bug, but for "Page Scope" components this time Under stress, we have random NPE, "conversation expired" and other strange eroors from time to time in production This is due to a flaw in the "BijectionInterceptor" class and it is quite easy to reproduce On a facelets page, we have a datatable with a list of h:commadLink, teh first page of a classic "list entities/showDetail" scheme. The controleur that manages the list is in "Page Scope" When the user clics on one of the link, then quickly clic on another link, another one etc... without waiting for the detail view to show up, we have two concurrent request addressed to the same Page Scope component (Verified by putting traces in the BijectionInterceptor class) In BijectionInterceptor, in that case, counter == 2 after line 77 meaning there is two concurrent thread running: the current thread + another one currently "using" the component The counter will be decrease for the first time on line 82, then a second time on line 129 and so, disinjection will occur on line 134. This occurs while there is another thread "using" the component, causing random NPE and other errors!!!! In fact this will happen each time counter >1, ie there is more than one "concurrent" request on the same component This alleviate some questions:- - is this normal that 2 (or more) concurrent request from the same user/conversation/page acces the same page scope component concurrently (I thought seam was taking care of this and was serializing such requests... - is this normal that on line 88, components are outjected, only when the last concurrent "user" of the component exits the interceptor and not when each request "eixts" the interceptor? -- 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

16 years, 12 months

4
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3437) Create protected isInitialized() and setInitialized( boolean ) methods in Credentials

by Mike Pettypiece (JIRA)

Create protected isInitialized() and setInitialized( boolean ) methods in Credentials ------------------------------------------------------------------------------------- Key: JBSEAM-3437 URL: https://jira.jboss.org/jira/browse/JBSEAM-3437 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.BETA1 Reporter: Mike Pettypiece It would be useful if there were protected methods isInitialized() and setInitialized( boolean ) in Credentials. I'm currently subclassing Credentials and right now I need access to the field "initialized". Having to shadow initialized (along with username and overriding it's get/setters) isn't ideal. -- 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

16 years, 12 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2890) NTLM integration

by Pete Muir (JIRA)

NTLM integration ---------------- Key: JBSEAM-2890 URL: http://jira.jboss.com/jira/browse/JBSEAM-2890 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.0.A1, 2.0.2.CR1 Reporter: Pete Muir Provide deeper integration with NTLM (and similar systems?) - for example a simple component which exposes the user logged in via NTLM, and automatically pushes that info into identity? -- 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

16 years, 12 months

2
2
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 2008