March 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5079) Ejb bean injection between multiple Ejb module

by Karoly Torok (JIRA)

Karoly Torok created JBSEAM-5079: ------------------------------------ Summary: Ejb bean injection between multiple Ejb module Key: JBSEAM-5079 URL: https://issues.jboss.org/browse/JBSEAM-5079 Project: Seam 2 Issue Type: Bug Components: EJB3 Affects Versions: 2.3.0.Final Environment: JBoss 7.1.1 Seam 2.3 Reporter: Karoly Torok Priority: Minor I'm trying to inject SLSB-s between multiple EJB module/project. These SLSBs are also Seam components (therefore they have both @Name and @Stateless annotation + @Local). The problem is that each time i want to inject a Bean from another project/module, Seam predicts that the component is under the module from where i inject. Consider the following: - MyEar.ear - MyEjb1.jar - MySLSB.class - MyEjb2.jar - MySeamComponent.class - MyWar.war Here i want to inject the MySLSB from the MySeamComponent. However they both belong to separate modules. Behind the curtain Seam predicts that the MySLSB is under the MyEjb2 module. Altough its not. I'm aware of that from JBoss v7 each beans are binded to a separate namespaces if they are belong to separate modules. Altough im not sure this is the default behaviour if the modules are not isolated (ear-subdeployments-isolated = false). Any suggestion is warmly welcome. -- 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, 2 months

1
0
0 / 0

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

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5068?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5068: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > seam-gen explode target touches .dodeploy forcing a restart, preventing hot-deployment > -------------------------------------------------------------------------------------- > > Key: JBSEAM-5068 > URL: https://issues.jboss.org/browse/JBSEAM-5068 > 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: Marek Schmidt > 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, 2 months

1
0
0 / 0

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

by Vaclav Dedik (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5068?page=com.atlassian.jira.plugi... ] Vaclav Dedik updated JBSEAM-5068: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/seam2/jboss-seam/pull/15 > seam-gen explode target touches .dodeploy forcing a restart, preventing hot-deployment > -------------------------------------------------------------------------------------- > > Key: JBSEAM-5068 > URL: https://issues.jboss.org/browse/JBSEAM-5068 > 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: Marek Schmidt > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (SEAMPERSIST-28) Create an example demonstrating EL in EJB-QL/HQL

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/SEAMPERSIST-28?page=com.atlassian.jira.pl... ] Tomas Remes updated SEAMPERSIST-28: ----------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Out of Date > Create an example demonstrating EL in EJB-QL/HQL > ------------------------------------------------- > > Key: SEAMPERSIST-28 > URL: https://issues.jboss.org/browse/SEAMPERSIST-28 > Project: Seam Persistence > Issue Type: Task > Reporter: Ondrej Skutka > Assignee: Tomas Remes > > Or you can modify an existing example. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-5064: --------------------------------------- just note that after JBSEAM-5073 fix double addition of conversation id in case of propagation="join" is fixed too. so outstanding issue is: "s:link / s:button with propagation="none" does propagate conversations even when it shouldn't" > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5064: ---------------------------------- Comment: was deleted (was: A comment with security level 'JBoss Employee' was removed.) > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5064: ---------------------------------- Comment: was deleted (was: Tomas Remes <tremes(a)redhat.com> made a comment on [bug 905033|https://bugzilla.redhat.com/show_bug.cgi?id=905033] s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler)) > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5064: ---------------------------------- Comment: was deleted (was: Tomas Remes <tremes(a)redhat.com> made a comment on [bug 905033|https://bugzilla.redhat.com/show_bug.cgi?id=905033] Clone of JBSEAM-5064) > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5064: ---------------------------------- Comment: was deleted (was: Marek Novotny <mnovotny(a)redhat.com> changed the Status of [bug 905033|https://bugzilla.redhat.com/show_bug.cgi?id=905033] from NEW to ASSIGNED) > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated JBSEAM-5064: -------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=905033) > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- 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, 2 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 March 2013