JBehave
  1. JBehave
  2. JBEHAVE-335

Migrate Web Runner to use Wicket as web application framework

    Details

    • Type: New Feature New Feature
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: web-3.0
    • Component/s: Web Runner
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support.

      From users' point of view the only change would be extend a Wicket Application class to specify configuration and steps instances, instead of a Waffle Registrar.

      A doc page should help in migrating from Registrar to Application class.

        Activity

        Mauro Talevi made changes -
        Field Original Value New Value
        Summary Migrate to Wicket as web application framework Refactor Web Runner to use Wicket as web application framework
        Description Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support.

        Users would extend a Wicket Application class to specify configuration and steps instances, similarly to what done with Waffle Registrar.

        Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wide community support.

        From users' point of view the only change would be extend a Wicket Application class to specify configuration and steps instances, instead of a Waffle Registrar.

        A doc page should help in migrating from Registrar to Application class.
        Mauro Talevi made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        Brian Repko added a comment -

        I have no preference one way or another (Wicket vs Waffle). If you are looking for same features in an action-based framework, then I would suggest Stripes or Play. Component-framework vs Action-framework doesn't really matter to me.

        Show
        Brian Repko added a comment - I have no preference one way or another (Wicket vs Waffle). If you are looking for same features in an action-based framework, then I would suggest Stripes or Play. Component-framework vs Action-framework doesn't really matter to me.
        Mauro Talevi made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Mauro Talevi added a comment -

        Brian, Wicket is not a pure MVC framework, but more a component-oriented one. It plays very nice with Java and rich-client features are
        easier than in other action-based frameworks. Other factors influencing the choice of framework are the community base and the documentation,
        both of which are very wide for Wicket.

        Show
        Mauro Talevi added a comment - Brian, Wicket is not a pure MVC framework, but more a component-oriented one. It plays very nice with Java and rich-client features are easier than in other action-based frameworks. Other factors influencing the choice of framework are the community base and the documentation, both of which are very wide for Wicket.
        Mauro Talevi made changes -
        Summary Refactor Web Runner to use Wicket as web application framework Migrate Web Runner to use Wicket as web application framework

          People

          • Assignee:
            Mauro Talevi
            Reporter:
            Mauro Talevi

            Dates

            • Created:
              Updated:
              Resolved: