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 reassigned JBIDE-15444: ----------------------------------- Assignee: Rob Stryker > 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-15398) CDI Builder is sloooow

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15398: -------------------------------- Description: After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min was: After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min -- 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-15398) CDI Builder is sloooow

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15398: ------------------------------------- The Maven Import wizard in m2e <=1.4 has a memory leak that retains ~350MB of memory during and after importing the WildFly codebase. This leak is fixed in m2e 1.5.0 (snapshots at http://nexus.tesla.io:8081/nexus/content/sites/m2e.extras/m2e/1.5.0/N/LAT...). This is the version I used to report this bug. I'm currently refactoring the m2e import process to make it much faster. > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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-15203) Error publishing html files to WildFly on Windows (WildFly locks deployed files)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15203?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15203: ----------------------------------- Assignee: Fred Bricon (was: Rob Stryker) Can you verify this was fixed? Seems the upstream issue was fixed. > Error publishing html files to WildFly on Windows (WildFly locks deployed files) > -------------------------------------------------------------------------------- > > Key: JBIDE-15203 > URL: https://issues.jboss.org/browse/JBIDE-15203 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.CR1 > Environment: Win 7 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.1.x > > > Created a simple maven web app, deployed onto a WildFly 8.0.0.Alpha2. The edited an index.html file and got > {noformat} > Error renaming D:\Dev\servers\wildfly-8.0.0.Alpha2\standalone\tmp\tmp8284536747609996823.html to D:\Dev\servers\wildfly-8.0.0.Alpha2\standalone\deployments\w.war\index.html. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {noformat} > Obviously the filesystem is identical. -- 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-12364) Cannot add a condition into "If" activity

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12364?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-12364. ------------------------------------- Verified with JBTIS 4.1.2 > Cannot add a condition into "If" activity > ----------------------------------------- > > Key: JBIDE-12364 > URL: https://issues.jboss.org/browse/JBIDE-12364 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 4.0.0.Alpha1 > Environment: Eclipse Juno EE > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Fix For: 4.0.0.Alpha1-SOA > > > Cannot add a condition into "If" activity. -- 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-12364) Cannot add a condition into "If" activity

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12364?page=com.atlassian.jira.plugi... ] Andrej Podhradsky resolved JBIDE-12364. --------------------------------------- Fix Version/s: 4.0.0.Alpha1-SOA (was: LATER) Resolution: Done This has been fixed in BPEL Editor 1.0.3 > Cannot add a condition into "If" activity > ----------------------------------------- > > Key: JBIDE-12364 > URL: https://issues.jboss.org/browse/JBIDE-12364 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 4.0.0.Alpha1 > Environment: Eclipse Juno EE > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Fix For: 4.0.0.Alpha1-SOA > > > Cannot add a condition into "If" activity. -- 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-11466) BPEL - deploy.xml editor blocked from WSDL generated by JBoss ESB

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11466?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-11466. ------------------------------------- Verified with JBTIS 4.1.2 > BPEL - deploy.xml editor blocked from WSDL generated by JBoss ESB > ----------------------------------------------------------------- > > Key: JBIDE-11466 > URL: https://issues.jboss.org/browse/JBIDE-11466 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel, esb > Affects Versions: 3.2.2.Final > Environment: JBoss Developer Studio 4.1.2 + JBoss SOA Platform 5.1.2 (default profile) > Reporter: Anonymous User > Assignee: Robert (Bob) Brodt > Priority: Blocker > Fix For: 3.3.0.CR1-SOA > > > BPEL deploy.xml editor blocked and error with generated ESB .wsdl files -- 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-8531) WSDL files should be accessible to BPEL project from another project (without copying)

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8531?page=com.atlassian.jira.plugin... ] Andrej Podhradsky closed JBIDE-8531. ------------------------------------ Verified with JBTIS 4.1.2 > WSDL files should be accessible to BPEL project from another project (without copying) > -------------------------------------------------------------------------------------- > > Key: JBIDE-8531 > URL: https://issues.jboss.org/browse/JBIDE-8531 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: bpel > Affects Versions: 3.2.0.CR1 > Environment: all > Reporter: Robert (Bob) Brodt > Assignee: Andrej Podhradsky > Fix For: 3.3.0.CR1-SOA, 4.0.0.Alpha1-SOA > > > SOA-P 5.2 PRD document requirement SOA-TOOL-2: > The SOA-5.2 PRD requirements include the ability of a BPEL project to reference WSDLs (and probably XSDs as well) in another project without having to make copies. The assumption is that all resources are in the same eclipse workspace, not in a file system folder or remote server. -- 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-11965) Cannot import a wsdl file generated by JBoss ESB into BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11965?page=com.atlassian.jira.plugi... ] Andrej Podhradsky resolved JBIDE-11965. --------------------------------------- Resolution: Done Maybe Bob forgot to set this issue as resolved because it is fixed in JBTIS 4.1.2 > Cannot import a wsdl file generated by JBoss ESB into BPEL project > ------------------------------------------------------------------ > > Key: JBIDE-11965 > URL: https://issues.jboss.org/browse/JBIDE-11965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.3.0.CR1-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0.Alpha1-SOA > > Attachments: helloworld.esb > > > Importing a wsdl file generated by JBoss ESB using 'Import' wizard throws the following error: > 'The WSDL file could not be imported.' > Note that it doesn't matter if we try to import the wsdl file from local or from the server. -- 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-11965) Cannot import a wsdl file generated by JBoss ESB into BPEL project

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11965?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-11965. ------------------------------------- Verified with JBTIS 4.1.2. > Cannot import a wsdl file generated by JBoss ESB into BPEL project > ------------------------------------------------------------------ > > Key: JBIDE-11965 > URL: https://issues.jboss.org/browse/JBIDE-11965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: bpel > Affects Versions: 3.3.0.CR1-SOA > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0.Alpha1-SOA > > Attachments: helloworld.esb > > > Importing a wsdl file generated by JBoss ESB using 'Import' wizard throws the following error: > 'The WSDL file could not be imported.' > Note that it doesn't matter if we try to import the wsdl file from local or from the server. -- 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