December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16021) Revisit whether file transfer requests can trust rse's isConnected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16021?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16021: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Revisit whether file transfer requests can trust rse's isConnected > ------------------------------------------------------------------- > > Key: JBIDE-16021 > URL: https://issues.jboss.org/browse/JBIDE-16021 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server, upstream > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > With the large speed increases in jbt's RSE integration, the new bottleneck is during the beginning of the publish event. > A block of code currently exists as follows: > {code} > boolean isConnected = fileSubSystem != null && fileSubSystem.isConnected(); > String connectionName = RSEUtils.getRSEConnectionName(behaviour.getServer()); > if( isConnected ) { > // The RSE tools might be mistaken here. The user may in fact have lost internet connectivity > NamedRunnableWithProgress run = new NamedRunnableWithProgress("Accessing Remote System Root") { > public Object run(IProgressMonitor monitor) throws CoreException, > SystemMessageException, RuntimeException { > getFileService().getRoots(monitor); > return Status.OK_STATUS; > } > }; > IProgressMonitor childMonitor = AbstractServerToolsPublisher.getSubMon(monitor, 100); > Exception e = RSERemotePublishHandler.wrapRemoteCallStatusTimeLimit(run, "null", "null", null, 15000, childMonitor); > {code} > It would seem strange for the rse's isConnected() method to be incorrect. Investigate whether it is still possible it is incorrect, and file an appropriate upstream bug, or, if no bug, simply remove the lines and improve speed. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-7515: ------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15917) Creation of subsystem framework

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15917?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15917: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Creation of subsystem framework > ------------------------------- > > Key: JBIDE-15917 > URL: https://issues.jboss.org/browse/JBIDE-15917 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > ASTools has a requirement for mixin-style behavior. The current similar API is called the BehaviorModel, however it does not allow for mixin-style behavior. The server can be in only 1 mode at any time, and so therefore can have only 1 set of systems at any time, and there are currently only 2 sets: a local set, and an rse set. > The contents of these sets change based on server version, so for example, AS 6 in 'rse' mode may stop with a java command to the shutdown jar launched over a remote shell, while Wildfly 8 will shutdown with a call to management. > A model needs to be created to resolve and load arbitrary systems, even those not declared by ASTools directly, or allow alternate implementations of the common systems for server types such as OpenShift or Teiid Designer. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14073) add remote deployment feature as EAP6 CLI does to JBDS.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14073?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14073: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > add remote deployment feature as EAP6 CLI does to JBDS. > ------------------------------------------------------- > > Key: JBIDE-14073 > URL: https://issues.jboss.org/browse/JBIDE-14073 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Gary Hu > Assignee: Rob Stryker > Labels: UHG > Fix For: 4.2.0.Alpha2 > > > EAP6 CLI provides feature to do remote deployment: > bin/jboss-cli.sh --connect --controller="127.0.0.1:9999" --command="deploy ../tmp/sample.war" --user="User" > Is it possible to have such feature available in JBDS? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15922) Convert Module Path calculator to subsystem framework

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15922?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15922: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Convert Module Path calculator to subsystem framework > ----------------------------------------------------- > > Key: JBIDE-15922 > URL: https://issues.jboss.org/browse/JBIDE-15922 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > As an example of the new subsystem framework, and as a critical dependency of the publishing framework, this API should be converted and heavily tested to ensure it works for all local and remote possible usecases. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14001) First restart of JBDS/App Server results in deployed archive being deleted from deploy directory.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14001?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14001: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > First restart of JBDS/App Server results in deployed archive being deleted from deploy directory. > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14001 > URL: https://issues.jboss.org/browse/JBIDE-14001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.0.1.Final > Environment: Windows 7 > Reporter: David Stephan > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > After Marking a jar as deployable and deploying to EAP server, the jar is deployed correctly. > Then, after restarting JBDS, then restarting the app server from within JBDS, the deployed jar is deleted. > After restarting the server again, the jar is deployed, and subsequent restarts don't remove the jar. > Possibly related, when you first mark the jar as deployable and deploy to a server, the context menu item changes to "Unmark as Deployable." After a restart of JBDS, this context menu item is back to "Mark as Deployable". -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14119) look at how to handle the different jmx views/perspectives between AS and FuseSource plugins

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14119?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-14119: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > look at how to handle the different jmx views/perspectives between AS and FuseSource plugins > -------------------------------------------------------------------------------------------- > > Key: JBIDE-14119 > URL: https://issues.jboss.org/browse/JBIDE-14119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > Talk with [~lhein] he knows more -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15916) Bump ASTools version to 3.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15916?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15916: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Bump ASTools version to 3.0 > --------------------------- > > Key: JBIDE-15916 > URL: https://issues.jboss.org/browse/JBIDE-15916 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > Since the planned changes are very large, a major version bump is required. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15915) Large-scale refactor to split major functionality into clear systems with public API

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15915?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15915: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Large-scale refactor to split major functionality into clear systems with public API > ------------------------------------------------------------------------------------ > > Key: JBIDE-15915 > URL: https://issues.jboss.org/browse/JBIDE-15915 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > ASTools currently suffers from tight coupling, mixing of API and non-API classes, an API that is not clear, a very long unit test run, and other symptoms which stem from the above problems. Several newer use-cases are impossible to solve without making the problem worse. > To solve these issues, ASTools needs to have its major functionality split up and separated. The API for each system needs to be clearly apparent and easy to use, from both core, ui, and other consumers. In general, if UI classes are not using the API and are reaching in to internal classes, then the API is insufficient and needs to be cleaned up. > This large-scale refactor will focus first on the deploy-only server as an example and can eventually be (easily) extended to the other server types. > https://community.jboss.org/wiki/JBossTools-DelegatingServersViaSubsystems -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15938) Convert getting and setting of server's primary deploy settings to subsystem

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15938?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15938: -------------------------------- Assignee: Rob Stryker Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Convert getting and setting of server's primary deploy settings to subsystem > ---------------------------------------------------------------------------- > > Key: JBIDE-15938 > URL: https://issues.jboss.org/browse/JBIDE-15938 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > -- 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, 4 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 December 2013