April 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5081) Upgrade Hibernate Search version to latest final 4.2.0.Final

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5081?page=com.atlassian.jira.plugi... ] Marek Novotny reassigned JBSEAM-5081: ------------------------------------- Assignee: Marek Novotny > Upgrade Hibernate Search version to latest final 4.2.0.Final > ------------------------------------------------------------ > > Key: JBSEAM-5081 > URL: https://issues.jboss.org/browse/JBSEAM-5081 > Project: Seam 2 > Issue Type: Bug > Components: Build > Reporter: Marek Novotny > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > Update latest versions through org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final BOM -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5072) Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5072?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5072: ------------------------------------------------- Marek Novotny <mnovotny(a)redhat.com> made a comment on [bug 904174|https://bugzilla.redhat.com/show_bug.cgi?id=904174] Have you tried to use global JNDI instead? > Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context > -------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-5072 > URL: https://issues.jboss.org/browse/JBSEAM-5072 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.2.0.GA, 2.2.1.Final, 2.2.2.Final > Reporter: Luan Cestari > > Description of problem: > Issue with TCCL which is causing the Quartz thread to not have access to the application's "java:app" context. In other words, Seam can`t find the beans in context, even that they are there (due the annotations and logs that confirm that). > EAP 6`s documentation that gives the steps to migrate Seam 2 applications: https://access.redhat.com/knowledge/docs/en-US/JBoss_Enterprise_Applicati... > Version-Release number of selected component (if applicable): > Seam 2.2 in EAP 6 > How reproducible: > Just create a Seam and Quartz bean and another Seam and EJB bean that on Startup will lookup for Seam/Quartz bean, but can`t find it. > Actual results: > Can`t find the bean > Expected results: > Find the bean > Additional info: > salesforce link: https://c.na7.visual.force.com/apex/Case_View?id=500A000000CQzrg&sfdc.ove... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5088) Upgrade GWT version

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5088: ------------------------------------- Summary: Upgrade GWT version Key: JBSEAM-5088 URL: https://issues.jboss.org/browse/JBSEAM-5088 Project: Seam 2 Issue Type: Feature Request Components: GWT Affects Versions: 2.3.0.Final Reporter: Marek Schmidt Assignee: Marek Novotny GWT version should be upgraded to the latest one (2.5 at the time of writing) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5087) seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5087?page=com.atlassian.jira.plugi... ] Vaclav Dedik resolved JBSEAM-5087. ---------------------------------- Resolution: Done Fixed. > seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment > ------------------------------------------------------------------------------------------ > > Key: JBSEAM-5087 > URL: https://issues.jboss.org/browse/JBSEAM-5087 > Project: Seam 2 > Issue Type: Bug > Components: Hot Deploy > Affects Versions: 2.3.0.Final > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT (2013-01-17) > Reporter: Vaclav Dedik > Assignee: Vaclav Dedik > Fix For: 2.3.1.CR1 > > > seam-gen generated explode target contains: > {code} > <touch file="${deploy.dir}/${project.name}.ear.dodeploy"/> > {code} > which forces the application to restart, which makes the hot-deployment feature useless. > The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. > One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5087) seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5087?page=com.atlassian.jira.plugi... ] Vaclav Dedik updated JBSEAM-5087: --------------------------------- Description: seam-gen generated explode target contains: {code} <touch file="${deploy.dir}/${project.name}.ear.dodeploy"/> {code} which forces the application to restart, which makes the hot-deployment feature useless. The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. was: seam-gen generated explode target contains: {code} <touch file="${deploy.dir}/${project.name}.war.dodeploy"/> {code} which forces the application to restart, which makes the hot-deployment feature useless. The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. > seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment > ------------------------------------------------------------------------------------------ > > Key: JBSEAM-5087 > URL: https://issues.jboss.org/browse/JBSEAM-5087 > Project: Seam 2 > Issue Type: Bug > Components: Hot Deploy > Affects Versions: 2.3.0.Final > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT (2013-01-17) > Reporter: Vaclav Dedik > Assignee: Vaclav Dedik > Fix For: 2.3.1.CR1 > > > seam-gen generated explode target contains: > {code} > <touch file="${deploy.dir}/${project.name}.ear.dodeploy"/> > {code} > which forces the application to restart, which makes the hot-deployment feature useless. > The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. > One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5087) seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5087?page=com.atlassian.jira.plugi... ] Vaclav Dedik updated JBSEAM-5087: --------------------------------- Steps to Reproduce: 1. create a EAR project by seam-gen 2. ant explode 3. go to http://127.0.0.1:8080/myproject 4. login as "admin" with an empty password 5. refresh the page 6. run "ant explode" 7. wait 30 seconds 8. refresh the page, notice you are not logged in as admin anymore, as the application has restarted, which is wrong. was: 1. create a WAR project by seam-gen 2. ant explode 3. go to http://127.0.0.1:8080/myproject 4. login as "admin" with an empty password 5. refresh the page 6. run "ant explode" 7. wait 30 seconds 8. refresh the page, notice you are not logged in as admin anymore, as the application has restarted, which is wrong. > seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment > ------------------------------------------------------------------------------------------ > > Key: JBSEAM-5087 > URL: https://issues.jboss.org/browse/JBSEAM-5087 > Project: Seam 2 > Issue Type: Bug > Components: Hot Deploy > Affects Versions: 2.3.0.Final > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT (2013-01-17) > Reporter: Vaclav Dedik > Assignee: Vaclav Dedik > Fix For: 2.3.1.CR1 > > > seam-gen generated explode target contains: > {code} > <touch file="${deploy.dir}/${project.name}.war.dodeploy"/> > {code} > which forces the application to restart, which makes the hot-deployment feature useless. > The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. > One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5087) seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5087?page=com.atlassian.jira.plugi... ] Vaclav Dedik updated JBSEAM-5087: --------------------------------- Workaround Description: Remove the {code} <touch file="${deploy.dir}/${project.name}.ear.dodeploy"/> {code} line from the explode target in the build.xml was: Remove the {code} <touch file="${deploy.dir}/${project.name}.war.dodeploy"/> {code} line from the explode target in the build.xml > seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment > ------------------------------------------------------------------------------------------ > > Key: JBSEAM-5087 > URL: https://issues.jboss.org/browse/JBSEAM-5087 > Project: Seam 2 > Issue Type: Bug > Components: Hot Deploy > Affects Versions: 2.3.0.Final > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT (2013-01-17) > Reporter: Vaclav Dedik > Assignee: Vaclav Dedik > Fix For: 2.3.1.CR1 > > > seam-gen generated explode target contains: > {code} > <touch file="${deploy.dir}/${project.name}.war.dodeploy"/> > {code} > which forces the application to restart, which makes the hot-deployment feature useless. > The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. > One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5087) seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5087?page=com.atlassian.jira.plugi... ] Vaclav Dedik updated JBSEAM-5087: --------------------------------- Assignee: Vaclav Dedik (was: Marek Novotny) > seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment > ------------------------------------------------------------------------------------------ > > Key: JBSEAM-5087 > URL: https://issues.jboss.org/browse/JBSEAM-5087 > Project: Seam 2 > Issue Type: Bug > Components: Hot Deploy > Affects Versions: 2.3.0.Final > Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT (2013-01-17) > Reporter: Vaclav Dedik > Assignee: Vaclav Dedik > Fix For: 2.3.1.CR1 > > > seam-gen generated explode target contains: > {code} > <touch file="${deploy.dir}/${project.name}.war.dodeploy"/> > {code} > which forces the application to restart, which makes the hot-deployment feature useless. > The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. > One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5087) seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment

