[ 
https://issues.apache.org/jira/browse/ODE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthieu Riou resolved ODE-271.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.1.1)
                   1.2
         Assignee: Matthieu Riou

Applied a few days ago. Resolving.

> Axis2TestBase: centralize server management in base class
> ---------------------------------------------------------
>
>                 Key: ODE-271
>                 URL: https://issues.apache.org/jira/browse/ODE-271
>             Project: ODE
>          Issue Type: Improvement
>          Components: Axis2 Integration
>    Affects Versions: 1.1.1, 1.2
>            Reporter: Alexis Midon
>            Assignee: Matthieu Riou
>             Fix For: 1.2
>
>         Attachments: ODE-271_1.patch
>
>
> The org.apache.ode.axis2.Axis2TestBase raison d'etre is to embed an ODE 
> server for test purpose. So concrete test classes may deploy processes, 
> invoke operations, etc.
> However as of today the server management is not at the base class level. 
> Subclasses are responsible for starting/stopping the server. And if a test 
> case does not stop the server the next test case to be executed will fail to 
> start the server (since the port is already used etc).
> Moreover management interface is kind of fuzzy (you have to call start to 
> start, but server.stop() to shutdown).
> This fix aims at centralize the server management in the base class.
> Server is started/stopped in JUnit setUp/tearDown methods. So subclasses do 
> not have to worry about anymore.
> Of course if subclasses have to perform custom setUp/tearDown steps, it's 
> their responsability to call the super methods.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to