Difficult code packaging design

it helps some times To avoid the deletion of 'target', I had to write a thread safe reference counted smart pointer. It is not that hard to do. The only thing you need to ensure is that the reference count is accessed within a critical section. See this post for more information.

wish helps you The complexity of EJB2 needs more programmer human resource. So EJB2 is good for programmer employment rate. This is a reason for EJB2 survive:)

this one helps. So you have three different types of users, and you want to impress your teacher by not merely using one table.
A good schema would be:

Hope this helps I am trying to create an API for my Rest services and i am struggling with the design rules that i try to follow. In generally i am trying to follow (among others) these guidelines: , A URL consists of several parts:

To fix the issue you can do Robin - I'm assuming that you are doing this with an eye toward offering a "generic" interface to these objects for your users. I did something similar in an earlier project and documented the UI that I ended up with in an answer I posted earlier.
To answer your specific question, you should be a bit careful here as you might be entering Architecture Astronaut territory (not a good thing). If the interfaces for each of your objects don't naturally overlap, forcing them to share a conceptual interface via odd machinations will just end up confusing your users. You can solve this problem by implementing Interfaces that call the "closest enough" function for very broad conceptual categories (e.g. files and applications are both "Opened" but the result is different for each). You can also use reflection to discover more about your objects at the point where you need to display the options available. Thus, you can do it. The question is, should you do it?