harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stepan Mishura" <stepan.mish...@gmail.com>
Subject Re: [testing] AXIS2 client-server scenario to integrate into new buildtest
Date Fri, 06 Apr 2007 03:51:53 GMT
On 4/4/07, Ilya Neverov wrote:
> Stepan,
>
> I agree with you - such an improvement of the test scenario
> configuring feature will add flexibility and it can solve some
> problems in a complex environment.
>

One more question: Currently I'm looking for a way how to eliminate
antcontib usage in the proposed framework. Is it possible to avoid
using antcontib's tasks in adaptor.xml?

Thanks,
Stepan.

> It will take some time for me to identify the best way for configuring
> service port number in the axis2_app. I'll try to provide a patch in
> the HARMONY-3538 ASAP.
>
> --
> Thank you.
> Ilya Neverov
>
> On 4/3/07, Stepan Mishura <stepan.mishura@gmail.com> wrote:
> > On 4/2/07, Ilya Neverov wrote:
> > > > Have you run the test scenario with CC? Is there any issue with 8080 port?
> > >
> > > Yes, CC occupies port 8080 by default so I got failures at first time.
> > > I changed CC launcher arguments to
> > >      -webport 8010
> > >
> > > and it solved the problem. I think that 8080 is a popular number for
> > > default port among many applications so for testing purposes better is
> > > to change the port used by CC :)
> > >
> >
> > I think that we should also try to set up another port for testing the
> > app. At least I see the  following reasons for this:
> > 1) CC may run several testing scenarios in a queue, for example,
> > TomCat - Jetty - AXIS2. As far as I understand if all tested apps use
> > the same port (i.e. 8080) it is not guaranteed that OS release the
> > port before CC start executing the next scenario in the queue.
> > 2) There may be app installed on machine that uses the port (8080) and
> > it may be undesirable to reconfigure it. So we should have opportunity
> > to set up a testing scenario to use any available port number.
> >
> > Thanks,
> > Stepan.
> >
> > > See line 130 in the BT/build.xml:
> > >            <arg line="-configfile ${cc.config.file} -webapppath
> > > ${ext.cc.location}/webapps/cruisecontrol -jmxport 8000 -webport
> > > 8010"/>
> > >
> > > Regards.
> > > -Ilya
> > >
> > > On 4/2/07, Stepan Mishura <stepan.mishura@gmail.com> wrote:
> > > > On 4/1/07, Ilya Neverov wrote:
> > > > > Hi,
> > > > >
> > > > > I tried to use new BT infrastructure proposed in the
> > > > >      https://issues.apache.org/jira/browse/HARMONY-3501
> > > > >
> > > > > to automate setup and run of AXIS2 client-server test scenario -
it
> > > > > appears to be very useful. With rather small adaptor.xml and
> > > > > parameters.xml I got an automation of  fetching binaries and setting
> > > > > infrastructure.
> > > > >
> > > > > The AXIS2 scenario's bundle is attached in the
> > > > >      http://issues.apache.org/jira/browse/HARMONY-3538
> > > > >
> > > >
> > > > Have you run the test scenario with CC? Is there any issue with 8080 port?
> > > >
> > > > Thanks,
> > > > Stepan.
> > > >
> > > > > where some description of the scenario is provided.
> > > > >
> > > > > The scenario works OK on Windows with recent Harmony build both on
> > > > > server and clien sides. I'll check its behavior with Harmony on Linux
> > > > > a bit later.
> > > > >
> > > > > --
> > > > > Thank you.
> > > > > Ilya Neverov


-- 
Stepan Mishura
Intel Enterprise Solutions Software Division

Mime
View raw message