August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23385) IllegalArgumentException when creating new JSF project

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23385?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23385: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > IllegalArgumentException when creating new JSF project > ------------------------------------------------------ > > Key: JBIDE-23385 > URL: https://issues.jboss.org/browse/JBIDE-23385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.2.AM2 > Environment: Devstudio 10.2.0.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.5.x > > > This is not reproducible allways (~1 out of 10). > When creating new JSF project (File->New->Other.. -> JBoss Tools Web ->JSF Project), sometimes I get > {noformat:title=can not connect() without a document}java.lang.IllegalArgumentException: can not connect() without a document > at org.eclipse.wst.sse.core.internal.FileBufferModelManager.connect(FileBufferModelManager.java:506) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl._incrCount(ModelManagerImpl.java:672) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1327) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.getExistingModelForRead(ModelManagerImpl.java:1274) > at org.jboss.tools.common.text.ext.util.StructuredModelWrapper.init(StructuredModelWrapper.java:64) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.getPageLocale(JSFMessageELCompletionEngine.java:600) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.processMessagePropertySegment(JSFMessageELCompletionEngine.java:553) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveLastSegment(JSFMessageELCompletionEngine.java:426) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:361) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:153) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolve(JSFMessageELCompletionEngine.java:139) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > and > {noformat:title=release was requested on a model that was not being managed} > org.jboss.tools.common.validation.JBTValidationException: release was requested on a model that was not being managed > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:171) > at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:84) > at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.eclipse.wst.sse.core.internal.util.Assert$AssertionFailedException: release was requested on a model that was not being managed > at org.eclipse.wst.sse.core.internal.util.Assert.isNotNull(Assert.java:124) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromRead(ModelManagerImpl.java:1941) > at org.eclipse.wst.sse.core.internal.model.ModelManagerImpl.releaseFromRead(ModelManagerImpl.java:1796) > at org.eclipse.wst.sse.core.internal.model.AbstractStructuredModel.releaseFromRead(AbstractStructuredModel.java:1026) > at org.eclipse.wst.xml.core.internal.document.DOMModelImpl.releaseFromRead(DOMModelImpl.java:880) > at org.eclipse.wst.html.core.internal.document.DOMStyleModelImpl.releaseFromRead(DOMStyleModelImpl.java:44) > at org.jboss.tools.common.text.ext.util.StructuredModelWrapper.dispose(StructuredModelWrapper.java:89) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.getPageLocale(JSFMessageELCompletionEngine.java:627) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.processMessagePropertySegment(JSFMessageELCompletionEngine.java:553) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveLastSegment(JSFMessageELCompletionEngine.java:426) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:361) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolveELOperand(JSFMessageELCompletionEngine.java:153) > at org.jboss.tools.jsf.model.JSFMessageELCompletionEngine.resolve(JSFMessageELCompletionEngine.java:139) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateElOperand(ELValidator.java:397) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateELExpression(ELValidator.java:359) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateEL(ELValidator.java:337) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateFile(ELValidator.java:304) > at org.jboss.tools.jst.web.kb.internal.validation.ELValidator.validateAll(ELValidator.java:241) > at org.jboss.tools.common.validation.ValidatorManager.validateAll(ValidatorManager.java:165) > ... 3 more > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20945) UI scaling messes up the address bar in BrowserSim

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20945?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-20945: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > UI scaling messes up the address bar in BrowserSim > -------------------------------------------------- > > Key: JBIDE-20945 > URL: https://issues.jboss.org/browse/JBIDE-20945 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.Final > Reporter: Jan Richter > Assignee: Ilya Buziuk > Labels: ui-scaling > Fix For: 4.5.x > > Attachments: browsersim.png > > > Setting a higher UI scale factor in your OS breaks the address bar. So far I got this on Windows 10 and Fedora 22 with Gnome. > Here is a screenshot from Windows: > !browsersim.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22377) Jax RS service - Run on Server: default id value is ignored in WS tester

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22377?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22377: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Jax RS service - Run on Server: default id value is ignored in WS tester > ------------------------------------------------------------------------ > > Key: JBIDE-22377 > URL: https://issues.jboss.org/browse/JBIDE-22377 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.4.0.Alpha1 > Reporter: Jan Richter > Assignee: Xavier Coulon > Fix For: 4.5.x > > > I have a project with the following jax-rs service: > {noformat} > @Path("/rest") > public class Service { > @GET > @Path("/{id}") > public String mainService(@PathParam("id") @DefaultValue("0") Integer id, > @MatrixParam("m1") @DefaultValue("m1") String m1, > @QueryParam("q1") @DefaultValue("q1") String q1) { > return id + " " + m1 + " " + q1; > } > > } > {noformat} > When I select 'run on server' on the service endpoint and then invoke the opened service tester, it shows blank id value even when the default is set to 0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-15488: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Web Service Tester doesn't work with https and self-signed certificate > ---------------------------------------------------------------------- > > Key: JBIDE-15488 > URL: https://issues.jboss.org/browse/JBIDE-15488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Juergen Zimmermann > Assignee: Xavier Coulon > Labels: jax-rs > Fix For: 4.5.x > > > If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests): > {code} > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22900) JavaModelException below BeanArchiveDetector.isAnnotatedBean (thrown in JavaElement.newNotPresentException)

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22900?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22900: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > JavaModelException below BeanArchiveDetector.isAnnotatedBean (thrown in JavaElement.newNotPresentException) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22900 > URL: https://issues.jboss.org/browse/JBIDE-22900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Final > Reporter: Automated Error Reporting Bot > Assignee: Viacheslav Kabanovich > Fix For: 4.5.x > > > The following problem was reported via the automated error reporting: > Message: MDBDescFileConst [in MDBDescFileConst.class [in com.siebel.integration.deploy.mdb [in C:\Users\mschaefermeyer\.m2\repository\siebel\siebel\8.1.1.11.8\siebel-8.1.1.11.8.jar]]] does not exist > {noformat} > org.eclipse.jdt.core.JavaModelException: MDBDescFileConst [in MDBDescFileConst.class [in com.siebel.integration.deploy.mdb [in C:\Users\mschaefermeyer\.m2\repository\siebel\siebel\8.1.1.11.8\siebel-8.1.1.11.8.jar]]] does not exist > at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:556) > at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:590) > at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:287) > at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302) > at org.eclipse.jdt.internal.core.BinaryType.getAnnotations(BinaryType.java:185) > at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.isAnnotatedBean(BeanArchiveDetector.java:255) > at org.jboss.tools.cdi.core.CDICoreBuilder.buildJars(CDICoreBuilder.java:426) > at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:236) > at org.jboss.tools.cdi.core.CDICoreBuilder.<init>(CDICoreBuilder.java:98) > at org.jboss.tools.cdi.core.CDICoreNature.load(CDICoreNature.java:420) > at org.jboss.tools.cdi.core.CDICoreNature.resolveStorage(CDICoreNature.java:393) > at org.jboss.tools.cdi.core.CDICoreNature.resolve(CDICoreNature.java:406) > at org.jboss.tools.cdi.core.CDICoreNature$1.run(CDICoreNature.java:338) > at org.jboss.tools.common.model.XJob.runInWorkspace(XJob.java:192) > at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 | > | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 | > | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150901-1347 | 0.13.0.v20150901-1347 | > | org.eclipse.jdt.core | 3.11.0.xx-201604081629-e45 | 3.12.0.v20160516-2131 | > | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.11.1.v20160128-1644 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.0.v20160505-1301 | > | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 | > | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 | > | org.eclipse.wst.jsdt.core | 2.0.0.v201604281930 | 2.0.0.v201604281930 | > | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 | > | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 | > | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 | > | org.jboss.tools.cdi.ui | 1.7.1.Final-v20160330-2256-B84 | 1.7.1.Final-v20160330-2256-B84 | > | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.7.1.Final-v20160408-2358-B112 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 | > | org.jboss.tools.jst.web.kb | 3.8.0.Final-v20160609-2146-B2 | 3.8.0.Final-v20160609-2146-B2 | > Operating Systems: > | Linux | 3.13.0 | 4.6.0 | > | MacOSX | 10.11.5 | 10.11.5 | > | Windows | 5.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571e7579e4b08bd809...] for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23024) [p2diff] Add ability to do binary comparison of IUs

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23024?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23024: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > [p2diff] Add ability to do binary comparison of IUs > --------------------------------------------------- > > Key: JBIDE-23024 > URL: https://issues.jboss.org/browse/JBIDE-23024 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, upstream > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Andre Dietisheim > Fix For: 4.5.x > > > See https://github.com/irbull/p2diff/issues/12 and JBIDE-22968 for context & why this enhancement is a good one. > Currently, only openshift has the potential to include a nested SNAPSHOT jar in the lib/ folder of openshift.client, so the problem is relatively localized. > In future however this may come back and be more urgent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22615) Explorer: Connections should get loaded from extension points

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22615?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22615: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Explorer: Connections should get loaded from extension points > ------------------------------------------------------------- > > Key: JBIDE-22615 > URL: https://issues.jboss.org/browse/JBIDE-22615 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: connection, openshift_v2, openshift_v3 > Fix For: 4.5.x > > > Connections are currently loaded in the core plugins for the v2 and v3 plugins: > * v2 [ExpressCoreActivator#start|https://github.com/jbosstools/jbosstools-opens...] > * v3 [OpenShiftCoreActivator#start|https://github.com/jbosstools/jbosstools-ope...] > We should load these with extension points. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19065) Versionwatch should check if found IUs fall in/out ranges defined in ignore.properties

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19065?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-19065: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Versionwatch should check if found IUs fall in/out ranges defined in ignore.properties > -------------------------------------------------------------------------------------- > > Key: JBIDE-19065 > URL: https://issues.jboss.org/browse/JBIDE-19065 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.2.Final > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 4.5.x > > > Improve report duplicate versions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19403) Remove JSF validation that is covered by Eclipse wst.jsf validation

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19403?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-19403: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > Remove JSF validation that is covered by Eclipse wst.jsf validation > ------------------------------------------------------------------- > > Key: JBIDE-19403 > URL: https://issues.jboss.org/browse/JBIDE-19403 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsf > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.x, 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23492) "What's New" Left menu is not scrollable

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23492?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23492: ------------------------------------- Fix Version/s: 4.5.x (was: 4.4.x) > "What's New" Left menu is not scrollable > ---------------------------------------- > > Key: JBIDE-23492 > URL: https://issues.jboss.org/browse/JBIDE-23492 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.4.1.Final > Reporter: Josef Kopriva > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.5.x > > Attachments: whatsnew-leftmenu.png > > > Left menu on page "What's New" is always on top, so when release (e.g. 4.3.0.Final) have more subitems I cannot see or scroll to release 4.1.2.Final, this item is accessible if I click on release with just a few items. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 August 2017