July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3185) Unable to run the project generated with seam-gen

by Paul Nutlis (JIRA)

Unable to run the project generated with seam-gen ------------------------------------------------- Key: JBSEAM-3185 URL: https://jira.jboss.org/jira/browse/JBSEAM-3185 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1, 2.0.3.CR1 Environment: OS: Linux x86_64 JBOSS: jboss-4.2.2.GA JDK: jdk1.5.0_05 Reporter: Paul Nutlis I'm trying to run a project generated with seam-gen. when I open the project in explorer nothing happens on the page and I see lots off stack trace messages running in server console: steps: 1. configure project: seam setup (all defaults) 2. create project: seam create-project 3. start jboss server: ./run.sh -b<myhost> 4. deploy project: seam deploy 5. navigate to the webpage of a project: http://<myhost>:8080/<myproj> 6. console exploads with stack trace. I tried both 2.0 and 2.1 versions of seam and got the same results on linux, I also tried the same steps on my laptop running XP with 2.0.3 CR1 and everything worked perfectly, I was able to get a starting page. Please prompt me what am I missing. -- 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, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3174) java.util.Calendar support in Remoting

by vdweij (JIRA)

java.util.Calendar support in Remoting -------------------------------------- Key: JBSEAM-3174 URL: https://jira.jboss.org/jira/browse/JBSEAM-3174 Project: Seam Issue Type: Feature Request Components: Remoting Affects Versions: 2.0.2.SP1 Reporter: vdweij Assignee: Shane Bryzak Currently only java.util.Date and descendent are supported as type for fields containing date values. Objects of type java.util.Calendar are also commonly used and in case of legacy code these objects cannot be (directly) used by Seam Remoting. It would be an improvement if objects with Calendar fields could be used on the client side. -- 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, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3183) Natural Nested Conversation END

by Tomas Cerny (JIRA)

Natural Nested Conversation END -------------------------------- Key: JBSEAM-3183 URL: https://jira.jboss.org/jira/browse/JBSEAM-3183 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Environment: Linux Gentoo, FF Reporter: Tomas Cerny Natural Nested Conversation I have chosen the harder way in my application. I have figured out that this combination does not work well now. The biggest problem I got into is when I end my root conversation, it does not close the children. Example: * root conversation id = contest:2 * child conversation id = exam:82 when I call root conversation end() it closes contest:2 conversation then there is new conversation open with identifier eg 19 and at this context is called Manager.removeCurrentConversationAndDestroyNestedContexts well this tries to remove the child conversation, but the problem is that this would work from conversation contest:2 context, but it does not work from conversation 19 context Workaround if(getConversationNestedChildren().size() > 0) { Conversation.instance().redirect(); } this fortunately uses the context of conversation contest:2. Even thought that the conversation is already ended and redirect is solved by pages.xml Related http://jira.jboss.org/jira/browse/JBSEAM-2606 Other problems Redirects to natural conversation sometimes causes Exception conversation name already in use. It seems that I cannot programmaticaly close root conversation and redirect to another (new) one. Because its children will get orphans! I think (I am sure you will be arguing) that the current life-cycle for natural nested conversation is wrong. The removal of children should happen immediately when parent is removed. -- 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, 5 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2994) Support all pages.xml through annotations for Wicket

by Pete Muir (JIRA)

Support all pages.xml through annotations for Wicket ---------------------------------------------------- Key: JBSEAM-2994 URL: http://jira.jboss.com/jira/browse/JBSEAM-2994 Project: Seam Issue Type: Feature Request Components: Wicket Affects Versions: 2.1.0.A1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Critical Fix For: 2.1.0.BETA1 Initially via a factory which will apply interceptors to all components which require Seam support Look at some sort of byte code enhancement later Also, support injection/disinjection -- 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, 5 months

2
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3180) Support joining named conversations

by Pete Muir (JIRA)

