[JBoss JIRA] (JBIDE-15592) Provide JAX-RS Parameters type validation
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15592?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-15592.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140722-2011-B194
> Provide JAX-RS Parameters type validation
> -----------------------------------------
>
> Key: JBIDE-15592
> URL: https://issues.jboss.org/browse/JBIDE-15592
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta2
>
>
> From JAX-RS 1.1 spec (chap 3.2):
> {quote}
> 1. Primitive types.
> 2. Types that have a constructor that accepts a single String argument.
> 3. Types that have a static method named valueOf or fromString with a single String argument that return an instance of the type. If both methods are present then valueOf MUST be used unless the type is an enum in which case fromString MUST be used.
> 4. List<T>, Set<T>, or SortedSet<T>, where T satisfies 2 or 3 above.
> {quote}
> JAX-RS 2.0 introduced the notion of ParamConverterProvider:
> {quote}
> Valid parameter types for each of the above annotations are listed in the corresponding Javadoc, however in general (excluding @Context) the following types are supported:
> 1. Types for which a ParamConverter is available via a registered ParamConverterProvider. See Javadoc for these classes for more information.
> 2. Primitive types.
> 3. Types that have a constructor that accepts a single String argument.
> 4. Types that have a static method named valueOf or fromString with a single String argument that return an instance of the type. If both methods are present then valueOf MUST be used unless the type is an enum in which case fromString MUST be used1.
> 5. List<T>, Set<T>, or SortedSet<T>, where T satisfies 3 or 4 above.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16753) Provide support for server-side Filters and Interceptors
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16753?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-16753.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140722-2011-B194
> Provide support for server-side Filters and Interceptors
> --------------------------------------------------------
>
> Key: JBIDE-16753
> URL: https://issues.jboss.org/browse/JBIDE-16753
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta1
>
>
> (See JAX-RS 2.0 spec., Chap.6)
> *Filters and Interceptors interfaces*
> As far as server-side JAX-RS is concerned, 4 types of interceptors should be support in the tooling:
> {code}
> public interface ContainerRequestFilter {
> void filter(ContainerRequestContext requestContext) throws IOException;
> }
> public interface ContainerResponseFilter {
> void filter(ContainerRequestContext requestContext,
> ContainerResponseContext responseContext) throws IOException;
> }
> public interface ReaderInterceptor {
> Object aroundReadFrom(ReaderInterceptorContext context)
> throws java.io.IOException, javax.ws.rs.WebApplicationException;
> public interface WriterInterceptor {
> void aroundWriteTo(WriterInterceptorContext context)
> throws java.io.IOException, javax.ws.rs.WebApplicationException;
> {code}
> User-defined Interceptors should implement one or more of those interfaces and *should* be annotated with {{@Provider}} to be automatically discovered. Without such annotation, they should be configured in the Application
> Optionally, user-defined ContainerRequestFilter can also be annotated with {{@PreMatching}} to indicate that it should be executed upon receiving a client request but before a resource method is matched
> *Binding*
> {quote}
> Global binding is the default type of binding. A filter or interceptor that has no annotations is assumed to be bound globally, i.e. it applies to all the resource methods in an application. Like any other provider, a filter or interceptor can be registered manually (e.g., via Application or Configuration) or be discovered automatically. Note that for a filter or interceptor to be automatically discovered it MUST be annotated with @Provider.
> A filter or interceptor can be associated with a resource class or method by declaring a new binding annota- tion à la CDI. These annotations are declared using the JAX-RS meta-annotation @NameBinding and are used to decorate both the filter (or interceptor) and the resource method or resource class.
> {quote}
> For example:
> {code}
> @Provider
> @Logged
> class LoggingFilter implements ContainerRequestFilter,
> ContainerResponseFilter {
> ...
> }
> @Path("/")
> public class MyResourceClass {
> @Logged
> @GET
> @Produces("text/plain")
> @Path("{name}")
> public String hello(@PathParam("name") String name) {
> ...
> }
> }
> @NameBinding
> @Target({ ElementType.TYPE, ElementType.METHOD })
> @Retention(value = RetentionPolicy.RUNTIME)
> public @interface Logged { }
> {code}
> In this particular case, the binding annotation should be detected (same way as HTTP Methods) and the tooling should provide a way to navigate between the resource class or resource method and the associated/bound provider.
> {quote}
> Binding annotations can also be applied to resource classes and Application subclasses. Binding annota- tions that decorate resource classes apply to all resource methods defined in them.
> {quote}
> In that case,
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16752) Provide validation for JAX-RS 2.0 Interceptors and Filters (with Name Binding)
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16752?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-16752.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140722-2011-B194
> Provide validation for JAX-RS 2.0 Interceptors and Filters (with Name Binding)
> ------------------------------------------------------------------------------
>
> Key: JBIDE-16752
> URL: https://issues.jboss.org/browse/JBIDE-16752
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta1
>
>
> *Interceptor bindings*
> {quote}
> A filter or interceptor class can be decorated with multiple binding annotations. In this case, in accordance with the semantics described in CDI, all those annotations must be present in the resource class or method for the binding to be established. For example, if LoggingFilter is defined as follows:
> {quote}
> {code}
> @Provider
> @Logged @Verbose
> class LoggingFilter implements ContainerRequestFilter,
> ContainerResponseFilter {
> ...
> }
> {code}
> {quote}
> then method hello above must be annotated with both @Logged and @Verbose for the binding to be in effect.
> {quote}
> {quote}
> Binding annotations can also be applied to resource classes and Application subclasses. Binding annotations that decorate resource classes apply to all resource methods defined in them.
> {quote}
> This means that validation should not report an error if binding annotation are found on Filters and Resource classes, Resource methods and the Application subclass (if defined)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16825) Provide support for new @BeanParam JAX-RS Annotation
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16825?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-16825.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140722-2011-B194
> Provide support for new @BeanParam JAX-RS Annotation
> ----------------------------------------------------
>
> Key: JBIDE-16825
> URL: https://issues.jboss.org/browse/JBIDE-16825
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Affects Versions: 4.1.1.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta3
>
>
> See JAX-RS Spec Appendix A (p66):
> BeanParam
> {quote}
> Can be used to inject a user-defined bean whose fields and properties may be annotated with JAX-RS param annotations.
> {quote}
> For example:
> {code}
> public class MyBeanParam {
> @PathParam("p")
> private String pathParam;
>
> @MatrixParam("m")
> @Encoded
> @DefaultValue("default")
> private String matrixParam;
>
> @HeaderParam("header")
> private String headerParam;
>
> private String queryParam;
>
> public MyBeanParam(@QueryParam("q") String queryParam) {
> this.queryParam = queryParam;
> }
>
> public String getPathParam() {
> return pathParam;
> }
> ...
> }
> {code}
> then
> {code}
> @POST
> public void post(@BeanParam MyBeanParam beanParam, String entity) {
> final String pathParam = beanParam.getPathParam(); // contains injected path parameter "p"
> ...
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17575) Support JAX-RS annotations on bean properties
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17575?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-17575.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140722-2011-B194
> Support JAX-RS annotations on bean properties
> ---------------------------------------------
>
> Key: JBIDE-17575
> URL: https://issues.jboss.org/browse/JBIDE-17575
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta3
>
>
> {{@PathParam}} and a-like annotations can also be applied on class bean properties. These annotations should be discovered and validation should take those elements into account.
> Until now we only supported fields/
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18010) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18010?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18010:
---------------------------------------
Nick, did you consulted with legal about some cases related to "Copyright (c) 2010-2014 Red Hat, Inc. and others." in files that were originally copied from Eclipse and have " Copyright (c) 2013 IBM Corporation and others" header?
Example https://github.com/jbosstools/jbosstools-arquillian/pull/87/files#diff-16....
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18010
> URL: https://issues.jboss.org/browse/JBIDE-18010
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3114
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17676:
----------------------------------
Sprint: Sprint to CR1 Release
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-attributes.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17978) Need to turn on 'angular'-Tern Module automatically in case of AngularJS is detected on a project
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17978?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17978:
----------------------------------
Sprint: Sprint to CR1 Release
> Need to turn on 'angular'-Tern Module automatically in case of AngularJS is detected on a project
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17978
> URL: https://issues.jboss.org/browse/JBIDE-17978
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
>
> At the moment, a user cannot use Content Assist for Angular.js by default, because the according Tern module isn't turned on by default.
> So, users have to do the following set up in order to use it:
> Add 'AngularJS module to Tern in order to make anguler-related stuff enabled on the project. In order to do that you should enable 'JBoss Experimental configuration' in Window -> Preferences -> General -> Capabilities first, then enable 'angilar' module in Project properties -> Tern -> Modules.
> We shall detect the angular usage on a project and turn that module on automatically.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3078:
--------------------------------
Sprint: Sprint to CR1 Release
> 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
> ---------------------------------------------------------------------
>
> Key: JBDS-3078
> URL: https://issues.jboss.org/browse/JBDS-3078
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 8.0.0.Beta3
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 8.0.0.CR1
>
> Attachments: 128_jbds_icon.png
>
>
> Building locally:
> {code}
> [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site ---
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9054877340821028927/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron489909634983575622/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> {code}
> Building in Jenkins:
> {code}
> [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site ---
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron5040285231221120320/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron8242740933405392439/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico{code}
> Is this a problem?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months