OK I agree. Really ejb:persistence is the perfect name for persistence tags of ejb.
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Patrick Lightbody > Sent: Wednesday, March 06, 2002 10:31 PM > To: [EMAIL PROTECTED] > Subject: Re: [Xdoclet-devel] Re: Proposal - ejb:persistence tags > > Well, let's decide on something. Personally, I think ejb:persistence is > exactly what it should be, since we talking about _EJBs_ here, nothing > else. > The changes being made are going to be in templates that use tags like > <ejb-name>, so let's not fool ourselves in to thinking that we can come up > with some grand naming scheme to work with all types of components. > > As for the words column and table-name, I think those should stay too. > Again, let's remember what we are trying to accomplish here. We want a > simple convention that will solve 80% of users needs. Let's be realistic > too, and realize that every single app server uses databases to persist > their EJBs. Also remember that if someone is trying to deploy a special > bean > using a special resource other than a database, it is likely that person > is > doing some pretty abnormal stuff and falls in the remaining 20%. That > person > can just not use these generic tags and go ahead with the pre-existing > vendor tags. > > My point is this: let's find generalizations that fit for 80%, and leave > the > remaining 20% alone. We can't find a magic schema that works for everyone, > so let's just agree on schema that works for _almost_everyone_. > > A decision needs to be made, and it needs to be made soon. > > -Pat > > > >From: David Jencks <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: Re: [Xdoclet-devel] Re: Proposal - ejb:persistence tags > >Date: Wed, 6 Mar 2002 09:06:54 -0500 > > > >Well, I don't like the db, so there;-) > > > >I think really the tag should be @persistence, but it is kind of long. > You > >don't want to identify the java end with ejb, and I don't want to > identify > >the persistent store at the other end with db or rm (resource manager) or > >eis (enterprise information system) or... > > > >Maybe @ps persistence store? > > > >david jencks > > > >On 2002.03.06 00:20:35 -0500 Ara Abrahamian wrote: > > > What about @db:persistence? :-) I don't like the ejb: in > > > ejb:persistence! > > > > > > And yes, the multi-tag approach will make it easy to write templates > for > > > this case, no need for a tag handler. > > > > > > Ara. > > > > > > > -----Original Message----- > > > > From: [EMAIL PROTECTED] [mailto:xdoclet- > devel- > > > > [EMAIL PROTECTED]] On Behalf Of David Jencks > > > > Sent: Wednesday, March 06, 2002 12:58 AM > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: [Xdoclet-devel] Re: Proposal - ejb:persistence tags > > > > > > > > I agree especially with "@ejb:persistence" over "db:*". Hopefully > > > soon we > > > > will have cmp to non-relational resource adapters/EIS > > > > > > > > Maybe the multi-tag approach would keep templates reasonably simple > > > while > > > > avoiding too many tag handler classes?? > > > > > > > > david jencks > > > > > > > > On 2002.03.05 14:39:47 -0500 Marcus Brito wrote: > > > > > > > > > > Read on. My answer is a bit long. > > > > > > > > > > Em Ter, 2002-03-05 às 12:49, Ara Abrahamian escreveu: > > > > > > > Class-level: > > > > > > > @ejb:persistence table-name="foo" datasrouce="jdbc/FooDS" > > > > > > > > > > > > > > method-level: > > > > > > > @ejb:persistence-field column="bar" > > > > > > > > > > > > Looks good. > > > > > > > > > > > > Marcus Brito (?) > > > > > > > > > > That's me :) > > > > > > > > > > > What do you think about @db:mapping instead of ejb:persistence? > We > > > can > > > > > > support JDO too for example. I really prefer this one. > > > > > > > > > > I really prefer @ejb:persistence instead of @db:mapping. > > > "persistence" > > > > > is a more generic word and the one used in the EJB specification. > > > There > > > > > is no need to use "database". > > > > > > > > > > However "table" and "column" are very database-centric terms > anyway > > > -- > > > > > perhaps we should use "schema" and "attribute". But then this may > > > cause > > > > > some confusion... well, let's see what other people have to say. > > > > > > > > > > I also prefer a single "ejb:persistence" tag instead of > > > > > "ejb:persistence" and "ejb:persistence-field". > > > > > > > > > > > The other question is how we're going to start implementing it > and > > > > from > > > > > > where. > > > > > > > > > > This is a task for people maintaing vendor tasks and templates. > They > > > > > should always look on these tags *in addition* to the > > > vendor-specific > > > > > tags. > > > > > > > > > > For example, in JBoss (which is my playing field) templates, it > > > should > > > > > look for @ejb:persistence table-name in addition no > > > @jboss:table-name. > > > > > The template would be something like this: > > > > > > > > > > <XDtClass:ifHasClassTag tagName="jboss:table-name"> > > > > > <table-name><XDtClass:classTagValue tagName="jboss:table-name" > > > > > paramName="table-name" paramNum="0"/></table-name> > > > > > </XDtClassifHasClassTag> > > > > > <XDtClass:ifDoesntHaveClassTag tagName="jboss:table-name"> > > > > > <XDtClass:ifHasClassTag tagName="ejb:persistence" > > > > > paramName="table-name"> > > > > > <table-name><XDtClass:classTagValue tagName="ejb:persistence" > > > > > paramName="table-name"/></table-name> > > > > > </XDtClass:ifHasClassTag> > > > > > </XDtClass:ifDoesntHaveClassTag> > > > > > > > > > > Note that using this approach enables the vendor template to use > the > > > > > "new" standard tags while retaining backwards compatibility. The > bad > > > > > news is that as you can see from the above example, the template > > > editing > > > > > will be a boring task. > > > > > > > > > > Another approach is to write a JBossTagHandler with methods like > > > > > ifHasTableName and getTableName, that would already look for the > > > correct > > > > > tags. If done this way, the above template would be like this: > > > > > > > > > > <XDtJBoss:ifHasTableName> > > > > > <table-name><XDtJBoss:tableName/></table-name> > > > > > </XDtJBoss:ifHasTableName> > > > > > > > > > > Much nicer, huh? The <XDtJBoss:tableName/> method would look first > > > for > > > > > the @jboss:table-name tag in the current class and if not found > look > > > for > > > > > @ejb:persistence table-name="" tag. > > > > > > > > > > The good news here is that coding the JBossTagHandler class is > more > > > fun > > > > > then editing templates. And far more easier to debug. The bad news > > > is, > > > > > well, that it would require coding a new class, what is a more > > > radical > > > > > approach then editing templates. > > > > > > > > > > My personal position on what was questioned above: The tags should > > > avoid > > > > > database-specific terms. The two mentioned examples could be: > > > > > > > > > > @ejb:persistence schema="table" > > > > > @ejb:persistence attribute="column" > > > > > > > > > > And about the option between modifying templates and writing new > tag > > > > > handlers, I prefer writing new tag handlers. It's more elegant. > > > > > > > > > > > > > > > -- > > > > > Ja ne, > > > > > Marcus Brito > > > > > mailto: [EMAIL PROTECTED] > > > > > > > > > > Anime Gaiden - De fãs para fãs, sempre. > > > > > http://www.animegaiden.com.br > > > > > > > > > > > > > _______________________________________________ > > > > Xdoclet-devel mailing list > > > > [EMAIL PROTECTED] > > > > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > > > > > > > > > > _______________________________________________ > > > Xdoclet-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > > > > > > > >_______________________________________________ > >Xdoclet-devel mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > > > _________________________________________________________________ > MSN Photos is the easiest way to share and print your photos: > http://photos.msn.com/support/worldwide.aspx > > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
