JSR 193, Client Side Container, has been withdrawn from the JCP process. Having noticed the many questions/concerns about this specification proposal, the submitter decided to withdraw the request. The spec had aimed to provide a common client infrastructure including things like: logging, security, internationalization, configuration, lifecycle management etc.

Check out JSR 193: Client Side Container.

The only official explanation on jcp.org was "Having noticed the many questions/concerns about this specification proposal, the submitter decided to withdraw the request. "

I think the spec seems good in order to expand the market for client side java applications, why should it be withdrawn?

From having a read of the JSR it looks like the submitter thought he had a nice polished spec and reference implementation that could be turned into a full product without excessive effort. It then looks like the JSR process raised a number of issues, ommisions etc. and he would have had to make so many changes that he decided to cut his losses.

The client side container is an interesting idea, but creating a container to support every possible type of client development for all organisations is not a trivial undertaking.

"creating a container to support every possible type of client development for all organisations is not a trivial undertaking"

No its not trivial.

However, look at Eclipse - we have a client-side container...

-Nick

Could someone provide the link to the downloadable spec?

TIA,

Adolfo Rodriguez