Not the interfaces are specific for a database, but the bean implementation methods. To get database metadata, for instance, for an Oracle database, you need a different implementation of the method. So, while the method will remain the same (actually the interfaces here are empty, only the superinterface has methods) the implementation methods could (and does) vary.
For a user, to specify the database she uses at configuration time or by selecting from a drop down list it's absolutely the same, so I am convinced that our architecture is well designed. Thanks, Marco ----- Original Message ----- From: "Konstantin Priblouda" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 07, 2003 9:36 AM Subject: Re: [Xdoclet-user] How to specify inheriting interfaces > > --- Marco Tedone <[EMAIL PROTECTED]> wrote: > > Hi, we are developing an unusual applicatoin, > > basically centered on session > > beans which manage database (not entity beans, > > because the data to be > > retrieved are dynamic). To make our application > > multi-database compliant, > > and following a pattern, we defined basically one > > Session bean for each used > > database (MySQL, Oracle, SQLServer, Postgresql and > > other could be added). > > The application then choose the right session bean > > depending on user > > selections and this is possible thanks to a common > > interface which all the > > database-specific interfaces inherit from. This way > > a client will have > > simply to get a reference to the super-interface (as > > the methods are common > > for every session bean) and polymorphism will be > > guaranteed. So far so good. > > So far we developed the session beans manually but > > now I would like to > > migrate to XDoclet, even because we are planning to > > develop other beans, and > > XDoclet will be of great help. > > > > As you will probably guess, our problem is how we > > could define via XDoclet > > that each database-specific interface will inherit > > from the common one (now > > is possible because all the interface was declared > > manually). > > You should definitely take a look at the hibernate... > You can use POJOs and decide which database to use on > configurtation level. Almost transparently.... > > S you will have no database specific interfaces at > all. > > 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!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 > _______________________________________________ > xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
