March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13596) Test generated for new Seam action or form contains errors

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13596?page=com.atlassian.jira.plugi... ] Tomas Remes updated JBIDE-13596: -------------------------------- Affects Version/s: 4.0.1.Final > Test generated for new Seam action or form contains errors > ---------------------------------------------------------- > > Key: JBIDE-13596 > URL: https://issues.jboss.org/browse/JBIDE-13596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.0.0.Final, 4.0.1.Final > Environment: JBDS 6.0.0.GA, Seam 2.3.1.Final > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha2 > > > Even there is not option how to create test for new Seam action and form in "New Seam Web project wizard", there is following option, how you can create this test, which is then not valid at all: > 1. New -> Seam Action > 2. Click on the settings link in the dialog > 3. Mark checkbox "Create test" > This should be either disabled or you can use seam-gen ant solution and fetch test libraries from Seam runtime. > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13596) Test generated for new Seam action or form contains errors

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13596?page=com.atlassian.jira.plugi... ] Tomas Remes commented on JBIDE-13596: ------------------------------------- So this is not going to be fixed in JBDS 6.0.1 release am I right?? Because this is still problem in JBDS 6.0.1.CR1. When I import Seam2.3 project generated by seam-gen and create new Seam action or form, then I also get not valid test for this component. > Test generated for new Seam action or form contains errors > ---------------------------------------------------------- > > Key: JBIDE-13596 > URL: https://issues.jboss.org/browse/JBIDE-13596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.0.0.Final > Environment: JBDS 6.0.0.GA, Seam 2.3.1.Final > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha2 > > > Even there is not option how to create test for new Seam action and form in "New Seam Web project wizard", there is following option, how you can create this test, which is then not valid at all: > 1. New -> Seam Action > 2. Click on the settings link in the dialog > 3. Mark checkbox "Create test" > This should be either disabled or you can use seam-gen ant solution and fetch test libraries from Seam runtime. > -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13875) Incorrect Module status when starting server/module

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13875?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13875: -------------------------------- Description: Create and deploy a webapp on an *stopped* AS or EAP server. * When the app server is started, the webapp module appears as "stopped", even though it's started. * When the server is restarted, The module just says "synchronized" * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. was: Create and deploy a webapp on an AS or EAP *stopped* server. * When the app server is started, the webapp module appears as "stopped", even though it's started. * When the server is restarted, The module just says "synchronized" * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. > Incorrect Module status when starting server/module > --------------------------------------------------- > > Key: JBIDE-13875 > URL: https://issues.jboss.org/browse/JBIDE-13875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Create and deploy a webapp on an *stopped* AS or EAP server. > * When the app server is started, the webapp module appears as "stopped", even though it's started. > * When the server is restarted, The module just says "synchronized" > * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13875) Incorrect Module status when starting server/module

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13875?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13875: -------------------------------- Description: Create and deploy a webapp on an AS or EAP *stopped* server. * When the app server is started, the webapp module appears as "stopped", even though it's started. * When the server is restarted, The module just says "synchronized" * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. was: Create and deploy a webapp on an AS or EAP server. * When the app server is started, the webapp module appears as "stopped", even though it's started. * When the server is restarted, The module just says "synchronized" * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. > Incorrect Module status when starting server/module > --------------------------------------------------- > > Key: JBIDE-13875 > URL: https://issues.jboss.org/browse/JBIDE-13875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Create and deploy a webapp on an AS or EAP *stopped* server. > * When the app server is started, the webapp module appears as "stopped", even though it's started. > * When the server is restarted, The module just says "synchronized" > * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13875) Incorrect Module status when starting server/module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13875?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13875: ------------------------------------- I've committed a fix for 'start' or 'restart' on the module. It seems we set the state to started, waited for the server to respond the module was up, but then we didnt set the state after that. For responding to a server 'restart', the work may be more, and I have to dig deeper. > Incorrect Module status when starting server/module > --------------------------------------------------- > > Key: JBIDE-13875 > URL: https://issues.jboss.org/browse/JBIDE-13875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Create and deploy a webapp on an AS or EAP server. > * When the app server is started, the webapp module appears as "stopped", even though it's started. > * When the server is restarted, The module just says "synchronized" > * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13875) Incorrect Module status when starting server/module

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13875?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13875: -------------------------------- Priority: Minor (was: Major) > Incorrect Module status when starting server/module > --------------------------------------------------- > > Key: JBIDE-13875 > URL: https://issues.jboss.org/browse/JBIDE-13875 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > Create and deploy a webapp on an AS or EAP server. > * When the app server is started, the webapp module appears as "stopped", even though it's started. > * When the server is restarted, The module just says "synchronized" > * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13875) Incorrect Module status when starting server/module

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-13875: ----------------------------------- Summary: Incorrect Module status when starting server/module Key: JBIDE-13875 URL: https://issues.jboss.org/browse/JBIDE-13875 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 4.1.0.Alpha1 Reporter: Fred Bricon Assignee: Rob Stryker Fix For: 4.1.0.Alpha2 Create and deploy a webapp on an AS or EAP server. * When the app server is started, the webapp module appears as "stopped", even though it's started. * When the server is restarted, The module just says "synchronized" * When one click "start" on the webapp module, its state stays in "starting" mode, even though the app is done starting. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13868) Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-13868: ----------------------------------- Assignee: Max Rydahl Andersen (was: Rob Stryker) Hey max... here's a PR for review. Not sure on maintenance status. > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.x > > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13868) Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13868: -------------------------------- Issue Type: Bug (was: Feature Request) > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13868) Project Archives incorrectly loading saved .packages

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13868?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13868: -------------------------------- Priority: Critical (was: Major) > Project Archives incorrectly loading saved .packages > ---------------------------------------------------- > > Key: JBIDE-13868 > URL: https://issues.jboss.org/browse/JBIDE-13868 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 4.0.0.Final > Environment: Eclipse juno 32 bit > Reporter: Rafael Sisto > Assignee: Rob Stryker > Priority: Critical > Attachments: .packages, loaded packages.png > > > After creating a project archive from the Project Archives window, consisting of a war file, a jar file and EarContent folder it creates the ear successfully. > After restarting eclipse (or closing and opening the project) the Project Archive does not load the jar and war archives, only the EarContent fileset. > Testing a little further, adding only a jar archive and a fileset works, but when adding the second jar (war in this case), the project archives loads only the fileset, discarding both jars. -- 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

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013