[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-18912:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Custom deploy dir with remote server using filesystem operations does not work
> ------------------------------------------------------------------------------
>
> Key: JBIDE-18912
> URL: https://issues.jboss.org/browse/JBIDE-18912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: help_wanted
> Fix For: 4.4.3.AM2
>
>
> This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used).
> Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles.
> I tried this several times and still could not get it to work.
> Perhaps it might be worth to try and get this in the final 4.2.1.Final build?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-20935) Central doesn't scale back after being enlarged on Windows
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20935?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20935:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Central doesn't scale back after being enlarged on Windows
> ----------------------------------------------------------
>
> Key: JBIDE-20935
> URL: https://issues.jboss.org/browse/JBIDE-20935
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Environment: Windows 10
> 250% UI scale
> Reporter: Jan Richter
> Assignee: Ilya Buziuk
> Labels: ui-scaling
> Fix For: 4.4.3.AM2
>
> Attachments: JBossCentral_not-rescaling_2015-10-14_14-39-28.mp4, central.png, screenshot-1.png
>
>
> When I maximize the central tab in eclipse and then restore it, instead of it scaling back to its confined space it stays expanded and adds scrollbars.
> Like so:
> !central.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22290?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22290:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Open via livereload quick access errors when no livereload server is present
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22290
> URL: https://issues.jboss.org/browse/JBIDE-22290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.4.3.AM2
>
>
> The following error is produced while the livereload server is starting:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4522)
> at org.eclipse.swt.SWT.error(SWT.java:4437)
> at org.eclipse.swt.SWT.error(SWT.java:4408)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-20108) Cannot connect to remote server in JMX Navigator - Authentication fails
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20108?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-20108:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Cannot connect to remote server in JMX Navigator - Authentication fails
> -----------------------------------------------------------------------
>
> Key: JBIDE-20108
> URL: https://issues.jboss.org/browse/JBIDE-20108
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> When I try to connect to a remote server via JMX Navigator, it fails on authentication:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2015-06-17 18:07:30.854
> !MESSAGE Error connecting to jmx for server JBoss EAP 6.4 marvin
> !STACK 1
> org.jboss.tools.jmx.core.JMXException: Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:94)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> 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:55)
> Caused by: javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> ... 7 more
> !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2015-06-17 18:07:30.854
> !MESSAGE Authentication against the remote JBoss instance has failed. Please verify your management credentials in the server editor.
> !STACK 0
> javax.security.sasl.SaslException: Authentication failed: the server presented no authentication mechanisms
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:388)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.ssl.JsseConnectedSslStreamChannel.handleReadable(JsseConnectedSslStreamChannel.java:183)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:198)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:333)
> at org.jboss.remotingjmx.RemotingConnector.internalRemotingConnect(RemotingConnector.java:230)
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:151)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:102)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:84)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:202)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:162)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:332)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connect(JBossServerConnection.java:76)
> 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:55)
> {code}
> This is different than JBIDE-19463 where the main problem was the missing runtime and we assumed that otherwise it would work.
> Note: I tried WildFly 8.2, WildFly 9.0.0.CR2, EAP 6.4 and all failed the same way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-21065:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.5.0.AM1)
(was: 4.4.3.AM1)
> Server host name address should not be defaulted during server adapter creation
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21065
> URL: https://issues.jboss.org/browse/JBIDE-21065
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.4.3.AM2
>
>
> I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}.
> This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address.
> Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23651) Incremental publish to remote server throws exception
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23651?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23651:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Incremental publish to remote server throws exception
> -----------------------------------------------------
>
> Key: JBIDE-23651
> URL: https://issues.jboss.org/browse/JBIDE-23651
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.2.Final
> Reporter: Rastislav Wagner
> Fix For: 4.4.3.AM2
>
>
> {code}
> failed to create folder /opt/wildfly/standalone/deployments/jboss-as-kitchensink-html5-mobile.war on host jawa32g2.mw.lab.eng.brq.redhat.com
> {code}
> {code}
> org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error
> at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:596)
> at org.eclipse.rse.internal.services.ssh.files.SftpFileService.createFolder(SftpFileService.java:1103)
> at org.jboss.ide.eclipse.as.rse.core.subsystems.RSEFilesystemController$3.run(RSEFilesystemController.java:107)
> at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.run(BarrierProgressWaitJob.java:85)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> Incremetal publish successfully completes (file is updated) but exception is logged in error because RSEFilesystemController is trying to create a folder on remote server which already exists (was created during full publish)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-19368) File not deployed to server on Windows
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19368?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-19368:
-------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> File not deployed to server on Windows
> --------------------------------------
>
> Key: JBIDE-19368
> URL: https://issues.jboss.org/browse/JBIDE-19368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.2.Final
> Environment: Windows 7, JBDS 4.2.2, EAP 6.4 ER1
> Reporter: Lucia Jelinkova
> Assignee: Lucia Jelinkova
> Priority: Minor
> Fix For: 4.4.3.AM2
>
> Attachments: deployments.zip, jsp-project.zip, workspace.zip
>
>
> Sometimes our automated EAP <-> JBDS compatibility UI tests fail on windows machine because one java file of the tested project is not deployed to the server (and is not in the deployment folder either).
> The tests runs like this:
> # Create server and start it
> # Import project with JSP file from ZIP into the workspace
> # Add server as targeted runtime via Properites
> # Right-click server and via Add/Remove modules add the imported project to the server
> # Open module's web page (right click + open in web browser)
> RESULT: JSP file compilation fails because it is not able to resolve HelloWorld.java class
> I have not seen any errors in server's console (except for the compilation error).
> {code}
> 05:25:04,990 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.4.Final-redhat-1
> 05:25:05,678 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
> 05:25:05,850 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.4.0.Alpha1 (AS 7.5.0.Final-redhat-11) starting
> 05:25:08,568 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.11.GA-redhat-2
> 05:25:08,584 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.11.GA-redhat-2
> 05:25:08,600 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
> 05:25:08,787 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 45) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
> 05:25:08,803 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) JBAS010280: Activating Infinispan subsystem.
> 05:25:08,850 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
> 05:25:08,881 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 36) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
> 05:25:08,928 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
> 05:25:08,975 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 47) JBAS015537: Activating WebServices Extension
> 05:25:09,131 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.1.0.Beta1-redhat-1
> 05:25:09,381 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.3.4.Final-redhat-1
> 05:25:09,584 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
> 05:25:09,600 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
> 05:25:09,725 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.29.Final-redhat-1)
> 05:25:10,334 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 15) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
> 05:25:10,412 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
> 05:25:10,553 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
> 05:25:10,881 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999
> 05:25:10,881 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
> 05:25:10,928 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory W:\workspace\eap-6x-jbds-compatibility-jbosstools-4.2.x-windows\8b0502d6\tests\org.jboss.ide.eclipse.as.ui.bot.test\target\requirements\jboss-eap-6.4\standalone\deployments
> 05:25:11,287 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> 05:25:12,100 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.1.Final-redhat-1
> 05:25:12,272 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 05:25:12,272 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 05:25:12,272 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.Alpha1 (AS 7.5.0.Final-redhat-11) started in 9016ms - Started 152 of 190 services (57 services are lazy, passive or on-demand)
> 05:25:25,990 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jsp-project.war in deployment directory. To trigger deployment create a file called jsp-project.war.dodeploy
> 05:25:26,084 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "jsp-project.war" (runtime-name: "jsp-project.war")
> 05:25:26,881 INFO [org.jboss.web] (ServerService Thread Pool -- 24) JBAS018210: Register web context: /jsp-project
> 05:25:27,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jsp-project.war" (runtime-name : "jsp-project.war")
> 05:25:39,693 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jsp-project].[jsp]] (http-localhost/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: JBWEB004062: Unable to compile class for JSP:
> JBWEB004060: An error occurred at line: 4 in the jsp file: /index.jsp
> HelloWorld cannot be resolved
> 1: <%@ page language="java" import="org.jboss.tools.tests.as.*" errorPage="" %>
> 2: <html>
> 3: <body>
> 4: <%=HelloWorld.sayHello()%>
> 5: </body>
> 6: </html>
> JBWEB004211: Stacktrace:
> at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:69) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:461) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:361) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:339) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:326) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:606) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-11.jar:7.5.0.Final-redhat-11]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
> {code}
> Do you have any idea why this could happen or how to continue with locating the problem?
> I am attaching the imported project as ZIP file, the workspace after import and also the content of deployments folder.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months