Matthieu Riou wrote:
I guess that would be me as the fix I did outlined another issue (as
described in the thread Luciano pointed at). So you guys expect to always
have all the tests passing on trunk all the time?
Yes, we do try to keep the tests passing. On the rare occasions where a
change b
I guess that would be me as the fix I did outlined another issue (as
described in the thread Luciano pointed at). So you guys expect to always
have all the tests passing on trunk all the time?
Cheers,
Matthieu
On Thu, Jun 5, 2008 at 12:57 PM, Mike Edwards <
[EMAIL PROTECTED]> wrote:
> Folks,
>
>
Simon Laws wrote:
On Fri, Jun 6, 2008 at 3:33 PM, ant elder <[EMAIL PROTECTED]> wrote:
On Fri, Jun 6, 2008 at 2:49 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
Simon Nash wrote:
I did a recent svn update and rebuild and I'm seeing the following test
error from the helloworld-bpel sample. Are
On Fri, Jun 6, 2008 at 3:33 PM, ant elder <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 6, 2008 at 2:49 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
>
> > Simon Nash wrote:
> >
> >> I did a recent svn update and rebuild and I'm seeing the following test
> >> error from the helloworld-bpel sample. Are oth
On Fri, Jun 6, 2008 at 2:49 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> Simon Nash wrote:
>
>> I did a recent svn update and rebuild and I'm seeing the following test
>> error from the helloworld-bpel sample. Are other people seeing this?
>> Any ideas?
>>
>> Simon
>>
>> I have committed a fix (
Simon Nash wrote:
I did a recent svn update and rebuild and I'm seeing the following test
error from the helloworld-bpel sample. Are other people seeing this?
Any ideas?
Simon
I have committed a fix (or at least a workaround) for this build
break problem. The revision number is r663938.
I
Folks,
Someone has updated the code in SVN since this afternoon - so I am
investigating.
Yours, Mike.
Mike Edwards wrote:
Simon,
I did an SVN update and build of Tuscany earlier this afternoon and I
did not see this failure.
The code currently checked in to the Tuscany SVN was fixed up
Luciano Resende wrote:
I guess this might be related to this thread [1].
[1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg32278.html
Thakns. I saw this and I agree it could be related, but the error
message is different. I was getting the "null local part" message
from an earlier
Simon,
I did an SVN update and build of Tuscany earlier this afternoon and I did not
see this failure.
The code currently checked in to the Tuscany SVN was fixed up to avoid the error listed by Luciano
and certainly seems to work for me.
Is anyone else seeing the same problem that Simon is g
I guess this might be related to this thread [1].
[1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg32278.html
On Thu, Jun 5, 2008 at 12:30 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> I did a recent svn update and rebuild and I'm seeing the following test
> error from the helloworld-bp
I did a recent svn update and rebuild and I'm seeing the following test
error from the helloworld-bpel sample. Are other people seeing this?
Any ideas?
Simon
Running helloworld.BPELHelloWorldTestCase
Completed calling new Process deployment code...
Invoking bpel component : {http://tuscany.ap
OK,
I committed fixes to the BPEL Sample, iTest and implementation code to fix the problems that folks
found in the build.
Sorry that I did not spot all these before I made the previous commit.
Yours, Mike.
Mike Edwards wrote:
Folks,
The problem seems to be with the testcase itself, in my opinion, but
before I go and hack the testcase, I'm posting to the list to see if
anyone knows why the sample is the way it is.
Look at the BPEL process - helloworld.bpel
It contains an import for the WSDL re
The BPEL process was only really processed by the ODE BPEL Engine
before, and looks like they were tolerant to that. The namespace was
there probably from it's original content when we copied from ODE
sample. But note that the BPEL process in the iTests does not have
this issue and they have either
Folks,
The problem seems to be with the testcase itself, in my opinion, but before I go and hack the
testcase, I'm posting to the list to see if anyone knows why the sample is the way it is.
Look at the BPEL process - helloworld.bpel
It contains an import for the WSDL referenced by the proces
Simon Laws wrote:
On Thu, May 8, 2008 at 10:24 AM, Simon Nash <[EMAIL PROTECTED]> wrote:
I just did a full checkout and build. The build failed in the
helloworld-bpel sample with the following exception.
Simon
Running helloworld.BPELHelloWorldTestCase
Tests run: 1, Failures: 0, Errors: 1, S
Folks,
I'll take a look at this - this is new code I checked in yesterday - built OK
for me.
Yours, Mike.
Simon Laws wrote:
On Thu, May 8, 2008 at 10:24 AM, Simon Nash <[EMAIL PROTECTED]> wrote:
I just did a full checkout and build. The build failed in the
helloworld-bpel sample with the
On Thu, May 8, 2008 at 10:24 AM, Simon Nash <[EMAIL PROTECTED]> wrote:
> I just did a full checkout and build. The build failed in the
> helloworld-bpel sample with the following exception.
>
> Simon
>
> Running helloworld.BPELHelloWorldTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
I just did a full checkout and build. The build failed in the
helloworld-bpel sample with the following exception.
Simon
Running helloworld.BPELHelloWorldTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.479 sec <<< FA
ILURE!
testInvoke(helloworld.BPELHelloWorldTestCa
19 matches
Mail list logo
