Board index » jbuilder » Another EJBModule Question

Another EJBModule Question


2004-01-17 04:57:51 AM
jbuilder12
Using the answers that Lata supplied, I was able to create an ejb-jar
exactly the way I wanted. Thank you very much, Lata!
see: JBX - Several EJBModules in a single project - how to get individual
EJBModules to include ONLY those classes that are necessary
However, I passed the information on to others and they are not getting the
same results.
It turns out that they are not using 'Automatic Source Packages'.
They implicitly add the packages that they care about using 'Add
Files/Packages/Classes'.
The projects in this case are different than the one in my original post.
Pictures and jars are worth thousands of words... see: 'JBX-one EjbModule'
project in the attachments directory.
There are two generated jars
1. GenTabcomp_NoAutoDiscover.jar (OneEjbModuleJPX1.png)
2. GenTabcomp_AutoDiscover.jar (OneEjbModuleJPX2.png)
The only difference between the two projects is that 'Project Properties |
General | Enable source package discovery and compilation' has been turned
on and off, and when off, the package com.guardian.wgs.gentabcomp was
manually added to the project.
No other settings were changed.
However the .jar files generated are quite different (take a look to see
what I mean). It seems that when 'Auto Discovery' is turned off, the
packages are not being built correctly.
Is this because only the top level package was manually added? If so, why
was the cmp package also added?
Thank you,
Joe E.
 
 

Re:Another EJBModule Question

Joe,
I took a look at the jar files you have uploaded to the attachments
group and see the problem. I have unfortunately not been able to
reproduce it.
Not all classes in your project get included in the EJB Jar. By default
the classes defined in the descriptors and any direct dependencies
are included in the EJB Jar. If you uncheck the option to include class
dependencies, then only the EJB classes referenced in the descriptor get
included in the EJB jar. This can be overriden with the use of filters
and file types.
Do you have any custom filters defined? Without filters, this seems to
work fine for me with/without source discovery.
Could you send me a small test case?
Thanks.
- Lata
Joe Enfield wrote:
Quote
Using the answers that Lata supplied, I was able to create an ejb-jar
exactly the way I wanted. Thank you very much, Lata!
see: JBX - Several EJBModules in a single project - how to get individual
EJBModules to include ONLY those classes that are necessary

However, I passed the information on to others and they are not getting the
same results.
It turns out that they are not using 'Automatic Source Packages'.
They implicitly add the packages that they care about using 'Add
Files/Packages/Classes'.

The projects in this case are different than the one in my original post.
Pictures and jars are worth thousands of words... see: 'JBX-one EjbModule'
project in the attachments directory.

There are two generated jars
1. GenTabcomp_NoAutoDiscover.jar (OneEjbModuleJPX1.png)
2. GenTabcomp_AutoDiscover.jar (OneEjbModuleJPX2.png)

The only difference between the two projects is that 'Project Properties |
General | Enable source package discovery and compilation' has been turned
on and off, and when off, the package com.guardian.wgs.gentabcomp was
manually added to the project.
No other settings were changed.

However the .jar files generated are quite different (take a look to see
what I mean). It seems that when 'Auto Discovery' is turned off, the
packages are not being built correctly.
Is this because only the top level package was manually added? If so, why
was the cmp package also added?

Thank you,
Joe E.


 

Re:Another EJBModule Question

Lata,
Sorry for the delay. I will try to pare down the project I have, and send
it to you directly (if that is ok).
I will try to have something for you by monday.
Thank you,
Joe E.
"Lata Amujuri" < XXXX@XXXXX.COM >wrote in message
Quote
Joe,
I took a look at the jar files you have uploaded to the attachments
group and see the problem. I have unfortunately not been able to
reproduce it.
Not all classes in your project get included in the EJB Jar. By default
the classes defined in the descriptors and any direct dependencies
are included in the EJB Jar. If you uncheck the option to include class
dependencies, then only the EJB classes referenced in the descriptor get
included in the EJB jar. This can be overriden with the use of filters
and file types.
Do you have any custom filters defined? Without filters, this seems to
work fine for me with/without source discovery.
Could you send me a small test case?

Thanks.

- Lata

Joe Enfield wrote:
>Using the answers that Lata supplied, I was able to create an ejb-jar
>exactly the way I wanted. Thank you very much, Lata!
>see: JBX - Several EJBModules in a single project - how to get
individual
>EJBModules to include ONLY those classes that are necessary
>
>However, I passed the information on to others and they are not getting
the
>same results.
>It turns out that they are not using 'Automatic Source Packages'.
>They implicitly add the packages that they care about using 'Add
>Files/Packages/Classes'.
>
>The projects in this case are different than the one in my original
post.
>Pictures and jars are worth thousands of words... see: 'JBX-one
EjbModule'
>project in the attachments directory.
>
>There are two generated jars
>1. GenTabcomp_NoAutoDiscover.jar (OneEjbModuleJPX1.png)
>2. GenTabcomp_AutoDiscover.jar (OneEjbModuleJPX2.png)
>
>The only difference between the two projects is that 'Project Properties
|
>General | Enable source package discovery and compilation' has been
turned
>on and off, and when off, the package com.guardian.wgs.gentabcomp was
>manually added to the project.
>No other settings were changed.
>
>However the .jar files generated are quite different (take a look to see
>what I mean). It seems that when 'Auto Discovery' is turned off, the
>packages are not being built correctly.
>Is this because only the top level package was manually added? If so,
why
>was the cmp package also added?
>
>Thank you,
>Joe E.
>
>

 

