The problem is what dependency am i missing? Here's a copy of the
next posting I made which shows what jar files I have in my classpath
for the task.
The reason I'm looking at XDoclet2 is that XDoclet1 doesn't support
something
I'm looking for:
/***
* @hibernate.class table="FIELDS" descriminator-value="0"
* @hibernate.descriminator column="DATA_TYPE"
*/
public interface Field {
/***
* @hibernate.id column="ID" generator-class="hilo" unsaved-value="0"
*/
int getId();
/***
* @hibernate.property column="NAME"
*/
String getName();
// setters go here
}
/***
* @hibernate.subclass discriminator-value="1"
proxy="com.synygy.field.CharField"
*/
public class CharFieldImpl implements Field, CharField {
...
public int getId() { return id; }
public String getName() { return name; }
/***
* @hibernate.property column="LENGTH"
*/
public int getLength() { return length; }
}
I'd like it to generate the following mapping:
<hibernate-mapping>
<class name="com.synygy.field.Field" table="FIELDS"
discriminator-value="-1">
<id name="id" column="id" type="integer" unsaved-value="0">
<generator class="hilo"/>
</id>
<discriminator column="DATA_TYPE" type="integer"/>
<property name="name" column="NAME" not-null="true"/>
<subclass name="com.synygy.field.CharFieldImpl"
proxy="com.synygy.field.CharField"
discriminator-value="1">
<property name="length" type="integer"/>
</subclass>
</class>
</hibernate-mapping>
However, xdoclet does not generate this, since it only considers the
Superclass
when determining what "subclass" elements to generate. That means, unless I
directly extend the base class (in this case Field, which is an interface),
than it doesn't pick up on CharFieldImpl as a subclass. If i make a
FieldImpl,
and map that instead, and have CharFieldImpl extend it, it works just fine.
Shouldn't the generation scheme be smart enough to deal with <subclass>
definations
if the base class is an interface, and the subclass is implementing it
(obviously, we'd
want to add an "extends" attribute to the @hibernate.subclass to distinguish
which
implemented interface we're dealing with for the mapping).
-----Original Message-----
From: Inger, Matthew
Sent: Thursday, July 15, 2004 11:11 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [Xdoclet-user] JSP 2.0 Support?
Using Maven 1.0 (not the beta).
Here's a list of the jar files I've included in the classpath.
Trying to build the xdoclet-plugins as whole doesn't work right
now, but once it fails, I can go build the hibernate plugin explicitly.
(by the way, i had to guess which jar files to pull from the maven
repository,
since the distributions xdoclet generates doesn't have the dependant jars
included in it)
bsf-2.3.0.jar log4j-1.2.8.jar
commons-beanutils-1.6.1.jar nanocontainer-1.0-beta-1.jar
commons-cli-1.0.jar nanocontainer-ant-1.0-beta-1.jar
commons-collections-2.1.jar picocontainer-1.0.jar
commons-discovery.jar qdox-1.5.jar
commons-jelly-1.0-beta-4.jar velocity-1.4-dev.jar
commons-jexl-1.0-beta-2.jar xdoclet-2.0.jar
commons-lang-2.0.jar xdoclet-plugin-beaninfo-1.0-SNAPSHOT.jar
commons-logging-1.0.4.jar xdoclet-plugin-hibernate-1.0-SNAPSHOT.jar
dom4j-1.4-dev-8.jar xdoclet-plugin-qtags-1.0-SNAPSHOT.jar
generama-1.0.jar xdoclet-testapp-pojo-1.0-SNAPSHOT.jar
-----Original Message-----
From: Konstantin Priblouda [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 15, 2004 10:47 AM
To: [EMAIL PROTECTED]
Subject: RE: [Xdoclet-user] JSP 2.0 Support?
--- "Inger, Matthew" <[EMAIL PROTECTED]> wrote:
> After trying to use XDoclet2, I've come to the
> conclusion that it's
> broken. Building of the entire module suite does
> not work. So, to try
> out what i wanted, I built just the hibernate
> module. That worked, but
> at runtime, I get a failure that means nothing to
> me. I can tell you
> for a fact (after looking at the source code), that
> HibernateMappingPlugin
> has the constructor that is mentioned in this
> exception. Why it's saying it
> can't satisfy the dependency, I don't know, and have
> been unable to figure
> out (thanks to the complexity of picocontainer).
and which maven version are you using? pre 1.0
( especially rc-4 ) is known to have problems with
snapshot dependencies ( in this case it downloads
really outdated pico/nano snapshots from ibiblio )
> Not to mention, it's virtually impossible to find
> any documentation how to
> even create the ANT task and run the thing.
look into maven.xml in root of xdoclet plugins?
regards,
=====
----[ Konstantin Pribluda ( ko5tik ) ]----------------
Zu Verstärkung meines Teams suche ich ab Sofort einen
Softwareentwickler[In] für die Festanstellung.
Arbeitsort: Mainz
Skills: Programieren, Kentnisse in OpenSource-Bereich
----[ http://www.pribluda.de ]------------------------
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
