July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-83) JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-83?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBTIS-83: ---------------------------------------- Ok. I've added the examples plugin that basically just has the org.jboss.tools.project.examples.projectExamplesXml extension point and depends on the project examples plug-ins. There's no real code there. Here's the PR: https://github.com/jbosstools/jbosstools-esb/pull/56 I can't test it because it doesn't find the property key "integrationstack.examples.url" in https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... and since it can't find the key, it throws a NPE on start-up... java.lang.NullPointerException at java.lang.StringBuilder.<init>(Unknown Source) at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getFullKey(VersionPropertiesProvider.java:232) at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.lookupValue(VersionPropertiesProvider.java:202) at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:154) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getPluginSites(ProjectExampleUtil.java:147) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getSites(ProjectExampleUtil.java:282) at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:319) at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) But if it did have the key in the right place, these would be the keys in the ide-config.properties file (which will probably change to be esb-specific and "integrationstack.esb.examples.url"): integrationstack.examples.url|jbosstools|4.2=http://github.com/jbosstools... integrationstack.examples.url|devstudio|8.0=http://github.com/jbosstools/... > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > -------------------------------------------------------- > > Key: JBTIS-83 > URL: https://issues.jboss.org/browse/JBTIS-83 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.0.0 > Reporter: Len DiMaggio > Assignee: Brian Fitzpatrick > Fix For: 4.0.0 > > Attachments: jbtis-project-examples-community-7.1.xml > > > JBoss ESB (aka SOA-P 5) Examples Need Updating/Migration > Steps as defined by Nick (thanks Nick!): > a) the contents of the examples are in a former employee's SVN workspace > and haven't been updated since a couple of years. They don't really work > as well as they could. > b) the examples are all mostly duplicated in the quickstarts folder that > ships with SOA-P 5.3.1. See > https://bugzilla.redhat.com/show_bug.cgi?id=951677 and > https://issues.jboss.org/browse/JBTIS-62 > Basically, we need to: > * fix the quickstarts in SOA-P 6 so they ACTUALLY WORK as importable > eclipse projects (merge in contents from duplicate examples in Denny's > workspace). Could decide to backport to 5.3 if there's a 5.3.2 planned; > if not, no great need. > * copy the older examples that are not already in SOA-P 5.3 - the ones > that are *exclusively* in Denny's workspace - into SOA-P 6 so they'll be > available there. > * update the BPEL Examples guide as needed > * document the fact that these examples are no longer available as > importable zipped example projects contributed by a plugin, but rather > as already-unpacked projects nested within the SOA-P runtime zip -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17735) JAX-RS Application wizard: double comments in generated class

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17735?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17735: --------------------------------------------- just to clarify - the first section is mainly for license/author info. The second is for class. And it is all configurable in the java preferences. > JAX-RS Application wizard: double comments in generated class > ------------------------------------------------------------- > > Key: JBIDE-17735 > URL: https://issues.jboss.org/browse/JBIDE-17735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.2.0.CR1 > > > JAX-RS Application class looks quite unusual, when is generated using JAX-RS Application wizard with option generate comments into default package. > {code} > @ApplicationPath("/rest") > /** > * > */ > /** > * @author rrabara > * > */ > public class App extends Application { > } > {code} > When it is generated into user defined package, then there is just one java doc comment: > {code} > @ApplicationPath("/rest") > /** > * @author rrabara > * > */ > public class App extends Application { > } > {code} > However, shouldn't the comment be above the annotation? It seems that it's the preferred way (e.g. see examples http://docs.oracle.com/javase/tutorial/java/annotations/predefined.html) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16329) Support JAX-RS 2.0

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16329?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-16329. ----------------------------------- Verified with JBDS 8.0.0 Beta3-v20140722-2011-B194 > Support JAX-RS 2.0 > ------------------ > > Key: JBIDE-16329 > URL: https://issues.jboss.org/browse/JBIDE-16329 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta3 > > > Support new JAX-RS 2.0 API, and including at the validation level where there should be no false positives when Facet version is 2.0. > Validators and reported error messages may need to be splitted per facet version. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3048) Could com.jboss.devstudio.core.central plugin inherit values in currentversion.properties from parent & root pom instead of hardcoding it?

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3048?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3048. ------------------------------- Not much to be verified by QE here I suppose. Closing. > Could com.jboss.devstudio.core.central plugin inherit values in currentversion.properties from parent & root pom instead of hardcoding it? > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3048 > URL: https://issues.jboss.org/browse/JBDS-3048 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, central > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 8.0.0.Beta3 > > > I see a new file was added after Beta2, on Apr 22: > {code:title=https://github.com/jbdevstudio/jbdevstudio-product/commit/30bec7071c11b2bfd941bde70093b5471af408cb#diff-62d4ce348c909d0dbe2c122f6b51d959R32} > default.version=8.0.0.Beta2 > version=${devstudio.version} > {code} > Since this file will need to be manually updated w/ every milestone, I was wondering if we could simply pull the value out of the parent pom & root pom, which inherit these values: > {code} > ${project version} = 8.0.0-SNAPSHOT > ${BUILD_ALIAS} = Beta3 > {code} > Then with some minor string manipulation you can produce the correct string, 8.0.0.Beta3. > (I have maven/ant code to do this, but you're in Java so YMMV.) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17448) repository-utils should allow skipping generation of web content

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17448?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17448. -------------------------------- > repository-utils should allow skipping generation of web content > ---------------------------------------------------------------- > > Key: JBIDE-17448 > URL: https://issues.jboss.org/browse/JBIDE-17448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Robert Munteanu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta3 > > > I'm using the repository-utils:generate-repository-facade goal to associate additional p2 update sites to my own update site. I'm not interested in generating an index.html file for it, but the default is to generate an update site with a JBoss layout. > Rather than providing my own index.html template, I'd prefer to skip the generation of web content altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17735) JAX-RS Application wizard: double comments in generated class

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17735?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-17735. ----------------------------------- Resolution: Won't Fix Upstream bug on Eclipse.org was marked as 'RESOLVED WONTFIX' : https://bugs.eclipse.org/bugs/show_bug.cgi?id=438759 > JAX-RS Application wizard: double comments in generated class > ------------------------------------------------------------- > > Key: JBIDE-17735 > URL: https://issues.jboss.org/browse/JBIDE-17735 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.2.0.CR1 > > > JAX-RS Application class looks quite unusual, when is generated using JAX-RS Application wizard with option generate comments into default package. > {code} > @ApplicationPath("/rest") > /** > * > */ > /** > * @author rrabara > * > */ > public class App extends Application { > } > {code} > When it is generated into user defined package, then there is just one java doc comment: > {code} > @ApplicationPath("/rest") > /** > * @author rrabara > * > */ > public class App extends Application { > } > {code} > However, shouldn't the comment be above the annotation? It seems that it's the preferred way (e.g. see examples http://docs.oracle.com/javase/tutorial/java/annotations/predefined.html) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17797) BeanParam: removal of @QueryParam/@MatrixParam annotation from field in Bean class is not reflected in JAX-RS Explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17797?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17797: --------------------------------------- [~rrabara], Can you verify that the bug is fixed on your machine ? Thanks. > BeanParam: removal of @QueryParam/@MatrixParam annotation from field in Bean class is not reflected in JAX-RS Explorer > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17797 > URL: https://issues.jboss.org/browse/JBIDE-17797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBoss WebServices Tools 1.7.0.CR1-v20140702-2329-B563 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17797) BeanParam: removal of @QueryParam/@MatrixParam annotation from field in Bean class is not reflected in JAX-RS Explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17797?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17797: ------------------------------------- Assignee: Radoslav Rábara (was: Xavier Coulon) > BeanParam: removal of @QueryParam/@MatrixParam annotation from field in Bean class is not reflected in JAX-RS Explorer > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-17797 > URL: https://issues.jboss.org/browse/JBIDE-17797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Environment: JBoss WebServices Tools 1.7.0.CR1-v20140702-2329-B563 > Reporter: Radoslav Rábara > Assignee: Radoslav Rábara > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17877) Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17877?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-17877: --------------------------------------- [~dgolovin], Can you provide me with steps to reproduce this bug (if it still occurs) ? Thanks. > Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17877 > URL: https://issues.jboss.org/browse/JBIDE-17877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > Exception below was fixed by checking instance of target obect before casting to IType see JBIDE-17716 and skipping the rest of the code. > Do we need to do something extra in this case? > {code} > org.jboss.tools.common > Error > Mon Jun 30 12:28:44 CEST 2014 > org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType > org.jboss.tools.common.validation.JBTValidationException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200) > at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) > Caused by: java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType > at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:79) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.getReturnType(JdtUtils.java:1143) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1067) > at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:1037) > at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.recordAST(CompilationUnitsRepository.java:112) > at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.getAST(CompilationUnitsRepository.java:76) > at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:413) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17412) An internal error occurred during: "Refreshing JBoss Tutorials...".

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17412?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-17412. ------------------------------ I didn't stumble onto this error in JBT 4.2.0.Beta3b. Closing. > An internal error occurred during: "Refreshing JBoss Tutorials...". > ------------------------------------------------------------------- > > Key: JBIDE-17412 > URL: https://issues.jboss.org/browse/JBIDE-17412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta3 > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Fix For: 4.2.0.Beta3 > > > I get the following error when opening JBT with Central enabled: > {code} > java.lang.NullPointerException > at java.lang.StringBuilder.<init>(StringBuilder.java:109) > at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getFullKey(VersionPropertiesProvider.java:232) > at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.lookupValue(VersionPropertiesProvider.java:202) > at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:154) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getPluginSites(ProjectExampleUtil.java:147) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getSites(ProjectExampleUtil.java:282) > at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:319) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:53) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > {code} -- 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 July 2014