> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Shunsuke Masuda > Sent: 18. april 2002 16:34 > To: [EMAIL PROTECTED] > Subject: [Xdoclet-user] WebSphere 4 PK class and etc. > > > Hello, > > WebSphere 4 complains of PK classes which have non-public > fields at deployment time. > To stop this, I think I need to write another entitypk.j and specify it > in ant's build files. Are there any other way? >
Let's assume you're using XDoclet 1.1.2... The entitypk.j template in CVS generates public fields (plus one serialVersionUID with package visibility). I don't remember how it is in XDoclet 1.1.2. Does WS complain about the serialVersionUID field or the member fields' visibility? And here is to the developers: This raises two questions: -Why are members public? Is there anywhere in the EJB 1.1 or EJB 2.0 spec that says pk fields must be public? I consider public fields the evil of all evils, so I think we sould at least provide an option to make the fields private. -Why does the serialVersionUID field have package visibility? Isn't it supposed to be private? Aslak > And I'd like to know about XDoclet's websphere support development. > Is it taken place by imitating AAT's output? Or there's some reference > about it? I feel there's some room I can help. > > Finally, I've just subscribed to this list. Could someone please tell me > where I can find "search" capability of the archive? > http://www.mail-archive.com/xdoclet-user%40lists.sourceforge.net/ http://www.mail-archive.com/xdoclet-devel%40lists.sourceforge.net/ > Regards, > Shunsuke Masuda > > > > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
