September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6656) Split out ModeShape documentation into separate plug-in

by Brian Fitzpatrick (JIRA)

Split out ModeShape documentation into separate plug-in ------------------------------------------------------- Key: JBIDE-6656 URL: https://jira.jboss.org/browse/JBIDE-6656 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Dan Florian Fix For: 3.2.x Would recommend splitting out the documentation bits into a separate plug-in so that they are more easily accessed by the documentation team. Easier for them to tweak a doc plug-in separate from the rest of the code to avoid any accidental code changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6460) Create a SeamTest automatically for new Entity or separately for existing entity

by Robb Greathouse (JIRA)

Create a SeamTest automatically for new Entity or separately for existing entity -------------------------------------------------------------------------------- Key: JBIDE-6460 URL: https://jira.jboss.org/browse/JBIDE-6460 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Affects Versions: 3.1.1 Environment: all Reporter: Robb Greathouse Assignee: Alexey Kazakov In order to further test driven development it would be handy to have a SeamTest create when creating a SeamEntity. Basically, the test would include a Search Test, a Create Test, a Select Test (after searching), an Update Test and a Delete Test. These are fairly simply to do and it would be easy to implement for Eclipse plugin. This would provide a basic test example to the user which could be built out as they built their application. Even more advanced would be to be able to build out the test from a use case and then build out the domain from there. Still working to figure out how to do that with Seam. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4267) Add add-identity-management support to new seam web projects

by Drew Arrigoni (JIRA)

Add add-identity-management support to new seam web projects ------------------------------------------------------------ Key: JBIDE-4267 URL: https://jira.jboss.org/jira/browse/JBIDE-4267 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples, Seam Reporter: Drew Arrigoni SEAM 2.1.2 introduced the "add-identity-management" keyword, which can generate a fully functional SEAM JpaIdentityManagement powered security management system. Here is a blog post explaining what it is: http://blog.hibernate.org/10904.lace Here is the seam-gen documentation for this feature: http://seamframework.org/Documentation/AddIdentityManagementToASeamgenPro... Would also be nice to have an example project with this stuff already set up to play around with. -- 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

14 years, 10 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5862) org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets fails with: expected:<[ a] > but was:<[ >] >

by Nick Boldt (JIRA)

org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets fails with: expected:<[ a] > but was:<[ >] > ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-5862 URL: https://jira.jboss.org/jira/browse/JBIDE-5862 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.1.0.CR2 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Regression JsfAllTests.testEditingSPecialSymbolsVPE_JBIDE3810 Failing for the past 1 build (Since #251 ) Took 13 sec. add description Error Message expected:<[ a] > but was:<[ >] > Stacktrace junit.framework.ComparisonFailure: expected:<[ a] > but was:<[ >] > at org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.compareVisualAndSourceTargets(EditingSPecialSymbolsVPE_JBIDE3810.java:160) at org.jboss.tools.jsf.vpe.jsf.test.jbide.EditingSPecialSymbolsVPE_JBIDE3810.testEditingSPecialSymbolsVPE_JBIDE3810(EditingSPecialSymbolsVPE_JBIDE3810.java:58) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3468) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3115) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) at org.eclipse.core.launcher.Main.main(Main.java:34) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... -- 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

14 years, 10 months

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-5387) OpenOn does not work for CSS links in HTML files for plain Web Projects

by Yahor Radtsevich (JIRA)

OpenOn does not work for CSS links in HTML files for plain Web Projects ----------------------------------------------------------------------- Key: JBIDE-5387 URL: https://jira.jboss.org/jira/browse/JBIDE-5387 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.1.GA Reporter: Yahor Radtsevich Assignee: Alexey Kazakov STEPS TO REPRODUCE: 1. Open the attached project. 2. Open file 'index.html' press Ctrl key and move the mouse cursor over text 'style.css' (try to invoke OpenOn functionality). ACTUAL RESULT: Nothing happens. EXPECTED RESULT: The link to the stylesheet should be underlined. -- 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

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6379) Unbound Java Build Path

by Burr Sutter (JIRA)

