![](https://dblp1.uni-trier.de/img/logo.ua.320x120.png)
![](https://dblp1.uni-trier.de/img/dropdown.dark.16x16.png)
![](https://dblp1.uni-trier.de/img/peace.dark.16x16.png)
Остановите войну!
for scientists:
![search dblp search dblp](https://dblp1.uni-trier.de/img/search.dark.16x16.png)
![search dblp](https://dblp1.uni-trier.de/img/search.dark.16x16.png)
default search action
WEH@SIGSOFT 2008: Atlanta, Georgia, USA
- Proceedings of the 4th International Workshop on Exception Handling, WEH 2008, Atlanta, Georgia, USA, November 14, 2008. ACM 2008, ISBN 978-1-60558-229-0
- Anatoliy Gorbenko
, Alexander B. Romanovsky
, Vyacheslav S. Kharchenko
, Alexey Mikhaylichenko:
Experimenting with exception propagation mechanisms in service-oriented architecture. 1-7 - Roy Krischer, Peter A. Buhr:
Asynchronous exception propagation in blocked tasks. 8-15 - Thorsten van Ellen, Wilhelm Hasselbring
:
Extended exceptions for contingencies and their implications for the engineering process. 16-23 - Christophe Dony, Chouki Tibermacine, Christelle Urtado
, Sylvain Vauttier
:
Specification of an exception handling system for a replicated agent environment. 24-31 - Jörg Kienzle:
On exceptions and the software development life cycle. 32-38 - Nélio Cacho
, Thomas Cottenier, Alessandro Garcia:
Improving robustness of evolving exceptional behaviour in executable models. 39-46 - Ivo Augusto Bertoncello, Marcelo Oliveira Dias, Patrick H. S. Brito, Cecília M. F. Rubira
:
Explicit exception handling variability in component-based product line architectures. 47-54 - Barbara Staudt Lerner, Stefan Christov, Alexander E. Wise, Leon J. Osterweil:
Exception handling patterns for processes. 55-61 - Hina Shah, Carsten Görg
, Mary Jean Harrold:
Why do developers neglect exception handling? 62-68
![](https://dblp1.uni-trier.de/img/cog.dark.24x24.png)
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.