Jerome Dochez wrote:
>>
>> We could update the info object such that no listeners are created by
>> default to address EJB unit test use case. When user sets the ports,
>> the corresponding listeners are created. Let me know if that sounds
>> okay to you.
>>
> I don't think I follow the exact proposal here...
>
Current behavior is that we create the some (http) ports by default. It
favors the webtier users. For EJB unit tests, this is not desirable. If
we change the default behavior such that only ports that are set in the
info is created, EJB users will be able to start the server without
having to create the webtier ports.
>>>> Please note that for Prelude, we are not supporting the implanted
>>>> use case yet. When we support "implanted" we can certainly use
>>>> glassfish.jar.
>>> I understand but we also know we want that support so we need to
>>> think about an API that will support both use cases.
>> Okay. Any ideas how you want to support that? Are you suggesting to
>> split the "all" jar to two?
> I think we just need to move the embedded API inside glassfish.jar,
> the uberjar will naturally obtain those classes from there, there
> should be no content different between the embedded uber jar and the
> implanted case.
>
Okay, sure.
--
Nazrul Islam - (408) 276-6468 - Sun Microsystems, Inc.