Unbound Java Build Path ----------------------- Key: JBIDE-6379 URL: https://jira.jboss.org/browse/JBIDE-6379 Project: Tools (JBoss Tools) Issue Type: Bug Components: core Affects Versions: 3.1.0.GA Environment: JBoss Developer Studio Version: 3.0.0.GA Build id: v201003100055R Build date: 201003100222 Reporter: Burr Sutter The settings in the Java Build Path become "unbound" between JBDS restarts. I have seen this on multiple Windows machines (32-bit JVM) and have heard that it happens on Linux as well. Specifically with the SOA Platform 5/ESB Libraries but sometimes with the JVM/JDK as well. My Projects are here: http://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/bsutter/soa5d... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7223) ModeShapeMessageConsole Illegally Extends MessageConsole

by Dan Florian (JIRA)

ModeShapeMessageConsole Illegally Extends MessageConsole -------------------------------------------------------- Key: JBIDE-7223 URL: https://jira.jboss.org/browse/JBIDE-7223 Project: Tools (JBoss Tools) Issue Type: Task Components: modeshape Affects Versions: 3.2.0.M2 Reporter: Dan Florian Fix For: 3.3.x ModeShapeMessageConsole is extending MessageConsole which has the @noextend annotation. Rewrite ModeShapeMessageConsole so that it is not a subclass of MessageConsole. This doesn't appear to be causing any runtime problems. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5851) New Seam Web Project -> -test project has hsqldb settings in any case

by Vitali Yemialyanchyk (JIRA)

New Seam Web Project -> -test project has hsqldb settings in any case --------------------------------------------------------------------- Key: JBIDE-5851 URL: https://jira.jboss.org/jira/browse/JBIDE-5851 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate, Seam Affects Versions: 3.1.0.CR2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Attachments: screenshot-init-configuration.jpg New -> Seam Web Project -> Configure Seam Facet Settings -> setup MySQL database -> general project has MySQL settings, but -test project has hsqldb settings -- 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

14 years, 10 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6708) MDB WTP Wizard Annotations for HornetQ

by Gary Lamperillo (JIRA)

MDB WTP Wizard Annotations for HornetQ -------------------------------------- Key: JBIDE-6708 URL: https://jira.jboss.org/browse/JBIDE-6708 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.1 Environment: JBDS 3.0.1 , EAP 5.1 Beta, HornetQ 2.1 Reporter: Gary Lamperillo Fix For: 3.1.2 Using the Message Driven Bean WTP Wizard that is in JBDS 3.0.1, an annotation in the format is created: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") HornetQ will need an annotation in the following format: @MessageDriven( activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"), @ActivationConfigProperty(propertyName = "useLocalTx", propertyValue = "true") }, mappedName = "queue/testQueue") Either HornetQ will nee to correspond to WTPs expectation or the wizard will need to be modified to accept the hornetq specific changes. Since the tooling will still need to work with other providers such as JBoss Messaging, a radio button will need to be added to the Wizard as well to select HornetQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
16
0 / 0

[JBoss JIRA] Created: (JBIDE-7102) Open xhtml file with VPE -> An internal error occurred during: "Refreshing XPath View".

by Vitali Yemialyanchyk (JIRA)

Open xhtml file with VPE -> An internal error occurred during: "Refreshing XPath View". --------------------------------------------------------------------------------------- Key: JBIDE-7102 URL: https://jira.jboss.org/browse/JBIDE-7102 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau 1) Open some xhtml file with VPE first time - so VPE start a little bit long time (XPath view was not active, was not opened); 2) Press "Show selection bar" just when this became be possible - do not sure could this be related with exception; 3) get exception message box; 4) exception in "Error Log": java.lang.RuntimeException: Не удалось преобразовать узел в дескриптор at org.apache.xml.dtm.ref.DTMManagerDefault.getDTMHandleFromNode(DTMManagerDefault.java:576) at org.apache.xpath.XPathContext.getDTMHandleFromNode(XPathContext.java:184) at org.apache.xpath.XPath.execute(XPath.java:303) at org.apache.xpath.jaxp.XPathExpressionImpl.eval(XPathExpressionImpl.java:129) at org.apache.xpath.jaxp.XPathExpressionImpl.eval(XPathExpressionImpl.java:99) at org.apache.xpath.jaxp.XPathExpressionImpl.evaluate(XPathExpressionImpl.java:184) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.evaluateXPath(XPathComputer.java:212) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.executeXPath(XPathComputer.java:185) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.doCompute(XPathComputer.java:165) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer.access$2(XPathComputer.java:164) at org.eclipse.wst.xml.xpath.ui.internal.views.XPathComputer$2.run(XPathComputer.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) 5) try to open other xhtml files - get this exception for every file open; 6) open XPath view - get this exception regularly - almost every mouse click; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

6
9
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 September 2010