August 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Moved: (SEAM-11) Explore the options of a Seam 2 -> CDI conversion tool

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/SEAM-11?page=com.atlassian.jira.plugin.syst... ] Pete Muir moved WELD-541 to SEAM-11: ------------------------------------ Project: Seam 3 (was: Weld) Key: SEAM-11 (was: WELD-541) Component/s: (was: Tooling) > Explore the options of a Seam 2 -> CDI conversion tool > ------------------------------------------------------ > > Key: SEAM-11 > URL: https://jira.jboss.org/browse/SEAM-11 > Project: Seam 3 > Issue Type: Feature Request > Reporter: Nicklas Karlsson > > Explore the options of writing a Seam 2 -> CDI conversion tool that would map the concepts from Seam 2 to CDI (e.g. @Factory -> @Produces) and suggest modifications. > Check if JBoss Tools has any suitable infrastructure for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Moved: (SEAMPERSIST-7) Support JPA on Tomcat, and use JPA TX management to support TX events

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/SEAMPERSIST-7?page=com.atlassian.jira.plugi... ] Pete Muir moved WELD-607 to SEAMPERSIST-7: ------------------------------------------ Project: Seam Persistence and Transactions (was: Weld) Key: SEAMPERSIST-7 (was: WELD-607) Component/s: (was: Servlet Container Support) > Support JPA on Tomcat, and use JPA TX management to support TX events > --------------------------------------------------------------------- > > Key: SEAMPERSIST-7 > URL: https://jira.jboss.org/browse/SEAMPERSIST-7 > Project: Seam Persistence and Transactions > Issue Type: Feature Request > 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/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-4672) s:graphicImage in rich:extendedDataTable - using byte array datasource results in wrong drawing

by Helge Mahrt (JIRA)

s:graphicImage in rich:extendedDataTable - using byte array datasource results in wrong drawing ----------------------------------------------------------------------------------------------- Key: JBSEAM-4672 URL: https://jira.jboss.org/browse/JBSEAM-4672 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.2.0.GA Environment: JDK 1.6.0 Update 18, Windows XP SP3, JBoss 4.2.2.GA, Oracle 10g express, Reporter: Helge Mahrt I am using the s:graphicImage in a rich:column within a rich:extendedDataTable: <rich:extendedDataTable id="languageDataTable" value="#{dtoList}" var="item" > <rich:column sortable="false"> <s:graphicImage value="#{item.imageData}"/> [...] </rich:column> </rich:extendedDataTable> imageData is a byte array which is bound to a BLOB in the database. Not all objects in the database have an image, in fact most have null in the image field. After encountering the first row, where the object behind does have an image, s:graphicImage keeps drawing this very image in every subsequent row, until it encounters another object with the image set. Per default imageData returned a byte array of 0 size when there is no image in the database. I tried replacing that value by null, but the behaviour did not change. There are no errors or execeptions showing up. I think s:imageData, when using byte arrays as source, is not properly reacting to invalid/null image data. As a work-around I used the rendered attribute to hide the s:graphicImage control when there is no image data. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-4686) Typo in Seam refguide

by Ondrej Skutka (JIRA)

Typo in Seam refguide --------------------- Key: JBSEAM-4686 URL: https://jira.jboss.org/browse/JBSEAM-4686 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.2.1.CR2 Reporter: Ondrej Skutka Priority: Trivial Chapter 18.5 Rendering Swing/AWT components says: "Seam now provides experimental support for rendering Swing components to into a PDF image." Please choose the better preposition from the "to into" and remove the other. Chapter 21.2 Receiving mails: "JBoss AS 5.x and newer has mail-ra.rar with applied the patches, ..." Incorrect use of article detected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4254) Postback is incorectly determined in integration tests for NonFacesRequest and JSF 1.2

by Michal Orman (JIRA)

Postback is incorectly determined in integration tests for NonFacesRequest and JSF 1.2 -------------------------------------------------------------------------------------- Key: JBSEAM-4254 URL: https://jira.jboss.org/jira/browse/JBSEAM-4254 Project: Seam Issue Type: Bug Affects Versions: 2.1.2.GA Reporter: Michal Orman If I create NonFacesRequest to view which invokes action (for loading data), and contain page parameters, postback is determined to true (where it should be false). It happens because MockResponseStateManager do not override ResponseStateManager#isPostback method which determines postback basing on request parameters. So no matter if it is FacesRequest or NonFacesRequest if view defines page parameters it will be evaluated as postback. It works on production, because ResponseStateManagerImpl (from jsf-impl-1.2_12) overrides this method and determines if request is postback basing on ResponseStateManager.VIEW_STATE_PARAM parameter in requests parameters map. -- 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

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4540) OpenId example doesn't work with JBossAS 6.0.0.M1

