I can see how this would be nice, but hibernate.query.imports already makes me feel a bit quesy (and can be a source of bugs). I don't really wish to compound this by introducing a similar thing into the mapping files.
----- Original Message ----- From: "Donnerstag, Juergen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 15, 2002 10:48 PM Subject: [Hibernate] XML Mapping Option: class prefix > > I'm fairly new to hibernate. Please apologize if this is silly question. > > I have several XML mapping files, one for each table. Each mapping file > contains several locations where fully qualified class names are required. > > Like hibernate.query.imports is there a way to define the package, or at > least some common root package which is used as a common prefix. I wouldn't > have to type in the fully qualified class name over and over again. Besides > it makes it easier to modify and more flexible. I could imagine a hibernate > property as default location and <hibernate-mapping> and <class> as > redefinition in case it is needed. > > regards > J�rgen > > > ------------------------------------------------------- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > _______________________________________________ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
