June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-21822: -------------------------------------- Assignee: (was: Mickael Istria) > Remote invocation problem when deploying and running EAP apps from JBDS > ----------------------------------------------------------------------- > > Key: JBIDE-21822 > URL: https://issues.jboss.org/browse/JBIDE-21822 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, server > Affects Versions: 4.3.0.Final > Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) > Maven home: /opt/apache-maven-3.3.9 > Java version: 1.8.0_74, vendor: Oracle Corporation > Java home: /usr/java/jdk1.8.0_74/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix" > Fedora 23 > Reporter: Michal Jurc > Fix For: 4.5.0.AM1 > > > When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed: > {code} > Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c > at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146) > at com.sun.proxy.$Proxy0.add(Unknown Source) > at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57) > at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38) > {code} > The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS). > I was so far unable to reproduce the issue on other machines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24116) NullPointerException in JSFPromptingProvider.getVariables

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24116?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24116: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > NullPointerException in JSFPromptingProvider.getVariables > --------------------------------------------------------- > > Key: JBIDE-24116 > URL: https://issues.jboss.org/browse/JBIDE-24116 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Reporter: Automated Error Reporting Bot > Fix For: 4.5.0.Final > > > The following problem was reported via the automated error reporting: > Message: > java.lang.NullPointerException: null > at org.jboss.tools.jsf.model.pv.JSFPromptingProvider.getVariables(JSFPromptingProvider.java:268) > at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:144) > at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:103) > at org.jboss.tools.jsf.model.JSFELCompletionEngine.resolveVariables(JSFELCompletionEngine.java:83) > at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:466) > at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolveELOperand(AbstractELCompletionEngine.java:282) > at org.jboss.tools.common.el.core.ca.AbstractELCompletionEngine.resolve(AbstractELCompletionEngine.java:165) > 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.validate(ELValidator.java:278) > at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) > 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) > Bundles: > | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 | > | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.11.2.v20161113-1700 | > | 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.eclipse.wst.xml.ui | 1.1.501.v201501212057 | 1.1.700.v201604272318 | > | org.jboss.tools.common.el.core | 3.7.1.Final-v20160408-2358-B112 | 3.8.3.v20161213-1258 | > | org.jboss.tools.common.text.xml | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160607-2053 | > | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.3.v20161213-1258 | > | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.3.v20161214-1452 | > | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.3.v20161214-1634 | > | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160628-0959 | > Operating Systems: > | Linux | 4.7.10.fc23 | 4.8.8.fc24 | > | MacOSX | 10.11.6 | 10.11.6 | > | Windows | 6.1.0 | 10.0.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/574e5d77e4b06056d20... 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21466) Don't scroll up the software/update list when Enable EA dialog is cancelled

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21466?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-21466: -------------------------------------- Assignee: (was: Mickael Istria) > Don't scroll up the software/update list when Enable EA dialog is cancelled > --------------------------------------------------------------------------- > > Key: JBIDE-21466 > URL: https://issues.jboss.org/browse/JBIDE-21466 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Priority: Optional > Fix For: LATER > > > Central -> software/update -> enable early access -> dialog opens. > Now when the dialog is closed, the software list is refreshed and scrolls to the top. Can it stop doing that when the dialog is cancelled or closed otherwise than with the 'Yes' button? Nothing changes if I don't say yes, so there is no point in refreshing the list, right? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21465) 'Disable some filters' option behaves strangely with 'Show installed'

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21465?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-21465: -------------------------------------- Assignee: (was: Mickael Istria) > 'Disable some filters' option behaves strangely with 'Show installed' > --------------------------------------------------------------------- > > Key: JBIDE-21465 > URL: https://issues.jboss.org/browse/JBIDE-21465 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Priority: Minor > Fix For: 4.5.0.AM1 > > Attachments: filter.png, installed.png > > > I've installed everything from central software/update -> now it says there is nothing to install and gives me an option to disable some filters. Clicking that produces the following dialog: > !filter.png|thumbnail! > The first strange part is, I actually need to uncheck the 'Show installed' checkbox in this dialog to show the installed plugins. It might be technically disabling the filter, but it looks weird. > The second strange thing is, after 'disabling the filter' it shows the installed plugins, but the 'Show installed' checkbox is still unchecked. > !installed.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20765) The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space.

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20765?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-20765: -------------------------------------- Assignee: (was: Mickael Istria) > The JBoss Central connectorDescriptor description field text should be displayed with some type of auto-formatting if it's too large for the label space. > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20765 > URL: https://issues.jboss.org/browse/JBIDE-20765 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central, central-update > Affects Versions: 4.3.0.CR1 > Reporter: Paul Leacu > Priority: Minor > Fix For: 4.5.0.AM1 > > > The JBoss Central connectorDescriptor description field should be displayed with some type of auto-formatting if it's too large for the label space. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19568) Disable the "Check for update" button while a check for update is in progress

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19568?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19568: -------------------------------------- Assignee: (was: Mickael Istria) > Disable the "Check for update" button while a check for update is in progress > ----------------------------------------------------------------------------- > > Key: JBIDE-19568 > URL: https://issues.jboss.org/browse/JBIDE-19568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Fix For: 4.5.0.AM1 > > > while trying to check JBIDE-18559 I clicked "checked for updates" in central and got nothing, not even a dialog. > In error log it was reporting this: > org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/Users/max/code/jbdevstudio/linuxtools-docker/org.eclipse.linuxtools.docker.core/target/. > at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395) > at sun.reflect.GeneratedMethodAccessor97.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.eclipse.oomph.util.ReflectUtil.invokeMethod(ReflectUtil.java:116) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.fail(CachingRepositoryManager.java:284) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager.loadRepository(CachingRepositoryManager.java:191) > at org.eclipse.oomph.p2.internal.core.CachingRepositoryManager$Metadata.loadRepository(CachingRepositoryManager.java:378) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96) > at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:117) > at org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:102) > at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.runModal(PreloadingRepositoryHandler.java:83) > at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > would have expected we told the user about this error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-18654: -------------------------------------- Assignee: (was: Mickael Istria) > run jdeps on our jars to see how dependent we are on api that might go away in Java 9 > ------------------------------------------------------------------------------------- > > Key: JBIDE-18654 > URL: https://issues.jboss.org/browse/JBIDE-18654 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Fix For: 4.3.x, 4.5.0.AM1 > > > Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9. > There is a tool called jdeps that we can use to check for this using the -jdkinternals flag. > https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool > The sooner the better we get this done as it is feedback to the Java 9 team. > If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21466) Don't scroll up the software/update list when Enable EA dialog is cancelled

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21466?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21466: ----------------------------------- Fix Version/s: LATER (was: 4.5.0.AM1) > Don't scroll up the software/update list when Enable EA dialog is cancelled > --------------------------------------------------------------------------- > > Key: JBIDE-21466 > URL: https://issues.jboss.org/browse/JBIDE-21466 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.3.1.Beta2 > Reporter: Jan Richter > Assignee: Mickael Istria > Priority: Optional > Fix For: LATER > > > Central -> software/update -> enable early access -> dialog opens. > Now when the dialog is closed, the software list is refreshed and scrolls to the top. Can it stop doing that when the dialog is cancelled or closed otherwise than with the 'Yes' button? Nothing changes if I don't say yes, so there is no point in refreshing the list, right? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20346) Jts quickstart (EAP 6.4) contains XML validation errors

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20346?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20346: ------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Jts quickstart (EAP 6.4) contains XML validation errors > ------------------------------------------------------- > > Key: JBIDE-20346 > URL: https://issues.jboss.org/browse/JBIDE-20346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples, upstream > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Radim Hopp > Fix For: 4.5.0.AM2 > > > jts quickstart contains XML validation errors after import: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:binding-name'. One of '{"urn:iiop":ejb-name}' is expected. jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 30 XML Problem > {noformat} > {noformat} > Referenced file contains errors (jar:file:/home/rhopp/eclipse/jbdevstudio-9.0.0.Beta2/studio/plugins/org.jboss.tools.as.catalog_3.1.0.Beta2-v20150716-2030-B26.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem > {noformat} > The same error was once reported in JBIDE-17871, but that jira was closed as duplicate (of JBIDE-12990), but this error is not in the original (JBIDE-12990) issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23891) EL syntax error: Expecting Expression on EL string concat operator

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23891?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23891: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > EL syntax error: Expecting Expression on EL string concat operator > ------------------------------------------------------------------ > > Key: JBIDE-23891 > URL: https://issues.jboss.org/browse/JBIDE-23891 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf > Affects Versions: 4.4.2.Final > Environment: Windows 10 > Eclipse Neon.2 (4.6.2) > JBoss Tools 4.4.2.Final (Marketplace) > JavaEE 7 > Reporter: thatsIch thatsIch > Priority: Minor > Fix For: 4.5.0.Final > > > The EL 3.0 specification [1] states > String Concatenation Operator - A += B > To evaluate A += B > ■ Coerce A and B to String. > ■ Return the concatenated string of A and B. > Used on a JSF Tag like > {code:java} > <h:outputText value="#{'foo' += 'bar'}" /> > {code} > leads to following warning: > *EL syntax error: Expecting expression.* > on the *=* part of the *+=* operator. > [1] http://download.oracle.com/otn-pub/jcp/el-3_0-fr-eval-spec/EL3.0.FR.pdf -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017