Hello, Florian.
You've raised some very interesting points, and it's great to see the interest in improving the rich-client experience for both end-users and developers.
I think most if not all of your suggestions focus on the ORB - as opposed to the ACC itself - and how the client program and the ORB could interact more with each other. So I expect we will hear from the ORB folks fairly soon.
It's important to keep a clear distinction between changes we might like to see in the ACC and changes we might like to see in the ORB. The two technologies are indeed closely related but are different. Especially with dependency injection available, a client developer can pay little or no attention to the ORB itself (although catching and reacting to failed remote method invocations is something every client developer should be able to do). The sorts of enhancements you have described would allow (not require) the client developer to interact much more directly with the ORB, without changing how he or she works with the ACC.
Certainly there are ways we can improve the ACC, and we would like to make several improvements in V3. I'm just asking that as we talk about these that we try to be clear about which piece we are talking about.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=216136