October 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4364) Fix joystickSellingTest in seambay example ftest

by Ondrej Skutka (JIRA)

Fix joystickSellingTest in seambay example ftest ------------------------------------------------ Key: JBSEAM-4364 URL: https://jira.jboss.org/jira/browse/JBSEAM-4364 Project: Seam Issue Type: Bug Components: Test Harness Reporter: Ondrej Skutka Assignee: Martin Gencur Add a delay before choosing a value from the combobox. It needs some time to get loaded with items. -- 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

15 years, 2 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4359) Create a functional test for remoting/gwt example

by Martin Gencur (JIRA)

Create a functional test for remoting/gwt example ------------------------------------------------- Key: JBSEAM-4359 URL: https://jira.jboss.org/jira/browse/JBSEAM-4359 Project: Seam Issue Type: Task Reporter: Martin Gencur Assignee: Martin Gencur Priority: Minor Fix For: 2.2.1.CR1 -- 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

15 years, 2 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4356) Creation of a functional test for remoting/helloworld example

by Martin Gencur (JIRA)

Creation of a functional test for remoting/helloworld example ------------------------------------------------------------- Key: JBSEAM-4356 URL: https://jira.jboss.org/jira/browse/JBSEAM-4356 Project: Seam Issue Type: Task Reporter: Martin Gencur Assignee: Martin Gencur Priority: Minor Fix For: 2.2.1.CR1 -- 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

15 years, 2 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4355) Create a functional test for seamspace example

by Martin Gencur (JIRA)

Create a functional test for seamspace example ---------------------------------------------- Key: JBSEAM-4355 URL: https://jira.jboss.org/jira/browse/JBSEAM-4355 Project: Seam Issue Type: Task Components: Examples Reporter: Martin Gencur Assignee: Martin Gencur Priority: Minor Fix For: 2.2.1.CR1 -- 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

15 years, 2 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4353) Create functional test for Guice example

by Martin Gencur (JIRA)

Create functional test for Guice example ---------------------------------------- Key: JBSEAM-4353 URL: https://jira.jboss.org/jira/browse/JBSEAM-4353 Project: Seam Issue Type: Task Components: Examples Reporter: Martin Gencur Assignee: Martin Gencur Priority: Minor Fix For: 2.2.1.CR1 Create functional test for Guice example. -- 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

15 years, 2 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4457) CLONE - seam script in distribution should have executable permission set

by Marek Novotny (JIRA)

CLONE - seam script in distribution should have executable permission set ------------------------------------------------------------------------- Key: JBSEAM-4457 URL: https://jira.jboss.org/jira/browse/JBSEAM-4457 Project: Seam Issue Type: Feature Request Components: Build Affects Versions: 2.2.0.GA Reporter: Ondrej Skutka Assignee: Karel Piwko Fix For: 2.2.1.CR1 -- 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

15 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4453) seam script in distribution should have executable permission set

by Ondrej Skutka (JIRA)

seam script in distribution should have executable permission set ----------------------------------------------------------------- Key: JBSEAM-4453 URL: https://jira.jboss.org/jira/browse/JBSEAM-4453 Project: Seam Issue Type: Feature Request Components: Build Affects Versions: 2.2.0.GA Reporter: Ondrej Skutka Assignee: Marek Novotny -- 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

15 years, 2 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1712) Allow options for SMPC per Nested Conversation

by Andy Gibson (JIRA)

Allow options for SMPC per Nested Conversation ---------------------------------------------- Key: JBSEAM-1712 URL: http://jira.jboss.com/jira/browse/JBSEAM-1712 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Environment: Windows XP, Seam 2.0 Beta, JBoss 4.2 Reporter: Andy Gibson I'd like to request the option to specify that a nested conversation gets it's own entity manager instance as opposed to sharing it with it's parent conversation and other nested conversations. The problem with nested conversations is that you can't actually use them to edit multiple entities since when you flush the PC, you flush it for all conversations. This makes nested conversations only really useful for browsing data, and creating new top level conversation to edit items to isolate the flushes. The only alternative is to use a non-Seam managed PC, and make use of the "PC per stateful bean" rule to map a single PC to a single backing bean, but you lose the benefits of a seam managed PC. What might be nice is something like : @Begin(nested=true, newPC=true) and <begin-conversation nested="true" newPC="true"/> which would indicate that this new nested conversation gets it's own entity manager instance. The attribute would be ignored if this wasn't a nested conversation, and obviously, by default, the attribute is set to false, and a shared PC would be used in the nested conversation in such cases. I'm already using one PC per conversation by using top level conversations to edit items, I'd just like to use one PC per nested conversation (where applicable) to get the benefits of nested conversations. There are a couple of posts in the forums where I've touched on some of my problems with this issue : http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111681 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111384 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=113362 -- 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

15 years, 2 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4450) Seam gen does not cope well with a with recursive schema

by Shaun Appleton (JIRA)

Seam gen does not cope well with a with recursive schema -------------------------------------------------------- Key: JBSEAM-4450 URL: https://jira.jboss.org/jira/browse/JBSEAM-4450 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.2.SP1 Reporter: Shaun Appleton Generate the following schema (in hypersonic) - CREATE TABLE COLOR ( CODIGO INTEGER, DESIGNACAO VARCHAR(30) NOT NULL, CONSTRAINT ARMAZENS_CP11 PRIMARY KEY (CODIGO) ) CREATE TABLE ARTICLE ( CODIGO VARCHAR(15), DESIGNACAO VARCHAR(50), C_COLOR INTEGER, CONSTRAINT ARTIGOS_CP11 PRIMARY KEY (CODIGO), CONSTRAINT ARTIGOS_CE121 FOREIGN KEY (C_COLOR) REFERENCES COLOR(CODIGO) ) CREATE TABLE ARTICLE_ROW ( C_ARTIGO VARCHAR(15), C_COLOR INTEGER, OBSERVACOES VARCHAR(4000), CONSTRAINT REL_ART_ARM_CP11 PRIMARY KEY (C_ARTIGO, C_COLOR), CONSTRAINT REL_ART_ARM_CE11 FOREIGN KEY (C_ARTIGO) REFERENCES ARTICLE (CODIGO), CONSTRAINT REL_ART_ARM_CE21 FOREIGN KEY (C_COLOR) REFERENCES COLOR(CODIGO) ) insert into article(codigo, designacao) values ('1', 'article 1') insert into article(codigo, designacao) values ('2', 'article 2') insert into color(codigo, designacao) values (1, 'blue') insert into color(codigo, designacao) values (2, 'red') insert into color(codigo, designacao) values (3, 'green') reverse engineer the schema (I used JBDS) and deploy. a) Select Article List b) Select edit to edit an article c) Select a color - green for example d) Select articleRows (still with edit article) e) Select Add Article row - notice color is as in step c even though in DB it is null. Debugging this shows that within ArticleRowHome ColorHome is being re-used from the previous edit of article. Whereas ArticleRow.color is not yet defined. This appears to be the first issue described in https://jira.jboss.org/jira/browse/JBSEAM-3454 (but not reported there). -- 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

15 years, 2 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4297) Add disable attribute for fileUpload

by Shervin Asgari (JIRA)

Add disable attribute for fileUpload ------------------------------------ Key: JBSEAM-4297 URL: https://jira.jboss.org/jira/browse/JBSEAM-4297 Project: Seam Issue Type: Feature Request Reporter: Shervin Asgari Why is there no disabled attribute on s:fileUpload? We have to hack it in by using javascript and adding the disabled attribute once the page is loaded. -- 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

15 years, 2 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues October 2009