October 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7435) Create RichFaces 4.0 & JSF 2.0 project examples

by Alexey Kazakov (JIRA)

Create RichFaces 4.0 & JSF 2.0 project examples ----------------------------------------------- Key: JBIDE-7435 URL: https://jira.jboss.org/browse/JBIDE-7435 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF, project-examples Reporter: Alexey Kazakov Assignee: Snjezana Peco See some mavanized RichFaces 4.0 examples here: http://anonsvn.jboss.org/repos/richfaces/trunk/archetypes/richfaces-arche... It would be nice to have such examples in our project example site. See the original request here JBIDE-7422 -- 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

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBDS-1387) Publishing project to Modeshape repo in JBDS 4.0 beta1 - Unhandled event loop exception

by Len DiMaggio (JIRA)

Publishing project to Modeshape repo in JBDS 4.0 beta1 - Unhandled event loop exception --------------------------------------------------------------------------------------- Key: JBDS-1387 URL: https://jira.jboss.org/browse/JBDS-1387 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Modeshape Affects Versions: 4.0.0.Beta1 Reporter: Len DiMaggio JBDS issue for JIRA: SOA-2506 -- 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

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6866) Duplicate entries in XML catalog

by Juergen Zimmermann (JIRA)

Duplicate entries in XML catalog -------------------------------- Key: JBIDE-6866 URL: https://jira.jboss.org/browse/JBIDE-6866 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.0.M1 Reporter: Juergen Zimmermann Assignee: Rob Stryker The following .xsd files are already provided by WTP 3.2.1, and additionally JBossTools provides them inside plugins\org.jboss.ide.eclipse.as.core_...jar : javaee_6.xsd ejb-jar_3_1.xsd application_6.xsd web-common_3_0.xsd web-app_3_0.xsd javaee_web_services_client_1_3.xsd -- 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

15 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7080) GWT facet doesn't work correctly with Web Module 2.4

by Snjezana Peco (JIRA)

GWT facet doesn't work correctly with Web Module 2.4 ---------------------------------------------------- Key: JBIDE-7080 URL: https://jira.jboss.org/browse/JBIDE-7080 Project: Tools (JBoss Tools) Issue Type: Bug Components: GWT Affects Versions: 3.2.0.M2 Reporter: Snjezana Peco Attachments: gwt.png Steps to reproduce: - call a new Dynamic Web Project wizard - choose Web module 2.4 - add the GWT facet - set the Java facet to the 1.5 version if that is required - click Finish You will get an error dialog as in the attached screenshot. Solution: Creating the GWT servlet for Web Module 2.4 or changing a declaration of the GWT facet to require Web module >= 2.5 -- 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

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7269) beans.xml validator shows invalid errors

by Lukas Jungmann (JIRA)

beans.xml validator shows invalid errors ---------------------------------------- Key: JBIDE-7269 URL: https://jira.jboss.org/browse/JBIDE-7269 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Beta1 Reporter: Lukas Jungmann Assignee: Alexey Kazakov Priority: Critical -create a dynamic web project with enabled CDI support -create some CDI beans there (at least one with @Alternative) -create beans.xml (File -> New -> Other -> xml) -edit beans.xml so it contains: <?xml version="1.0" encoding="UTF-8"?> <beans 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/beans.xsd"> <alternatives> <class></class> </alternatives> </beans> -save file => content of the class element is underlined as error saying "..element must specify the name of an alternative bean class..", but the class is annotated with @Alternative my exact steps were: -create a dynamic web project with enabled CDI support -copy org.jboss.jsr299.tck.tests.policy.broken.same.type.twice package from tck project to the one created in previous step -create beans.xml with following content: <?xml version="1.0" encoding="UTF-8"?> <beans 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/beans.xsd"> <alternatives> <class>org.jboss.jsr299.tck.tests.policy.broken.same.type.twice.Cat</class> </alternatives> </beans> -save the beans.xml file => error says that the 'Cat' class is not @Alternative, but the class is @RequestScoped @Alternative class Cat { } and war deployment doesn't show any errors -- 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

