[JBoss JIRA] (JBIDE-19368) File not deployed to server on Windows
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19368?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19368:
-------------------------------------
[~ljelinko] - The only thing I can think is that the publish is occuring before the workspace had a chance to build the project. This would mean the bin / output folder for your jars is empty, and so the classes aren't present.
I would suggest forcing a build on your project before publishing and see if that fixes the problem. If you want more checks, you should run a build, verify the .class file exists in build/classes, and then execute your publish.
Let me know if this helps at all.
> 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
> 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
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19441) Application Client module 6.0 and JCA Module 1.6 cannot both be selected
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19441?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-19441.
---------------------------------
Fix Version/s: 4.3.0.Alpha2
Resolution: Done
Fixed. The default facet list for eap6.1+ has been changed to be specific per fixed-facet requirement. This means web 3.0 is only the default for web projects, not for all faceted projects. The same for other facet / project types as well.
So for JPA, I've made it so the default facet list is java, jpa, and utility facet. This ensures the JPA project can be deployed. IF the user prefers it to be some other set of facets, he can customize the facets, uncheck the utility, and instead check ejb / web / connector / whatever he wants.
> Application Client module 6.0 and JCA Module 1.6 cannot both be selected
> ------------------------------------------------------------------------
>
> Key: JBIDE-19441
> URL: https://issues.jboss.org/browse/JBIDE-19441
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Sande Gilda
> Assignee: Rob Stryker
> Fix For: 4.3.0.Alpha2
>
>
> To recreate this issue:
> 1. Choose File --> New --> Project --> JPA Project
> 2. Enter a project name and choose a JBoss EAP 6.4 Runtime
> An error appears at the top of the dialog saying:
> Application Client module 6.0 and JCA Module 1.6 cannot both be selected.
> It appears that when you select the runtime, it adds *all* Java EE facets:
> web,ejb,jca,web fragment
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3394:
------------------------------------
I'm happy to ack this JIRA - where are the flags? ;-)
> Use cordova platform downloads from npm
> ---------------------------------------
>
> Key: JBDS-3394
> URL: https://issues.jboss.org/browse/JBDS-3394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Fix For: 9.0.0.Alpha2
>
>
> Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available.
> Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm.
> cordova-ios
> ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ]
> cordova-android
> [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ]
> cordova-wp8
> [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19441) Application Client module 6.0 and JCA Module 1.6 cannot both be selected
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19441?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-19441:
-------------------------------------
So it seems what is happening is as follows:
The wizard (whether dynamic web or JPA project) gets a list of fixed facets. For Dynamic web, this is Java and jst.web. For JPA project, it's Java and jpt.jpa.
It then gets a list of default facets for our runtime. For wildfly, as6, and all previous, we typically just list the default Java version. But for eap6.1, we specifically list a version of each facet. Why? because our EAP 6.1+ runtime expresses 'support' for higher facets even when we'd like the default to be a lower version. This is so users can upversion to higher spec without issue.
Why does this work for dynamic web project on eap6.1+ but not for JPA? Because the framework will automatically remove any facets that 'conflict' with the primary / fixed facets. In the case of a dynamic web project, the fixed facet is jst.web, and so all the others (app-client, ejb, ear, etc) all conflict and are removed. In the case of JPA, none of our defaults conflict with the JPA facet individually; they only conflict with each other. So it adds all of our default facets to the default config, and removes none of them (since none conflict).
I'll be looking into a solution.
> Application Client module 6.0 and JCA Module 1.6 cannot both be selected
> ------------------------------------------------------------------------
>
> Key: JBIDE-19441
> URL: https://issues.jboss.org/browse/JBIDE-19441
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Sande Gilda
> Assignee: Rob Stryker
>
> To recreate this issue:
> 1. Choose File --> New --> Project --> JPA Project
> 2. Enter a project name and choose a JBoss EAP 6.4 Runtime
> An error appears at the top of the dialog saying:
> Application Client module 6.0 and JCA Module 1.6 cannot both be selected.
> It appears that when you select the runtime, it adds *all* Java EE facets:
> web,ejb,jca,web fragment
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19564?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-19564:
-------------------------------------
Assignee: Xavier Coulon
Sprint: Sprint #1 April 2015
> Use background job to detect default connection settings
> --------------------------------------------------------
>
> Key: JBIDE-19564
> URL: https://issues.jboss.org/browse/JBIDE-19564
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: docker
> Affects Versions: 4.3.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Alpha2
>
>
> In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19498) docker container view
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-19498.
-----------------------------------
Resolution: Done
The view shows the creation date instead of the CPU/Mem consumption for now.
> docker container view
> ---------------------
>
> Key: JBIDE-19498
> URL: https://issues.jboss.org/browse/JBIDE-19498
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 4.3.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.3.0.Alpha2
>
> Attachments: container_mockup.bmml, container_mockup.png
>
>
> the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years