December 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3290) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project

by Mustafa Musaji (JIRA)

Mustafa Musaji created JBDS-3290: ------------------------------------ Summary: Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project Key: JBDS-3290 URL: https://issues.jboss.org/browse/JBDS-3290 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: integration, runtime Affects Versions: 8.0.0.GA Reporter: Mustafa Musaji If you have a POM for a project that defines the following {code} <project> ... <dependencyManagement> <dependencies> <dependency> <groupId>org.jboss.bom</groupId> <artifactId>eap6-supported-artifacts</artifactId> <version>6.3.1.GA</version> <scope>import</scope> <type>pom</type> </dependency> </dependencies> </dependencyManagement> ... <dependencies> <dependency> <groupId>commons-beanutils</groupId> <artifactId>commons-beanutils</artifactId> <scope>provided</scope> </dependency> </dependencies> </project> {code} The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3290) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3290?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3290: ----------------------------- CDW pm_ack: ? CDW release: ? Target Release: 8.0.3.GA > Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project > --------------------------------------------------------------------------------------------------- > > Key: JBDS-3290 > URL: https://issues.jboss.org/browse/JBDS-3290 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: integration, runtime > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > > If you have a POM for a project that defines the following > {code} > <project> > ... > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.jboss.bom</groupId> > <artifactId>eap6-supported-artifacts</artifactId> > <version>6.3.1.GA</version> > <scope>import</scope> > <type>pom</type> > </dependency> > </dependencies> > </dependencyManagement> > ... > <dependencies> > <dependency> > <groupId>commons-beanutils</groupId> > <artifactId>commons-beanutils</artifactId> > <scope>provided</scope> > </dependency> > </dependencies> > </project> > {code} > The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-355) Enable JBDSIS Marketplace entry or entries for product groupings - Luna

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-355?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-355: ---------------------------------- So - to be clear - the list above differs from JBoss Central connectors by: + adding JBoss Fuse Development - removing SOA 5.x Development Would it make things simpler by having the Eclipse Marketplace entries match JBDSIS JBoss Central connectors exactly? All we would need to do is keep SOA 5.x and add JBoss Fuse. Also - please review: https://docs.google.com/a/redhat.com/presentation/d/1DVVAAghJ7w2meTKG9QLA... > Enable JBDSIS Marketplace entry or entries for product groupings - Luna > ----------------------------------------------------------------------- > > Key: JBTIS-355 > URL: https://issues.jboss.org/browse/JBTIS-355 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.0.GA > Reporter: Paul Leacu > Assignee: Nick Boldt > Attachments: jbtis355.png > > > * In JBDS 8.1, add a new com.jboss.devstudio.core.central.feature that packages up com.jboss.devstudio.core.central plugin - JBDS-3210 > ** include this in com.jboss.devstudio.core.feature instead of the plugin? > * enable usage tracking in JBT IS components' MANIFST.MF files - JBTIS-290 > * create four connectors, each based on the content in JBDS IS disco plugin.xml's top four BIG connectors; include com.jboss.devstudio.core.CENTRAL.feature in order to install Central along for the ride - JBTIS-358 > (For JBDS 9, we will look at making the Central feature much smaller so the footprint is significantly smaller - see JBIDE-18734.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18935) Webservices and Rest New and Noteworthy for 4.2.1.Final

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18935?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-18935. --------------------------------- Release Notes Text: No relevant N&N for 4.2.1.Final Resolution: Rejected > Webservices and Rest New and Noteworthy for 4.2.1.Final > ------------------------------------------------------- > > Key: JBIDE-18935 > URL: https://issues.jboss.org/browse/JBIDE-18935 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.2.1.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18935) Webservices and Rest New and Noteworthy for 4.2.1.Final

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18935?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-18935: ------------------------------------- Assignee: Brian Fitzpatrick I only have bugfixes for 4.2.1.Final. What about you ? > Webservices and Rest New and Noteworthy for 4.2.1.Final > ------------------------------------------------------- > > Key: JBIDE-18935 > URL: https://issues.jboss.org/browse/JBIDE-18935 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Alexey Kazakov > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.2.1.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Webservices and Rest is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Webservices and Rest by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Valentin Baciu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Valentin Baciu commented on JBIDE-18953: ---------------------------------------- Hi Xavier, yes, the workaround works. Thank you. > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-18953: --------------------------------------- [~baciuv] Please, let me know if this workaround works for you ;-) Thanks > Unexpected JAX-RS validation error for client filters > ----------------------------------------------------- > > Key: JBIDE-18953 > URL: https://issues.jboss.org/browse/JBIDE-18953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha1 > > > We are using JAX-RS client filters in our project. One of the classes looks like this: > ... > import java.io.IOException; > import javax.ws.rs.client.ClientRequestContext; > import javax.ws.rs.client.ClientRequestFilter; > import javax.ws.rs.client.ClientResponseContext; > import javax.ws.rs.client.ClientResponseFilter; > import javax.ws.rs.ext.Provider; > ... > @Provider > public class ClientFilter implements ClientRequestFilter, ClientRequestFilter > { > ... > } > The class is part of a Dynamic Web Project with JAX-RS support turned on. > The combination of @Provider and either of the ClientRequestFilter or ClientRequestFilter appears to confuse the JAX-RS validator which produces the following error: > The Provider must implement at least one of the following interfaces: javax.ws.rs.ext.MessageBodyReader, javax.ws.rs.ext.MessageBodyWriter, javax.ws.rs.ext.ExceptionMapper, javax.ws.rs.ext.ReaderInterceptor, javax.ws.rs.ext.WriterInterceptor, javax.ws.rs.container.ContainerRequestFilter, javax.ws.rs.container.ContainerResponseFilter or javax.ws.rs.ext.ContextResolver. > I suspect the validator needs to be enhanced to also accept the two client filter interfaces when checking the @Provider annotation? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3256: ----------------------------------- I consider this to be the "basic" requirement for JBoss Tools/JBDS - a JBoss focused set of Eclipse tooling. > JBoss specific Docker Tooling (Basic Integration) > ------------------------------------------------- > > Key: JBDS-3256 > URL: https://issues.jboss.org/browse/JBDS-3256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Reporter: Burr Sutter > Assignee: Andre Dietisheim > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-371) Update JBTIS composites for Luna Beta2

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-371?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-371. ------------------------------ Fix Version/s: 8.0.0.Beta2 Resolution: Done All beta2 components updated. > Update JBTIS composites for Luna Beta2 > -------------------------------------- > > Key: JBTIS-371 > URL: https://issues.jboss.org/browse/JBTIS-371 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 4.2.0.Beta1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.0.Beta2, 4.2.0.Beta2 > > > Catch all for updates to the IS composites for Beta2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-20) aggregate SOA source features into a single site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-20?page=com.atlassian.jira.plugin.s... ] Paul Leacu resolved JBTIS-20. ----------------------------- Fix Version/s: 8.0.0.Beta2 4.2.0.Beta2 Resolution: Done Source bundles now aggregated for all components. > aggregate SOA source features into a single site > ------------------------------------------------ > > Key: JBTIS-20 > URL: https://issues.jboss.org/browse/JBTIS-20 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: releng > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta2, 4.2.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 December 2014