On Jan 17, 2012, at 10:04 AM, Bernhard Thalmayr wrote:
> Thanks for the information Cheng.
>
> Do you know why nearly every jar of GF installation has been
> configured as dependency in gf-client.jar?
>
> Wouldn't it be a good idea to specify only the jars which are really
> needed?
The Class-Path list in gf-client.jar supports all of the technologies
that might be used from an app client: EJBs, web services, JMS, etc.
That's why the list is longer than the EJB-only list Cheng refers to.
- Tim
>
> Regards,
> Bernhard
>
> On 1/17/12, Cheng Fang <cheng.fang_at_oracle.com> wrote:
>> Hi Bernhard,
>>
>> Which GlassFish jars are required on the client side depends on your
>> application and there is no one-size-fit-all minimum set of jar
>> files.
>> For a simple remote EJB invocation, there are about 31 individual
>> GlassFish jar files that need to be present in client classpath.
>> This
>> can change from release to release. One way to find out is to
>> start the
>> client with -verbose:class option.
>>
>> -Cheng
>>
>> On 1/16/12 10:41 AM, Bernhard Thalmayr wrote:
>>> Hi experts,
>>> according to the EJB FAQ 'gf-client.jar' has to be used to connect
>>> to
>>> remote EJBs.
>>>
>>> However gf-client.jar references nearly all JARs provided with
>>> GlassFish installation.
>>>
>>> I'm pretty sure this is not needed ... is it?
>>>
>>> How can I create a minimalisitc set of JARs/dependencies to
>>> connect to
>>> remote EJBs?
>>>
>>> TIA,
>>> Bernhard
>>>
>>
>
>
> --
> IT-Consulting Bernhard Thalmayr
> - Painstaking Minds -
> 83620 Vagen (Munich area)
> Germany