The VMWare components are marked as 'experimental'. Anyone using them is 
about to discover what that means, namely, the interfaces aren't stable. 
I've just reworked things so that when negotiations with the VMWare 
services go wrong, exceptions should always be thrown [1]. That means 
the callers have to catch them. This can result in better code, but it 
may surprise things that didnt expect such frequent exceptions.

The code that uses it in the repository (Avalanche) is building, but if 
anyone finds something stops working, you now know who to blame -me. 
Feel free to complain.

[1] http://jira.smartfrog.org/jira/browse/SFOS-450

-- 
-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Smartfrog-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartfrog-users

Reply via email to