Ken,
Steps 1 & 4 apply to any application architecture. With out ejb, steps 2 & 3 are
replaced by check and modify if needed all JDBC statements that touch the
modified table(s). Seems to me the EJB solution is easier.
Bulk accessors and BMP would eliminate steps 2 & 3 in most cases. You'll still
need to update some class but you don't need to redeploy your beans. You can
also use XML for chunks of data that aren't an integral part of your business
logic, then only steps 1 & 4 are needed.
--Victor
Ken Burcham wrote:
> Hiya!
>
> I'm just getting into the ejb fray after doing various other kinds of java
> stuff for the last couple of years. I'm wondering about the maintenance
> issue with ejb.
>
> My fear is (using cmp), doesn't the table to ejb mapping by hand get really
> unwieldy? Like say you need to add a field to your table/bean. Seems like
> that would require:
>
> 1) adding the field to the db
> 2) adding the field to your remote interface and bean implementation
> 3) adding the field to your deployment descriptor
> 4) taking advantage of the new field in your servlet, webpages, etc.
>
> with bmp, then you even have to update your sql.
>
> When multiplied over 1000 objects, does this become a maintenance nightmare?
> Or is there a better way/I'm missing something (often the case!).
>
> Thanks for talking with me about this.
>
> ken.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
