May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1051) Conversation Picker no longer renders

by Tony Herstell (JIRA)

Conversation Picker no longer renders ------------------------------------- Key: JBSEAM-1051 URL: http://jira.jboss.com/jira/browse/JBSEAM-1051 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.0.GA Environment: Seam 1.2.0.Patch 1, IceFaces 1.6.0.DR1, JBoss Server Reporter: Tony Herstell http://gaming.homeip.net:8080/risingstars (it should be rendering when you jump out of a conversation using the menu i.e. Find+update and then use the menu to Find+Start a delete. This stopped working when I moved onto Seam 1.2.0.Patch 1 -- 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

17 years, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1314) Default bundle for each page

by H T (JIRA)

Default bundle for each page ---------------------------- Key: JBSEAM-1314 URL: http://jira.jboss.com/jira/browse/JBSEAM-1314 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.3.0.BETA1 Reporter: H T Make a page have a default bundle file instead of allowing it to be specified as an attribute of the "page" element. Say if we have person.xhtml, Seam looks for person.page.xml by default and associates it with person.xhtml. We should also ask Seam to look for PersonMessages.properties. This is more of a convention issue than anything else. -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1195) enforce startup dependency of EntityManagerFactory on Ejb

by Matt Drees (JIRA)

enforce startup dependency of EntityManagerFactory on Ejb --------------------------------------------------------- Key: JBSEAM-1195 URL: http://jira.jboss.com/jira/browse/JBSEAM-1195 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Reporter: Matt Drees Priority: Minor A war project created by seam gen uses an EntityManagerFactory component. Integration tests using the Embedded EJB container work because the Ejb component starts before the EMF component, but this is by chance only. If the EMF component starts before the Ejb component, it fails. This has been experienced when trying to run a war project on Tomcat. I'll attach a test that shows this. I believe the solution would be to add "org.jboss.seam.core.ejb" to the depends list of EntityManagerFactory's @Startup annotation. -- 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

17 years, 8 months

3
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1143) Hot Deploy causing MyEclipse IDE to die

by Tony Herstell (JIRA)

Hot Deploy causing MyEclipse IDE to die --------------------------------------- Key: JBSEAM-1143 URL: http://jira.jboss.com/jira/browse/JBSEAM-1143 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Environment: MyEclipse. Java 1.6. Windows Reporter: Tony Herstell Priority: Minor Hot Deploy causing MyEclipse IDE to die. Working in Exploded deploy mode, so server is run through the IDE, and is running constantly. So... I am changing code that is copied directly to the deploy area of JBoss automaticlly (works great for .xhtml files) Seems to be when re-factroing code (I think its sometimes when I refactor a class and move it to another package)... I used to get a message saying JBoss can't cope with the change and MyEclipse reccomends a re-start (click Yes to re-start).. now I don't.. The JVM running the IDE bales back to desktop! I will endevour to trace exactly what causes it. ONLY happened with latest version of Seam. -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1300) AJAX4JSF call/partial view rerender from a view triggers the Seam page action for the view

by John Chesher (JIRA)

AJAX4JSF call/partial view rerender from a view triggers the Seam page action for the view ------------------------------------------------------------------------------------------ Key: JBSEAM-1300 URL: http://jira.jboss.com/jira/browse/JBSEAM-1300 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.0.GA Reporter: John Chesher I reused the AJAX4JSF search page/code from the booking example to build a search page for my application. I decided to make the search EJB session-scoped, so that my search criteria would still be there anytime I came back to the screen. I also wanted to display the "previous" search results whenever I came back to that page, but I wanted to perform a new search, just in case the results would be different searching with the same criteria, but at this new point in time. So, I added a page action in pages.xml. Everything seemed to work fine, but I noticed that whenever I do an AJAX-based search from the screen, it does the search twice, once for the AJAX call and apparently once again for the page action defined in pages.xml. I hadn't thought about it, but a coworker suggested that was behavior he was not expecting, as he thought the AJAX call would be a get rather than a post and that, since the entire page is not rerendered (we tested and it's not), Seam would not execute the page action specified in pages.xml. I implemented a "workaround" by having my AJAX call invoke a dummy method (does almost nothing), then letting the method specified on the page action do the real work of the search. This seems to provide the functionality I want without doing a redundant search when doing the AJAX-driven search, but we felt this was a pretty odd way to have to implement this functionality. Code snippets are below. Am I missing something? Is there a more "correct"/elegant way to implement the desired functionality when using Seam and AJAX4JSF together? The less-than-elegant solution I have now works, but I want to ensure I haven't leveraged unintended functionality, which could yield unexpected results or could be disallowed in a future release, or something like 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

17 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1305) Incorrect XML encoding for complex return objects from Seam remote methods

by Michael Yuan (JIRA)

