[JBoss JIRA] (JBIDE-13207) Inactive Deployment Scanner dialog has no context info and apply changes even if Ok not pressed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13207?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-13207:
--------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.0.x)
(was: 4.1.x)
> Inactive Deployment Scanner dialog has no context info and apply changes even if Ok not pressed
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13207
> URL: https://issues.jboss.org/browse/JBIDE-13207
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 4.1.0.Alpha2
>
>
> Create EAP 6.0 runtime server make sure it has a defaeult scanner interval of "0".
> Start EAP 6.0
> Wait N seconds/do other stuff.
> Up comes a dialog saying:
> Inactive Deployment Scanner?
> Warning: One or more deployments scanners have scan-interval of 0.
> These scanners are inactive. If this is intentional, press 'Ok'
> And then there is a table witha scanner name and then an editable scanner interval.
> 1) There is *zero* infon on what this relates to - I would have expected at least a reference to the name of the server there is a problem with.
> 2) The dialog says I should press Ok if i'm ok - but there is no cancel button or instructions on what I otherwise can do.
> 3) The title talks about "scan-interval" the table says "Scanner Interval"
> 4) When changing the value and then closing the dialog with the red button or escape -> changes made to the config xml file - BAD!
> Suggestion:
> Title: Inactive Deployment Scanner found
> subtitle: Inactive Deployment scanner found
> Text: 'servername' contains one or more deployment scanners that are currently inactive (scan-interval=0).
> This means their folds will not be scanned for new deployments nor changes. If this is intentional, presss 'Ok',
> or if you want a different interval (recommended is: <thedefaultnumber>s ) change it in the table below and then press 'Ok'.
> Table: show the actual location the scanner is related to - otherwise users have no idea/context what scanner it is.
> Ok
> and if user press Escape or closes dialog without pressing ok -> no changes made anywhere!
--
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
[JBoss JIRA] (JBIDE-13375) 6 test failures in org.jboss.tools.ws.creation.core.test.command.JBossWS*
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13375?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13375:
-------------------------------------------
Is this still failing?
> 6 test failures in org.jboss.tools.ws.creation.core.test.command.JBossWS*
> -------------------------------------------------------------------------
>
> Key: JBIDE-13375
> URL: https://issues.jboss.org/browse/JBIDE-13375
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.2.Final
> Reporter: Nick Boldt
> Assignee: Brian Fitzpatrick
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.component--ws/156/testReport/}
> Test Result
> 6 failures (+6) , 13 skipped (±0)
> 440 tests (±0)
> Took 42 min.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest.testDeployResult 1 min 46 sec 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult 20 min 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testInitialClientCommand 15 ms 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testClientCodeGenerationCommand 7 ms 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest.testRemoveClientJarsCommand 7 ms 1
> >>> org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest.testMergeWebXMLCommand 20 min 1{code}
--
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
[JBoss JIRA] (JBIDE-13545) Pressing Enter key should invoke WebService
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13545?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick resolved JBIDE-13545.
---------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.x)
Resolution: Out of Date
Functionality already exists.
> Pressing Enter key should invoke WebService
> --------------------------------------------
>
> Key: JBIDE-13545
> URL: https://issues.jboss.org/browse/JBIDE-13545
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Webservices
> Affects Versions: 4.1.0.Alpha1
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Alpha2
>
>
> It would be useful, if pressing Enter in URL text field of Web Service Tester invokes web service. Now if I am trying different values in url (e.g. matrix, query or path parameters) I have to click with mouse on invoke button placed on the right side of the view, which is little bit less user friendly
--
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
[JBoss JIRA] (JBIDE-13908) Runtime (jbosstools-base) build fails
by Snjezana Peco (JIRA)
Snjezana Peco created JBIDE-13908:
-------------------------------------
Summary: Runtime (jbosstools-base) build fails
Key: JBIDE-13908
URL: https://issues.jboss.org/browse/JBIDE-13908
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.1.0.Alpha1
Reporter: Snjezana Peco
Assignee: Snjezana Peco
The runtime build (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo..., for instance) sometimes fails with the following exception:
!ENTRY org.eclipse.osgi 4 0 2013-04-02 17:23:05.842
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4392)
at org.eclipse.swt.SWT.error(SWT.java:4307)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3692)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
at org.eclipse.swt.widgets.Display.release(Display.java:3392)
at org.eclipse.swt.graphics.Device.dispose(Device.java:248)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:140)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
Caused by: java.lang.NullPointerException
at org.jboss.tools.runtime.ui.RuntimeWorkbenchUtils$1.run(RuntimeWorkbenchUtils.java:20)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 21 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
13 years
[JBoss JIRA] (JBIDE-13844) JarAccess should ignore .class entries in jar files
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13844?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-13844:
-------------------------------------
Please provide steps how to verify this jira or verify and close it.
> JarAccess should ignore .class entries in jar files
> ---------------------------------------------------
>
> Key: JBIDE-13844
> URL: https://issues.jboss.org/browse/JBIDE-13844
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: respin-b
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> Memory problem were reported https://community.jboss.org/message/804026#804026
> JarAccess is used by internal model to optimize requests to jar files. It builds a map that binds parent folder path to its content. At present, maps include paths for all entries so that in a large workspace with 500-1000 jars memory consumed by these maps may add up to 70Mb. However, for a long time .class entries from JarAccess are not used directly for presentation in ui. Class selector based on it had been replaced by Eclipse's Class selector years ago. Builders in CDI and Seam get classes from JDT model. Open-ons work with JDT elements as well. Hence, if internal model has no more data on .class entries, it should not affect anything, while the profit is significant - memory consumed by maps in JarAccess may drop 5 to 10 times.
--
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
[JBoss JIRA] (JBIDE-13837) KB Builder does complete scanning of content of every jar file
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-13837:
-------------------------------------
Please provide steps how to verify this jira or verify and close it.
> KB Builder does complete scanning of content of every jar file
> ---------------------------------------------------------------
>
> Key: JBIDE-13837
> URL: https://issues.jboss.org/browse/JBIDE-13837
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: respin-b
> Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> Memory problem were reported https://community.jboss.org/message/804026#804026
> At present, KB builder scans for facelet taglibs everywhere in jar files, not only in META-INF folder. That results in complete loading of model objects for jar content, which otherwise would remain unloaded. Once loaded, it is not easy to release them, since objects are shared by projects referencing the same jar.
> Complete scanning was implemented as fix for https://issues.jboss.org/browse/JBIDE-5764 in February 2010.
> JSF implementation jsf-impl-2.0.1.jar contains facelet tag libraries in /com/sun/faces/metadata/taglib.
> However, it is recommended that facelet taglib xml files be packaged into META-INF folder. It seems that jsf-impl-2.0.1.jar is a special case. I suggest that we stop doing complete scanning of all jars and do it only for JSF 2 implementation jar.
--
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