March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19397) unify/merge "Debug As... > Remote Java Application" with JMX vm list

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19397?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-19397 at 3/5/15 3:21 AM: --------------------------------------------------------------------- Please look in our code in jbosstools not the platform. https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... We've had this feature for close to 3 years now: http://docs.jboss.org/tools/whatsnew/core/core-news-3.3.0.M3.html The code that uses the sun code is here: https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... which is the exact same as used in jmx for this: https://github.com/jbosstools/jbosstools-server/blob/master/jmx/plugins/o... was (Author: maxandersen): Please look in our code and in jbosstools not the platform. https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... We've had this feature for close to 3 years now: http://docs.jboss.org/tools/whatsnew/core/core-news-3.3.0.M3.html The code that uses the sun code is here: https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... which is the exact same as used in jmx for this: https://github.com/jbosstools/jbosstools-server/blob/master/jmx/plugins/o... > unify/merge "Debug As... > Remote Java Application" with JMX vm list > -------------------------------------------------------------------- > > Key: JBIDE-19397 > URL: https://issues.jboss.org/browse/JBIDE-19397 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > today we got jmx view that lists running hotspot jvms and allow introspection. > We also have Debug As > Remote Java Application which I believe uses the exact same API but allow for launching a remote java app. > It would be nice if we could make jmx view have a context menu for "connect debugger" that works in similar fashion and even better, have remote java application just use the existing model so we don't have this use of sun api's spread out over two places. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19397) unify/merge "Debug As... > Remote Java Application" with JMX vm list

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19397?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19397: --------------------------------------------- Please look in our code and in jbosstools not the platform. https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... We've had this feature for close to 3 years now: http://docs.jboss.org/tools/whatsnew/core/core-news-3.3.0.M3.html The code that uses the sun code is here: https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/... which is the exact same as used in jmx for this: https://github.com/jbosstools/jbosstools-server/blob/master/jmx/plugins/o... > unify/merge "Debug As... > Remote Java Application" with JMX vm list > -------------------------------------------------------------------- > > Key: JBIDE-19397 > URL: https://issues.jboss.org/browse/JBIDE-19397 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > today we got jmx view that lists running hotspot jvms and allow introspection. > We also have Debug As > Remote Java Application which I believe uses the exact same API but allow for launching a remote java app. > It would be nice if we could make jmx view have a context menu for "connect debugger" that works in similar fashion and even better, have remote java application just use the existing model so we don't have this use of sun api's spread out over two places. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19397) unify/merge "Debug As... > Remote Java Application" with JMX vm list

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19397?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19397: ------------------------------------- I find it very difficult to understand this suggestion. The Debug as -> Remote Java Application, only connects a debugger to servers that were launched with debug flags, specifically -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=1044. If a user has not exposed a debugging port, then the remote java application (or any other implementation, even one I write myself) cannot connect to it to debug. Looking at JavaRemoteApplicationLaunchConfigurationDelegate, I see absolutely no jdk classes or references that overlap in any way with any code in jvmmonitor. A significant amount of the implementation appears to be in org.eclipse.wst.jsdt.debug package, with classes like CFTransportService, packet handshake readings, all sorts of very low level protocol writing. > We also have Debug As > Remote Java Application which I believe uses the exact same API but allow for launching a remote java app. This debug as -> remote java application is, obviously, contributed by platform > It would be nice if we could [...] have remote java application just use the existing model so we don't have this use of sun api's spread out over two places. I have absolutely no idea what you're asking. We do not control the functionality of "Remote Java Application". We also have no existing model that does absolutely anything with the packet protocol used to connect a debugger, so even if we did control the "Remote Java Application" launch config, we cannot "have remote java application just use the existing model". > which I believe uses the exact same API but allow for launching a remote java app. I have no idea where you get this belief from. JVM Monitor's discovering existing jvm's is run through a sun class, yes. But Remote Java Application launch configurations requires a host and a port, does not use any such sun APIs, and seems to be a protocol, fully implemented by eclipse in the org.eclipse.wst.jsdt.debug packages with no use of internal sun jdk classes at all. I did see a few references to strings like "com.sun.jdi.SocketListen", but these seem to be a name of a ListeningConnector found via the Bootstrap.virtualMachineManager().listeningConnectors().iterator(); API, which JDT seems to compile against and not get via reflection or anything. > unify/merge "Debug As... > Remote Java Application" with JMX vm list > -------------------------------------------------------------------- > > Key: JBIDE-19397 > URL: https://issues.jboss.org/browse/JBIDE-19397 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > today we got jmx view that lists running hotspot jvms and allow introspection. > We also have Debug As > Remote Java Application which I believe uses the exact same API but allow for launching a remote java app. > It would be nice if we could make jmx view have a context menu for "connect debugger" that works in similar fashion and even better, have remote java application just use the existing model so we don't have this use of sun api's spread out over two places. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19407) NPE in BeansXmlValidationDelegate

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19407?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19407: -------------------------------------- Fix Version/s: 4.3.0.Alpha2 Assignee: Viacheslav Kabanovich > NPE in BeansXmlValidationDelegate > --------------------------------- > > Key: JBIDE-19407 > URL: https://issues.jboss.org/browse/JBIDE-19407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Alpha2 > > > Test case: > 1. Create CDI Web Project > 2. Open file "beans.xml" > 3. Make follow changes: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <beans xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd"> > <interceptors> > <class>asdfgdfgdfgdgs</class> > </interceptors> > <decorators> > <class>decor</class> > </decorators> > <alternatives> > <stereotype>ste</stereotype> > <class>alt</class> > </alternatives> > </beans> > {code} > 4. Try to see list of quick fixes on problem annotations (text hoover and with ruler action) > FAIL: > {code} > org.jboss.tools.common.validation.JBTValidationException > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) > at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) > at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) > at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) > at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) > at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) > Caused by: java.lang.NullPointerException > at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate$AlternativeClassValidator.getUnknownTypeErrorMessage(BeansXmlValidationDelegate.java:500) > at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate.getType(BeansXmlValidationDelegate.java:282) > at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate.validateTypeBeanForBeansXml(BeansXmlValidationDelegate.java:189) > at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate.validateBeansXml(BeansXmlValidationDelegate.java:131) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:621) > at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:560) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19407) NPE in BeansXmlValidationDelegate

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-19407: ------------------------------------- Summary: NPE in BeansXmlValidationDelegate Key: JBIDE-19407 URL: https://issues.jboss.org/browse/JBIDE-19407 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.3.0.Alpha1 Reporter: Daniel Azarov Test case: 1. Create CDI Web Project 2. Open file "beans.xml" 3. Make follow changes: {code} <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://jboss.org/schema/cdi/beans_1_0.xsd"> <interceptors> <class>asdfgdfgdfgdgs</class> </interceptors> <decorators> <class>decor</class> </decorators> <alternatives> <stereotype>ste</stereotype> <class>alt</class> </alternatives> </beans> {code} 4. Try to see list of quick fixes on problem annotations (text hoover and with ruler action) FAIL: {code} org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:254) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.validate(ReconcileStepForValidator.java:381) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ReconcileStepForValidator.reconcileModel(ReconcileStepForValidator.java:259) at org.eclipse.jface.text.reconciler.AbstractReconcileStep.reconcile(AbstractReconcileStep.java:95) at org.eclipse.wst.sse.ui.internal.reconcile.validator.ValidatorStrategy.reconcile(ValidatorStrategy.java:269) at org.eclipse.wst.sse.ui.internal.reconcile.DocumentRegionProcessor.process(DocumentRegionProcessor.java:321) at org.eclipse.wst.sse.ui.internal.reconcile.StructuredRegionProcessor.process(StructuredRegionProcessor.java:258) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:691) Caused by: java.lang.NullPointerException at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate$AlternativeClassValidator.getUnknownTypeErrorMessage(BeansXmlValidationDelegate.java:500) at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate.getType(BeansXmlValidationDelegate.java:282) at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate.validateTypeBeanForBeansXml(BeansXmlValidationDelegate.java:189) at org.jboss.tools.cdi.internal.core.validation.BeansXmlValidationDelegate.validateBeansXml(BeansXmlValidationDelegate.java:131) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:621) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:560) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) ... 10 more {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18431) consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18431?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18431: ------------------------------------ PR applied & built (https://github.com/jbosstools/jbosstools-aerogear/pull/126 ), as well as my three in JBDS-18432: https://github.com/jbosstools/jbosstools-build-sites/pull/177, https://github.com/jbdevstudio/jbdevstudio-product/pull/278, https://github.com/jbosstools/jbosstools-discovery/pull/269 anything else to be done here? Or can this be resolved? > consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0 > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18431 > URL: https://issues.jboss.org/browse/JBIDE-18431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Should we consider refactoring org.jboss.tools.vpe.cordovasim_3.6.0 to org.jboss.tools.cordovasim_3.7.0 or org.jboss.tools.aerogear.cordovasim_3.7.0, since it's no longer in the VPE project but in the Aerogear project? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18432) consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18432?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18432: ------------------------------------ My three PRs are applied: https://github.com/jbosstools/jbosstools-build-sites/pull/177, https://github.com/jbdevstudio/jbdevstudio-product/pull/278, https://github.com/jbosstools/jbosstools-discovery/pull/269 > consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18432 > URL: https://issues.jboss.org/browse/JBIDE-18432 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Should we consider refactoring org.jboss.tools.vpe.browsersim_3.6.0 to org.jboss.tools.browsersim_3.7.0, since it's no longer in the VPE project but in the Browsersim project? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19406) Faces config validation incorrectly reports error in <validator-class>

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19406?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19406: ----------------------------------- Affects Version/s: 4.2.2.Final (was: 4.3.0.Alpha1) > Faces config validation incorrectly reports error in <validator-class> > ---------------------------------------------------------------------- > > Key: JBIDE-19406 > URL: https://issues.jboss.org/browse/JBIDE-19406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.2.2.Final > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.3.CR1 > > > Validation error message > "validator-class references to %className% that does not extend javax.faces.validator.Validator faces-config.xml" > appears when class %className% correctly implements interface javax.faces.validator.Validator. Validation incorrectly assumes that it is a class to be extended. > see https://bugzilla.redhat.com/show_bug.cgi?id=1178800 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19406) Faces config validation incorrectly reports error in <validator-class>

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19406: -------------------------------------- Summary: Faces config validation incorrectly reports error in <validator-class> Key: JBIDE-19406 URL: https://issues.jboss.org/browse/JBIDE-19406 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf Affects Versions: 4.3.0.Alpha1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Alpha2 Validation error message "validator-class references to %className% that does not extend javax.faces.validator.Validator faces-config.xml" appears when class %className% correctly implements interface javax.faces.validator.Validator. Validation incorrectly assumes that it is a class to be extended. see https://bugzilla.redhat.com/show_bug.cgi?id=1178800 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19406) Faces config validation incorrectly reports error in <validator-class>

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19406?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19406: ----------------------------------- Fix Version/s: 4.2.3.CR1 (was: 4.3.0.Alpha2) > Faces config validation incorrectly reports error in <validator-class> > ---------------------------------------------------------------------- > > Key: JBIDE-19406 > URL: https://issues.jboss.org/browse/JBIDE-19406 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.2.3.CR1 > > > Validation error message > "validator-class references to %className% that does not extend javax.faces.validator.Validator faces-config.xml" > appears when class %className% correctly implements interface javax.faces.validator.Validator. Validation incorrectly assumes that it is a class to be extended. > see https://bugzilla.redhat.com/show_bug.cgi?id=1178800 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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 March 2015