Bug 162911

My idea is to have one universal RCP client which to be common for all
applications with the following requirements:
1. NetBeans Platform based
2. OSGi bundles and OSGi Framework for module management instead NBM
3. Java Web Start (JNLP) based on Java EE Application Client specification:
http://java.sun.com/xml/ns/javaee/application-client_5.xsd
4. Specialized Servlet on the Server which to handle the whole start-up mechanism: preparing
and signing the JARs according the requirements of Java EE Application Client
specification.
5. The communication between the Server and the Client to be based on
Distributed OSGi (RFC-119). In this case the client will use all services
(local and remote) as local and the communications and the used protocols (RMI,
CORBA, JMS, WS, SOAP, etc.) will be hidden for the bundles.
6. Single Sign On mechanism. If the user is entered into the application from
the Web and then starts the application there will not need to login again.
7. Integrated bundles for authentication which to support all popular
specifications like username/password, certificate, etc.
8. Integrated bundles for user registration with customization options
9. Different certificate whit which to be signed the user bundles and the
Distributed JWS OSGi Client. This option is good because the all common
functionality can be signed with one certificate and all user specific
application bundles will be signed with another certificate. Now in one JWS
Application Client all JARs MUST be signed with one certificate. In case that
this client will be universal and will be used from many and different
project/applications, their bundles should be signed whit vendor specific
certificate while the client will be signed with one unique certificate.
10. All bundles will be stored in the local computer using OSGi Bundle
Repository (OBR) specification.