[jbosstools-issues] [JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally

Max Rydahl Andersen (JIRA) issues at jboss.org
Mon Jan 12 10:38:49 EST 2015


    [ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031830#comment-13031830 ] 

Max Rydahl Andersen commented on JBIDE-18900:
---------------------------------------------


imagine you could not edit the startup arguments to your project in eclipse ? Why not just always use the same main class  as defined in your jar projects manifest.mf ? Why would you need something else ?

one simple reasons: What you test/develop is *not* exactly the same as your production deployment settings.

feedhenry is a very good example of this - if we had done what you vote for here using feedhenry in development mode would be impossible for users to do.

Thus being able to customize the start argument are important.

Adding parameters could simply be a field and the field would just be *appended* to the content page; thus:

||content| |start value|parameter value|actual start page||reason||
|null | null | null | index.html | default value for content when null is index.html|
|index.html | null | url=localhost:8088 | index.html?url=localhost:8088 | combine content + parameter value with a ? since content had no ? 
|index.html?cordovamode=true | null | url=blah | index.html?cordovamode=true&url=blah | combine content + parameter value with a & since content contains a ?|
|index.html | cordovatesting.html| url=testing | cordovatesting.html?url=testing | content is ignored since start value is now explicitly set||

 Above are pretty basic and standard behavior of how launch configs or even any custom configuration that likes convention over configuration works.

 about the #1 to #3:

#1: my assumption is that "run cordovasim w/feedhenry" creates an *additional* launchconfig, not just reuses the one "run cordovasim"  uses. Just like when you have test classes in your java project and uses "run junit" it will actually not  reuse the same launchconfiguration if your focus is a different class.

same here - run cordavsim will run the "plain" launch configuration without start page configured, and "run cordovasim w/feedhenry" would create or reuse the launchconfig that has the parameter/start page set.

#2 

start value can either be empty (null) or contain a value empty string or a value (i.e. "startme.html")

At launch:
if start value = null then take content flag value else use the start value
 
#3 
so users will still have to manually toggle between running with or without feedhenry so this does not actually solve the original problem afaics ? 

> CordovaSim: Can't run default FeedHenry app locally
> ---------------------------------------------------
>
>                 Key: JBIDE-18900
>                 URL: https://issues.jboss.org/browse/JBIDE-18900
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cordovasim
>    Affects Versions: 4.2.1.Final
>            Reporter: Ilya Buziuk
>            Assignee: Ilya Buziuk
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: configuration.png, cordovasimFH.png, hello_tom.png, newLaunch.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip
>
>
> Basically, the situation is the following: 
> 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field )
> 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio
> 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail!
> 4. However, there is an option to use *local* server instead of *remote* one
> 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner
> 6. In order to run local server one needs:
> - unpack the app
> - run *npm install .*
> - run *grunt serve*
> Need to find the way to made CordovaSim use this *local* server



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jbosstools-issues mailing list