Incorrect XML encoding for complex return objects from Seam remote methods -------------------------------------------------------------------------- Key: JBSEAM-1305 URL: http://jira.jboss.com/jira/browse/JBSEAM-1305 Project: JBoss Seam Issue Type: Bug Reporter: Michael Yuan It seems that Seam remoting in 1.2.1 GA (and also the code in CVS) does not correctly encode the return value object from a Seam remote method. For instance, the remote/progressbar example does not work in JBoss AS 4.0.5 GA or 4.2.0. The return XML in the AJAX request misses a <member> tag: Error: mismatched tag. Expected: </member>. Source File: http://localhost:8080/seam-progressbar/seam/resource/remoting/execute Line: 1, Column: 291 Source Code: <envelope><header><context><conversationId>3</conversationId></context></header><body><result id="0"><value><ref id="0"/></value><refs><ref id="0"><bean type="progress"><member name="handler"><member name="percentComplete"><number>1</number></member><member name="status"><null/></member></bean></ref></refs></result></body></envelope> -- 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

17 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-614) API Documentation for the org.jboss.seam.ui.* classes

by Todd Smart (JIRA)

API Documentation for the org.jboss.seam.ui.* classes ----------------------------------------------------- Key: JBSEAM-614 URL: http://jira.jboss.com/jira/browse/JBSEAM-614 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 1.1.1.GA Reporter: Todd Smart This is related in some ways to http://jira.jboss.org/jira/browse/JBSEAM-301. It is very difficult (without reviewing the source code) to understand the Seam UI class and tag libraries. At a minimum, the API should be included in the documentation IMO. Regards, Todd -- 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

17 years, 8 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-844) Fire an event on AuthorizationException

by Ben Catherall (JIRA)

Fire an event on AuthorizationException --------------------------------------- Key: JBSEAM-844 URL: http://jira.jboss.com/jira/browse/JBSEAM-844 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.1.6.GA Reporter: Ben Catherall When an AuthorizationException is thrown in Identity.checkRestriction, it would be useful if an event is raised in the same way it is for a NotLoggedInException. A suitable event name might be "org.jboss.seam.notAuthorized" -- 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

17 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1237) Examples are broken

by Shane Bryzak (JIRA)

Examples are broken ------------------- Key: JBSEAM-1237 URL: http://jira.jboss.com/jira/browse/JBSEAM-1237 Project: JBoss Seam Issue Type: Bug Components: Examples Reporter: Shane Bryzak Priority: Blocker Fix For: 1.3.0.BETA1 A number of the examples are broken, most likely because of the upgrade to the JSF RI. Before the next release we need to fix them all and test them thoroughly. A few examples: The booking example throws the following exception when searching for hotels: javax.faces.el.MethodNotFoundException: /main.xhtml @24,101 actionListener="#{hotelSearch.find}": Method not found: Hote lSearchingAction:abe6-pthmok-f0w4r0et-1-f0w4v1kx-r.find(javax.faces.event.ActionEvent) at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:71) at javax.faces.component.UICommand.broadcast(UICommand.java:376) at org.ajax4jsf.framework.ajax.AjaxActionComponent.broadcast(AjaxActionComponent.java:47) at org.ajax4jsf.framework.ajax.AjaxViewRoot.processEvents(AjaxViewRoot.java:180) at org.ajax4jsf.framework.ajax.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:158) at org.ajax4jsf.framework.ajax.AjaxViewRoot.processApplication(AjaxViewRoot.java:329) at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) The seam-issues example throws a NoClassDefFoundError when opening the home page: java.lang.NoClassDefFoundError org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlRendererUtils.writePrettyLineSeparator(HtmlRendererUtils.java:484) org.apache.myfaces.custom.datalist.HtmlListRenderer.encodeBegin(HtmlListRenderer.java:54) javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:785) javax.faces.component.UIData.encodeBegin(UIData.java:879) org.apache.myfaces.component.html.ext.HtmlDataTableHack.encodeBegin(HtmlDataTableHack.java:169) javax.faces.component.UIComponent.encodeAll(UIComponent.java:884) javax.faces.render.Renderer.encodeChildren(Renderer.java:137) javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:809) javax.faces.component.UIComponent.encodeAll(UIComponent.java:886) javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) Security is broken for the manager user in dvd store (the manager/manager login doesn't work). -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1292) conversations re-started in pageflows

by Andy Gibson (JIRA)

conversations re-started in pageflows ------------------------------------- Key: JBSEAM-1292 URL: http://jira.jboss.com/jira/browse/JBSEAM-1292 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Windows XP, JBoss 4.0.5, Eclipse & Exadel, IE 6.09, Seam-gen generated app, using MySQL 5 as the backend. Reporter: Andy Gibson See forum post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043286#4043286 The problem is that when you use the <begin-conversation> tag in pages.xml with a pageflow, any time the page is rendered Seam attemps to re-perform the conversation requirements. (starting, joining or creating a new nested one). Note, this is ONLY a problem when using a pageflow, without a pageflow, everything runs fine. If you use @Begin annotations on a method with a pageflow, then everything is fine. It appears to only be when using begin-conversation in pages.xml with a pageflow. For the difference options, here are the results : <begin-conversation> results in an error (beginning conversation from long running conversation) <begin-conversation join="true"> works ok because it just joins the conversation it started first time it hit the page <begin-conversation nested="true"> causes a new nested conversation to be created each time the page is rendered Somewhat similar to issue http://jira.jboss.org/jira/browse/JBSEAM-608 which was related to the pageflow re-starting on each render, except now it is the conversation that is trying to re-start on each render. At the end of my attached forum post, I describe why using just join=true is not a practical solution for more complex scenarios involving nested flows. -- 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

17 years, 8 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2007