[JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18094:
-------------------------------------
I've merged this in, because I want to get QE used to testing with it and see their feedback. I'll do a fuller writeup tomorrow.
> Do not force restart modules when server is run in debug mode
> -------------------------------------------------------------
>
> Key: JBIDE-18094
> URL: https://issues.jboss.org/browse/JBIDE-18094
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Rob Stryker
> Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.png, serversetting.bmml, serversetting.png, update_dialog_based_on_existing_hcr.bmml, update_dialog_based_on_existing_hcr.png
>
>
> The request is that modules should not force-restart when a server is in debug mode. More often than not, a change to a .class file, when the server is in debug mode, does not require any special action or force-restart of the module. The changes to the .class file will be picked up automatically.
> Ideally, we would also detect a hotcode replace failure, and then force-restart the module if possible.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2720:
--------------------------------------------
Thanks for the feedback [~mkalkov] - i'm interested to hear if you are looking at VPE visual editor for JSF work or HTML ? if "just" html is the html preview doing enough for your ?
asking since we are hitting limits of xulrunner not working on newer versions of linux and considering phasing it out. Just wanted to hear which parts of the VPE you are mainly using.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Mikhail Kalkov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Mikhail Kalkov commented on JBIDE-2720:
---------------------------------------
I'm running JBoss Developer Studio 8.0.0.Beta3 with OracleJDK 7u67 windows x64 on fully patched Windows 7 Professional 64-bit. After installing the XulRunner Feature from http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr... and restarting Eclipse, VPE and BrowserSim seem to work smoothly apart from one "out of handles" error. I've also got some errors when trying to add VPE commands to the toolbar, but this is not critical. Besides that I had to manually enable BrowserSim command group in perspective customization in order to get BrowserSim icon. Finally, I've installed Oracle jdk-8u20-windows-x64, told BrowserSim to use it and was able to enjoy LiveReload. I'm happy as a clam! Thanks a lot!
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-9179) Bad behaviour of the JAX-RS Capabilities popup
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9179?page=com.atlassian.jira.plugin... ]
Xavier Coulon updated JBIDE-9179:
---------------------------------
Fix Version/s: 4.2.1.Final
4.3.0.Alpha1
(was: 4.2.0.CR1)
> Bad behaviour of the JAX-RS Capabilities popup
> -----------------------------------------------
>
> Key: JBIDE-9179
> URL: https://issues.jboss.org/browse/JBIDE-9179
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 3.3.0.M1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: JAX-RS, upstream
> Fix For: 4.2.1.Final, 4.3.0.Alpha1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When setting the JAX-RS Facet on a dynamic web project, a popup window requires to choose the JAX-RS implementation library for the project, and optionally to specify the servlet class name to update the web.xml deployment descriptor accordingly. When choosing 'Disable library configuration' or 'Pure JEE6 implementation', the 'Servlet Information' panel is not disabled as expected. This is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=338898
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 9 months
[JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18094:
---------------------------------------------
Suggestion on how to make clear when what is active.
> Do not force restart modules when server is run in debug mode
> -------------------------------------------------------------
>
> Key: JBIDE-18094
> URL: https://issues.jboss.org/browse/JBIDE-18094
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Rob Stryker
> Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.png, serversetting.bmml, serversetting.png
>
>
> The request is that modules should not force-restart when a server is in debug mode. More often than not, a change to a .class file, when the server is in debug mode, does not require any special action or force-restart of the module. The changes to the .class file will be picked up automatically.
> Ideally, we would also detect a hotcode replace failure, and then force-restart the module if possible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17836) Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
by Lucia Jelinkova (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17836?page=com.atlassian.jira.plugi... ]
Lucia Jelinkova commented on JBIDE-17836:
-----------------------------------------
Yes, I get the error always but the maven artefact in error log can be different.
> Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17836
> URL: https://issues.jboss.org/browse/JBIDE-17836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
> Attachments: screencast.ogv
>
>
> When I have JBOSS_AS_REMOTE_7.X profile selected in the launch configuration and I deselect it and select some other profile, the following error is logged in error log:
> {code}
> /home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist
> Java Model Exception: Java Model Status [/home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getUnderlyingResource(JarPackageFragmentRoot.java:215)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder_(PackageFragmentRootTools.java:82)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder(PackageFragmentRootTools.java:74)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:65)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:80)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.next(FilteringIterator.java:68)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath_(SimpleJavaResourceLocator.java:144)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath(SimpleJavaResourceLocator.java:135)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.MavenResourceLocator.getWorkspacePath(MavenResourceLocator.java:137)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.getPersistenceXml(JpaProjectConfigurator.java:119)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:92)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:304)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:286)
> at org.eclipse.m2e.profiles.core.internal.management.ProfileManager.updateActiveProfiles(ProfileManager.java:87)
> at org.eclipse.m2e.profiles.ui.internal.actions.ProfileSelectionHandler$UpdateProfilesJob.runInWorkspace(ProfileSelectionHandler.java:319)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-8874) Support XML documents for XSLT compliant browser
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8874?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-8874:
------------------------------------------
Attachment: screenshot-2.png
> Support XML documents for XSLT compliant browser
> ------------------------------------------------
>
> Key: JBIDE-8874
> URL: https://issues.jboss.org/browse/JBIDE-8874
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot59.png, xml-xsl.png
>
>
> Would be good to have support to show documents for XSLT compliant browser like
> {code:title=cdcatalog.xsl|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!-- Edited by XMLSpy® -->
> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:template match="/">
> <html>
> <body>
> <h2>My CD Collection</h2>
> <table border="1">
> <tr bgcolor="#9acd32">
> <th>Title</th>
> <th>Artist</th>
> </tr>
> <xsl:for-each select="catalog/cd">
> <tr>
> <td><xsl:value-of select="title"/></td>
> <td><xsl:value-of select="artist"/></td>
> </tr>
> </xsl:for-each>
> </table>
> </body>
> </html>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {code:title=page.xml|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <?xml-stylesheet type="text/xsl" href="cdcatalog.xsl"?>
> <!-- Edited by XMLSpy® -->
> <catalog>
> <cd>
> <title>Empire Burlesque</title>
> <artist>Bob Dylan</artist>
> <country>USA</country>
> <company>Columbia</company>
> <price>10.90</price>
> <year>1985</year>
> </cd>
> <cd>
> <title>Hide your heart</title>
> <artist>Bonnie Tyler</artist>
> <country>UK</country>
> <company>CBS Records</company>
> <price>9.90</price>
> <year>1988</year>
> </cd>
> <cd>
> <title>Greatest Hits</title>
> <artist>Dolly Parton</artist>
> <country>USA</country>
> <company>RCA</company>
> <price>9.90</price>
> <year>1982</year>
> </cd>
> </catalog>
> {code}
> Visual part of editor would look like:
> !screenshot59.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-8874) Support XML documents for XSLT compliant browser
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8874?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov commented on JBIDE-8874:
-----------------------------------------------
I change the processor and make editor available to open XML files. You have done practically the same I do. But on Windows the result will look like this
!screenshot-1.png|thumbnail!
But when I open this page in default browser the result will look like this:
!screenshot-2.png|thumbnail!
Why it happens - see my comment above.
> Support XML documents for XSLT compliant browser
> ------------------------------------------------
>
> Key: JBIDE-8874
> URL: https://issues.jboss.org/browse/JBIDE-8874
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha1
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot59.png, xml-xsl.png
>
>
> Would be good to have support to show documents for XSLT compliant browser like
> {code:title=cdcatalog.xsl|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!-- Edited by XMLSpy® -->
> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:template match="/">
> <html>
> <body>
> <h2>My CD Collection</h2>
> <table border="1">
> <tr bgcolor="#9acd32">
> <th>Title</th>
> <th>Artist</th>
> </tr>
> <xsl:for-each select="catalog/cd">
> <tr>
> <td><xsl:value-of select="title"/></td>
> <td><xsl:value-of select="artist"/></td>
> </tr>
> </xsl:for-each>
> </table>
> </body>
> </html>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {code:title=page.xml|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <?xml-stylesheet type="text/xsl" href="cdcatalog.xsl"?>
> <!-- Edited by XMLSpy® -->
> <catalog>
> <cd>
> <title>Empire Burlesque</title>
> <artist>Bob Dylan</artist>
> <country>USA</country>
> <company>Columbia</company>
> <price>10.90</price>
> <year>1985</year>
> </cd>
> <cd>
> <title>Hide your heart</title>
> <artist>Bonnie Tyler</artist>
> <country>UK</country>
> <company>CBS Records</company>
> <price>9.90</price>
> <year>1988</year>
> </cd>
> <cd>
> <title>Greatest Hits</title>
> <artist>Dolly Parton</artist>
> <country>USA</country>
> <company>RCA</company>
> <price>9.90</price>
> <year>1982</year>
> </cd>
> </catalog>
> {code}
> Visual part of editor would look like:
> !screenshot59.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months