{smallsort}

Re:Another EJBModule Question

That's good.
Thanks.
- Lata
Joe Enfield wrote:
Quote
Lata,

Sorry for the delay. I will try to pare down the project I have, and send
it to you directly (if that is ok).
I will try to have something for you by monday.

Thank you,
Joe E.


"Lata Amujuri" < XXXX@XXXXX.COM >wrote in message
news:400c66d2$ XXXX@XXXXX.COM ...

>Joe,
>I took a look at the jar files you have uploaded to the attachments
>group and see the problem. I have unfortunately not been able to
>reproduce it.
>Not all classes in your project get included in the EJB Jar. By default
>the classes defined in the descriptors and any direct dependencies
>are included in the EJB Jar. If you uncheck the option to include class
>dependencies, then only the EJB classes referenced in the descriptor get
>included in the EJB jar. This can be overriden with the use of filters
>and file types.
>Do you have any custom filters defined? Without filters, this seems to
>work fine for me with/without source discovery.
>Could you send me a small test case?
>
>Thanks.
>
>- Lata
>
>Joe Enfield wrote:
>
>>Using the answers that Lata supplied, I was able to create an ejb-jar
>>exactly the way I wanted. Thank you very much, Lata!
>>see: JBX - Several EJBModules in a single project - how to get

individual

>>EJBModules to include ONLY those classes that are necessary
>>
>>However, I passed the information on to others and they are not getting

the

>>same results.
>>It turns out that they are not using 'Automatic Source Packages'.
>>They implicitly add the packages that they care about using 'Add
>>Files/Packages/Classes'.
>>
>>The projects in this case are different than the one in my original

post.

>>Pictures and jars are worth thousands of words... see: 'JBX-one

EjbModule'

>>project in the attachments directory.
>>
>>There are two generated jars
>>1. GenTabcomp_NoAutoDiscover.jar (OneEjbModuleJPX1.png)
>>2. GenTabcomp_AutoDiscover.jar (OneEjbModuleJPX2.png)
>>
>>The only difference between the two projects is that 'Project Properties

|

>>General | Enable source package discovery and compilation' has been

turned

>>on and off, and when off, the package com.guardian.wgs.gentabcomp was
>>manually added to the project.
>>No other settings were changed.
>>
>>However the .jar files generated are quite different (take a look to see
>>what I mean). It seems that when 'Auto Discovery' is turned off, the
>>packages are not being built correctly.
>>Is this because only the top level package was manually added? If so,

why

>>was the cmp package also added?
>>
>>Thank you,
>>Joe E.
>>
>>
>


 

Re:Another EJBModule Question

I've sent you an example. did you get it?
Thanks,
Joe E.
"Lata Amujuri" < XXXX@XXXXX.COM >wrote in message
Quote
That's good.

Thanks.

- Lata

Joe Enfield wrote:
>Lata,
>
>Sorry for the delay. I will try to pare down the project I have, and
send
>it to you directly (if that is ok).
>I will try to have something for you by monday.
>
>Thank you,
>Joe E.
>
>
>"Lata Amujuri" < XXXX@XXXXX.COM >wrote in message
>news:400c66d2$ XXXX@XXXXX.COM ...
>
>>Joe,
>>I took a look at the jar files you have uploaded to the attachments
>>group and see the problem. I have unfortunately not been able to
>>reproduce it.
>>Not all classes in your project get included in the EJB Jar. By default
>>the classes defined in the descriptors and any direct dependencies
>>are included in the EJB Jar. If you uncheck the option to include class
>>dependencies, then only the EJB classes referenced in the descriptor get
>>included in the EJB jar. This can be overriden with the use of filters
>>and file types.
>>Do you have any custom filters defined? Without filters, this seems to
>>work fine for me with/without source discovery.
>>Could you send me a small test case?
>>
>>Thanks.
>>
>>- Lata
>>
>>Joe Enfield wrote:
>>
>>>Using the answers that Lata supplied, I was able to create an ejb-jar
>>>exactly the way I wanted. Thank you very much, Lata!
>>>see: JBX - Several EJBModules in a single project - how to get
>
>individual
>
>>>EJBModules to include ONLY those classes that are necessary
>>>
>>>However, I passed the information on to others and they are not getting
>
>the
>
>>>same results.
>>>It turns out that they are not using 'Automatic Source Packages'.
>>>They implicitly add the packages that they care about using 'Add
>>>Files/Packages/Classes'.
>>>
>>>The projects in this case are different than the one in my original
>
>post.
>
>>>Pictures and jars are worth thousands of words... see: 'JBX-one
>
>EjbModule'
>
>>>project in the attachments directory.
>>>
>>>There are two generated jars
>>>1. GenTabcomp_NoAutoDiscover.jar (OneEjbModuleJPX1.png)
>>>2. GenTabcomp_AutoDiscover.jar (OneEjbModuleJPX2.png)
>>>
>>>The only difference between the two projects is that 'Project
Properties
>
>|
>
>>>General | Enable source package discovery and compilation' has been
>
>turned
>
>>>on and off, and when off, the package com.guardian.wgs.gentabcomp was
>>>manually added to the project.
>>>No other settings were changed.
>>>
>>>However the .jar files generated are quite different (take a look to
see
>>>what I mean). It seems that when 'Auto Discovery' is turned off, the
>>>packages are not being built correctly.
>>>Is this because only the top level package was manually added? If so,
>
>why
>
>>>was the cmp package also added?
>>>
>>>Thank you,
>>>Joe E.
>>>
>>>
>>
>
>