> Well, i wasn't thinking any tags would be changed, per se. Just a new
> attribute or tag would be added and then the templates would detect
> whether
> to use the app server tag (@jboss:column-name) or the generic tag.

Yup, but my point is that the attributes/tags should be good/generic to
cover all cases. And this is very important: we should support multiple
app servers in one bean. I know some framework writer or those who
support multiple servers use Xdoclet and put @wl:/@websphere/@etc tags
in their source. Naming the tag @ejb:column-name is not a solution. Is
it for websphere or weblogic? Sure if you don't specify it it's for all
app servers, but if you want to differentiate then you should be able to
specify it. Think of it, it should be common to use different values for
the same tag for different servers.

Ara.

> >From: "Ara Abrahamian" <[EMAIL PROTECTED]>
> >To: "'Patrick Lightbody'" <[EMAIL PROTECTED]>,
> ><[EMAIL PROTECTED]>
> >Subject: RE: [Xdoclet-user] Generic "column name" support
> >Date: Tue, 11 Dec 2001 20:52:26 +0330
> >
> > > From: Patrick Lightbody [mailto:[EMAIL PROTECTED]]
> > > Sent: Tuesday, December 11, 2001 8:46 PM
> > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > Subject: RE: [Xdoclet-user] Generic "column name" support
> > >
> > >
> > > It doesn't seem to me that it is anything more than adding some
> >"if/else"
> > > logic to the .j files and deciding on a location to place this
global
> > > name.
> > > I'd be more than happy to send in some patches with my ideas for
this.
> >:)
> >
> >The implementation should be straight forward (thanks to the template
> >engine). The important thing is semantics. This is very debatable and
> >remember it's easy to modify template files but expensive to change
@tag
> >semantics (specially from an end-user's perspective).
> >
> >Ara.
> >
> > > >From: "Ara Abrahamian" <[EMAIL PROTECTED]>
> > > >To: "'Patrick Lightbody'" <[EMAIL PROTECTED]>,
> > > ><[EMAIL PROTECTED]>
> > > >Subject: RE: [Xdoclet-user] Generic "column name" support
> > > >Date: Tue, 11 Dec 2001 13:38:40 +0330
> > > >
> > > >Go back to old ejbdoclet archives, we've already talked about it
> >there
> > > >:o)
> > > >In fact I proposed what I called *unified persistence tags*. I'm
too
> > > >much busy these days to tackle it lonely. So you're welcome to
join
> > > >Xdoclet-devel list and continue this discussion there and
actually
> > > >implement it. It's tricky to find a good generic solution for it.
> > > >
> > > >PS: These kind of standard @tags should be even embraced by Sun
and
> >ejb
> > > >vendors too, it'll let you define a set of standard @tags and
viola
> >it
> > > >deploys on anything. And I'm not talking about embracing Xdoclet
and
> >its
> > > >engine but just the @tags.
> > > >
> > > >Ara.
> > > >
> > > > > -----Original Message-----
> > > > > From: [EMAIL PROTECTED]
> >[mailto:xdoclet-user-
> > > > > [EMAIL PROTECTED]] On Behalf Of Patrick Lightbody
> > > > > Sent: Tuesday, December 11, 2001 1:17 PM
> > > > > To: [EMAIL PROTECTED]
> > > > > Subject: [Xdoclet-user] Generic "column name" support
> > > > >
> > > > > A feature I'd like to see is for the vendor tasks to start
> >supporting
> > > >a
> > > > > generic "column" tag. Right now, I need to do:
> > > > >
> > > > > @jboss:column-name name="id"
> > > > > @orion:persistence persistence-name="id"
> > > > >
> > > > > To declare for orion and jboss that the column for that value
be
> >named
> > > > > "id".
> > > > > I think we can still keep support for this, but why add:
> > > > >
> > > > > @ejb:column-name name="id"
> > > > >
> > > > > Yes, I know technically there is no concept of a "column name"
in
> >the
> > > > > standard ejb-jar.xml, so putting it in the ejb namespace might
> >suck,
> > > >but
> > > > > basically, the idea is to get all the <vendor>.j files to
agree on
> >a
> > > >way
> > > > > to
> > > > > specify these column names as possible. This would allow for
my
> >EJBs
> > > >to
> > > > > support app servers that I didn't even plan on.
> > > > >
> > > > > In fact, this idea could be extended further even, such as
> >table-name,
> > > >and
> > > > > auto-create-table and auto-remove-table. I suppose this list
would
> > > >have to
> > > > > be limited to a common subset the major of the vendor tasks
> >support
> > > > > though.
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > -Pat
> > > > >
> > > > >
_________________________________________________________________
> > > > > Get your FREE download of MSN Explorer at
> > > >http://explorer.msn.com/intl.asp
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Xdoclet-user mailing list
> > > > > [EMAIL PROTECTED]
> > > > > https://lists.sourceforge.net/lists/listinfo/xdoclet-user
> > > >
> > > >
> > > >_________________________________________________________
> > > >Do You Yahoo!?
> > > >Get your free @yahoo.com address at http://mail.yahoo.com
> > > >
> > > >
> > > >_______________________________________________
> > > >Xdoclet-user mailing list
> > > >[EMAIL PROTECTED]
> > > >https://lists.sourceforge.net/lists/listinfo/xdoclet-user
> > >
> > >
> > > _________________________________________________________________
> > > Get your FREE download of MSN Explorer at
> >http://explorer.msn.com/intl.asp
> >
> >
> >_________________________________________________________
> >Do You Yahoo!?
> >Get your free @yahoo.com address at http://mail.yahoo.com
> >
> 
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at
http://explorer.msn.com/intl.asp


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to