June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20038) Unable to run older Hybrid Mobile projext with CordovaSim

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20038?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-20038: ------------------------------------- I just used default Hybrid Mobile project created with older version of JBDS because I fixed project to be able to run with CordovaSim I do not have it anymore. Testing on Fedora 21 all my old projects run properly with CordovaSim. WIll try tomorrow with Fedora 22 where it was not working. > Unable to run older Hybrid Mobile projext with CordovaSim > --------------------------------------------------------- > > Key: JBIDE-20038 > URL: https://issues.jboss.org/browse/JBIDE-20038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, cordovasim > Affects Versions: 4.3.0.Beta1 > Environment: JBDS Beta1-v20150605-2014-B34 Fedora 22 KDE Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Attachments: cordovasimerror.png > > > When running older Hybrid Mobile project with CordovaSim I'm getting error: > !cordovasimerror.png! > Project doesn't have set Cordova Engine properly. When setting Cordova Engine for project via project preferences dialog I have to select cordova engine many times to get button OK enabled. > Error log: > {noformat} > !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-06-11 10:20:03.754 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/accerror/www/index.html'. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:830) > at org.eclipse.core.internal.resources.File.getContents(File.java:269) > at org.eclipse.core.internal.resources.File.getContents(File.java:260) > at org.jboss.tools.cordovasim.eclipse.servlet.internal.WorkspaceFileServlet.doGet(WorkspaceFileServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > !SUBENTRY 1 org.eclipse.core.resources 4 274 2015-06-11 10:20:03.754 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-06-11 10:20:03.923 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/accerror/www/index.html'. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:830) > at org.eclipse.core.internal.resources.File.getContents(File.java:269) > at org.eclipse.core.internal.resources.File.getContents(File.java:260) > at org.jboss.tools.cordovasim.eclipse.servlet.internal.WorkspaceFileServlet.doGet(WorkspaceFileServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > !SUBENTRY 1 org.eclipse.core.resources 4 274 2015-06-11 10:20:03.923 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !ENTRY org.jboss.tools.browsersim.eclipse 4 0 2015-06-11 10:20:03.924 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > !STACK 1 > org.eclipse.core.internal.resources.ResourceException: Resource is out of sync with the file system: '/accerror/www/index.html'. > at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:830) > at org.eclipse.core.internal.resources.File.getContents(File.java:269) > at org.eclipse.core.internal.resources.File.getContents(File.java:260) > at org.jboss.tools.cordovasim.eclipse.servlet.internal.WorkspaceFileServlet.doGet(WorkspaceFileServlet.java:56) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:808) > at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587) > at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221) > at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127) > at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061) > at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:332) > at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310) > at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257) > at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) > at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) > at java.lang.Thread.run(Thread.java:745) > !SUBENTRY 1 org.eclipse.core.resources 4 274 2015-06-11 10:20:03.925 > !MESSAGE Resource is out of sync with the file system: '/accerror/www/index.html'. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on JBIDE-19641: ------------------------------------------ [~kabirkhan] I'm not sure what problem your recent comments are addressing. My impression was the WFLY-669 fix (https://github.com/emuckenhuber/wildfly/commit/03b0c954143bb61064c6095c6d...) avoids the issue with InputStreamEntry.InMemoryEntry, at least for the call paths JBDS is using. Oh, I see. Your test wasn't using the call path JBDS does. Yes, if you pass in an InputStream to the DeploymentPlan it needs to read the whole thing to determine the size. We should improve that but AFAIK that doesn't impact JBDS. The chunking algorithm I used for sending response streams to the client is smarter. If we can use that while remaining compatible with older servers that would be better. Another option is the unused InputStreamEntry.CachingStreamEntry. Copying to disk makes me vaguely uncomfortable though. > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi... ] Vsevolod Golovanov edited comment on JBIDE-20071 at 6/16/15 9:17 AM: --------------------------------------------------------------------- JBIDE-19688 suggests that "explodiness" may depend on installed project facets. Maybe in this task it would be more correct to make Web Fragment Modules deploy exploded, since e.g. Utility Modules probably don't need that. was (Author: vsevolodgolovanov): JBIDE-19688 suggests that "explodiness" may depend on installed project facets. Maybe in this task it would be enough to make Web Fragment Modules deploy exploded. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3461) Creating bottom-up web service with a client result in error

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3461?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3461: ----------------------------------- Not a thing in the error log and in the log file. > Creating bottom-up web service with a client result in error > ------------------------------------------------------------ > > Key: JBDS-3461 > URL: https://issues.jboss.org/browse/JBDS-3461 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: webservices > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > > When creating a bottom-up web service along with a client using the web service wizard, it will create the service, but on the next step it throws an error saying: 'Selection must be WSDL.' > Note, this does not happen in Eclipse with JBT 4.3.0.Beta1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20071) Allow deploying exploded jars to war/WEB-INF/lib

