[JBoss JIRA] (JBIDE-19192) provide option for disable html preview
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19192?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19192:
-----------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-19192 (was: JBDS-3340)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Component/s: visual-page-editor-core
(was: visual-page-editor-core)
Docs QE Status: (was: NEW)
> provide option for disable html preview
> ---------------------------------------
>
> Key: JBIDE-19192
> URL: https://issues.jboss.org/browse/JBIDE-19192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.2.Final
> Environment: win8.1 64 eclipse luna 4.4.0 jboss 4.2.2
> Reporter: jim harber
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Attachments: Clipboard01.png
>
>
> when i use tween.js to create a html page,i create an array,here is the problem:
> var eles = [];
> //push such as 500 elements into eles;
> ..
> then i need call a function to update every element in eles,when these two line:
> requestAnimationFrame(animate);
> TWEEN.update();
> already in the function,i can't see a change in preview and it makes eclipse shutdown,so i put this two line when i finish the other codes,this time preview become normal.
> every time when i type to for(var i=0;i<eles.length;i) eclipse gets stuck. so i wonder is thers any chance i can shutdown living view,i checked preferences panel i didn't find anything.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19153) Unable to use hibernate console when DTD is not accessible (hibernate.org down)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19153?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19153:
-----------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Alpha1)
(was: 4.2.3.Beta1)
> Unable to use hibernate console when DTD is not accessible (hibernate.org down)
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19153
> URL: https://issues.jboss.org/browse/JBIDE-19153
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Final
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Fix For: 4.3.x
>
>
> Inaccessible DTD causes blocking Hibernate Console usage (as DTD cannot be loaded)
> If DTD is not accessible It would be more useful to disable DTD validation rather than block further usage and just show some warning.
> {code}
> org.hibernate.HibernateException: Could not parse configuration: C:\Users\jpeterka\workspace\tmp\hb\mvn-hibernate35\src\main\java\hibernate.cfg.xml
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1586)
> at org.hibernate.cfg.Configuration.configure(Configuration.java:1554)
> at org.jboss.tools.hibernate.proxy.ConfigurationProxy.configure(ConfigurationProxy.java:94)
> at org.hibernate.console.ConfigurationFactory.loadConfigurationXML(ConfigurationFactory.java:350)
> at org.hibernate.console.ConfigurationFactory.configureStandardConfiguration(ConfigurationFactory.java:278)
> at org.hibernate.console.ConfigurationFactory.buildConfiguration(ConfigurationFactory.java:175)
> at org.hibernate.console.ConfigurationFactory.createConfiguration(ConfigurationFactory.java:97)
> at org.hibernate.eclipse.console.common.HibernateExtension$5.execute(HibernateExtension.java:166)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189)
> at org.hibernate.eclipse.console.common.HibernateExtension.buildWith(HibernateExtension.java:163)
> at org.hibernate.eclipse.console.common.HibernateExtension.build(HibernateExtension.java:134)
> at org.hibernate.console.ConsoleConfiguration.build(ConsoleConfiguration.java:189)
> at org.hibernate.eclipse.console.workbench.ConsoleConfigurationWorkbenchAdapter.getChildren(ConsoleConfigurationWorkbenchAdapter.java:43)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:98)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:233)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.dom4j.DocumentException: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd Nested exception: Server returned HTTP response code: 503 for URL: http://hibernate.org/dtd/hibernate-configuration-3.0.dtd
> at org.dom4j.io.SAXReader.read(SAXReader.java:484)
> at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1576)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19184) Threadlock when JS autocomplete turned on
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19184?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-19184:
---------------------------------------
Should be possible to replicate in debug mode, just set breakpoint according hover thread stacktrace. Request for doc hover. Let it stay on that breakpoint (UI should no be blocked, because it is a different thread) and request for content assist. It should stack on the same line of code.
It is probably, Tern problem processing request for huge projects.
BTW would be good to see if there are any errors on node.js side.
> Threadlock when JS autocomplete turned on
> -----------------------------------------
>
> Key: JBIDE-19184
> URL: https://issues.jboss.org/browse/JBIDE-19184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.2.Final
> Environment: JBDS 8.0.2
> Reporter: Mustafa Musaji
> Assignee: Victor Rubezhny
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
> Attachments: threaddump_jdk1.7.0_71_1422011702000.txt
>
>
> Seeing a thread lock when using large JS projects when trying to autocomplete. Please refer to attached thread dump.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19191) Make v3 explorer style labels consistent and useful
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19191:
-------------------------------------
Summary: Make v3 explorer style labels consistent and useful
Key: JBIDE-19191
URL: https://issues.jboss.org/browse/JBIDE-19191
Project: Tools (JBoss Tools)
Issue Type: Task
Components: openshift
Affects Versions: 4.3.0.Alpha1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Make styling consistent by removing parens where needed and modifying such that one could logically determine how to "walk" from one resource to another where it makes sense (i.e. service selector to pod)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months