March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-981) Fix non-MultipartRequest requests passed to the fileUpload control

by Shane Bryzak (JIRA)

Fix non-MultipartRequest requests passed to the fileUpload control ------------------------------------------------------------------ Key: JBSEAM-981 URL: http://jira.jboss.com/jira/browse/JBSEAM-981 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.2.0.GA Reporter: Shane Bryzak Assigned To: Shane Bryzak Fix For: 1.2.1.GA Various products are wrapping multipart requests with their own request class. The fileUpload control should account for this and iterate through the wrapped requests to find a MultipartRequest. -- 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

19 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-965) fileUpload component should delete temporary files

by Leo Baschy (JIRA)

fileUpload component should delete temporary files -------------------------------------------------- Key: JBSEAM-965 URL: http://jira.jboss.com/jira/browse/JBSEAM-965 Project: JBoss Seam Issue Type: Patch Components: JSF Affects Versions: 1.2.0.GA Environment: Windows XP, Java 1.5 Reporter: Leo Baschy If configured to write to temporary files then Seam fileUpload component marks them for delete on exit from JVM. Until then they accumulate (in the usual temporary directory), for each upload, as long as the server is running. The application developer only has the InputStream, which doesn't allow file deletion. The application developer can call close() for the InputStream, but that doesn't delete the file. -- 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

19 years, 1 month

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1012) Document ResourceServlet, and that it is needed for s:selectDate!

by Gavin King (JIRA)

Document ResourceServlet, and that it is needed for s:selectDate! ----------------------------------------------------------------- Key: JBSEAM-1012 URL: http://jira.jboss.com/jira/browse/JBSEAM-1012 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Gavin King Assigned To: Shane Bryzak Priority: Blocker Fix For: 1.2.1.GA -- 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

19 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1003) "Business keys" as conversation ids

by Gavin King (JIRA)

"Business keys" as conversation ids ----------------------------------- Key: JBSEAM-1003 URL: http://jira.jboss.com/jira/browse/JBSEAM-1003 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Shane Bryzak Priority: Critical Fix For: 1.2.1.GA It's much nicer to see business keys in URLs than some crappy "cid=123" stuff. -- 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

19 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1008) Page description of unused page is accessed

by Christian Bauer (JIRA)

Page description of unused page is accessed ------------------------------------------- Key: JBSEAM-1008 URL: http://jira.jboss.com/jira/browse/JBSEAM-1008 Project: JBoss Seam Issue Type: Bug Components: Core Reporter: Christian Bauer Priority: Minor This was triggered by a change in the last 10 days (sorry, don't know when): <pages login-view-id="/loginRequired.xhtml"> <page view-id="/docEdit.xhtml" login-required="true" no-conversation-view-id="/message.xhtml"> <description>Edit Document '#{documentHome.instance.name}'</description> <page view-id="/loginRequired.xhtml" action="#{browser.redirectToLastBrowsedPageWithConversation}"/> I'm not logged in and I access /docEdit.xhtml. I see a redirect to /loginRequired.xhtml and my browser.redirectFoo() fires this redirect.returnToCapturedView(). The navigation etc. works fine, but I get an exception in the log earlier: Accessing /docEdit.xhtml (this is actually another redirect before this): 19:15:17,276 DEBUG [Lifecycle] >>> Begin web request 19:15:17,277 DEBUG [SeamPhaseListener] after phase: RESTORE_VIEW(1) 19:15:17,277 DEBUG [Manager] Found conversation id in request parameter: 3 19:15:17,277 DEBUG [Manager] Restoring conversation with id: 3 19:15:17,277 DEBUG [AbstractSeamPhaseListener] After restoring conversation context: ConversationContext(3) 19:15:17,277 DEBUG [AbstractSeamPhaseListener] committing transaction after phase: RESTORE_VIEW(1) 19:15:17,278 DEBUG [SeamPhaseListener] before phase: RENDER_RESPONSE(6) 19:15:17,278 DEBUG [AbstractSeamPhaseListener] beginning transaction prior to phase: RENDER_RESPONSE(6) 19:15:17,282 DEBUG [Manager] redirecting to: /wiki/loginRequired.seam?cid=3&clr=true 19:15:17,283 DEBUG [SeamPhaseListener] after phase: RENDER_RESPONSE(6) 19:15:17,286 DEBUG [ResourceBundle] loaded resource bundle: messages 19:15:17,287 DEBUG [ResourceBundle] resource bundle missing: ValidatorMessages 19:15:17,291 DEBUG [ResourceBundle] loaded resource bundle: org/hibernate/validator/resources/DefaultValidatorMessages 19:15:17,300 DEBUG [AbstractSeamPhaseListener] committing transaction after phase: RENDER_RESPONSE(6) >>> 19:15:17,340 DEBUG [RootInterceptor] intercepted: documentHome.POST_CONSTRUCT >>> 19:15:17,342 DEBUG [RootInterceptor] intercepted: documentHome.create >>> 19:15:17,343 DEBUG [RootInterceptor] intercepted: wikiLinkResolver.POST_CONSTRUCT >>> 19:15:17,343 DEBUG [RootInterceptor] intercepted: nodeDAO.POST_CONSTRUCT >>> 19:15:17,356 DEBUG [RootInterceptor] intercepted: userDAO.POST_CONSTRUCT 19:15:17,360 WARN [Interpolator] exception interpolating string: Edit Document '#{documentHome.instance.name}' javax.faces.el.EvaluationException: Cannot get value for expression '#{documentHome.instance.name}' at org.apache.myfaces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:402) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:57) at org.jboss.seam.core.Interpolator.interpolateExpressions(Interpolator.java:88) at org.jboss.seam.core.Interpolator.interpolate(Interpolator.java:67) at org.jboss.seam.pages.Page.renderDescription(Page.java:100) at org.jboss.seam.core.Manager.prepareBackswitch(Manager.java:1056) at org.jboss.seam.jsf.AbstractSeamPhaseListener.afterRender(AbstractSeamPhaseListener.java:220) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:116) at org.apache.myfaces.lifecycle.PhaseListenerManager.informPhaseListenersAfter(PhaseListenerManager.java:89) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:391) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) So the /loginRequired.xhtml call results in creation of documentHome, apparently to get the page description of /docEdit.xhtml. But since I'm not logged in, documentHome can't be constructed (the authenticatedUser injection doesn't work). I know I shouldn't even show the 'Edit Document' button if the user isn't logged in, but I don't see why the page description is needed if I'm redirecting "over" the page. -- 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