by Vaclav Dedik (JIRA)

Vaclav Dedik created JBSEAM-5087: ------------------------------------ Summary: seam-gen EAR explode target touches .dodeploy forcing a restart, preventing hot-deployment Key: JBSEAM-5087 URL: https://issues.jboss.org/browse/JBSEAM-5087 Project: Seam 2 Issue Type: Bug Components: Hot Deploy Affects Versions: 2.3.0.Final Environment: AS 7.1.1.Final, Seam 2.3.1-SNAPSHOT (2013-01-17) Reporter: Vaclav Dedik Assignee: Marek Novotny Fix For: 2.3.1.CR1 seam-gen generated explode target contains: {code} <touch file="${deploy.dir}/${project.name}.war.dodeploy"/> {code} which forces the application to restart, which makes the hot-deployment feature useless. The problem is that on AS7 at least one touch of the dodeploy is necessary, as it wouldn't deploy otherwise. One possible way to fix this could perhaps be to check for the existence of the .deployed file and touch the .dodeploy only if such file doesn't exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5086) localization settings via component.xml doesn't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5086?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBSEAM-5086: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=903177 > localization settings via component.xml doesn't work > ---------------------------------------------------- > > Key: JBSEAM-5086 > URL: https://issues.jboss.org/browse/JBSEAM-5086 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.3.0.Final > Reporter: Tomas Remes > Fix For: 2.3.1.CR1 > > > Adding following snippet to components.xml does not work as expected: > <inter:locale-config default-locale="cs" supported-locales="en cs"/> > And it produces following message in server log after application deployment: > "SEVERE [javax.faces] (MSC service thread 1-2) Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory. Attempting to find backup." > If you check class org.jboss.seam.international.LocaleConfig.java and its initLocaleConfig() method, then you'll notice that application variable resolves always to null in this case, therefore the locales are never set correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2013