by Martin Gencur (JIRA)

OpenId example doesn't work with JBossAS 6.0.0.M1 ------------------------------------------------- Key: JBSEAM-4540 URL: https://jira.jboss.org/jira/browse/JBSEAM-4540 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.0.GA Environment: JBossAS 6.0.0.M1 Reporter: Martin Gencur After enterring login, password and submitting the form in OpenId example the 404 Http status code is returned with: type: Status report message: /seam-openid/openid.seam description: The requested resource (/seam-openid/openid.seam) is not available. but the JBossAS console shows: 09:23:12,091 INFO [ConsumerManager] Verifying authentication response... 09:23:12,092 INFO [ConsumerManager] Received positive auth response. 09:23:12,093 INFO [ConsumerManager] Found association: {HMAC-SHA256}{4b750fee}{DFVFmA==} verifying signature locally... 09:23:12,094 INFO [ConsumerManager] Verification succeeded for: http://seamqa.myopenid.com/ The openid.seam (openid.xhtml) is view which is automatically generated by Seam. The openid feature logs in to remote authentication page and redirects automatically back to the openid.xhtml which is not available. -- 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

14 years, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBSEAM-4636) tasks_jboss5.editTurtleTask fails

by Jozef Hartinger (JIRA)

tasks_jboss5.editTurtleTask fails --------------------------------- Key: JBSEAM-4636 URL: https://jira.jboss.org/jira/browse/JBSEAM-4636 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.1.CR1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 2.2.1.CR2 ERROR: Option with value 'School' not found Stacktrace com.thoughtworks.selenium.SeleniumException: ERROR: Option with value 'School' not found at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.DefaultSelenium.select(DefaultSelenium.java:315) at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.editTask(SeleniumTasksTest.java:277) at org.jboss.seam.example.tasks.test.selenium.SeleniumTasksTest.editTurtleTask(SeleniumTasksTest.java:129) ... Removed 22 stack frames -- 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

14 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBSEAM-4666) QueueConnection.stop() can not be called from an EJB containrer as stated in JEE5 spec section EE 6.6

by Denis Forveille (JIRA)

QueueConnection.stop() can not be called from an EJB containrer as stated in JEE5 spec section EE 6.6 ----------------------------------------------------------------------------------------------------- Key: JBSEAM-4666 URL: https://jira.jboss.org/browse/JBSEAM-4666 Project: Seam Issue Type: Bug Components: Async Affects Versions: 2.2.1.CR1 Environment: WebSphere v7.0.0.9 Reporter: Denis Forveille Assignee: Denis Forveille Priority: Minor Fix For: 2.2.1.CR2 In WebSphere, when the application "shuts down", the method annotated by @Destroy is called on the QueueConnection seam component. This method raise an exception on the queueConnection.stop() call It is illegal to do so from an EJB container as specified in the JEE5 specs section EE 6.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4629) Disable default behaviour of auto-save for process instances

by Tihomir Surdilovic (JIRA)

Disable default behaviour of auto-save for process instances ------------------------------------------------------------ Key: JBSEAM-4629 URL: https://jira.jboss.org/jira/browse/JBSEAM-4629 Project: Seam Issue Type: Bug Affects Versions: 2.2.1.CR1 Reporter: Tihomir Surdilovic When injecting org.jboss.seam.bpm.ProcessInstance in a Seam components the code ends up in the following code snipped of this class: ******** if (processId!=null) { //TODO: do we need to cache this?? return ManagedJbpmContext.instance().getProcessInstanceForUpdate(processId); } ******** the org.jbpm.JbpmContext#getProcessInstanceForUpdate(processId) method will get a process instance from the db and will register it for auto-save. It will then be saved automatically at the close() . Continuous registering for auto-save can cause performance issues as when the jbpmContext closes it will save all instances in the autoSaveProcessInstances list which can be huge. The proposed fix is to change to the code to: if (processId!=null) { return ManagedJbpmContext.instance().getProcessInstance(processId); } -- 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

14 years, 5 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2974) <s:fileUpload> doesnt work inside <h:dataTable>

by Denis Forveille (JIRA)

<s:fileUpload> doesnt work inside <h:dataTable> ----------------------------------------------- Key: JBSEAM-2974 URL: http://jira.jboss.com/jira/browse/JBSEAM-2974 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR2 Reporter: Denis Forveille (see the forum entry in ref) -- 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

14 years, 5 months

4
9
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues August 2010