For your information XINS 1.0.0
release candidate 3 has
been release. This is probably the lastest
release candidate before XINS 1.0.0 final.
INTRODUCED IN XINS 1.0.0 RELEASE CANDIDATE 3:
* Generation of specification documentation:
bug #1064487: The function name is not written in the examples.
* XINS/Java Client Framework:
- Removed log message
which previously had the ID 2101, since it did not add
information. Previously it was logged right after a call
performed, whether it was successful or not. Replaced
it by a log message
that indicates that a successful XINS
result was received. This message
previously had ID 2111,
but it was never actually logged. Now it is, but
The ID 2111 is now used for a new log message for
exceptions caught while calling the XINS
- Removed log message with ID 2107 (XINS result received,
status code is
considered acceptable) since it not
- Now actually logging message 2109 (Unrecognized
I/O error while calling
SF.net bug #1063672 (XINS call logging: Only first failure
logged). Each individual failure is now logged, per
- Unified translations in the 21xx range.
level of the following log messages to WARNING:
. 2103 (was INFO);
2104 (was INFO);
. 2105 (was INFO);
. 2106 (was INFO);
. 2108 (was
. 2109 (was NOTICE);
. 2111 (was INFO);
2112 (was INFO).
- Added log message 2113: XINS call request
* XINS/Java Common Library:
- Changed the level of
all Logdoc messages in the 'service' group to DEBUG.
Proper logging is the responsibility of the ServiceCaller subclass
UnexpectedExceptionCallException constructor: The 'cause'
is now mandatory.
Wanadoo Nederland BV, http://www.wanadoo.nl
Muiderstraat 1, Postbus
11095, 1001 GB Amsterdam
T : +31 (0)20 535 59