July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3158) TestNG fails for action in Seam 2.0.x web project when server is running.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-3158?page=all ] Pete Muir closed JBSEAM-3158. ----------------------------- Resolution: Done > TestNG fails for action in Seam 2.0.x web project when server is running. > ------------------------------------------------------------------------- > > Key: JBSEAM-3158 > URL: http://jira.jboss.com/jira/browse/JBSEAM-3158 > Project: Seam > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.1.0.A1, 2.0.3.CR1 > Reporter: Anton Klimkovich > Assigned To: Pete Muir > Fix For: 2.0.3.GA, 2.1.0.BETA1 > > Attachments: exception.txt, exception2.txt > > > EXECUTE: Create Seam 2.0.x web project (War or Ear) > EXECUTE: Create Action > EXECUTE: Run the project on the JBOss AS > EXECUTE: Run TestNG for ActionTest.xml > FAILURE: TestNG failed. > Log attached. > TestNG works for action created in Seam 1.2.x web project. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3158) TestNG fails for action in Seam 2.0.x web project when server is running.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-3158?page=comments#action_12421075 ] Pete Muir commented on JBSEAM-3158: ----------------------------------- We have to make a change in the Embedded Bootstrap to avoid the port conflict. This is fixed for AS 4.2, but as AS 4.3 introduces JBoss Messaging, a new conflict arises. > TestNG fails for action in Seam 2.0.x web project when server is running. > ------------------------------------------------------------------------- > > Key: JBSEAM-3158 > URL: http://jira.jboss.com/jira/browse/JBSEAM-3158 > Project: Seam > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.1.0.A1, 2.0.3.CR1 > Reporter: Anton Klimkovich > Assigned To: Pete Muir > Fix For: 2.1.0.BETA1, 2.0.3.GA > > Attachments: exception.txt, exception2.txt > > > EXECUTE: Create Seam 2.0.x web project (War or Ear) > EXECUTE: Create Action > EXECUTE: Run the project on the JBOss AS > EXECUTE: Run TestNG for ActionTest.xml > FAILURE: TestNG failed. > Log attached. > TestNG works for action created in Seam 1.2.x web project. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Moved: (JBSEAM-3158) TestNG fails for action in Seam 2.0.x web project when server is running.

by Pete Muir (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-3158?page=all ] Pete Muir moved JBIDE-2454 to JBSEAM-3158: ------------------------------------------ Project: Seam (was: Tools (JBoss Tools)) Key: JBSEAM-3158 (was: JBIDE-2454) Component/s: Test Harness (was: Seam) Fix Version/s: 2.0.3.GA 2.1.0.BETA1 (was: 3.0.0.alpha) Affects Version/s: 2.1.0.A1 2.0.3.CR1 (was: 2.1.2) > TestNG fails for action in Seam 2.0.x web project when server is running. > ------------------------------------------------------------------------- > > Key: JBSEAM-3158 > URL: http://jira.jboss.com/jira/browse/JBSEAM-3158 > Project: Seam > Issue Type: Bug > Components: Test Harness > Affects Versions: 2.1.0.A1, 2.0.3.CR1 > Reporter: Anton Klimkovich > Assigned To: Pete Muir > Fix For: 2.0.3.GA, 2.1.0.BETA1 > > Attachments: exception.txt, exception2.txt > > > EXECUTE: Create Seam 2.0.x web project (War or Ear) > EXECUTE: Create Action > EXECUTE: Run the project on the JBOss AS > EXECUTE: Run TestNG for ActionTest.xml > FAILURE: TestNG failed. > Log attached. > TestNG works for action created in Seam 1.2.x web project. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2390) fileUpload doesn't work with Trinidad

by Robert Morse (JIRA)

fileUpload doesn't work with Trinidad ------------------------------------- Key: JBSEAM-2390 URL: http://jira.jboss.com/jira/browse/JBSEAM-2390 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.1.CR1, 2.0.0.GA Environment: Mac OS X 10.5, Java 1.5 Reporter: Robert Morse fileUpload stops working when Trinidad is integrated with a project. See: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=120188&postdays=... for further details and discussion. -- 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-1052) seam-dev.properties, seam-prod.properties

by Pete Muir (JIRA)

