[JBoss JIRA] (JBIDE-18959) New Datalist wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18959:
---------------------------------------------
Summary: New Datalist wizard for HTML5 palette
Key: JBIDE-18959
URL: https://issues.jboss.org/browse/JBIDE-18959
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18953:
-----------------------------------
Fix Version/s: 4.2.2.Final
> 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.2.2.Final, 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
[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:
---------------------------------------
[~akazakov], you're right, that could be doable for 4.2.2, too. Sorry about that.
> 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
[JBoss JIRA] (JBIDE-18815) Include freemarker.jar in FreeMarker IDE as maven dependency
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18815?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18815:
----------------------------------
Summary: Include freemarker.jar in FreeMarker IDE as maven dependency (was: Update freemarker.jar in FreeMarker IDE)
> Include freemarker.jar in FreeMarker IDE as maven dependency
> ------------------------------------------------------------
>
> Key: JBIDE-18815
> URL: https://issues.jboss.org/browse/JBIDE-18815
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Alpha1
>
>
> FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18746) Update freemarker.jar in FreeMarker IDE
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18746?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-18746:
----------------------------------
Labels: new_and_noteworthy (was: )
> Update freemarker.jar in FreeMarker IDE
> ---------------------------------------
>
> Key: JBIDE-18746
> URL: https://issues.jboss.org/browse/JBIDE-18746
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Labels: new_and_noteworthy
> Fix For: 4.2.1.CR1
>
>
> FreeMarker IDE still comes with FreeMarker 2.3.18 from 2011. As the plugin uses FreeMarker for parsing templates (for error markers), this means that no constructs introduced since then are recognized by it (there's a quite a few), and also that it doesn't benefit from the error message fixes/improvements made since then.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months