A client in one ear calling an ejb in another ear is a circumstance where you do not want a custom loader-repository. For this you want the default flat visibility since you are sharing types between deployments. You'll have to explain why the client is in ear1 calling ear2 rather than being in ear2.
Hi Scott. Thanks for the help. Sorry for late answer. I was having some problems getting my messages to the list and just now I saw it was working again...
Jae Gangemi sent me some explanations about how to get them working. I have to have the class used by both ears in the flat visibility as you are saying too.
The client is in fact using the ear2 which is using as a client the ear1.
The ear1 is holding components which will be used by more than one ear appication and so I decided to put them in a separate ear.
Regards,
Francisco Figueiredo Jr.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
