September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15444) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15444?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-15444. ------------------------------- > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Server] > ----------------------------------------------------- > > Key: JBIDE-15444 > URL: https://issues.jboss.org/browse/JBIDE-15444 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Server] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15444) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15444?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15444. --------------------------------- Resolution: Done > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Server] > ----------------------------------------------------- > > Key: JBIDE-15444 > URL: https://issues.jboss.org/browse/JBIDE-15444 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Server] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11964) Wrong name of the imported WSDL into BPEL project using 'Import' wizard

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11964?page=com.atlassian.jira.plugi... ] Andrej Podhradsky edited comment on JBIDE-11964 at 9/6/13 5:38 AM: ------------------------------------------------------------------- Maybe Bob forgot to set this issue as resolved, but this is already fixed was (Author: apodhrad): Maybe Bob forgot to set this assie as resolved, but this is already fixed > Wrong name of the imported WSDL into BPEL project using 'Import' wizard > ----------------------------------------------------------------------- > > Key: JBIDE-11964 > URL: https://issues.jboss.org/browse/JBIDE-11964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.3.0.CR1-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Minor > Fix For: 4.0.0.Alpha1-SOA > > > The name of the imported wsdl file is 'wsdl'. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11964) Wrong name of the imported WSDL into BPEL project using 'Import' wizard

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11964?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-11964. ------------------------------------- Verified with JBTIS 4.1.2 > Wrong name of the imported WSDL into BPEL project using 'Import' wizard > ----------------------------------------------------------------------- > > Key: JBIDE-11964 > URL: https://issues.jboss.org/browse/JBIDE-11964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.3.0.CR1-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Minor > Fix For: 4.0.0.Alpha1-SOA > > > The name of the imported wsdl file is 'wsdl'. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11964) Wrong name of the imported WSDL into BPEL project using 'Import' wizard

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11964?page=com.atlassian.jira.plugi... ] Andrej Podhradsky resolved JBIDE-11964. --------------------------------------- Resolution: Done Maybe Bob forgot to set this assie as resolved, but this is already fixed > Wrong name of the imported WSDL into BPEL project using 'Import' wizard > ----------------------------------------------------------------------- > > Key: JBIDE-11964 > URL: https://issues.jboss.org/browse/JBIDE-11964 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.3.0.CR1-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Minor > Fix For: 4.0.0.Alpha1-SOA > > > The name of the imported wsdl file is 'wsdl'. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-166: ----------------------------------------- I think that by installing BPEL feature also AS feature should be installed. > Deploying BPEL project to a server is not working > ------------------------------------------------- > > Key: JBTIS-166 > URL: https://issues.jboss.org/browse/JBTIS-166 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 4.1.2 > Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Attachments: deploying_as51.log, deploying_as51.png, running_as51.log, running_as51.png > > > This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? > Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. > You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). > Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). > See the attachments. > Original description: > Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. > But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. > In JBDS 4 and 5 it works fine for both adapters. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-166: ------------------------------------ Attachment: running_as51.log deploying_as51.log running_as51.png deploying_as51.png > Deploying BPEL project to a server is not working > ------------------------------------------------- > > Key: JBTIS-166 > URL: https://issues.jboss.org/browse/JBTIS-166 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 4.1.2 > Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Attachments: deploying_as51.log, deploying_as51.png, running_as51.log, running_as51.png > > > This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? > Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. > You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). > Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). > See the attachments. > Original description: > Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. > But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. > In JBDS 4 and 5 it works fine for both adapters. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-166: ------------------------------------ Description: This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). See the attachments. Original description: Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. In JBDS 4 and 5 it works fine for both adapters. was: This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. You need to install JBoss AS feature from JBT Core update site. Original description: Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. In JBDS 4 and 5 it works fine for both adapters. > Deploying BPEL project to a server is not working > ------------------------------------------------- > > Key: JBTIS-166 > URL: https://issues.jboss.org/browse/JBTIS-166 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 4.1.2 > Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > > This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? > Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. > You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). > Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). > See the attachments. > Original description: > Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. > But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. > In JBDS 4 and 5 it works fine for both adapters. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-166: ------------------------------------ Description: This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. You need to install JBoss AS feature from JBT Core update site. Original description: Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. In JBDS 4 and 5 it works fine for both adapters. was: Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. In JBDS 4 and 5 it works fine for both adapters. > Deploying BPEL project to a server is not working > ------------------------------------------------- > > Key: JBTIS-166 > URL: https://issues.jboss.org/browse/JBTIS-166 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 4.1.2 > Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > > This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? > Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. > You need to install JBoss AS feature from JBT Core update site. > Original description: > Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. > But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. > In JBDS 4 and 5 it works fine for both adapters. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-6010) Tooling Support for Byteman Rule Injection

by Masao Kunii (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6010?page=com.atlassian.jira.plugin... ] Masao Kunii commented on JBIDE-6010: ------------------------------------ We have similar concept plugin and would like to contribute it. How can I do? Our tool has: - Byteman rule editor which has basic editor functions such as code completion, syntax highlight, jump, etc - Agent view to show Byteman agents and rules applied to the agents - Install rules via Byteman agents in the agent view It does't have debugger like #3. > Tooling Support for Byteman Rule Injection > ------------------------------------------ > > Key: JBIDE-6010 > URL: https://issues.jboss.org/browse/JBIDE-6010 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: z - Legacy - integration > Reporter: Andrew Dinn > Labels: integration > Fix For: LATER > > > It would be nice to have support for Byteman in these areas: > 1) editor support for creation and modification of Byteman rule files > 2) debugger support for detection of successful or ailed rule injection at runtime > 3) debugger support for stepping through injected rule code > the byteman agent already runs a listener which provides the info required for ii. -- 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

12 years, 7 months

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 September 2013