March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10439) Implement a JAX-RS 'post-reconcile' mechanism

by Xavier Coulon (Created) (JIRA)

Implement a JAX-RS 'post-reconcile' mechanism ---------------------------------------------- Key: JBIDE-10439 URL: https://issues.jboss.org/browse/JBIDE-10439 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.Beta1 In its current implementation, the JAX-RS core plugin processes annotation changes in the working copies, assuming that they will all be caught (ie, in 'post-change' events). However, in some situations, changing and then saving a compilation unit just after (ie, saving before the 'post-change' event occurs) can lead to sync' issue, where the java model is saved and the jax-rs did not apply the changes. To avoid such a situation, a 'post-reconcile' processing should be done, too. This processing should do a kind of a 'clean' analyse of the given compilation unit build the associated JAX-RS elements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] (JBIDE-11341) Error log: Resource '/testjsfportlet/src' already exists

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11341: --------------------------------------- Summary: Error log: Resource '/testjsfportlet/src' already exists Key: JBIDE-11341 URL: https://issues.jboss.org/browse/JBIDE-11341 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn, project-examples Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Snjezana Peco Priority: Minor Fix For: 3.3.0.CR1 When I import _JBoss JSF Portlet Example_, delete it and import it again, I get the following error in the Error log: {code} Resource '/testjsfportlet/WebContent/WEB-INF/classes' already exists. org.eclipse.core.internal.resources.ResourceException: Resource '/testjsfportlet/WebContent/WEB-INF/classes' already exists. at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:299) at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:286) at org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:30) at org.eclipse.core.internal.resources.Folder.create(Folder.java:95) at org.eclipse.core.internal.resources.Folder.create(Folder.java:125) at org.jboss.tools.common.model.filesystems.impl.FileSystemImpl.getResource(FileSystemImpl.java:87) at org.jboss.tools.common.model.filesystems.impl.FileSystemsImpl.addChild_0(FileSystemsImpl.java:64) at org.jboss.tools.common.model.impl.XModelObjectImpl.addChild(XModelObjectImpl.java:271) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.loadChildren(XModelObjectLoaderUtil.java:321) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoaderUtil.loadChildren(FileSystemsLoader.java:277) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.load(XModelObjectLoaderUtil.java:98) at org.jboss.tools.common.model.util.XModelObjectLoaderUtil.load(XModelObjectLoaderUtil.java:690) at org.jboss.tools.common.model.filesystems.impl.FileSystemsLoader.load(FileSystemsLoader.java:101) at org.jboss.tools.common.model.loaders.impl.RootLoaderImpl.load(RootLoaderImpl.java:33) at org.jboss.tools.common.model.impl.XModelImpl.load(XModelImpl.java:410) at org.jboss.tools.common.model.XModelFactory.createInstance(XModelFactory.java:36) at org.jboss.tools.common.model.XModelFactory.getModel(XModelFactory.java:29) at org.jboss.tools.common.model.project.ModelNature.createProject(ModelNature.java:134) at org.jboss.tools.common.model.project.ModelNature.setProject(ModelNature.java:64) at org.eclipse.core.internal.resources.NatureManager.createNature(NatureManager.java:234) at org.eclipse.core.internal.resources.Project.getNature(Project.java:448) at org.jboss.tools.common.model.util.EclipseResourceUtil.getModelNature(EclipseResourceUtil.java:263) at org.jboss.tools.jst.web.ui.navigator.XProjectContentProvider.getChildren(XProjectContentProvider.java:55) at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96) at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139) at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:119) at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider$1.run(JEE5ContentProvider.java:142) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
5
0 / 0

[JBoss JIRA] (JBIDE-10250) Restore error decorators on the JAX-RS endpoints icons when validation detects errors

by Xavier Coulon (Created) (JIRA)

Restore error decorators on the JAX-RS endpoints icons when validation detects errors -------------------------------------------------------------------------------------- Key: JBIDE-10250 URL: https://issues.jboss.org/browse/JBIDE-10250 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon An error decoration icon should be set on the endpoints icons when the validation detects errors. Existed in the previous version, should be restored :-/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
9
0 / 0

[JBoss JIRA] (JBIDE-11380) switch to new OpenShift logo

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-11380: ---------------------------------------- Summary: switch to new OpenShift logo Key: JBIDE-11380 URL: https://issues.jboss.org/browse/JBIDE-11380 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 Attachments: new-openshift-logo.png OpenShift switched to a new logo in the latest iteration. We have to make sure we use this new logo for our wizard title areas, icons, etc. !new-openshift-logo.png! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
10
0 / 0

