On Fri, 17 Aug 2001 [EMAIL PROTECTED] wrote:
> If you're putting together something that can read sql CREATE TABLE
nup... something that reads a table... it must already exist - I'm using
java.sql.DatabaseMetaData
> I have the impression that most of the XDoclet people are also JBoss
> people, but I am (at least for the time being) working mostly with WLS 6.1.
I've lost track of who's who... but there is also a WLS movement.... and
the key drive atm is to get everything up to scratch for ejb2
> With CMR, a Customer EJB could have a CMR method like java.util.Collection
> getAccounts() managed by the container. The Account EJB could have a
> Customer getCustomer() method. Further, it is possible to make relations
> unidirectional (in the example, the Account.getCustomer() might not be
> defined). If I make a gui tool that spits out SQL, and your tool generates
> XDoclet EJBs, I think your tool could be able to figure out the CMR stuff
> by looking at the SQL and the foreign keys. It wouldn't be able to know
yep... I almost went down that road last night, but held myself back to
get something basic done first. here's my plan:
1. basic 1 table -> 1 bean mapping
2. take a schema, and model it as a heap of ejbs...
cheesr
dim
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/xdoclet-devel
