January 2011 - jbosstools-issues - Jboss List Archives

[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-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-7956) GWT integration cannot be installed

by Libor Zoubek (JIRA)

GWT integration cannot be installed ----------------------------------- Key: JBIDE-7956 URL: https://issues.jboss.org/browse/JBIDE-7956 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, GWT Affects Versions: 3.2.0.CR1 Environment: nightly update site zip 20101215-1434-H4-CR1 Reporter: Libor Zoubek Assignee: Nick Boldt Cannot complete the install because one or more required items could not be found. When attempting to install GWT integration I get: Software being installed: JBoss GWT Integration (Experimental) 1.0.0.v20101215-1434-H4-CR1 (org.jboss.tools.gwt.feature.feature.group 1.0.0.v20101215-1434-H4-CR1) Missing requirement: JBoss Tools GWT (Experimental) 1.0.0.v20101215-1434-H4-CR1 (org.jboss.tools.gwt.core 1.0.0.v20101215-1434-H4-CR1) requires 'bundle com.google.gwt.eclipse.sdkbundle.2.1.0 [2.1.0,3.0.0)' but it could not be found Cannot satisfy dependency: From: JBoss GWT Integration (Experimental) 1.0.0.v20101215-1434-H4-CR1 (org.jboss.tools.gwt.feature.feature.group 1.0.0.v20101215-1434-H4-CR1) To: org.jboss.tools.gwt.core [1.0.0.v20101215-1434-H4-CR1] google updatesite is present at version Google App Engine Java SDK 1.4.0 1.4.0.v201012021502 com.google.appengine.eclipse.sdkbundle.e36.feature.1.4.0.feature.group Google Plugin for Eclipse 3.6 1.4.1.v201012170127 com.google.gdt.eclipse.suite.e36.feature.feature.group Google Web Toolkit SDK 2.1.1 2.1.1.v201012170127 com.google.gwt.eclipse.sdkbundle.e36.feature.2.1.1.feature.group looks like google have renamed features few days ago :-/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

7
38
0 / 0

[JBoss JIRA] Created: (JBIDE-8281) OpenOn doesn't work for #{msgs.prompt} in JSF2 project.

by Alexey Kazakov (JIRA)

OpenOn doesn't work for #{msgs.prompt} in JSF2 project. ------------------------------------------------------- Key: JBIDE-8281 URL: https://issues.jboss.org/browse/JBIDE-8281 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.CR1 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Priority: Critical Fix For: 3.2.x, 3.3.x 1. Create JSF2 KickStart project via New JSF Project Wizard. 2. Open inputname.xhtml 3. Ctrl+Click on #{msgs.prompt} within <ez:input id="inputname" label="#{msgs.prompt}". Nothing happened. Code completion works. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8187) Filter instances: should be able to filter instances upon "Alias"

by Andre Dietisheim (JIRA)

Filter instances: should be able to filter instances upon "Alias" ------------------------------------------------------------------ Key: JBIDE-8187 URL: https://issues.jboss.org/browse/JBIDE-8187 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 3.2.1 Currently instances may not be filtered upon their alias value. This should be possible. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8216) jsf-tags breaks wtp-capibilites

by nimo stephan (JIRA)

jsf-tags breaks wtp-capibilites ------------------------------- Key: JBIDE-8216 URL: https://issues.jboss.org/browse/JBIDE-8216 Project: Tools (JBoss Tools) Issue Type: Feature Request Environment: JSF, JbossTools Reporter: nimo stephan With Eclipse WTP, I can click a css-class within a html-editor to jump automatically to that css-class. This only works, when referencing the html with the stylesheet: <link rel="stylesheet" href="style.css" type="text/css"/> But when using the jsf-tag: <h:outputStylesheet name="style.css" type="text/css"/> then the linking between html and css does no more work! So it would be nice, if jboss-tools does resolve such an issue. In generally, Jboss Tools should be aware of JSF-Tags and involve them nicely so that the capabilites of WTP are not cut. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
6
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-8090) Missing dialog titles

by Libor Zoubek (JIRA)

Missing dialog titles --------------------- Key: JBIDE-8090 URL: https://issues.jboss.org/browse/JBIDE-8090 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Libor Zoubek Assignee: Andre Dietisheim Priority: Minor I ve found several dialogs where are missing dialog titles. It should be fixed. It is good convention to have titled dialogs and it is goot for bot tests too. * New/Edit Connection * Launch Instance * Setting up filters * Selecting EC2 key -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
16
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 January 2011