July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11465) Wrong source insertion after dnd an element into the <div /> with no end tag on JSP page.

by Denis Maliarevich (JIRA)

Denis Maliarevich created JBIDE-11465: ----------------------------------------- Summary: Wrong source insertion after dnd an element into the <div /> with no end tag on JSP page. Key: JBIDE-11465 URL: https://issues.jboss.org/browse/JBIDE-11465 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.Beta2 Reporter: Denis Maliarevich Assignee: Denis Maliarevich Fix For: 3.3.0.Beta3 After DnD an element into the <div /> with no end tag on JSP page -- it is inserted at the end of the tag, but not inside of it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2710) jsf validator should warn against empty id (id="")

by Max Rydahl Andersen (JIRA)

jsf validator should warn against empty id (id="") -------------------------------------------------- Key: JBIDE-2710 URL: https://jira.jboss.org/jira/browse/JBIDE-2710 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Minor Fix For: 3.0.0.beta1 See JBIDE-2631 for what happens if users have id="" Would be good if we could implement this as a validation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-10592) deployments tab war module deployment location is ignored

by erik van altena (Created) (JIRA)

deployments tab war module deployment location is ignored --------------------------------------------------------- Key: JBIDE-10592 URL: https://issues.jboss.org/browse/JBIDE-10592 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Eclipse Indigo SR1 Reporter: erik van altena Assignee: Rob Stryker Priority: Minor This bug report is created as per requested in this closed issue: https://issues.jboss.org/browse/JBIDE-10590 I have a Mavenized project (m2eclipse, JBoss Tools Maven Integration) which I publish to a JBoss 7 runtime (standalone) by dragging it to the runtime instance. To work around the publish directory names not matching the maven pom configuration, I use the runtime deployment tab to override the directory names that the project modules are deployed under in the deployments folder of the server. (next part copy/pasted from original issue comments) But then I run into the next oddity: the settings for the war module seem to be ignored out of the box. The deployment tab mentions the war module as being deployed as 'app-web.war' while in fact it ends up in the deployments directory as 'app-web-1.0.0-SNAPSHOT.war', just like Maven would name it if you don't provide a finalName. However, as soon as I tab over the deployment locations and save the changes to the runtime configuration, upon full publish the web module gets the directory name as it is listed in the deployments tab. To be a little more specific: I get this behavior when I haven't made changes yet to the war entry in the deployment tab; the tab indicates the correct name but the result after publishing is wrong. When I then press tab to navigate to the deployment-location of the war, I don't change anything but I hit CTRL+S to save changes, upon full publish the name is then correct. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

8
25
0 / 0

[JBoss JIRA] Created: (JBDS-293) properties editor very slow

by Martin Trummer (JIRA)

properties editor very slow --------------------------- Key: JBDS-293 URL: http://jira.jboss.com/jira/browse/JBDS-293 Project: Developer Studio Issue Type: Bug Components: visualeditor Affects Versions: 1.0.0.GA Reporter: Martin Trummer Assigned To: Max Andersen unfortunately I can't provide a recipe to reproduce the problem. However: It seems to happen when: I open 2 properties files - each about 300 lines I have the properties files open for some time (not using it) then I add a line and save it: in this case eclipse is stuck for 1-2 seconds. I only have about 300 properties in the editor. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

6
11
0 / 0

[JBoss JIRA] (JBDS-2230) JBDS Central discovery is broken

