There is a problem that when deployement of a new CMP bean, all existed
data base is delete (DROP TABLE) by default behavior. is there a way
to disable DROP CRAETE TABLE and instead use an existing table.
P.s.
WebLogic solution was to enable mapping between Table name, and Fields
to existing table name and fields. However this require you to create the
table yourself.
> -----Original Message-----
> From: Andreas Schaefer [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, July 19, 2000 8:31 AM
> To: jBoss Dev Developer
> Subject: [jBoss-Dev] CMP Database Mapping
>
> Hi Geeks
>
> After I found out how to setup a CMP for my PostgreSQL DB
> I tried to do the same for the actual jBoss from the CVS repository.
> But this seems to be quite different and I was wondering if someone
> can give me a hint how to setup.
>
>
> At my actual company we use Stored Procedures to update or delete
> data on the DB. Because of the actual discussion how to move to EJB
> we also encounter the problem that Stored Procedure could not be used
> within a CMP Entity Bean (WebLogic).
> According to my understanding of CMP it should be possible for an
> application server to support this because if you map your Entity Bean
> to an "Insert", "Update" or "Delete" SQL statement or to particular Stored
> Procedure call should not that big difference.
> The difference is that instead of mapping members to record attributes it
> needs also to map members to the parameter in the "Insert" and "Update"
> Stored Procedure.
> This will make jBoss at little bit more advanced to WebLogic, what do you
> think?
>
> Have fun
>
> Andreas Schaefer
>
> P.S.: You maybe think why should jBoss support Stored Procedures for
> CMP. But it works simmilar that setter/getter methods in Java Beans
> because it allows the DB administrator to get his/her hands between the
> call and the change of the data. This is necessary if the DB administrator
> wants to implement a stronger security or advanced constraints. In
> addition
> it can increase the performance because Stored Procedures are compiled
> on the DB. This becomes more important if the DB is not only used by
> EJB beans but also by other (mostly legacy) applications.
>
