[
https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-21822:
----------------------------------------
The simplest action would be that the quickstart either specifies the eclipse .project to
enforce Eclipse project name in whatever way they are imported, or to have the quickstart
use folder name as project name.
For Easymport, that would be possible to add the ability for the "project
configurator" to compute and return the desired project name, howeve, the API is in
Platform and it's passed API freeze, so it's not something that can be done soon.
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
Assignee: Rob Stryker
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
(v6.4.11#64026)