by Vsevolod Golovanov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20071?page=com.atlassian.jira.plugi... ] Vsevolod Golovanov commented on JBIDE-20071: -------------------------------------------- JBIDE-19688 suggests that "explodiness" may depend on installed project facets. Maybe in this task it would be enough to make Web Fragment Modules deploy exploded. > Allow deploying exploded jars to war/WEB-INF/lib > ------------------------------------------------ > > Key: JBIDE-20071 > URL: https://issues.jboss.org/browse/JBIDE-20071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.3.Final > Environment: JBoss Developer Studio 8.1.0.GA > Reporter: Vsevolod Golovanov > > There were JBIDE-10318, JBIDE-9836 before. They were pretty strict in that deploying expoded JARs in WAR/WEB-INF/lib is not allowed for some reason. The only actual reason seemed to be that the server at the time refused to deploy such structure. Maybe the server was in the wrong? This was fixed in AS7-4704. > Now with Wildfly 8.2.0.Final exploded JARs in WAR/WEB-INF/lib deploy correctly, at least Weld, EJB, JSF seem to work fine. > The main use case for this is creating a modular web application, with different parts implemented in separate projects. Hot deploying of resources, such as Facelets' XHTMLs, is crucial for development. So the JARs need to be exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20087) Automatically integrate the app with FeedHenry

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-20087: ---------------------------------- Summary: Automatically integrate the app with FeedHenry Key: JBIDE-20087 URL: https://issues.jboss.org/browse/JBIDE-20087 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Reporter: Pavol Srna Fix For: 4.3.0.Beta2 There is almost anything I can do in FH cloud with the newly pushed app until I integrate the app with FeedHenry (creating fhconfig.json, downloading feedhenry.js ..) Even the FeedHenry editor doesn't work. It would be super cool if the tooling could integrate the app with FH automatically, however I'm not familiar with FH API if that is even possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20086) [FeedHenry] Layout problems in 'New FeedHenry Application' wizard

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20086?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-20086: ------------------------------- Attachment: git_remote_name_dissapeared.png layout.png > [FeedHenry] Layout problems in 'New FeedHenry Application' wizard > ----------------------------------------------------------------- > > Key: JBIDE-20086 > URL: https://issues.jboss.org/browse/JBIDE-20086 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Beta1 > Reporter: Pavol Srna > Fix For: 4.3.0.Beta2 > > Attachments: git_remote_name_dissapeared.png, layout.png > > > 1) The overall layout is bad > 2) Click on back and next (or rescale), and 'Git remote name' field disappears. > Please see screenshots attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20086) [FeedHenry] Layout problems in 'New FeedHenry Application' wizard

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-20086: ---------------------------------- Summary: [FeedHenry] Layout problems in 'New FeedHenry Application' wizard Key: JBIDE-20086 URL: https://issues.jboss.org/browse/JBIDE-20086 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.3.0.Beta1 Reporter: Pavol Srna Fix For: 4.3.0.Beta2 1) The overall layout is bad 2) Click on back and next (or rescale), and 'Git remote name' field disappears. Please see screenshots attached. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3461) Creating bottom-up web service with a client result in error

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-3461?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBDS-3461: ----------------------------------------- Are you seeing anything in the log? > Creating bottom-up web service with a client result in error > ------------------------------------------------------------ > > Key: JBDS-3461 > URL: https://issues.jboss.org/browse/JBDS-3461 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: webservices > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > > When creating a bottom-up web service along with a client using the web service wizard, it will create the service, but on the next step it throws an error saying: 'Selection must be WSDL.' > Note, this does not happen in Eclipse with JBT 4.3.0.Beta1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3461) Creating bottom-up web service with a client result in error

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBDS-3461?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick reassigned JBDS-3461: --------------------------------------- Assignee: Brian Fitzpatrick > Creating bottom-up web service with a client result in error > ------------------------------------------------------------ > > Key: JBDS-3461 > URL: https://issues.jboss.org/browse/JBDS-3461 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: webservices > Affects Versions: 9.0.0.Beta1 > Reporter: Jan Richter > Assignee: Brian Fitzpatrick > > When creating a bottom-up web service along with a client using the web service wizard, it will create the service, but on the next step it throws an error saying: 'Selection must be WSDL.' > Note, this does not happen in Eclipse with JBT 4.3.0.Beta1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 2015