September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18259?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18259: ---------------------------------- Attachment: refresh-mbean.png > Refresh MBean section keeps blinking in the status bar > ------------------------------------------------------ > > Key: JBIDE-18259 > URL: https://issues.jboss.org/browse/JBIDE-18259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > Attachments: refresh-mbean.png > > > When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. > Screenshot: > !refresh-mbean.png! > I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. > A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar

by Martin Malina (JIRA)

Martin Malina created JBIDE-18259: ------------------------------------- Summary: Refresh MBean section keeps blinking in the status bar Key: JBIDE-18259 URL: https://issues.jboss.org/browse/JBIDE-18259 Project: Tools (JBoss Tools) Issue Type: Bug Components: jmx Affects Versions: 4.2.0.CR1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.CR2 When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18259) Refresh MBean section keeps blinking in the status bar

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18259?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18259: ---------------------------------- Description: When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. Screenshot: !refresh-mbean.png! I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. was: When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. > Refresh MBean section keeps blinking in the status bar > ------------------------------------------------------ > > Key: JBIDE-18259 > URL: https://issues.jboss.org/browse/JBIDE-18259 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > When you connect to a local process in the JMX Navigator and then check out some mbeans in the Properties view, there will be a "Refresh MBean section" message blinking in the status bar at the bottom of Eclipse every second or so. > Screenshot: > !refresh-mbean.png! > I understand that the tooling must keep refreshing the mbeans list (probably), but it's annoying to keep blinking in the status bar like this. We should probably remove that message. > A minor issue is that the wording seems odd. Shouldn't it be "Refreshing MBean section..." or something like that? I'm not sure what the convention is here. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16898) no error handling for nonexisting remote home

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16898?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16898: --------------------------------------------- so for some reason server-config is not set I reckon? > no error handling for nonexisting remote home > --------------------------------------------- > > Key: JBIDE-16898 > URL: https://issues.jboss.org/browse/JBIDE-16898 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Downloaded EAP 6.2 via downlod runtimes. > configured it to use remote, entered in bogus name for home folder. > This is in the console log: > "/> > /> > Error: Unable to access jarfile urft/jboss-modules.jar > JBTOOLS_SERVER_START_CMD:JBoss Enterprise Application Platform 6.1+1395830330282:11785 > />" > I would have expected some validation or better info in the console on what users should do now. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17846) Seam configurator doesnt set seam runtime

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17846?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-17846. ------------------------------------ verified in JBDS 8.0.0.CR1-v20140831-0335-B201 > Seam configurator doesnt set seam runtime > ----------------------------------------- > > Key: JBIDE-17846 > URL: https://issues.jboss.org/browse/JBIDE-17846 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.Beta2 > Reporter: Rastislav Wagner > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16042) Server Editor: "Open launch configuration" errors

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16042?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-16042. --------------------------------- Closing as duplicate. > Server Editor: "Open launch configuration" errors > ------------------------------------------------- > > Key: JBIDE-16042 > URL: https://issues.jboss.org/browse/JBIDE-16042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: server_adapter_editor > Fix For: 4.2.0.CR1 > > Attachments: open-launch-config-error.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18258?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-18258: ---------------------------------- Description: When I set up a local server, then a remote server and then I start the local server, I get errors: {code} !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. {code} I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know. was: When I set up a local server, then a remote server and then I start the local server, I get errors: {code} !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. {code} > "Cannot find navigator content extension" when starting a local server after setting up a remote server > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18258 > URL: https://issues.jboss.org/browse/JBIDE-18258 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Critical > Labels: respin-a > Fix For: 4.2.0.CR1 > > > When I set up a local server, then a remote server and then I start the local server, I get errors: > {code} > !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700 > !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. > !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703 > !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. > !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895 > !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. > {code} > I'm not exactly sure how this works, but strangely, the errors are thrown even after I remove the remote server. But they did not occur before I created the remote server. So perhaps it has something to do with the existence of the remote system and not really the remote server itself? I don't know. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18258) "Cannot find navigator content extension" when starting a local server after setting up a remote server

by Martin Malina (JIRA)

Martin Malina created JBIDE-18258: ------------------------------------- Summary: "Cannot find navigator content extension" when starting a local server after setting up a remote server Key: JBIDE-18258 URL: https://issues.jboss.org/browse/JBIDE-18258 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.CR1 Reporter: Martin Malina Assignee: Rob Stryker Priority: Critical Fix For: 4.2.0.CR1 When I set up a local server, then a remote server and then I start the local server, I get errors: {code} !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.700 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.703 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. !ENTRY org.eclipse.ui.navigator 4 0 2014-09-04 11:46:26.895 !MESSAGE Cannot find navigator content extension (using triggerPoints) for object "org.jboss.modules.Main [22362]" parent path: "R/". Check that you have an expression for this object in a navigatorContent triggerPoints or enablement. {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18090) Wrong JAX-RS Filter/Annotation binding problem report

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18090?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-18090. ----------------------------------- Verified with JBDS 8.0.0.CR1-v20140831-0335-B201 > Wrong JAX-RS Filter/Annotation binding problem report > ------------------------------------------------------ > > Key: JBIDE-18090 > URL: https://issues.jboss.org/browse/JBIDE-18090 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > > The JAX-RS validator reports a false problem on Interceptors and Filters with binding annotations, when multiple binding anntotations on the target Resource or Resource Methods are involved. > Eg: > {code} > @Target({ ElementType.TYPE, ElementType.METHOD }) > @Retention(value = RetentionPolicy.RUNTIME) > @NameBinding > public @interface RequestIfNoneMatchBinding { } > {code} > and > {code} > @Target({ ElementType.TYPE, ElementType.METHOD }) > @Retention(value = RetentionPolicy.RUNTIME) > @NameBinding > public @interface CacheInvalidationBinding {} > {code} > with > {code} > @Provider > @PreMatching > @RequestIfNoneMatchBinding > public class RequestIfNoneMatchFilter implements ContainerRequestFilter { > @Override > public void filter(final ContainerRequestContext requestContext) throws IOException { > ... > } > } > {code} > on > {code} > @RequestScoped > @Path("/foo") > public class RestResource { > @GET > @RequestIfNoneMatchBinding > @CacheControlBinding > public Response getAll() { > return Response.ok().build(); > } > } > {code} > The {{RequestIfNoneMatchFilter}} class will have a JAX-RS problem reported while it should not be the case. > The spec mentions that the resource/resource method should be annotated with all the same binding annotations as the Filter/Interceptor, which is the case here. Nothing prevents a resource / resource method to be bound to multiple Filter or Interceptor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3132) Use devstudio.redhat.com instead of devstudio.jboss.com in JBDS usage

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-3132?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-3132. ---------------------------- I couldn't find any reference to devstudio.jboss.com except for one case, where it was in javadoc and it was affecting nothing (and it is reported in JBDS-3009). Closing > Use devstudio.redhat.com instead of devstudio.jboss.com in JBDS usage > --------------------------------------------------------------------- > > Key: JBDS-3132 > URL: https://issues.jboss.org/browse/JBDS-3132 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 8.0.0.CR1 > > > google analytics usage tracking needs updating ot handle the change of domain name. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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