15 years, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6623) [Designer] Using New Metadata Modeling Model Project wizard throws exception if not run in Designer perspective

by Brian Fitzpatrick (JIRA)

[Designer] Using New Metadata Modeling Model Project wizard throws exception if not run in Designer perspective --------------------------------------------------------------------------------------------------------------- Key: JBIDE-6623 URL: https://jira.jboss.org/browse/JBIDE-6623 Project: Tools (JBoss Tools) Issue Type: Bug Components: teiid Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Fix For: 3.2.x When I created a new Model Project in a perspective other than the Designer perspective, I get an error in the new project wizard in a clean workspace. I was able to cancel out of the project wizard, manually select Open Project on the popup, and open the project to continue, but it would be good if we didn't automatically throw an issue if the wizard is available in other perspectives. Or perhaps pop up a dialog suggesting the user should pop into the Designer perspective for additional functionality (kind of like when Eclipse flips into the Debug perspective when it goes into Debug mode and offers the choice). !ENTRY org.teiid.designer.ui 4 0 2010-07-15 09:56:16.584 !MESSAGE Resource '/MyModelProject' is not open. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/MyModelProject' is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:137) at org.eclipse.core.internal.resources.Project.getDescription(Project.java:379) at com.metamatrix.modeler.ui.wizards.NewModelProjectWizard.performFinish(NewModelProjectWizard.java:94) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) 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:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) 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$New.executeHandler(WizardHandler.java:254) 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:3552) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3171) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- 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

15 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7439) Code completion for #{cc.attrs.<name>.*} based on <cc:attribute type="..." .../>

by Alexey Kazakov (JIRA)

Code completion for #{cc.attrs.<name>.*} based on <cc:attribute type="..." .../> -------------------------------------------------------------------------------- Key: JBIDE-7439 URL: https://jira.jboss.org/browse/JBIDE-7439 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x For example there is a composition component: <cc:interface> <cc:attribute name="myattr" type="java.lang.String" /> </cc:interface> Then ctrl+space for <h:outputData value="#{cc.attrs.myattr.|}"/> should provide code completion for java.lang.String -- 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

15 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6081) Overall scrolling for 'Deployment' tab in JBoss AS Server configuration editor

by Denis Golovin (JIRA)

Overall scrolling for 'Deployment' tab in JBoss AS Server configuration editor ------------------------------------------------------------------------------ Key: JBIDE-6081 URL: https://jira.jboss.org/jira/browse/JBIDE-6081 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Denis Golovin Assignee: Rob Stryker Priority: Minor Attachments: jboss-deploy-config-scroll.png Sometimes it happens and there is no place to show deployment settings for modules. We have several options to fix it: 1. Fix text layout on top of the tab to be justified 2. Add vertical scroll bar -- 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

15 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7456) There is no JBoss Tools XML Editor in the list of "Open with..." for web.xml v.3.0

by Alexey Kazakov (JIRA)

There is no JBoss Tools XML Editor in the list of "Open with..." for web.xml v.3.0 ---------------------------------------------------------------------------------- Key: JBIDE-7456 URL: https://jira.jboss.org/browse/JBIDE-7456 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta2 1. Create JSF 2.0 & Servlet 3.0 project via New JSF Project wizard. 2. Try to "Open with..." on web.xml. Ther is not our XML Editor. -- 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

15 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7457) DnD doesn't work in composite component file editor (VPE)

by Alexey Kazakov (JIRA)

DnD doesn't work in composite component file editor (VPE) --------------------------------------------------------- Key: JBIDE-7457 URL: https://jira.jboss.org/browse/JBIDE-7457 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.Beta2 1. Open any composite component (*.xhtml) in VPE. 2. Try to DnD any tag lib or tag from Palette to source tab. For example <h:outputText> 3. outputText is inserted instead of <h:outputText .../>. The same for tag lib (name space) declarations. -- 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

15 years, 4 months

3
3
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 October 2010