Greg,
That was exactly what I thought, but that doesn't seem to be the case. Because
there are also 'normal' MDB's (not extending a base class)
and they work perfectly. Included is the source code for both types of MDB. As
you can see both have exactly the same tags only with
different values. Because the not-extending MDB does work, and I use the same
build script for all MDB's, it is unlikely that the build script
is incorrect. Do you have any other suggestions?
MDB NOT extending a base class:
/**
* @ejb.bean name="VeprRekenMainframeServiceMDB
* transaction-type="Container"
* destination-type="javax.jms.Queue"
* description="MessageDrivenBean for the mainframe
VeprRekenService"
*
* @jboss.destination-jndi-name name="jms/VeprRekenMainframeServiceRequestQ"
*
* @jboss.resource-ref res-ref-name="jms/VeprRekenMainframeServiceCF"
* resource-name="JmsXA2"
*
* @jboss.resource-manager res-man-name="JmsXA2"
* res-man-jndi-name="Java:/JmsXA2"
*
* @ejb.resource-ref res-ref-name="jms/VeprRekenMainframeServiceCF"
* res-type="javax.jms.QueueConnectionFactory"
* res-auth="Container"
*
* Bean implementation class for Enterprise Bean: VeprRekenMainframeServiceMDB
*/
public class VeprRekenMainframeServiceMDBBean implements
javax.ejb.MessageDrivenBean, javax.jms.MessageListener {
...
}
MDB extending a base class:
/**
* @ejb.bean name="VeprRekenServiceMDB"
* transaction-type="Container"
* destination-type="javax.jms.Queue"
* description="MessageDrivenBean for the VeprRekenService"
*
* @jboss.destination-jndi-name name="jms/VeprRekenServiceRequestQ"
*
* @jboss.resource-ref res-ref-name="jms/VeprRekenServiceCF"
* resource-name="JmsXA1"
*
* @jboss.resource-manager res-man-name="JmsXA1"
* res-man-jndi-name="Java:/JmsXA1"
*
* @ejb.resource-ref res-ref-name="jms/VeprRekenServiceCF"
* res-type="javax.jms.QueueConnectionFactory"
* res-auth="Container"
*
* Bean implementation class for Enterprise Bean: VeprBeheerServiveMDB
*/
public class VeprRekenServiceMDBBean extends CIMdbBase {
...
}
-----Oorspronkelijk bericht-----
Van: [EMAIL PROTECTED] namens GrÃgory Joseph
Verzonden: wo 22-12-2004 14:56
Aan: [EMAIL PROTECTED]
CC:
Onderwerp: Re: [Xdoclet-user] How to use xdoclet when a MDB extends a
base class
Jasper,
All you need to do is have all the required tags on your implementation
classes. If that doesn't work and you're sure you have all the needed
tags, then I suspect your build script is incorrect: make sure the
source fileset picks up *MDB, for instance.
HTH,
greg
> Hi there,
>
> I have a problem with using xdoclet together with MDB's. I have
> several MDB's and each of them extends from the same base class. This
> base class implements the MessageListener and MessageDrivenBean
> interfaces. When I put xdoclet tags in the MDB nothing gets generated.
> Of course you could put the xdoclet tags in the base class, but there
> are two problems with that solution:
>
> 1. I don't have access to the source code of the base class
> 2. And even if I had access, each MDB uses a different
> ConnectionFactory and Queue, and putting the xdoclet tags in the base
> class would mean that the all use the same ConnectionFactory and
Queue.
>
>
> Does anyone have any suggestions how to solve this problem?
>
> Regards,
> Jasper de Barbanson
>
This e-mail (including any attachments) may contain information which
is privileged or confidential or constitute non-public information.It is to be
conveyed only to the intended recipient(s).If you received this e-mail in
error, please notify the sender immediately by e-mail or telephone and delete
the e-mail from your system without reading, copying or disclosing its contents
to any other person.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
Disclaimer
Dit bericht met eventuele bijlagen is vertrouwelijk en uitsluitend bestemd voor
de geadresseerde. Indien u niet de bedoelde ontvanger bent, wordt u verzocht de
afzender te waarschuwen en dit bericht met eventuele bijlagen direct te
verwijderen en/of te vernietigen. Het is niet toegestaan dit bericht en
eventuele bijlagen te vermenigvuldigen, door te sturen, openbaar te maken, op
te slaan of op andere wijze te gebruiken. Ordina N.V. en/of haar
groepsmaatschappijen accepteren geen verantwoordelijkheid of aansprakelijkheid
voor schade die voortvloeit uit (de inhoud van) de verzending van dit bericht.
This e-mail and any attachments are confidential and is solely intended for the
addressee only. If you are not the intended recipient, please notify the sender
and delete and/or destroy this message and any attachments immediately. It is
prohibited to copy, to distribute, to disclose or to use this e-mail and any
attachments in any other way. Ordina N.V. and/or its group companies do not
accept any responsibility nor liability for any damage resulting from (the
content of) the transmission of this message.
<<winmail.dat>>
