August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17687) create savara features overview for tools.jboss.org

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17687?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17687: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > create savara features overview for tools.jboss.org > --------------------------------------------------- > > Key: JBIDE-17687 > URL: https://issues.jboss.org/browse/JBIDE-17687 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: website > Reporter: Max Rydahl Andersen > Assignee: Gary Brown > Fix For: 4.2.x > > > Create a features/savara.adoc in jbosstools-website describing the main/cool features > We are refreshing jboss.org/tools (new name: tools.jboss.org) and one of the areas on the new website is a features overview page to let visitors know what features are actually covered in jboss tools. > You can see the current list at http://tools-stg.jboss.org/features/ following the pattern of component/project logo + component name + "tag line". > And then individual pages like http://tools-stg.jboss.org/features/openshift.html which follows the pattern of alternating paragraph + image/screenshot with title/tagline + description for each main feature. > It would be great if you could help create this page for your component. > The process is as follows: > git@github.com:jbosstools/jbosstools-website.git > cd jbosstools-website/features > create componentname.adoc (use i.e. openshift.adoc as inspiration with respect to header names) > Submit this page and related images as pullrequest > The expected launch of the site is end of march so the sooner the better :) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15474) "Further Configuration" for JAX-RS Facet should be optional

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15474?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15474: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > "Further Configuration" for JAX-RS Facet should be optional > ----------------------------------------------------------- > > Key: JBIDE-15474 > URL: https://issues.jboss.org/browse/JBIDE-15474 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream, webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > - library configuration should be optional, since users may work with Maven > - web.xml configuration (servlet mapping) should be optional as well, since it has not been required since JavaEE6. > Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=431081 to track this request at the Eclipse WTP level. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9179) Bad behaviour of the JAX-RS Capabilities popup

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9179?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-9179: --------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > Bad behaviour of the JAX-RS Capabilities popup > ----------------------------------------------- > > Key: JBIDE-9179 > URL: https://issues.jboss.org/browse/JBIDE-9179 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 3.3.0.M1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Minor > Labels: JAX-RS, upstream > Fix For: 4.2.0.CR1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > When setting the JAX-RS Facet on a dynamic web project, a popup window requires to choose the JAX-RS implementation library for the project, and optionally to specify the servlet class name to update the web.xml deployment descriptor accordingly. When choosing 'Disable library configuration' or 'Pure JEE6 implementation', the 'Servlet Information' panel is not disabled as expected. This is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=338898 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17591) org.jboss.tools.common.el.core.test fails on Max OS X Mavericks

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17591?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17591: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > org.jboss.tools.common.el.core.test fails on Max OS X Mavericks > --------------------------------------------------------------- > > Key: JBIDE-17591 > URL: https://issues.jboss.org/browse/JBIDE-17591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.2.0.Beta2 > Environment: Mac OS X Mavericks > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.0.CR1 > > Attachments: org.jboss.tools.common.el.core.test.CommonELAllTests2.txt > > > {code}junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:55) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.Assert.assertNotNull(Assert.java:256) > at junit.framework.Assert.assertNotNull(Assert.java:248) > at junit.framework.TestCase.assertNotNull(TestCase.java:417) > at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:68) > 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:601) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at junit.framework.TestSuite.runTest(TestSuite.java:255) > at junit.framework.TestSuite.run(TestSuite.java:250) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84) > at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104) > 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:601) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110) > at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175) > at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86) > at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21) > 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:601) > at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:379) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) > 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:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) > at org.eclipse.equinox.launcher.Main.main(Main.java:1438) > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2876) Include EAP 6.3 in bundled JBDS+EAP universal installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2876?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2876: -------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > Include EAP 6.3 in bundled JBDS+EAP universal installer > ------------------------------------------------------- > > Key: JBDS-2876 > URL: https://issues.jboss.org/browse/JBDS-2876 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer, requirements > Reporter: Michelle Murray > Assignee: Nick Boldt > Priority: Blocker > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17419) new JAX-RS Resource wizard : should be able to set default resource suffix in preferences

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17419?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17419: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > new JAX-RS Resource wizard : should be able to set default resource suffix in preferences > ----------------------------------------------------------------------------------------- > > Key: JBIDE-17419 > URL: https://issues.jboss.org/browse/JBIDE-17419 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.2.x > > > When creating a JAX-RS resource for an existing entity, say foo.bar.Person, the default resource name will be PersonEndpoint. I would personally prefer to use PersonResource. > It'd be nice to be able to set that suffix in the workspace (project?) preferences. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17477) Remember to skip application creation in JAX-RS Wizard

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17477?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17477: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > Remember to skip application creation in JAX-RS Wizard > ------------------------------------------------------ > > Key: JBIDE-17477 > URL: https://issues.jboss.org/browse/JBIDE-17477 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.x > > > The JAX-RS Resource creation wizard provides a page to create a JAX-RS Application in the project if none was found, but the user may want to skip this step if she plans to deploy her application in a non JEE6/7 environment - which would require a custom configuration (e.g.: a servlet dispatcher) to activate and use the JAX-RS resources. > The wizard should remember that choice, so the user would not have to explicitly skip this step for each new JAX-RS resource she wants to create. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17457) JAX-RS Resource Wizard has inconsistent validation of target entity

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17457?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17457: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > JAX-RS Resource Wizard has inconsistent validation of target entity > ------------------------------------------------------------------- > > Key: JBIDE-17457 > URL: https://issues.jboss.org/browse/JBIDE-17457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > The wizard should let the user click on the 'Finish' button even if no 'Target entity was specified', in which case, the JAX-RS Resource Methods checkboxes should be all unselected and disabled and the generated code should only contain the package and type declaration (no method) > BUT when you actually type in class for entity and it does not exist or you edit the field to be be blank the wizard shows an error where it should just be a warning and allow you to create it as if you hadn't edited the field. > Should only make it an error if one of the methodstub checkboxes actually requires a type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17178) Problem with filters and interceptors defined as inner classes

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17178?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17178: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > Problem with filters and interceptors defined as inner classes > -------------------------------------------------------------- > > Key: JBIDE-17178 > URL: https://issues.jboss.org/browse/JBIDE-17178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > It seems that filter and interceptors are not recognized if they are defined as inner classes. > e.g. there is no warning "The @Provider annotation is missing ...". -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17078) JAX-RS Problems doesn't appears after the JAX-RS Support is activated

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17078?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-17078: ---------------------------------- Sprint: Sprint Beta2 CF, Sprint to Beta3 Release (was: Sprint to Beta3 Release) > JAX-RS Problems doesn't appears after the JAX-RS Support is activated > --------------------------------------------------------------------- > > Key: JBIDE-17078 > URL: https://issues.jboss.org/browse/JBIDE-17078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > JAX-RS validation runs when there is a change in the project with JAX-RS Support. However, it doesn't run right after the JAX-RS Support is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
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 August 2014