Santiago.,
Can we pull the FCS jars from here
http://kohsuke.sfbay.sun.com/hudson/job/jaxws-ri/
The current WAR file is built with deletgate=true but there are no jars
in WSpex-as.war , if we bundle
this with the build, like we do with tango, it should use the latest FCS
code rather than the appserver
bundle.
/s
Santiago Pericas-Geertsen wrote:
>
> On Aug 1, 2006, at 9:43 PM, Sameer Tyagi wrote:
>
>> WSPex generates the war already for the Fcs branch WSpex-as.war,
>> We just need to run a test with that driver in the japex config file...
>
>
> Right, so adding these new drivers should take just a second.
> Currently, the Japex drivers for JAX-WS 2.0 use the version bundled
> in Glassfish. If we want to test a more recent version, we'll need to
> update the benchmark to generate the WSpex-as.war with the latest
> runtime in it.
>
> -- Santiago
>
>> Kohsuke Kawaguchi wrote:
>>
>>>
>>> Currently, we only see WSIT vs JAX-WS rearch (presumably to monitor
>>> the regression in WSIT.)
>>>
>>> Can we also add JAX-WS 2.0 FCS to the mix, so that we can keep
>>> track of any regression in the whole rearch stack vs the baseline?
>>> This is also going to be a good material when we talk about this
>>> thing in public.
>>>
>>> I know it's just a matter of tweaking japex driver configuration,
>>> but Santiago, I thought you'd be able to do it quickly :-)
>>>
>>>
>>> (and I'm planning to generate charts from series of WSPex runs in
>>> Hudson, just like we do for unit tests.)
>>>
>>
>> --
>>
>> ----------------------------------------------------------------------
>> --------
>> Accessline: 1-877-325-9504 Internal: x51601
>> Timezone : EDT - Eastern Standard Time, GMT -5:00
>> AIM : sameersjc
>> Blog : blogs.sun.com/sameert
>>
>>
>
>
--
------------------------------------------------------------------------------
Accessline: 1-877-325-9504
Internal: x51601
Timezone : EDT - Eastern Standard Time, GMT -5:00
AIM : sameersjc
Blog : blogs.sun.com/sameert