[JBoss JIRA] (JBIDE-13646) Support for Apache Cordova config.xml
by Stefan Bunciak (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13646?page=com.atlassian.jira.plugi... ]
Stefan Bunciak closed JBIDE-13646.
----------------------------------
Verified in JBoss Tools 4.1.0.Beta1b
> Support for Apache Cordova config.xml
> -------------------------------------
>
> Key: JBIDE-13646
> URL: https://issues.jboss.org/browse/JBIDE-13646
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Gorkem Ercan
> Assignee: Gorkem Ercan
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Tools needs to generate a model out of config.xml to use with various tasks. Also a multipage editor is needed to make it easier for the develoers to modify the config.xml. The model should also provide listeners for changes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14626) Server View, Show In -> ... issues
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14626?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14626:
-------------------------------------
The use-case for remote servers is a known issue and is expected. Since we did not launch the server and do not have a reference to its process, we currently can't show anything for the debug view, and we also cannot disable the action. So for that use case, nothing can be done.
For case 1, what's missing is a bring-to-front... so i'm adding that.
> Server View, Show In -> ... issues
> ----------------------------------
>
> Key: JBIDE-14626
> URL: https://issues.jboss.org/browse/JBIDE-14626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
>
> I can confirm, that 'Show In -> Debug' (JBIDE-13482) now works fine with local servers, but for remote server it still does nothing (even if Debug View hasn't been shown yet).
> Also, 'Show In -> Server Log' do not work neither for local nor remote server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13552) BrowserSim: Ripple integration
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13552?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-13552:
-------------------------------------
[~vpakan], could you create a separate jira for that
> BrowserSim: Ripple integration
> ------------------------------
>
> Key: JBIDE-13552
> URL: https://issues.jboss.org/browse/JBIDE-13552
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Yahor Radtsevich
> Assignee: Yahor Radtsevich
> Fix For: 4.1.0.Beta1
>
> Attachments: captureaudio.png
>
>
> Ripple is an emulator, which provides mobile environment (such as Cordova API) to HTML applications.
> Ripple extension for Chrome is written in HTML/JavaScript with usage of Chrome extensions API and some Chrome-only API. When run as an extension, Ripple looks like a mobile iframe in the center of a browser window, and several controls around this iframe, including Geolocation, Orientation and Messaging. These controls allow to change "answers" for queries to emulated API.
> *On the high level our plan is to:*
> 1. get rid of dependencies to Chrome extensions API and Chrome-only API
> 2. replace the mobile iframe with BrowserSim popup window
> 3. implement missing pieces
> 4. replace some Ripple controls with BrowserSim controls
> 5. integrate our Ripple-BrowserSim simulator in Eclipse
> 6. other issues
> *More details follow:*
> *1. get rid of dependencies to Chrome extensions API and Chrome-only API*
> This includes:
> - allow Ripple code to access {{window}} and {{document}} objects of Cordova applications. _*Resolved* by hosting Ripple and Cordova applications on the same Jetty server_
> - allowing cross-origin XHR from BrowserSim. _We *resolved* this by implementation of a Jetty-based proxy_
> - Web SQL API is deprecated and it is not available in BrowserSim on Windows. _We *resolved* it by our own implementation of this API in pure JavaScript JBIDE-13813._
> - allow to upload files to simulate Cordova Camera API. The problem is that some Chrome API is not available in BrowserSim (an example is {{window.URL.createObjectURL(blob)}}). _We *resolved* it by an upload file servlet in Jetty_
> *2. replace the mobile iframe with BrowserSim popup window*
> - there is bug in SWT which leads to multiple popups being opened instead of one. _*Resolved.* We already found a workaround for it_
> - iframe should be removed from the control page. _*Resolved*. The iframe all JS dependencies to it are removed._
> - need a way to change BrowserSim skin while running as popup. The problem is that when the skin is changing, we loose connection with the parent window. _*Resolved*. Now we refresh the parent window after the skin is changed. After refresh the parent window tries to open a new popup, and we connect already created new skin to it.*_
> *3. implement missing pieces*
> - Compas API does not work in both CordovaSim and original Ripple. *Resolved* actually it works - bad demo sample
> - Capture API (audio and video recording using an external app) does not work in both CordovaSim and original Ripple *Resolved* JBIDE-14300
> - Media API (audio playback and recording) does not work in CordovaSim now (not sure if it works in original Ripple) *Not a bug* JBIDE-14306
> - Bar code scanner? *Resolved* JBIDE-14362
> *4. replace some Ripple controls with BrowserSim controls*
> - the {{backbutton}} event should be fired when user presses the Back button in BrowserSim. _*Resolved*_
> - Ripple's orientation change should be replaced by BrowserSim's one. _*Resolved*_
> *5. integrate our Ripple-BrowserSim simulator in Eclipse*
> - provide an easy way to run our simulator from Eclipse, probably add something like "Open in CordovaSim" toolbar item/context menu *Resolved* JBIDE-14083
> *6. other issues*
> - CordovaSim should show an error if jetty port is not available. _*Resolved*_
> - A bug: if there are two Cordova projects in the workspace with {{index.html}} and we run CordovaSim for both these projects, than only one of the {{index.html}} files may be showed in both cases. The problem is that by default Jetty allows the {{If-modified-since}} header and the file with an earlier modification date will never be returned. _*Resolved* by not returning this header._
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13959) AS7 custom deploy scanner should be removed upon server stop
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13959?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-13959:
--------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> AS7 custom deploy scanner should be removed upon server stop
> ------------------------------------------------------------
>
> Key: JBIDE-13959
> URL: https://issues.jboss.org/browse/JBIDE-13959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
>
> This is something that I noticed before but didn't care too much about.
> But today it prevented me from starting a server, so I think it should be fixed if possible.
> Today when I tried to start an EAP server I got this:
> {code}
> 09:27:02,401 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
> 09:27:05,636 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
> 09:27:05,948 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
> 09:27:13,994 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "deployment-scanner"),
> ("scanner" => "jbosstoolsscanner1")
> ]): java.lang.IllegalArgumentException: JBAS015053: /Users/rasp/jbossqa/JBDS/6.0.1/workspace-354/.metadata/.plugins/org.jboss.ide.eclipse.as.core/jboss-eap-6.0.1/deploy does not exist
> at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.<init>(FileSystemDeploymentService.java:165)
> at org.jboss.as.server.deployment.scanner.DeploymentScannerAdd.execute(DeploymentScannerAdd.java:118)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:313) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_43]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_43]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_43]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]
> 09:27:14,053 ERROR [org.jboss.as.controller.management-operation] JBAS014784: Failed executing subsystem deployment-scanner boot operations
> 09:27:14,060 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 09:27:14,117 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 48ms
> {code}
> What's happening? It's simple, in another install of JBDS, in another workspace, I had this server and used workspace metadata deployment, so a custom deployment scanner was created. But since then I removed the JBDS installation and workspace. But the deployment scanner still remained in the standalone.xml.
> Would it be possible to remove it with server stop? Or do you see any other options here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13959) AS7 custom deploy scanner should be removed upon server stop
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13959?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-13959.
---------------------------------
Resolution: Done
pushed to beta2
> AS7 custom deploy scanner should be removed upon server stop
> ------------------------------------------------------------
>
> Key: JBIDE-13959
> URL: https://issues.jboss.org/browse/JBIDE-13959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta2
>
>
> This is something that I noticed before but didn't care too much about.
> But today it prevented me from starting a server, so I think it should be fixed if possible.
> Today when I tried to start an EAP server I got this:
> {code}
> 09:27:02,401 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
> 09:27:05,636 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
> 09:27:05,948 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
> 09:27:13,994 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "deployment-scanner"),
> ("scanner" => "jbosstoolsscanner1")
> ]): java.lang.IllegalArgumentException: JBAS015053: /Users/rasp/jbossqa/JBDS/6.0.1/workspace-354/.metadata/.plugins/org.jboss.ide.eclipse.as.core/jboss-eap-6.0.1/deploy does not exist
> at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.<init>(FileSystemDeploymentService.java:165)
> at org.jboss.as.server.deployment.scanner.DeploymentScannerAdd.execute(DeploymentScannerAdd.java:118)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:313) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_43]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_43]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_43]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]
> 09:27:14,053 ERROR [org.jboss.as.controller.management-operation] JBAS014784: Failed executing subsystem deployment-scanner boot operations
> 09:27:14,060 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 09:27:14,117 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 48ms
> {code}
> What's happening? It's simple, in another install of JBDS, in another workspace, I had this server and used workspace metadata deployment, so a custom deployment scanner was created. But since then I removed the JBDS installation and workspace. But the deployment scanner still remained in the standalone.xml.
> Would it be possible to remove it with server stop? Or do you see any other options here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-13959) AS7 custom deploy scanner should be removed upon server stop
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13959?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-13959:
--------------------------------
Issue Type: Bug (was: Feature Request)
> AS7 custom deploy scanner should be removed upon server stop
> ------------------------------------------------------------
>
> Key: JBIDE-13959
> URL: https://issues.jboss.org/browse/JBIDE-13959
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.0.Beta1
>
>
> This is something that I noticed before but didn't care too much about.
> But today it prevented me from starting a server, so I think it should be fixed if possible.
> Today when I tried to start an EAP server I got this:
> {code}
> 09:27:02,401 INFO [org.jboss.modules] JBoss Modules version 1.1.3.GA-redhat-1
> 09:27:05,636 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-2
> 09:27:05,948 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) starting
> 09:27:13,994 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([
> ("subsystem" => "deployment-scanner"),
> ("scanner" => "jbosstoolsscanner1")
> ]): java.lang.IllegalArgumentException: JBAS015053: /Users/rasp/jbossqa/JBDS/6.0.1/workspace-354/.metadata/.plugins/org.jboss.ide.eclipse.as.core/jboss-eap-6.0.1/deploy does not exist
> at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService.<init>(FileSystemDeploymentService.java:165)
> at org.jboss.as.server.deployment.scanner.DeploymentScannerAdd.execute(DeploymentScannerAdd.java:118)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:313) [jboss-as-controller-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_43]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_43]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_43]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-2.jar:2.0.0.GA-redhat-2]
> 09:27:14,053 ERROR [org.jboss.as.controller.management-operation] JBAS014784: Failed executing subsystem deployment-scanner boot operations
> 09:27:14,060 FATAL [org.jboss.as.server] JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 09:27:14,117 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.1.GA (AS 7.1.3.Final-redhat-4) stopped in 48ms
> {code}
> What's happening? It's simple, in another install of JBDS, in another workspace, I had this server and used workspace metadata deployment, so a custom deployment scanner was created. But since then I removed the JBDS installation and workspace. But the deployment scanner still remained in the standalone.xml.
> Would it be possible to remove it with server stop? Or do you see any other options here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months