19 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1007) seam-gen integrated with entityConverter to implement foreign-key constraints with selectList

by Jeffrey Constantin (JIRA)

seam-gen integrated with entityConverter to implement foreign-key constraints with selectList --------------------------------------------------------------------------------------------- Key: JBSEAM-1007 URL: http://jira.jboss.com/jira/browse/JBSEAM-1007 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Jeffrey Constantin Priority: Optional Have seam-gen "optionally" generate selectlist (<h:selectOneMenu>) tags in generated application based on foreign-key constraints in the data model -OR- user-entered meta data (like data-type mapping in Eclipse IDE). Given a data model with foreign-key constraints enabled, seam-gen could recognize the relationship and automatically build the proper tags as explained in the SeamEntityConverter page ("http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamEntityConverter") COPIED FROM SeamEntityConverter PAGE: -------------------------------------------------------------------------- If you create or edit the record of an employee, you want to set the department. This list of available departments has to be fetched from the database. You can do this by defining a query object in components.xml: <framework:entity-query name="departments" ejbql="select d from Department d" /> Now you can use the seam component "departments" with the s:selectitems tag: <h:selectOneMenu value="#{employee.department}"> <s:selectItems value="#{departments.resultList}" var="department" label="#{department.name}"/> <ec:convertEntity /> </h:selectOneMenu > --------------------------------------------------------------- -- 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

19 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-954) Don't flush the SMPC at the end of the "render" txn

by Gavin King (JIRA)

Don't flush the SMPC at the end of the "render" txn --------------------------------------------------- Key: JBSEAM-954 URL: http://jira.jboss.com/jira/browse/JBSEAM-954 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA This should at least be an option. Its a performance and semantic improvement. -- 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

19 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-274) More flexible mapping of URLs to view ids

by Stuart Robertson (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-274?page=comments#action_12355461 ] Stuart Robertson commented on JBSEAM-274: ----------------------------------------- It would be nice if this mechanism were also useful for things like mailing email confirmation links and such. As in the user signs up and gives their email, we email them a link which when clicked, indicates that they received the email at that address. Or sending users links which take them right to a certain spot in the application (click here to view your latest invoice...). > More flexible mapping of URLs to view ids > ----------------------------------------- > > Key: JBSEAM-274 > URL: http://jira.jboss.com/jira/browse/JBSEAM-274 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Gavin King > Assigned To: Gavin King > Fix For: 1.3.0.BETA1 > > > For example, I want to be able to use a URL like this: > http://mydomain.com/myblog/archive/200306 > To get me to archive.xhtml with a request parameter 200306 (not really a request parameter, but we could try to abstract that so that it can be used with @RequestParameter). > Not sure if this is possible without changing the JSF implementation. -- 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

19 years, 1 month

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-998) Hot deploy of pages.xml

by Gavin King (JIRA)

Hot deploy of pages.xml ----------------------- Key: JBSEAM-998 URL: http://jira.jboss.com/jira/browse/JBSEAM-998 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.1.GA Changes to the pages.xml file should be immediately visible without a container restart in debug mode. This affects the Exceptions and Pages components. -- 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

19 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-970) Hot deployment for pages.xml, components.xml and JavaBean components

by Gavin King (JIRA)

Hot deployment for pages.xml, components.xml and JavaBean components -------------------------------------------------------------------- Key: JBSEAM-970 URL: http://jira.jboss.com/jira/browse/JBSEAM-970 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.2.1.GA We can create a scanning classloader, and redeploy Component, Pages, Events, Exceptions when necessary.... -- 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

19 years, 1 month

1
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 March 2007