Jagadish Prasath Ramu wrote:
> On Sat, 2009-04-04 at 17:17 +0530, Sahoo wrote:
>
>> Jagadish Prasath Ramu wrote:
>>
>>> On Fri, 2009-04-03 at 23:39 +0530, Sahoo wrote:
>>>
>>>
>>>> Yes and No. Yes, if it can't run without ejb-api in the system, no if
>>>> the dependency is an optional (optional refers to OSGi import-package
>>>> optional attribute) one.
>>>>
>>>>
>>> With the currently planned distributions (web profile and Java EE
>>> profile), I would assume that it is needed for both and hence won't be
>>> optional.
>>>
>>>
>> That was not my point. Is the connector module coded such that it can
>> live without ejb module?
>>
> Yes and No.
> w.r.t this issue, yes it may be possible if container-common have those
> abstractions, which may necessitate changes in web & ejb modules.
>
Let's go for it.
> I remember you stating that modules need to be merged. If thats the
> case, then, no, as connectors inbound support, will depend on private
> api of ejb module.
>
>
Given that inbound message delivery to an MDB is not active in the
absence of an MDB container, we should be able to mark the dependency as
optional provided rest of connectors runtime can function correctly.
Thanks,
Sahoo