[JBoss JIRA] (JBIDE-11109) Some actions on OpenShift console view do not have sense for more applications

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11109: --------------------------------------- Summary: Some actions on OpenShift console view do not have sense for more applications Key: JBIDE-11109 URL: https://issues.jboss.org/browse/JBIDE-11109 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 When you select two applications on OpenShift Express console view and right click them, you can perform some actions that are applied just to one of selected applications (e. g. Web Browser, Import). Only delete action is performed on both of them. Please deactivate/remove the other actions in case more applications are selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
11
0 / 0

[JBoss JIRA] (JBIDE-11198) CDI Validation reports N+1 problems per file even N problems per file configured in CDI Validation Preferences

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-11198: ------------------------------------- Summary: CDI Validation reports N+1 problems per file even N problems per file configured in CDI Validation Preferences Key: JBIDE-11198 URL: https://issues.jboss.org/browse/JBIDE-11198 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.0.Beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
0 / 0

[JBoss JIRA] (JBIDE-11209) Wrong host name when creating OpenShift server from existing OpenShift enabled workspace project

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11209: --------------------------------------- Summary: Wrong host name when creating OpenShift server from existing OpenShift enabled workspace project Key: JBIDE-11209 URL: https://issues.jboss.org/browse/JBIDE-11209 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Fix For: 3.3.0.Beta2 When I create a new OpenShift server for an existing OpenShift enabled workspace project, the host is not set properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
8
0 / 0

[JBoss JIRA] (JBIDE-11242) Users should be warned when WFK maven repo is missing

by Martin Malina (JIRA)

Martin Malina created JBIDE-11242: ------------------------------------- Summary: Users should be warned when WFK maven repo is missing Key: JBIDE-11242 URL: https://issues.jboss.org/browse/JBIDE-11242 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 3.3.0.Beta1 Reporter: Martin Malina Assignee: Snjezana Peco Fix For: 3.3.0.Beta2 When you create a new archetype-based project from JBoss Central with EAP runtime you will be given a warning if you don't have the EAP maven repo installed. Similarly users should be warned when they try to create a Spring or Richfaces project with EAP runtime but don't have the WFK maven repo installed. Right now what happens is that if you don't have the repo installed you'll get an error about missing dependency versions. The reason for that is that the bom containing the versions is not found. See JBIDE-11232. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
5
0 / 0

[JBoss JIRA] (JBIDE-11195) Consider renaming "OpenShift Express Console" to "OpenShift Explorer" or "OpenShift Navigator"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11195: ------------------------------------------- Summary: Consider renaming "OpenShift Express Console" to "OpenShift Explorer" or "OpenShift Navigator" Key: JBIDE-11195 URL: https://issues.jboss.org/browse/JBIDE-11195 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta2 OpenShift Express Console is a bit misleading since its not a console in the sense of what eclipse calls a console OpenShift Explorer (as in Database Explorer) seems a better fit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
6
0 / 0

[JBoss JIRA] (JBIDE-11381) Generating a portlet with init parameter leads to invalid portlet.xml

by Miroslav Cupak (JIRA)

Miroslav Cupak created JBIDE-11381: -------------------------------------- Summary: Generating a portlet with init parameter leads to invalid portlet.xml Key: JBIDE-11381 URL: https://issues.jboss.org/browse/JBIDE-11381 Project: Tools (JBoss Tools) Issue Type: Bug Components: Portal/GateIn Affects Versions: 3.2.1.Final Environment: JBDS 4.1.0.GA (v20110801-1408-H978-GA), EPP 5.2.1.ER02 Reporter: Miroslav Cupak Assignee: Snjezana Peco If you follow the _Steps to reproduce_ section and use the _Create Portlet_ wizard in JBDS to generate a portlet with init parameter, you will end up with a _portlet.xml_ file which is not valid with respect to its XML Schema (http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd). Namely, the following fragment of code is generated: {code:xml} <init-param> <name>test</name> <value>test</value> <description>test</description> </init-param> {code} The problem here is the position of the _description_ element in the _init-param_ section, which should be before the _name_ and _value_, i.e. the code should look like this: {code:xml} <init-param> <description>test</description> <name>test</name> <value>test</value> </init-param> {code} With strict validation enabled by default in newer versions of GateIn/EPP, this causes the following error during deployment: {code} ERROR [PortletApplicationDeployer] Cannot read portlet.xml jndi:/localhost/portlet-generic-jbds-5/WEB-INF/portlet.xml org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'description'. No child element is expected at this point. {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
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 March 2012