Everything looks fine now. Thanks (-:
Cheers,
Jürgen.
-Original Message-
From: Luciano Resende [mailto:[EMAIL PROTECTED]
Sent: Monday, February 25, 2008 12:33 AM
To: tuscany-user@ws.apache.org
Subject: Re: Build process fails on german system
I have added the workaround under revision
Luciano Resende wrote:
In this particular sample scenario, what if we always set the system
property in case of a SecurityException ? This would avoid issues in
multiple/different languages.
It feels like a hack, as it could pick up the wrong exception condition.
Despite this, I think it's the
I have added the workaround under revision #630706.
Jürgen, let me know if you still have other issues.
On Sun, Feb 24, 2008 at 12:28 PM, Simon Nash [EMAIL PROTECTED] wrote:
Luciano Resende wrote:
In this particular sample scenario, what if we always set the system
property in case of a
In this particular sample scenario, what if we always set the system
property in case of a SecurityException ? This would avoid issues in
multiple/different languages.
On Wed, Feb 20, 2008 at 9:23 AM, Mike Edwards
[EMAIL PROTECTED] wrote:
Hmm, this looks like one of the those flaws in Java
Hi,
Could you please let me know what was the exception you had to modify ?
Of course. Here's the diff, the file is in
java\sca\samples\calculator-implementation-policies\src\test\java\calculator\
Index: CalculatorTestCase.java
Hmm, this looks like one of the those flaws in Java exceptions - there
is no way of having something like a number to uniquely identify an
exception beyond its class - using strings is a bad idea, for exactly
this issue with language conversions.
This has led to the message string being used