seam-dev.properties, seam-prod.properties ----------------------------------------- Key: JBSEAM-1052 URL: http://jira.jboss.com/jira/browse/JBSEAM-1052 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.0.GA Reporter: Pete Muir Priority: Optional In the same way you have persistence-dev.xml, there should be seam-dev.properties to allow you to configure your application differently when in dev/prod (e.g. disable random password generation). AFAICS seam.properties must be in WEB-INF/classes/seam.properties for it to be read (it isn't read in ejb-jar/seam.properties as it's not in the classloader) -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3156) Decide the image src url in generated HTML on s:graphicImage

by Susanne Jarl (JIRA)

Decide the image src url in generated HTML on s:graphicImage ------------------------------------------------------------ Key: JBSEAM-3156 URL: http://jira.jboss.com/jira/browse/JBSEAM-3156 Project: Seam Issue Type: Feature Request Reporter: Susanne Jarl Priority: Minor I would like to be able to set the image url when I use s:graphicImage and get the image from a database. As for now the generated url in html code always starts with /seam/resource/graphicImage and I can only change the ending of the url by using the attribute filename. I want to decide the whole url. The reason I want this is for search engine optimization. -- 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

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3154) Better if Context.remove() actually returns what was removed.

by Tobias Hill (JIRA)

Better if Context.remove() actually returns what was removed. -------------------------------------------------------------- Key: JBSEAM-3154 URL: http://jira.jboss.com/jira/browse/JBSEAM-3154 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.2.SP1 Reporter: Tobias Hill In short: it is quite common to let a remove-method on map-like structures return the removed object. I can't see any reason why Context.remove() has to return void. It would let me write: Object bar = getSessionContext().remove("foo"); Instead of: Object bar = getSessionContext().get("foo"); getSessionContext().remove("404-error"); -- 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

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3153) Template property deleted in UIDecorate class

by Jean-Baptiste Meyer (JIRA)

Template property deleted in UIDecorate class --------------------------------------------- Key: JBSEAM-3153 URL: http://jira.jboss.com/jira/browse/JBSEAM-3153 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.SP1 Environment: MacOSX. 10.5.4 jboss-4.2.2.GA java5 Reporter: Jean-Baptiste Meyer In the documentation of seam 2.0.0 http://docs.jboss.org/seam/2.0.0.GA/ui/apidocs/org/jboss/seam/ui/componen..., the HtmlDecorate has a template attribute. However in last version this property disappeared. I would like to generate a decorate biding it to a rich:panel. here is what I use in my xhtml : <rich:panel binding="#{configurationTypeInstanceManagerBean.layout}" /> Here is my setter in my bean ; public void setLayout(UIComponent layout) { this.layout = layout; HtmlDecorate decorate = new HtmlDecorate() ; HtmlOutputText text = new HtmlOutputText() ; text.setValue("test") ; text.setTitle("test") ; text.setId("test") ; decorate.getChildren().add(text) ; HtmlInputText in = new HtmlInputText() ; in.setId("in") ; in.setSize(40) ; layout.getChildren().add(decorate) ; layout.processRestoreState(ctx, decorate ) ; } Adding a template to have a code like that : <s:decorate id="configurationNameDecoration" template="/layout/edit.xhtml">... seem to be very complicated to do know. I don't see any documentation why this template property has been deleted. I blocked in my work because of 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, 6 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2662) Map Spring transaction status codes back to JTA status codes in SpringTransaction.JtaSpringSynchronizationAdapter

by Michael Youngstrom (JIRA)

Map Spring transaction status codes back to JTA status codes in SpringTransaction.JtaSpringSynchronizationAdapter ----------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2662 URL: http://jira.jboss.com/jira/browse/JBSEAM-2662 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 2.1.0.A1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.1.x SpringTransaction.JtaSpringSynchronizationAdapter doesn't map SpringTransaction status codes back to JTA codes when adapting Spring synchronization to JTA Synchornization -- 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

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1844) @Raise event does not work with @Observer in the same bean

by Ilya Doe (JIRA)

@Raise event does not work with @Observer in the same bean ---------------------------------------------------------- Key: JBSEAM-1844 URL: http://jira.jboss.com/jira/browse/JBSEAM-1844 Project: JBoss Seam Issue Type: Bug Reporter: Ilya Doe If the method that is annotated with @RaiseEvent is in the same stateful bean (conversation scoped) with the method annotated @Observer; when the observer method is called all to-be injected fields are null. See details in the forum post: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4074789 -- 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
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 July 2008