xADL Extension for embedded systems

This was actually my master diploma thesis.
I've investigate most of the languages that are used for describing software architecture.
Problems:
Most of the languages are invented for particular problems(projects) and doesn't fit other problems, and has strange syntax, lack of tool and knowledge, lack of interoperability.
Embedded systems evolves in recent years most of the languages used to describe software architecture doesn't fit well to their requirements, because of that a language that is extensible should be picked(no need for coming up with a new language it is born dead). There are few good articles why UML is not good:
UML is not language for describing software architecture, but OOP design.
UML extensibility via extending meta model is not good enough, or if it is than the result will be no longer UML.
Using UML artifacts (diagrams) as architecture artifacts will bring more obfuscation.
The Solution:
Picked up language is called xADL which is based on XML Schema(extensibility).
It already contains some core functionality for describing connector and components. The initial request was for having language that is capable of describing non-functional architecture characteristics.
I will continue my post later...... have to find where my thesis is....... :)

Why Oracle AS (9) shouldn't be used for J2EE development

1.Because it throws "MEANINGFUL" NullPointerException if your slsb ejb is incorrect.
2.All its errors are "MEANINGFUL"
3.Because its classLoader structure is "MEANINGFUL"
4.Because its threads loose their state in webapp rmi lookup, and "MEANINGFUL" throw NullPointerException on !!!!! home.create() (because it "CLEVERLY" discover that USER IS NULL in the current thread session, and tries to SHOW IT IN Exception)
5.Because such simple scenarios as : Separate EAR(war only) file lookup SLSB from separate ear IS ALMOST IMPOSSIBLE with OC4J.
6.Because even if it is POSSIBLE, this comes after hours of spell casting.