January 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2227) Write some docs on how to use SeamTest without TestNG

by Dmitriy Lapko (JIRA)

Write some docs on how to use SeamTest without TestNG ----------------------------------------------------- Key: JBSEAM-2227 URL: http://jira.jboss.com/jira/browse/JBSEAM-2227 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 2.0.0.GA Reporter: Dmitriy Lapko -- 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, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2505) ServletContexts instance returns null request during JSF request

by Jacob Orshalick (JIRA)

ServletContexts instance returns null request during JSF request ---------------------------------------------------------------- Key: JBSEAM-2505 URL: http://jira.jboss.com/jira/browse/JBSEAM-2505 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.1.CR1 Reporter: Jacob Orshalick The ServletContexts.instance().getRequest() currently returns null during a JSF request. I would think this should be returning the external context for a JSF request. Remoting handlers, ContextualHttpServletRequest, and the SoapRequestHandler all set the HttpServletRequest into the ServletContexts instance. I have applied a patch in the FacesLifecycle.beginRequest() and it does the trick. I would be happy to submit the patch if you agree. Thanks. -- 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, 10 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2507) javax.faces.application.ApplicationFactory exception when send a email from ActionHandler

by Stefano Zaccaria (JIRA)

javax.faces.application.ApplicationFactory exception when send a email from ActionHandler ----------------------------------------------------------------------------------------- Key: JBSEAM-2507 URL: http://jira.jboss.com/jira/browse/JBSEAM-2507 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 2.0.0.GA Environment: Windows vista, JBOSS AS 4.2.2GA, Seam 2.0.0GA Reporter: Stefano Zaccaria Fix For: 2.0.1.GA When send a e-mail from ActionHandler I recived a javax.faces.application.ApplicationFactory exception -- 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, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2553) <s:fileUpload> terminates UPDATE_MODEL phase

by Kenneth Christensen (JIRA)

<s:fileUpload> terminates UPDATE_MODEL phase -------------------------------------------- Key: JBSEAM-2553 URL: http://jira.jboss.com/jira/browse/JBSEAM-2553 Project: JBoss Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.0.1.CR2 Environment: Seam 2.0.1.CR2 Reporter: Kenneth Christensen Priority: Critical JSF components placed before the <s:fileUpload> component will be updated (model). JSF components placed after the <s:fileUpload> component will NOT be updated (model). Example: ... ... <h:form id="importDocumentForm" enctype="multipart/form-data"> ... ... <h:inputText value="#{libraryDomain.title}" required="true"/> <-------- title is updated correctly ... ... <s:fileUpload id="file" required="true" data="#{importLibraryFileUi.data}" fileName="#{importLibraryFileUi.fileName}" fileSize="#{importLibraryFileUi.fileSize}" contentType="#{importLibraryFileUi.fileContentType}"/> ... ... <h:inputText value="#{libraryDomain.description}" required="true"/> <-------- description is NOT updated ! ... ... </h:form> ... ... -- 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

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2561) s:defaultAction does not work in Firefox browser

by Carsten Labinsky (JIRA)

s:defaultAction does not work in Firefox browser ------------------------------------------------ Key: JBSEAM-2561 URL: http://jira.jboss.com/jira/browse/JBSEAM-2561 Project: JBoss Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.1.CR1 Environment: Seam 2.0.1.CR1 Facelets 1.1.x JSF 1.2 Richfaces 3.1.3 JBoss AS 4.2.2.GA Reporter: Carsten Labinsky Priority: Minor We use the new <s:defaultAction /> inside a <h:commandButton>. The rendered code in fact reacts as expected when using Internet Explorer. In Firefox browsers, the behaviour when hitting the enter/return key is the same as before. -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1679) passing callId to callback after async call

by Christoph Aigner (JIRA)

passing callId to callback after async call ------------------------------------------- Key: JBSEAM-1679 URL: http://jira.jboss.com/jira/browse/JBSEAM-1679 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 2.0.0.BETA1 Reporter: Christoph Aigner Assigned To: Shane Bryzak Priority: Trivial passing callId (remote.js / line 732): call.callback(value, context, callId); makes it possible to differentiate between simultanous calls of certain functions, as callId is already returned on function call necessary if options/variables are related to certain backend-calls. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1672) Dependency on JMS

by Ralph Schaer (JIRA)

Dependency on JMS ----------------- Key: JBSEAM-1672 URL: http://jira.jboss.com/jira/browse/JBSEAM-1672 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 2.0.0.BETA1 Environment: JavaBeans, Hibernate, Tomcat 6.0.13, Java 6, Windows XP Reporter: Ralph Schaer Assigned To: Shane Bryzak Priority: Optional Seam Remoting has a dependency on JMS. The problem is that the RequestHandlerFactory instantiate the PollHandler in the constructor. In a non EE environment like Tomcat I have to put a JMS library into the classpath although the application does not need JMS. Not a big deal, but maybe it's possible to change Seam Remoting that it loads PollHandler only when there is a JMS library in the classpath. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2560) Update the use of EntityManager in documentation

by Mark Schmatz (JIRA)

Update the use of EntityManager in documentation ------------------------------------------------ Key: JBSEAM-2560 URL: http://jira.jboss.com/jira/browse/JBSEAM-2560 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Environment: the documentation at e.g. http://docs.jboss.com/seam/2.0.1.GA/reference/en/html_single/index.html Reporter: Mark Schmatz Especially for beginners it's hard to understand which way of using the EntityManager is the best or at least the way you recommend. If I remember right you recommend using the following 'Seamish' style: @In private EntityManager entityManager but in the documentation you can find both, the above and the classic EJB style: @PersistenceContext private EntityManager em; For consistency reasons I would prefer having just the Seam way and propose updating the documentation accordingly. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1224) Consider integration of security with App Framework

by Pete Muir (JIRA)

Consider integration of security with App Framework --------------------------------------------------- Key: JBSEAM-1224 URL: http://jira.jboss.com/jira/browse/JBSEAM-1224 Project: JBoss Seam Issue Type: Feature Request Components: Core, Security Affects Versions: 1.2.1.GA Reporter: Pete Muir Assigned To: Shane Bryzak >From the forums: 'One down side to using EntityHome for generic crud is lack of built in security. One needs to be careful when using Homes for crud operations that allow or require RequestParameters. You need to ensure the operation on this ID is valid. You don't want to expose information you shouldn't and you definitely don't want to modify or destroy information you shouldn't. For example, you don't want a user to update or delete another user's entity just by changing an ID in the URL and hitting return. Seam supports entity level security and you can probably extend a Home to double check access restrictions prior to operations. Likewise, you don't want private information available on lets say a user profile screen, to be available to anyone able to modify a URL.' -- 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

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-895) Support re-setting the principal in identity without relogin

by Christian Bauer (JIRA)

Support re-setting the principal in identity without relogin ------------------------------------------------------------ Key: JBSEAM-895 URL: http://jira.jboss.com/jira/browse/JBSEAM-895 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Christian Bauer Assigned To: Shane Bryzak Priority: Minor I'm allow my users to change passwords and usernames while they are logged in. After such a change of credentials, I need to replace the principal in the identity component. This can currently only be done through logout() and login(), manually by the user. I want to do this automatically, and I don't want to destroy the session for that. -- 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

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