[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15887:
------------------------------------------
I switched back in time up to Alpha1 and even before. Still the same: very sluggish.
But weird enough, when running JBDS7.1.Beta1b I see it very responsive: [^openshift-jbds71Beta1b.ogv]
> Application wizard: typing application name is delayed, sluggish, poor responsiveness
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-15887
> URL: https://issues.jboss.org/browse/JBIDE-15887
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: openshift-jbds7-ga.ogv, openshift-jbds71Beta1b.ogv, openshift.ogv
>
>
> If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner.
--
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, 5 months
[JBoss JIRA] (JBDS-2802) Investigate use of SpringIDE 3.4 in JBT/JBDS Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2802?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on JBDS-2802 at 11/6/13 5:13 PM:
------------------------------------------------------------
JBDS-2690, JBDS-2691 are identical in nature, predate Spring IDE 2.4 (upstream bug : https://issuetracker.springsource.com/browse/STS-3602) and can be worked around
JBDS-2719 (upstream bug https://jira.springsource.org/browse/IDE-1312) is caused by the missing org.springframework.ide.eclipse.ajdt.feature
So, given the nature of these bugs, none is a regression, I propose we proceed with Spring IDE 3.4 (+org.springframework.ide.eclipse.ajdt.feature)
was (Author: fbricon):
JBDS-2690, JBDS-2691 are identical in nature, predate Spring IDE 2.4 and can be worked around
JBDS-2719 is caused by the missing org.springframework.ide.eclipse.ajdt.feature
So, given the nature of these bugs, none is a regression, I propose we proceed with Spring IDE 3.4 (+org.springframework.ide.eclipse.ajdt.feature)
> Investigate use of SpringIDE 3.4 in JBT/JBDS Central
> ----------------------------------------------------
>
> Key: JBDS-2802
> URL: https://issues.jboss.org/browse/JBDS-2802
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Affects Versions: 7.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Marián Labuda
>
> New mirror for SpringIDE 3.4.0.201310051539-RELEASE:
> http://download.jboss.org/jbosstools/updates/requirements/springide/3.4.0...
--
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, 5 months
[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15887:
----------------------------------------
Summary: Application wizard: typing application name is delayed, sluggish, poor responsiveness
Key: JBIDE-15887
URL: https://issues.jboss.org/browse/JBIDE-15887
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.1.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.1.CR1
If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner.
--
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, 5 months
[JBoss JIRA] (JBDS-2690) Internal problem when spring project from jboss central is used
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2690?page=com.atlassian.jira.plugin.... ]
Fred Bricon edited comment on JBDS-2690 at 11/6/13 5:04 PM:
------------------------------------------------------------
This issue and its workarounds are similar to JBDS-2691.
In order to fix this issue, we need an updated spring archetype version. See WFK2-222
was (Author: fbricon):
In order to fix this issue, we need an updated spring archetype version. See WFK2-222
> Internal problem when spring project from jboss central is used
> ---------------------------------------------------------------
>
> Key: JBDS-2690
> URL: https://issues.jboss.org/browse/JBDS-2690
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-dependencies, upstream
> Affects Versions: 7.0.0.CR1
> Environment: JBDS 7.0.0.CR1a, L64
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.x, 8.0.x
>
>
> I have this error when Spring 3.2 or Spring 3.3 is installed:
> {code}
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2521)
> at java.lang.Class.getDeclaredMethods(Class.java:1845)
> at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:159)
> at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:106)
> at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:257)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:73)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:748)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:741)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:625)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:584)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:450)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 23 more
> {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
12 years, 5 months