You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by viola lu <vi...@gmail.com> on 2011/07/12 16:52:11 UTC
Class-Path in manifest file of applicationclient module.
Hi, Dev:
I met a problem when deploy an ear which packages an ejb, application
client, web app. And the EJB is in the class-path of app client module
manifest, but Appclientmodulebuilder class doesn't add this class-path of
manifest to module's LinkedHashSet<String> classpath, So it's not in the
class path of AppclientDeplomentContext either. Is it correct?
--
viola
Apache Geronimo
Re: Class-Path in manifest file of applicationclient module.
Posted by viola lu <vi...@gmail.com>.
But if it's by design, appclient calls ejbs like :
@EJB
private static TradeSLSBRemote tradeSLSBRemote;
it will not find TradeSLSBRemote class in its class finder. Currently, i
have to pakcage all ejb interface to ear lib folder, making ejb interface in
appclient classpath.
On Tue, Jul 12, 2011 at 11:29 PM, Ivan <xh...@gmail.com> wrote:
> From the word of 'library', I do not think that ejb module is belong to
> this scope.
>
>
> 2011/7/12 Shawn Jiang <ge...@gmail.com>
>
>> Components in the application client container must have access to the
>> following
>> classes and resources.
>> • The content of the application client jar file.
>> • The transitive closure of any libraries referenced by the above jar file
>> (as spec-
>> ified in Section EE.8.2, “Library Support”).
>>
>>
>>
>>
>> On Tue, Jul 12, 2011 at 11:10 PM, Ivan <xh...@gmail.com> wrote:
>>
>>> Hmm, I double checked the spec, so which rule should cover this request
>>> ?
>>>
>>> --->
>>> • The Java EE API classes specified in Table EE.6-1 for the containers
>>> other than
>>> the application client container.
>>> • Any installed libraries available in the application server.
>>> • Other classes or resources contained in the application package, and
>>> specified
>>> by an explicit use of an extension not defined by this specification.
>>> • Other classes and resources that are part of the implementation of the
>>> applica-
>>> tion server.
>>> <---
>>>
>>>
>>> 2011/7/12 Shawn Jiang <ge...@gmail.com>
>>>
>>>> per java ee 6 spec: EE.8.3.3 Application Client Container Class
>>>> Loading Requirements
>>>>
>>>> Components in the application client container must not have access to
>>>> the
>>>> following classes and resources, *unless such classes or resources are
>>>> covered by
>>>> one of the rules above.*
>>>>
>>>> If the ejb jar is in the class-path of app client module, the module
>>>> will have the access to ejb jar.
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Jul 12, 2011 at 10:59 PM, Ivan <xh...@gmail.com> wrote:
>>>>
>>>>> Yes, it is by design. App client modules should not have access to web
>>>>> modules, ejb modules and other app client modules in the same ear package.
>>>>>
>>>>>
>>>>> 2011/7/12 viola lu <vi...@gmail.com>
>>>>>
>>>>>> Hi, Dev:
>>>>>>
>>>>>> I met a problem when deploy an ear which packages an ejb, application
>>>>>> client, web app. And the EJB is in the class-path of app client module
>>>>>> manifest, but Appclientmodulebuilder class doesn't add this class-path of
>>>>>> manifest to module's LinkedHashSet<String> classpath, So it's not in the
>>>>>> class path of AppclientDeplomentContext either. Is it correct?
>>>>>> --
>>>>>> viola
>>>>>>
>>>>>> Apache Geronimo
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ivan
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Shawn
>>>>
>>>
>>>
>>>
>>> --
>>> Ivan
>>>
>>
>>
>>
>> --
>> Shawn
>>
>
>
>
> --
> Ivan
>
--
viola
Apache Geronimo
Re: Class-Path in manifest file of applicationclient module.
Posted by Ivan <xh...@gmail.com>.
>From the word of 'library', I do not think that ejb module is belong to this
scope.
2011/7/12 Shawn Jiang <ge...@gmail.com>
> Components in the application client container must have access to the
> following
> classes and resources.
> • The content of the application client jar file.
> • The transitive closure of any libraries referenced by the above jar file
> (as spec-
> ified in Section EE.8.2, “Library Support”).
>
>
>
>
> On Tue, Jul 12, 2011 at 11:10 PM, Ivan <xh...@gmail.com> wrote:
>
>> Hmm, I double checked the spec, so which rule should cover this request ?
>>
>> --->
>> • The Java EE API classes specified in Table EE.6-1 for the containers
>> other than
>> the application client container.
>> • Any installed libraries available in the application server.
>> • Other classes or resources contained in the application package, and
>> specified
>> by an explicit use of an extension not defined by this specification.
>> • Other classes and resources that are part of the implementation of the
>> applica-
>> tion server.
>> <---
>>
>>
>> 2011/7/12 Shawn Jiang <ge...@gmail.com>
>>
>>> per java ee 6 spec: EE.8.3.3 Application Client Container Class Loading
>>> Requirements
>>>
>>> Components in the application client container must not have access to
>>> the
>>> following classes and resources, *unless such classes or resources are
>>> covered by
>>> one of the rules above.*
>>>
>>> If the ejb jar is in the class-path of app client module, the module
>>> will have the access to ejb jar.
>>>
>>>
>>>
>>>
>>> On Tue, Jul 12, 2011 at 10:59 PM, Ivan <xh...@gmail.com> wrote:
>>>
>>>> Yes, it is by design. App client modules should not have access to web
>>>> modules, ejb modules and other app client modules in the same ear package.
>>>>
>>>>
>>>> 2011/7/12 viola lu <vi...@gmail.com>
>>>>
>>>>> Hi, Dev:
>>>>>
>>>>> I met a problem when deploy an ear which packages an ejb, application
>>>>> client, web app. And the EJB is in the class-path of app client module
>>>>> manifest, but Appclientmodulebuilder class doesn't add this class-path of
>>>>> manifest to module's LinkedHashSet<String> classpath, So it's not in the
>>>>> class path of AppclientDeplomentContext either. Is it correct?
>>>>> --
>>>>> viola
>>>>>
>>>>> Apache Geronimo
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Ivan
>>>>
>>>
>>>
>>>
>>> --
>>> Shawn
>>>
>>
>>
>>
>> --
>> Ivan
>>
>
>
>
> --
> Shawn
>
--
Ivan
Re: Class-Path in manifest file of applicationclient module.
Posted by Shawn Jiang <ge...@gmail.com>.
Components in the application client container must have access to the
following
classes and resources.
• The content of the application client jar file.
• The transitive closure of any libraries referenced by the above jar file
(as spec-
ified in Section EE.8.2, “Library Support”).
On Tue, Jul 12, 2011 at 11:10 PM, Ivan <xh...@gmail.com> wrote:
> Hmm, I double checked the spec, so which rule should cover this request ?
>
> --->
> • The Java EE API classes specified in Table EE.6-1 for the containers
> other than
> the application client container.
> • Any installed libraries available in the application server.
> • Other classes or resources contained in the application package, and
> specified
> by an explicit use of an extension not defined by this specification.
> • Other classes and resources that are part of the implementation of the
> applica-
> tion server.
> <---
>
>
> 2011/7/12 Shawn Jiang <ge...@gmail.com>
>
>> per java ee 6 spec: EE.8.3.3 Application Client Container Class Loading
>> Requirements
>>
>> Components in the application client container must not have access to the
>>
>> following classes and resources, *unless such classes or resources are
>> covered by
>> one of the rules above.*
>>
>> If the ejb jar is in the class-path of app client module, the module
>> will have the access to ejb jar.
>>
>>
>>
>>
>> On Tue, Jul 12, 2011 at 10:59 PM, Ivan <xh...@gmail.com> wrote:
>>
>>> Yes, it is by design. App client modules should not have access to web
>>> modules, ejb modules and other app client modules in the same ear package.
>>>
>>>
>>> 2011/7/12 viola lu <vi...@gmail.com>
>>>
>>>> Hi, Dev:
>>>>
>>>> I met a problem when deploy an ear which packages an ejb, application
>>>> client, web app. And the EJB is in the class-path of app client module
>>>> manifest, but Appclientmodulebuilder class doesn't add this class-path of
>>>> manifest to module's LinkedHashSet<String> classpath, So it's not in the
>>>> class path of AppclientDeplomentContext either. Is it correct?
>>>> --
>>>> viola
>>>>
>>>> Apache Geronimo
>>>>
>>>>
>>>
>>>
>>> --
>>> Ivan
>>>
>>
>>
>>
>> --
>> Shawn
>>
>
>
>
> --
> Ivan
>
--
Shawn
Re: Class-Path in manifest file of applicationclient module.
Posted by Ivan <xh...@gmail.com>.
Hmm, I double checked the spec, so which rule should cover this request ?
--->
• The Java EE API classes specified in Table EE.6-1 for the containers other
than
the application client container.
• Any installed libraries available in the application server.
• Other classes or resources contained in the application package, and
specified
by an explicit use of an extension not defined by this specification.
• Other classes and resources that are part of the implementation of the
applica-
tion server.
<---
2011/7/12 Shawn Jiang <ge...@gmail.com>
> per java ee 6 spec: EE.8.3.3 Application Client Container Class Loading
> Requirements
>
> Components in the application client container must not have access to the
> following classes and resources, *unless such classes or resources are
> covered by
> one of the rules above.*
>
> If the ejb jar is in the class-path of app client module, the module will
> have the access to ejb jar.
>
>
>
>
> On Tue, Jul 12, 2011 at 10:59 PM, Ivan <xh...@gmail.com> wrote:
>
>> Yes, it is by design. App client modules should not have access to web
>> modules, ejb modules and other app client modules in the same ear package.
>>
>>
>> 2011/7/12 viola lu <vi...@gmail.com>
>>
>>> Hi, Dev:
>>>
>>> I met a problem when deploy an ear which packages an ejb, application
>>> client, web app. And the EJB is in the class-path of app client module
>>> manifest, but Appclientmodulebuilder class doesn't add this class-path of
>>> manifest to module's LinkedHashSet<String> classpath, So it's not in the
>>> class path of AppclientDeplomentContext either. Is it correct?
>>> --
>>> viola
>>>
>>> Apache Geronimo
>>>
>>>
>>
>>
>> --
>> Ivan
>>
>
>
>
> --
> Shawn
>
--
Ivan
Re: Class-Path in manifest file of applicationclient module.
Posted by Shawn Jiang <ge...@gmail.com>.
per java ee 6 spec: EE.8.3.3 Application Client Container Class Loading
Requirements
Components in the application client container must not have access to the
following classes and resources, *unless such classes or resources are
covered by
one of the rules above.*
If the ejb jar is in the class-path of app client module, the module will
have the access to ejb jar.
On Tue, Jul 12, 2011 at 10:59 PM, Ivan <xh...@gmail.com> wrote:
> Yes, it is by design. App client modules should not have access to web
> modules, ejb modules and other app client modules in the same ear package.
>
>
> 2011/7/12 viola lu <vi...@gmail.com>
>
>> Hi, Dev:
>>
>> I met a problem when deploy an ear which packages an ejb, application
>> client, web app. And the EJB is in the class-path of app client module
>> manifest, but Appclientmodulebuilder class doesn't add this class-path of
>> manifest to module's LinkedHashSet<String> classpath, So it's not in the
>> class path of AppclientDeplomentContext either. Is it correct?
>> --
>> viola
>>
>> Apache Geronimo
>>
>>
>
>
> --
> Ivan
>
--
Shawn
Re: Class-Path in manifest file of applicationclient module.
Posted by Ivan <xh...@gmail.com>.
Yes, it is by design. App client modules should not have access to web
modules, ejb modules and other app client modules in the same ear package.
2011/7/12 viola lu <vi...@gmail.com>
> Hi, Dev:
>
> I met a problem when deploy an ear which packages an ejb, application
> client, web app. And the EJB is in the class-path of app client module
> manifest, but Appclientmodulebuilder class doesn't add this class-path of
> manifest to module's LinkedHashSet<String> classpath, So it's not in the
> class path of AppclientDeplomentContext either. Is it correct?
> --
> viola
>
> Apache Geronimo
>
>
--
Ivan