Support joining named conversations ----------------------------------- Key: JBSEAM-3180 URL: https://jira.jboss.org/jira/browse/JBSEAM-3180 Project: Seam Issue Type: Feature Request Components: Wicket Reporter: Pete Muir -- 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, 5 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3179) Add method to Query for retrieving all records ignoring the maxResults

by Alex Savitsky (JIRA)

Add method to Query for retrieving all records ignoring the maxResults ---------------------------------------------------------------------- Key: JBSEAM-3179 URL: https://jira.jboss.org/jira/browse/JBSEAM-3179 Project: Seam Issue Type: Feature Request Components: Framework Reporter: Alex Savitsky Sometimes, I find myself using the same query in two distinct use cases - with the maxResults limit, and without one. Say, if I have a list of entities that is used as a dropdown lookup in another entity, then I need all records (let's say there are about 200 of them) when I'm making a dropdown, yet I might need only a subset of records when I'm making a management screen and want the entites paginated. Or I need to paginate entities for the screen display, but retrieve them all in a report that uses the same query. Right now I ended up overriding framework.Query class, adding the following method to it: public List<E> getAllResults() { Integer currentMaxResults = maxResults; setMaxResults(null); List<E> result = getResultList(); setMaxResults(currentMaxResults); return result; } and using #{query.allResults} when I need them all. Maybe it makes sense to add it to this class on a permanent basis? It surely won't break anything, and might help covering an important usecase. -- 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, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3155) Make forum archive searchable

by Marco Brandizi (JIRA)

Make forum archive searchable ----------------------------- Key: JBSEAM-3155 URL: http://jira.jboss.com/jira/browse/JBSEAM-3155 Project: Seam Issue Type: Feature Request Reporter: Marco Brandizi I cannot search for messages among the 2774 messages the user forum archive is composed of: http://www.seamframework.org/Community/SeamUsers i.e.: the archive is a useless waste of disk space. -- 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, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1526) Support selective validation with a:region

by Christian Bauer (JIRA)

Support selective validation with a:region ------------------------------------------ Key: JBSEAM-1526 URL: http://jira.jboss.com/jira/browse/JBSEAM-1526 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer In complex forms I'd like to be able to customize validation per region: <h:form> <a:region> <h:inputText value="#{foo.bar}"/> <a:region> <h:inputText value="#{bar.foo}"/> <a:commandButton action="#{bar.baz}"/> </a> <a:commandButton action="#{foo.baz}"/> </a> </h:form> If the nested button is pressed, I only want #{bar.foo} validated (there is an <s:validateAll> around it). If the outer button is pressed, I want both properties validated. I realize that this is a major issue regarding model updates, however, I don't need to update the model for any non-validated property because a) it is not decoded on the server anyway (? I don't understand the a:region docs) b) i don't need an updated model because my action doesn't expect it c) i don't need an updated model because i am re-rendering an area that doesn't expect it -- 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, 6 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3171) use rich:calendar for timestamp fields

by Dan Allen (JIRA)

use rich:calendar for timestamp fields -------------------------------------- Key: JBSEAM-3171 URL: https://jira.jboss.org/jira/browse/JBSEAM-3171 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1, 2.0.3.CR1 Reporter: Dan Allen Assignee: Dan Allen Priority: Minor Fix For: 2.0.3.GA, 2.1.0.BETA1 We would like to demonstrate the <rich:component> tag's time support. -- 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, 6 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3170) s:conversationPropagation/link/button should support flush mode for conversations

by Scott Olcott (JIRA)

s:conversationPropagation/link/button should support flush mode for conversations --------------------------------------------------------------------------------- Key: JBSEAM-3170 URL: https://jira.jboss.org/jira/browse/JBSEAM-3170 Project: Seam Issue Type: Feature Request Components: JSF Controls Affects Versions: 2.1.0.A1, 2.0.3.CR1, 2.0.2.SP1 Reporter: Scott Olcott -- 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, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008