June 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1646) jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload" in JBDS 4

by Brian Fitzpatrick (JIRA)

jBPM upload URL is: "/jbpm-console/upload" but it should be "/gpd-deployer/upload" in JBDS 4 -------------------------------------------------------------------------------------------- Key: JBDS-1646 URL: https://issues.jboss.org/browse/JBDS-1646 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: jBPM Affects Versions: 4.0.1 Reporter: Brian Fitzpatrick Assignee: Koen Aers Priority: Critical Fix For: 4.1.0.CR1, 5.0.0.M1 See SOA-3052, but this seems to be the same issue we've fought for several releases as far as the URL goes between JBoss Tools & JBDS. Koen mentioned he thought Snjezana might know where the code is in JBDS to set the correct preference. Denis might also know. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
11
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-8137) org.jboss.ide.eclipse.as.core requires jbt.bpel.facet.core facet

by Denis Golovin (JIRA)

org.jboss.ide.eclipse.as.core requires jbt.bpel.facet.core facet ---------------------------------------------------------------- Key: JBIDE-8137 URL: https://issues.jboss.org/browse/JBIDE-8137 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Rob Stryker Attachments: screenshot47.png JBoss AS adapter installed without bpel leads to error message from org.eclipse.wst.common.project.facet.core -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
18
0 / 0

[JBoss JIRA] Created: (JBIDE-8773) Maven Seam configurator is ineffective on seam-ear-archetype projects

by Fred Bricon (JIRA)

Maven Seam configurator is ineffective on seam-ear-archetype projects --------------------------------------------------------------------- Key: JBIDE-8773 URL: https://issues.jboss.org/browse/JBIDE-8773 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.2.0.Final Environment: JBT 3.2 Helios SR2 m2e-core 0.12.2.20110415-2017 (see https://repository.sonatype.org//content/sites/forge-sites/m2e/0.12.2/S/) m2eclipse-wtp 0.12.0.201104210906 (see https://repository.sonatype.org/content/sites/forge-sites/m2eclipse-wtp/0...) Reporter: Fred Bricon Attachments: seam-config.zip When creating a project from the seam-ear-archetype (see http://code.google.com/p/open-archetypes/wiki/seamEarArchetype), the Seam Maven configurator doesn't install the seam facet on any project. I'm prepping for staging m2eclipse-wtp 0.12, so I don't know if this is a regression or not. The JBoss Maven facet is correctly installed, the Seam configurator appears on the lifecycle mapping page. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8696) If there is CDI facet, Maven CDI Configurator isn't called

by Snjezana Peco (JIRA)

If there is CDI facet, Maven CDI Configurator isn't called ---------------------------------------------------------- Key: JBIDE-8696 URL: https://issues.jboss.org/browse/JBIDE-8696 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.2.1, 3.3.0.M1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8404) 2 failing tests in jsf.vpe

by Nick Boldt (JIRA)

2 failing tests in jsf.vpe -------------------------- Key: JBIDE-8404 URL: https://issues.jboss.org/browse/JBIDE-8404 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Final Reporter: Nick Boldt Assignee: Alexey Kazakov http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_stable_branch.compon... org.jboss.tools.jsf.vpe.jsf.test.JsfAllTests.testCAforJSPFiles Number of ca proposals shouldn't be a 0 org.jboss.tools.jsf.vpe.jstl.test.JstlAllTests.testRequestEncoding Caused by: java.lang.NullPointerException at org.eclipse.wst.sse.ui.internal.style.SemanticHighlightingReconciler.reconcile(SemanticHighlightingReconciler.java:115) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.endProcessing(DocumentRegionProcessor.java:119) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor.run(DirtyRegionProcessor.java:682) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7461) OpenOns for #{cc.attrs.*}

by Alexey Kazakov (JIRA)

OpenOns for #{cc.attrs.*} ------------------------- Key: JBIDE-7461 URL: https://jira.jboss.org/browse/JBIDE-7461 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.3.x 1. Create JSF 2 project via New JSF Project wizard. 2. Open ebContent/resources/demo/input.xhtml 3. See ELs like #{cc.attrs.action} Ctrl+click on "action" within this EL should point to it's declaration: <composite:attribute name="action"... -- 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

3
4
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-8845) Implement open-on on tag attribute names

by Viacheslav Kabanovich (JIRA)

Implement open-on on tag attribute names ---------------------------------------- Key: JBIDE-8845 URL: https://issues.jboss.org/browse/JBIDE-8845 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich For example, in <h:outputText value="#{Message.header}"/>, if user tries open-on on name region of attribute 'value', html_basic.tld should be opened with selected element <attribute> corresponding to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
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 June 2011