You think fugly?  It already does fugly reflection and decapitalization for
the first letter  just to match the accessor to a column name.  Why is it
any more fugly to process underscores?  

I do suppose that databases that do identify case within the column name
could make things a little wierd (e.g. would getThisField() translate to
'this_field' or 'thisField'?).  But still I believe the SQL-92 spec is for
case insensitive column names.  From a perfromance standpoint, its
practically no difference (all happens when the concrete class is created at
deployment time).  

I'll try the orion-ejb-jar.xml, but I'm guessing I'm going to need to
provide a complete orion-ejb-jar.xml file, not just the hierarchy required
for the cmp-field-mapping fields.  Theres a lot of junk in there I don't
want to follow and if I'm doing quick development I will need to far more
than makes sense.  Which definately makes our existing persistence, caching,
and coding paradigm easier to use than CMP EJB, once again seems to indicate
that EJB might still not be needed for most serverside applications (still
more hype and 'neat' technology than is practical in the majority of
situations, IMHO).

-----Original Message-----
From: Hani Suleiman [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 12:32 PM
To: Aaron Tavistock; Orion-Interest <[EMAIL PROTECTED]>
Subject: Re: [orion-interest]EJB2.0 spec or implementation?


On 28/12/01 3:20 pm, "Aaron Tavistock" <[EMAIL PROTECTED]> wrote:

> 
> More importantly, I'm aware I can change the post-deployment descriptor
> created by Orion but thats a major pain-in-da-behind if I'm doing
> development and want to redeploy several times.  When I've tried putting
an
> partial orion-ejb-jar.xml into the package, its never worked right,
implying
> that I need to copy a previously deployed version to modify - again
> extremely cumbersome.
> 
Well, this IS the correct way to do it. I don't see why you can't just do it
once. Having a partial orion-ejb-jar.xml certainly does work. You just need
to make sure it has sufficient information in it and is usable. Start off
with a complete one and start trimming things, and check it works after
every trim! Adding an automatic underscoring thing is too too fugly!


Reply via email to