by Max Rydahl Andersen (JIRA)

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12391) Quick Fix "Add tag library definition" should add missing required attribute(s)

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-12391: ------------------------------------- Summary: Quick Fix "Add tag library definition" should add missing required attribute(s) Key: JBIDE-12391 URL: https://issues.jboss.org/browse/JBIDE-12391 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: jsp/jsf/xml source editing Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.4.0.M1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12359) Quick fixes don't work in WTP XML Editor

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12359: -------------------------------------- Summary: Quick fixes don't work in WTP XML Editor Key: JBIDE-12359 URL: https://issues.jboss.org/browse/JBIDE-12359 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.4.0.M1 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.4.0.M1 Create JSF2 KickStart project. Open faces-config.xml Add #{user.names} there: {code} <?xml version="1.0" encoding="UTF-8"?> <faces-config xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd" version="2.0"> <navigation-rule> <from-view-id>/pages/inputname.xhtml</from-view-id> <navigation-case> <from-outcome>greeting</from-outcome> <to-view-id>/pages/greeting.xhtml</to-view-id> </navigation-case> </navigation-rule> #{user.names} <application> <resource-bundle> <base-name>resources</base-name> <var>msgs</var> </resource-bundle> </application> </faces-config> {code} Save the file. Open it with XML Editor (not JBoss XML Editor). Move the mouse over the problem marker on #{user.names} Click on Configure Problem Severity... quick fix. Nothing happend. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
12
0 / 0

[JBoss JIRA] (JBIDE-11784) jbosstools-3.3_stable_branch.tests is running out of memory (heap)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11784: ---------------------------------- Summary: jbosstools-3.3_stable_branch.tests is running out of memory (heap) Key: JBIDE-11784 URL: https://issues.jboss.org/browse/JBIDE-11784 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 3.3.0.Beta3 {code} Exception in thread "[Timer] - Main Queue Handler" java.lang.OutOfMemoryError: Java heap space at org.eclipse.equinox.internal.util.impl.tpt.threadpool.ThreadPoolFactoryImpl.execute0(ThreadPoolFactoryImpl.java:94) at org.eclipse.equinox.internal.util.impl.tpt.timer.TimerImpl.run(TimerImpl.java:110) at java.lang.Thread.run(Thread.java:662) [ERROR] Java heap space -> [Help 1] java.lang.OutOfMemoryError: Java heap space {code} http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
20
0 / 0

[JBoss JIRA] Created: (JBIDE-2101) XPath pattern matches disappear

by Galder Zamarreno (JIRA)

XPath pattern matches disappear ------------------------------- Key: JBIDE-2101 URL: http://jira.jboss.com/jira/browse/JBIDE-2101 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.0.beta1 Reporter: Galder Zamarreno I created a new category in the XML configuration view of the server called Server and added a new XPath like this: Name: jmx invoker XPath Pattern: /server/mbean/xmbean/operation/descriptors/interceptors/interceptor It worked fine first time around but now, although I can see the XPath, I can't see the matched XML files. Same happens in the "Ports" category. I'll attach screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
18
0 / 0

[JBoss JIRA] (JBIDE-11655) Failed while installing JPA 2.0.

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11655: ---------------------------------------- Summary: Failed while installing JPA 2.0. Key: JBIDE-11655 URL: https://issues.jboss.org/browse/JBIDE-11655 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Marius Bogoevici java.lang.NullPointerException at org.eclipse.jpt.common.core.internal.resource.ModuleResourceLocator.getDefaultResourceLocation(ModuleResourceLocator.java:34) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.defaultResourceLocation(JpaFacetInstallDelegate.java:141) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createPersistenceXml(JpaFacetInstallDelegate.java:111) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.createProjectXml(JpaFacetInstallDelegate.java:101) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetInstallDelegate.execute_(JpaFacetInstallDelegate.java:62) at org.eclipse.jpt.jpa.core.internal.facet.JpaFacetActionDelegate.execute(JpaFacetActionDelegate.java:34) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.jboss.tools.maven.jpa.configurators.JpaProjectConfigurator.configureFacets(JpaProjectConfigurator.java:124) at org.jboss.tools.maven.jpa.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:87) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:234) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:150) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$1.doCreateMavenProjects(MavenImportWizard.java:164) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.MavenImportWizard$3.runInWorkspace(MavenImportWizard.java:249) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

5
15
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 July 2012