David Budworth is working on it but it won't be ready for 1.1 release: <David Budworth> But, in case it matters, there is the issue that if someone chooses JBoss 3.0 in the build.xml, xdoclet will crash 90% of the time.
So, we may want to totally disable jbosscmp-jdbc.xml generation completely (jboss can run fine with no jbosscmp/jaws at all, it'll make up defaults that work pretty well) </David Budworth> I'm going to disable jbosscmp-jdbc.xml generation. And AFAIK Aslak filed a bug report in this regard (self referencing relation). Btw, there's a typo in your source files: @jboss:relation, not @jboss-relation. I hope we'll fix these problems and make jboss3 full support functional in 1.1.1 release (which I hope will be ready shortly after 1.1 release!). Cheers, Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-user- > [EMAIL PROTECTED]] On Behalf Of Shaw, Chris > Sent: Wednesday, January 09, 2002 12:16 PM > To: '[EMAIL PROTECTED]' > Subject: [Xdoclet-user] RE: JBoss v3.0 and Oracle typemapping > > Hi, > > If I remove the mutators/accessors relating to the Division/Person 1:M > mapping then XDoclet doesn't bomb out when creating the relationship XML > tags in > jbosscmp-jdbc.xml > > Have I forgotten some tags? [I assumed that only the relation name is > needed > for the getOne() methods, and the name+foreign-key info is needed only on > the getMany() side] > > In DivisionBean this simply involved removing: > /** > * All Persons who work for this Division > * > * @return all persons of this division > * > * @ejb:interface-method view-type="local" > * @ejb:relation > * name="division-person" > * role-name="one-division-has-many-persons" > * multiple="yes" > * > * @weblogic:relation > * name="division-person" > */ > public abstract Collection getPersons(); > and > /** > * @param persons all persons of this division > * > * @ejb:interface-method view-type="local" > */ > public abstract void setPersons(Collection persons); > ================================================================= > and in the PersonBean I just removed the following... > /** > * Division that this Person works for > * > * @return division of this person > * > * @ejb:interface-method view-type="local" > * @ejb:relation > * name="division-person" > * role-name="many-persons-have-one-division" > * > * @weblogic:relation > * name="division-person" > * key-column="d_id" > * foreign-key-column="d_id_fk" > * > * @jboss-relation > * pk-field="d_id" > * foreign-key-column="d_id_fk" > */ > public abstract DivisionLocal getDivision(); > and > /** > * @param division division of this person > * > * @ejb:interface-method view-type="local" > */ > public abstract void setDivision(DivisionLocal division); > > Regards > > Chris > -=-=-= > > -----Original Message----- > From: Shaw, Chris > Sent: 08 January 2002 16:17 > To: '[EMAIL PROTECTED]' > Subject: RE: JBoss v3.0 and Oracle typemapping > > > More info... > > You can see from the error that it bombs out when creating: > jbosscmp-jdbc.xml > which is at the point where it is writing the foreign-key-mapping > > ..after the bean information I get the following relationship info....this > is all that the *rest* of the file contains.... > > <relationships> > <ejb-relation> > <ejb-relation-name>mentor-person</ejb-relation-name> > > <!-- one to many --> > <foreign-key-mapping> > > <ejb-relationship-role> > > <ejb-relationship-role-name>many-persons-have-one-mentor</ejb- > relationship-r > ole-name> > <fk-constraint>false</fk-constraint> <!-- there wont be a > fk > here --> > <foreign-key-fields /> > </ejb-relationship-role> > > <ejb-relationship-role> > > <ejb-relationship-role-name>many-persons-have-one-mentor</ejb- > relationship-r > ole-name> > <fk-constraint>true</fk-constraint> > <foreign-key-fields> > <foreign-key-field> > <field-name>id</field-name> > <column-name>p_id</column-name> > </foreign-key-field> > </foreign-key-fields> > </ejb-relationship-role> > > </foreign-key-mapping> > > </ejb-relation> > <ejb-relation> > <ejb-relation-name>division-person</ejb-relation-name> > > <!-- one to many --> > <foreign-key-mapping> > > <ejb-relationship-role> > > <ejb-relationship-role-name>many-persons-have-one-division</ejb- > relationship > -role-name> > > ....and here it just abruptly stops.... > > Chris > -=-=-= > > (BTW, I was wrong, it does not work at all whether with Oracle8 or > Hypersonic SQL, sorry). > > -----Original Message----- > From: Shaw, Chris > Sent: 08 January 2002 14:55 > To: '[EMAIL PROTECTED]' > Subject: RE: JBoss v3.0 and Oracle typemapping > > > Apologies....I forgot to include the error message: > > [ejbdoclet] Running <jboss/> > [ejbdoclet] Generating jboss.xml. > [ejbdoclet] Generating jaws.xml. > [ejbdoclet] Generating jbosscmp-jdbc.xml. > [ejbdoclet] Running XDoclet failed: > [ejbdoclet] <<Shouldn't swap now>> > [ejbdoclet] 1 error > [ejbdoclet] 9 warnings > [ejbdoclet] javadoc: In doclet class xdoclet.DocletTask$DocletMain, > method > start has thrown an exception java.lang.reflect.InvocationTargetException > > and running ant in verbose mode gives the following: > at xdoclet.DocletTask.execute(DocletTask.java:217) > at > org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:104) > > Regards > > Chris > -=-=-= > > -----Original Message----- > From: Shaw, Chris > Sent: 08 January 2002 11:29 > To: '[EMAIL PROTECTED]' > Subject: JBoss v3.0 and Oracle typemapping > > > Hi, > > If I use typemapping of 'Oracle8' then this works with setting the JBoss > version as 2.4 > ...but fails when I set JBoss version as 3.0 (see below)......it works > with > Hypersonic SQL typemapping for both BTW. > > Chris > -=-=-= > > <jboss version="3.0" xmlencoding="UTF-8" typemapping="Oracle8" > datasource="OracleDS" destdir="${build.dir}/ejb/META-INF"/> > > Any e-mail message from the European Central Bank (ECB) is sent in good > faith but shall neither be binding nor construed as constituting a > commitment by the ECB except where provided for in a written agreement. > This e-mail is intended only for the use of the recipient(s) named above. > Any unauthorised disclosure, use or dissemination, either in whole or in > part, is prohibited. > If you have received this e-mail in error, please notify the sender > immediately via e-mail and delete this e-mail from your system. > > > _______________________________________________ > Xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
