RE: [Xdoclet-user] Utility class in the wrong package

inal Message- > From: Marcus Brito [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 11, 2002 6:20 AM > To: James Cook > Subject: Re: [Xdoclet-user] Utility class in the wrong package > > > Em Seg, 2002-03-11 às 00:30, James Cook escreveu: > > The class is begin generat

[Xdoclet-user] Utility class in the wrong package

I am using the tag to generate a default Util class. (Nice feature BTW) The class is begin generated with the same package as is specified in the ejbdoclet task. This is because I do not overwrite the setting in the utilobject task. The problem is that this causes the correct package declaration

[Xdoclet-user] get/setData on Remote interface

Generation of the DAO and its associated bulk accessors/mutators is a nice feature. XDoclet is properly generating the DAO and the appropriate methods on MyEntityBeanCMP. However, what good are these methods without exposing them to the remote interface? In order to use these methods, they have t

[Xdoclet-user] DAO Object Name

Any way to change the name of the generated data access object? ___ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user

[Xdoclet-user] Generation biased on EntityBean interface

It seems that the generation of support classes is heavily biased on the deployable bean implementing the EntityBean interface. I have an entity bean superclass that does the implementing of EntityBean. This is a design that I have seen many others use also. This base class performs some dummy i

RE: [Xdoclet-user] Home not recognizing PK generation is off

same results. By BaseEntityBean superclass has all of its generates set to false. jim > -Original Message- > From: Ara Abrahamian [mailto:[EMAIL PROTECTED]] > Sent: Saturday, March 09, 2002 12:20 AM > To: 'James Cook'; [EMAIL PROTECTED] > Subject: RE: [Xdoclet

RE: [Xdoclet-user] Home not recognizing PK generation is off

I tried this, using: * @ejb:bean * primkey-class = "java.lang.String" * primkey-field = "categoryID" * @ejb:pk * generate= "false" I have tried it with and with

[Xdoclet-user] Home not recognizing PK generation is off

I have defined the following fields in my bean class: * @ejb:bean * primkey-field = "java.lang.Integer" * @ejb:pk * generate= "false" Yet the Home interface continues to generate this: public com.

RE: [Xdoclet-user] Beans extending superclasses

t. I think the sample CustomerBean that extends PersonBean gives you an example more in line with a deployable bean scenario. jim > -Original Message- > From: Ara Abrahamian [mailto:[EMAIL PROTECTED]] > Sent: Thursday, March 07, 2002 10:29 AM > To: 'James Cook'; [EMA

[Xdoclet-user] Running Xdoclet inside of IntelliJ IDEA

I am experiencing a very strange problem with my ejbdoclet task. At the command prompt, I can execute the Ant build without any difficulty. However, inside of IDEA, I get the following error while executing the task: Cannot find doclet class xdoclet.DocletTask$DocletMain Note that it is not comp

[Xdoclet-user] Beans extending superclasses

My EntityBeans need to _extend_ a superclass. If the name of this superclass is BaseEntityBean, the xdoclet generates Home and Remote interfaces that extend an interface called BaseEntityHome? I don't want this. Where is it coming up with BaseEntityHome (or BaseEntity in the case of my Remote inte