The spec does not allow this. CMR needs to be in the same jar file

Jan

-----Original Message-----
From: Ionel Gardais [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 26, 2003 9:27 AM
To: [EMAIL PROTECTED]
Subject: [Xdoclet-user] [ SOS ] ejb ref is hell (prayer to the xdoclet
gurus)

Hi,

Does anybody succeed in working with ejb external reference AND CMR ?

My problem is that one of my CMR field is a bean from an external bean.

For my beans to compile with the external reference, I need to include 
the external beans' source inside my own beans source tree (if I don't, 
I get a "file not found" from Xdoclet saying it didn't find the source 
for the referenced beans)

Unfortunatly, the source of the external beans are processed by the 
deploymentdescriptor and the jboss tasks : this leads to an error when I 
deploy my bean package because JBoss says that the referenced beans JNDI 
name already exists.

I didn't find any ways to exclude the imported external bean source from 
these tasks so they shouldn't be processed.

Does the fact that I use this external bean reference as a CMR field can 
affect XDoclet ? (managing a CMR by two different datasources)

Please help I am really stuck with this and this block my whole project.
Thanks a lot,
ionel



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
************************************************************************
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, please notify the sender of this email 
immediately. You should not copy, use or disseminate the 
information contained in the email.
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Capco.

http://www.capco.com
***********************************************************************

Reply via email to