You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "jun aoki (JIRA)" <ji...@apache.org> on 2012/11/17 10:47:12 UTC

[jira] [Created] (OOZIE-1077) standalone execution with jetty

jun aoki created OOZIE-1077:
-------------------------------

             Summary: standalone execution with jetty
                 Key: OOZIE-1077
                 URL: https://issues.apache.org/jira/browse/OOZIE-1077
             Project: Oozie
          Issue Type: Task
          Components: workflow
    Affects Versions: trunk
            Reporter: jun aoki
            Priority: Trivial
             Fix For: trunk


workflowgenerator should be able to run standalone quickly.
jetty has a maven plugin i.e. http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin

and the pom should utilize it, where 
mvn jetty:run-war
runs jetty with wfgen and developers can access at http://localhost:8080/


--
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

[jira] [Updated] (OOZIE-1077) standalone execution with jetty

Posted by "jun aoki (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OOZIE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jun aoki updated OOZIE-1077:
----------------------------

    Attachment: plugin_install.png

Alejandro, thank you for your comment.
I tried mvn gwt:run. It looks a neat GWT practice, though will require a browser plugin. (Screenshot attached)
mvn jetty:run does not require any other software (once you write it in pom.xml).

Do you think jetty comes handy?
                
> standalone execution with jetty
> -------------------------------
>
>                 Key: OOZIE-1077
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1077
>             Project: Oozie
>          Issue Type: Task
>          Components: workflow
>    Affects Versions: trunk
>            Reporter: jun aoki
>            Priority: Trivial
>              Labels: maven, test
>             Fix For: trunk
>
>         Attachments: plugin_install.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> workflowgenerator should be able to run standalone quickly.
> jetty has a maven plugin i.e. http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
> and the pom should utilize it, where 
> mvn jetty:run-war
> runs jetty with wfgen and developers can access at http://localhost:8080/

--
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

[jira] [Commented] (OOZIE-1077) standalone execution with jetty

Posted by "jun aoki (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OOZIE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499494#comment-13499494 ] 

jun aoki commented on OOZIE-1077:
---------------------------------

Alejandro, never mind. I also found http://127.0.0.1:8888/ will show the page without the plugin upon mvn gwt:run, which seems totally equivalent to my jetty idea.
Case closed.
                
> standalone execution with jetty
> -------------------------------
>
>                 Key: OOZIE-1077
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1077
>             Project: Oozie
>          Issue Type: Task
>          Components: workflow
>    Affects Versions: trunk
>            Reporter: jun aoki
>            Priority: Trivial
>              Labels: maven, test
>             Fix For: trunk
>
>         Attachments: plugin_install.png
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> workflowgenerator should be able to run standalone quickly.
> jetty has a maven plugin i.e. http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
> and the pom should utilize it, where 
> mvn jetty:run-war
> runs jetty with wfgen and developers can access at http://localhost:8080/

--
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