> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Torgeir > Veimo > Sent: 3. januar 2003 11:58 > To: [EMAIL PROTECTED] > Subject: [Xdoclet-user] stricter rules for full-qualified vs unqualified > class names in ebjdoclet in v1.2? > > > We had these @ejb tags which generated fine under xdoclet 1.1.2; > > @ejb:pk > class="com.somewhere.ejbcontainer.domain.IntegerIntegerPK" > generate="false" > > @ejb:finder > signature="com.somewhere.ejbcontainer.domain.LEtoRoleMapRemote > findByPrimaryKey(IntegerIntegerPK key)" > > However, under xdoclet 1.2beta2 I need to use a full qualified classname > parameter for the IntegerIntegerPK param in the finder method, otherwise > I get two finder methods generated in the Home class; > > @ejb:finder > signature="com.somewhere.ejbcontainer.domain.LEtoRoleMapRemote > findByPrimaryKey(com.somewhere.ejbcontainer.domain.IntegerIntegerPK > key)" > > > Is this correct by design in v1.2? >
This is intentional. The short story is that if you refer to a class that hasn't been generated yet, you need to tell XDoclet its fully qualified name. There are some other good reasons too, and if you search the mailing lists you'll find out why we had to make this decision. Cheers, Aslak > -- > Torgeir Veimo <[EMAIL PROTECTED]> > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
