[JBoss JIRA] (JBIDE-3235) Missing properties view for servers elements
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3235?page=com.atlassian.jira.plugin... ]
Rob Stryker commented on JBIDE-3235:
------------------------------------
The current double-click behavior is to run the "editFileAction", which opens the file for editing.
Are you suggesting you would prefer the double-click action to be the "changeValueAction" instead, and if the user wishes to edit the file, he should right-click and select "Edit File"?
I can make this happen easily with a 1 line patch.
> Missing properties view for servers elements
> --------------------------------------------
>
> Key: JBIDE-3235
> URL: https://issues.jboss.org/browse/JBIDE-3235
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 3.3.x
>
>
> Before I could directly edit properties for ports in properties view.
> Now I need to right click and choose Change Value and get a non-standard edit in the tree.
> This I could probably live with if I could just double click the value and edit it like in properties view.
> Properties view was though also nice to give other details than just access to edit.
> i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3289:
-------------------------------------
Similar problem is JBIDE-18995, when early access features installed from stable update site without "Enable Early Access" warning dialog.
> JBoss Central proxy wizards need to recognize early access.
> -----------------------------------------------------------
>
> Key: JBDS-3289
> URL: https://issues.jboss.org/browse/JBDS-3289
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.2.GA
> Reporter: Paul Leacu
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 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 resolved JBIDE-18953.
-----------------------------------
Resolution: Done
Change was pushed to 'jbosstools-4.2.x' branch without a PR :/ (but with proper post-push review by [~fbricon])
> 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
>
>
> 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, 3 months
[JBoss JIRA] (JBIDE-18953) Unexpected JAX-RS validation error for client filters
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18953?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-18953:
-------------------------------------
+1 for 4.2.2
> 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
>
>
> 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, 3 months