Timeframe for an update to WSDL import utility

Hello Bruneau,

do you have a timeframe for an update to the WSDL import utility? I checked 
http://cc.codegear.com/Item/24535 and the latest version is from dec 06 
which I guess is the one bundled with the december update to Delphi.

I would also like to know if you know when the internal error (triggered by 
code generated from the importer) problem is likely to be fixed?

Regards,

Erik F. Andersen
Ascott Software A/S 

Hello,

My apologies for the delay -  I've been under the weather lately.

Since the Dec. update I've resolved the issue with weak class aliases
(affects aliases of TXSxxxx types). The Dec 06 update out there right now is
actually latter than the official Dec. update because my cutoff time was
much much earlier (October??). So the Dec 06 update has something else fixed
that I can't remember right now.

I don't know the timeframe for the internal error; I'm afraid it might be a
little while simply because I sense that the compiler folks are deep in
implementation work for Unicode and Generics lately; at least, that's the
impression I get from the email going by. I think I've mentioned that I can
do something at the importer level that would alleviate this problem but I
cannot fix is totally at the importer level. If the base type declared is
never used and only the alias to the base type is used, I can shortcircuit
the base type - therefore eliminating the need of a strong alias - the
source of the Internal Error. However, in cases where the Service refers to
both the base type and the alias type, I need a strong alias to register
unique name/namespace for each.

Anything else I'm forgetting; please let me know. I've been away from the
newsgroup for a little while and I'm probably forgetting some outstanding
items.

Cheers,

Bruneau.