Jerome Dochez wrote:
> Sahoo wrote:
>> A few comments:
>>
>> 1. Since common-ee-util depends on Java EE APIs, how can we have a
>> distribution of just the web container or the ejb container without
>> distributing ejb-apis or servlet-apis respectively?
> so far we cannot. the issues is not limited to common-ee-util. for
> instance, look at management-api in the Java EE APis. it imports
> ejb-api which imports jaxrpc-apis. Of course we would want
> management-api in a web distribution. The Java EE APIs have not gone
> through a rigourous effort to allow for on demand pick and choose.
Are we allowed to distribute some javax APIs without implementing them?
I say this because, it should not happen that because of some classes in
common-ee-util, we are forced to ship the whole javaee.jar.
>
>>
>> 5. Why is there a single module called glassfish-ee-api?
> I don't understand that question, can u elaborate.
Having one module with all kinds of ee-api does not sound too good in a
modular world, does it? I would like to see how we are planning to have
standalone containers like ejb container or web container in v3. I
propose the following:
each container has at least two modules, viz: container-impl and
container-api. api module is needed to break circular dependency during
build. It can contain both user APIs as well as internal APIs - they can
be distinguished by package names. This way, we avoid having two jumbo
modules called glassfish-ee-api and internal-api.
Thanks,
Sahoo