April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-5436) Code assist for JSF functions in EL.

by Alexey Kazakov (JIRA)

Code assist for JSF functions in EL. ------------------------------------ Key: JBIDE-5436 URL: https://jira.jboss.org/jira/browse/JBIDE-5436 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.2.next For example: #{rich:clientId('id')} #{rich:element('id')} #{rich:component('id')} #{rich:findComponent('id')} -- 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

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8820) Code Assist doesn't work properly for .drl file

by Vlado Pakan (JIRA)

Code Assist doesn't work properly for .drl file ----------------------------------------------- Key: JBIDE-8820 URL: https://issues.jboss.org/browse/JBIDE-8820 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.1.M1 Environment: Linux 32bit, java sun jdk 1.6_24, jbdevstudio-product-linux-gtk-4.1.0.v201104171649R-H346-M1 Reporter: Vlado Pakan Assignee: Kris Verlaenen 1. Create a new Drools project: File -> New -> Other -> Drools Project Choose Name, click Next Check all options Choose Drools Runtime, click Finish 2. Open sample.drl file 3. Invoke Code Assist bellow line with import statement. It works. Context menu with available statements is displayed 4. Invoke Code Assist at the beginning of line with m : Message( status ... . No context menu is displayed It's was working in JBDS 4.0.0.GA version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
9
0 / 0

[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-8543) StringIndexOutOfBoundsException in Export DDL wizard

by Pavol Srna (JIRA)

StringIndexOutOfBoundsException in Export DDL wizard ---------------------------------------------------- Key: JBIDE-8543 URL: https://issues.jboss.org/browse/JBIDE-8543 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.Final Environment: JBDS 4.0.GA, linux 32bit Reporter: Pavol Srna Fix For: 3.2.1 Exception Stack Trace: java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.charAt(String.java:686) at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard.fileModified(ExportDdlWizard.java:584) at com.metamatrix.modeler.internal.ui.wizards.ExportDdlWizard$18.modifyText(ExportDdlWizard.java:465) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:173) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$Export.executeHandler(WizardHandler.java:98) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:274) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8190) RSE Panel in New Server Wizard has wrong layout on Win7.

by Dominik Pospisil (JIRA)

RSE Panel in New Server Wizard has wrong layout on Win7. -------------------------------------------------------- Key: JBIDE-8190 URL: https://issues.jboss.org/browse/JBIDE-8190 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.CR1 Reporter: Dominik Pospisil Assignee: Rob Stryker RSE Panel in New Server Wizard has wrong layout on Win7. Both New Host and Browse button are not visible even if the whole dialog is expanded. Note that everything is fine on linux / gtk platform. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
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-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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2011