April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16956) Incorrect id is generated if project name ends with a dot character

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16956?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-16956: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Incorrect id is generated if project name ends with a dot character > ------------------------------------------------------------------- > > Key: JBIDE-16956 > URL: https://issues.jboss.org/browse/JBIDE-16956 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Priority: Trivial > Fix For: 4.6.x > > > 1. Set project name to "a." > ERROR: ID is set to "a.." I guess it should be "a." -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20838) Misleading dialog displayed to user when installing example and dependent packages

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20838?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20838: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Misleading dialog displayed to user when installing example and dependent packages > ---------------------------------------------------------------------------------- > > Key: JBIDE-20838 > URL: https://issues.jboss.org/browse/JBIDE-20838 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR2 > Reporter: Len DiMaggio > Priority: Minor > Fix For: 4.6.x > > Attachments: Screenshot.png > > > Steps to recreate: > * After a clean install, from Central install create a project such as a Java EE project > * Observe the dialog in the attached screenshot - after the required packages are installed the user is returned to Central - as a user I would have expected to have had the project created automatically after the required packages were installed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25287) Jolokia Connection errors are swallowed

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25287?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25287: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Jolokia Connection errors are swallowed > --------------------------------------- > > Key: JBIDE-25287 > URL: https://issues.jboss.org/browse/JBIDE-25287 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Affects Versions: 4.5.0.Final, 4.5.1.AM3 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Labels: jmx, jolokia, openshift > Fix For: 4.6.x > > Attachments: image-2017-10-24-13-30-30-715.png > > > even if it is better than before as we don't have a ClassCastException (see [JBIDE-23869]), as mentioned in [my last comment|https://issues.jboss.org/browse/JBIDE-23869?focusedCommentId=1346...] the error reported by Jolokia when deployed on OpenShift is still swallowed. > I have another use case for which I have: > !image-2017-10-24-13-30-30-715.png|thumbnail! > with stack in log > {noformat} > !ENTRY org.jboss.tools.jmx.core 4 0 2017-10-24 13:27:33.523 > !MESSAGE An error occurred while opening the connection. > !STACK 0 > java.io.IOException: Remote error status=404 (Invalid status of type java.lang.String('Failure') received) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:326) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:115) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > Caused by: org.jolokia.client.exception.J4pRemoteException: Invalid status of type java.lang.String('Failure') received > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:67) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:313) > ... 4 more > {noformat} > although when using a Rest client i have this error which contains far more information: > {noformat} > { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "pods "camel-ose-springboot-xml-3-t99hx" not found", > "reason": "NotFound", > "details": { > "name": "camel-ose-springboot-xml-3-t99hx", > "kind": "pods" > }, > "code": 404 > } > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20771) Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20771?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20771: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Livereload not working with projects hosted on local Server with Content Security Policy (CSP) enabled > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20771 > URL: https://issues.jboss.org/browse/JBIDE-20771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.6.x > > Attachments: csp.png > > > This problem might be treated as an edge case from the first glance, but actually it might have a sufficient impact on Livereload in the short run. *CSP* is sort of security policy which complements *CORS*. However, Content Security Policy and CORS are two separate things. CORS is the web service declaring which apps are authorized to call the service. > Content Security Policy is kind of the opposite: it's the app that declares which services can be called. > Basically, [Content Security Policy|http://www.html5rocks.com/en/tutorials/security/content-security-p...] is supported by new versions on major browsers in order to prevent Cross-site scripting (XSS) attacks. However, this policy restricts the usage of LiveReload to the certain extend. > Steps to reproduce: > 1) Create default *jboss-as-kitchensink-html5-mobile* > 2) Add CSP meta tag > {code} > <meta http-equiv="Content-Security-Policy" content="default-src *; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.js"> > {code} > ^ allow to use jquery (other stuff is hosted locally) > 3) In Preferences (General -> Web Browser) add newest version of chrome and set as default > 4) Run the project on the Local Server (Tomcat) > 5) In the Server View right-click on the hosted project -> Show In -> Web Browser via LiveReload > 6) Edit and save index.html > 7) ERROR: Livereload is broken - CSP has prevented *livereload.js* injection > !csp.png! > N.B. LiveReload will work with the file protocol (right click on index.html -> *Open With* -> *Web Browser with LiveReload*) even with CSP enabled, cause in this case livereload.js is hosted on the same port (35729 by default) as the whole project > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24893) Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24893?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24893: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Feature Request - Development tools - eclipse launch configurations should be possible to be inferred from domain home > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24893 > URL: https://issues.jboss.org/browse/JBIDE-24893 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-platform, server > Affects Versions: 4.5.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Rob Stryker > Priority: Optional > Fix For: 4.6.x > > > Hi, > I believe that eclipse development with wildfly is quite cumbersome at the moment of defining a new wildfly domain runtime, in particular in regard to the resutilng "open launch configurations". > When we consider what happens with weblogic domains, they normally all have a dedicated bin/ folder. > I do the same thing when a create a fresh new wildfly domain, i enrich it with an additional bin/ folder where I pump in scripts to start/stop etc.. the domain. > Where in particular, the start script is created with properties like java options that matter to our deployments. > Weblogic start plugin uses the startWeblogic.cmd in the bin folder. > Naturally, this does not happen on Wildfly because the concept for the bin scripts is different. They are generic and domain independent. > But It would in any case be very nice, if it were possible to have some sort of convention that when the eclipse plugin looks at a stand alone domain, it could at least hunt for some sort of configuration file, such as an .eclipse_launch_parameters config, to override the default settings. > If such a mechanism would exist, i could enhance my create domain logic to pump into such a configuration file the same setting that is use in my start wildfly scripts.bat.sh. > As it stands, every time I create a new runtime I need to open the configuration page. > Go to the launch configurations, remove the heap settings. > And then go to my startup domain scripts, search for the java opts that I care about, and copy them over. > This is quite time wasteful. > It would be extremely helpful to be able to dodge point and click configuration, once I tell wildfly where the folder for my stand alone domain is located. > Many thanks for taking into consideration this enhancement request for widlfly eclipse plugin. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22333) HIDDEN below WtpUtils.evaluateXPathExpression (thrown in DOMParser.parse)

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22333?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22333: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > HIDDEN below WtpUtils.evaluateXPathExpression (thrown in DOMParser.parse) > ------------------------------------------------------------------------- > > Key: JBIDE-22333 > URL: https://issues.jboss.org/browse/JBIDE-22333 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Automated Error Reporting Bot > Assignee: Xavier Coulon > Fix For: 4.6.x > > > The following problem was reported via the automated error reporting: > Message: Error while analyzing web deployment descriptor > {noformat} > HIDDEN: Le type d'élément "url-pattern" doit se terminer par la balise de fin correspondante "</url-pattern>". > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(null:-1) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(null:-1) > at org.jboss.tools.ws.jaxrs.core.wtp.WtpUtils.evaluateXPathExpression(WtpUtils.java:232) > at org.jboss.tools.ws.jaxrs.core.wtp.WtpUtils.getApplicationPath(WtpUtils.java:88) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsWebxmlApplication$Builder.build(JaxrsWebxmlApplication.java:98) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsWebxmlApplication$Builder.build(JaxrsWebxmlApplication.java:80) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processWebDeploymentDescriptorChange(JaxrsMetamodel.java:682) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processResourceChange(JaxrsMetamodel.java:610) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.processAffectedResources(JaxrsMetamodel.java:574) > at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:77) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.7.0.v20150330-2103 | > | org.jboss.tools.ws.jaxrs.core | 1.8.1.Final-v20160331-0952-B76 | 1.8.1.Final-v20160331-0952-B76 | > Operating Systems: > | Linux | 4.4.0 | 4.4.6.fc22 | > | MacOSX | 10.10.5 | 10.10.5 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571a4f45e4b0e9dd9c...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22108) xcodeproj is shown as a directory in Project Explorer

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22108?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22108: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > xcodeproj is shown as a directory in Project Explorer > ----------------------------------------------------- > > Key: JBIDE-22108 > URL: https://issues.jboss.org/browse/JBIDE-22108 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.6.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491074 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8371) Query Parameters View: apply parameter value on focus lost

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8371?page=com.atlassian.jira.plugin... ] Jeff MAURY updated JBIDE-8371: ------------------------------ Fix Version/s: 4.6.x (was: 4.5.x) > Query Parameters View: apply parameter value on focus lost > ---------------------------------------------------------- > > Key: JBIDE-8371 > URL: https://issues.jboss.org/browse/JBIDE-8371 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 3.2.0.CR1 > Reporter: Dmitry Geraskov > Assignee: Koen Aers > Fix For: 4.6.x > > > Test case: > 1. create query in HQL Editor: > from test.Message m where m.id = :id > 2. propulate the parameter in Parameters view > 3. change type to valid(integer) > 4. enter the value, but do not press Enter > 5. Run the query. > The value is not applied and considered as null. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20737) On Linux, non-root user is not able to use auto-detect to access running Docker instance

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20737?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20737: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > On Linux, non-root user is not able to use auto-detect to access running Docker instance > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20737 > URL: https://issues.jboss.org/browse/JBIDE-20737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.3.0.CR1 > Environment: RHEL 7 > OpenJDK 1.8 > Version: 9.0.0.CR1 > Build id: CR1-v20150912-1100-B100 > Build date: 20150912-1100 > CR1 includes: > com.spotify.docker.client_3.1.1.jar > org.eclipse.linuxtools.docker.core_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.docs_1.1.0.201509082008.jar > org.eclipse.linuxtools.docker.ui_1.1.0.201509082008.jar > Reporter: Len DiMaggio > Assignee: Xavier Coulon > Fix For: 4.6.x > > Attachments: nonroot_1.png, nonroot_2.png, nonroot_3.png, root.png > > > On linux, a root user is able to rely on autoconnect to automatically connect to a running Docker instance (at unix:///var/run/docker.sock) > A non-root user is not able to connect. No warning or error is written to the UI/dialog. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23359) Validation of exception handler - handlers must not throw exceptions

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23359?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23359: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Validation of exception handler - handlers must not throw exceptions > -------------------------------------------------------------------- > > Key: JBIDE-23359 > URL: https://issues.jboss.org/browse/JBIDE-23359 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi-extensions > Affects Versions: 4.4.2.AM2 > Reporter: Lukáš Valach > Assignee: Jeff MAURY > Fix For: 4.6.x > > > As stated in the deltaspike documentation, exception handlers must not throw checked exceptions, and should avoid throwing unchecked exceptions. > ??Handlers must not throw checked exceptions, and should avoid throwing unchecked exceptions. Should a handler throw an unchecked exception it will propagate up the stack and all handling done via DeltaSpike will cease. Any exception that was being handled will be lost.?? > I checked that throwing exceptions from handler really causes problems. > I suggest to add validation which could display error when user attempts to throw checked exception and warning when try to throw unchecked exception. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 April 2018