To address your JAWS question: An insert is run at the end of the
ejbCreate call. Are you populating all the required (non-NULL) fields in
your bean implementation in the ejbCreate call? Or do you call ejbCreate
and then a number of "setters" to add all the required columns? If the
latter, how do you ensure all calls are within one transaction?
Aaron
On Sun, 24 Sep 2000, Birgit und Gerd wrote:
> Hi,
>
> we are evaluating JBoss for a comercial project.
> At the moment we are working with Weblogic.
> We are looking for cheap alternativ for our smaller
> customers.
>
> In 2.0 BETA-PROD-01 I found two problems that keeps us
> from trying to do the step from testing level
> to production level with JBoss:
>
> 1. The EntityContext does return null in its
> getPrimaryKey method.
>
> 2. I'm using Jaws for CMP. I have an Entity
> Bean with two CMP Attributes id and name.
> When I create an Entity in a transaction the
> following SQL is fired:
> INSERT INTO Table1 (Name,Id) VALUES (null, 193)
> UPDATE Table1 SET Name= 'New Row' ,Id= 193 WHERE Id= 193
>
> Since everything takes place in one transaction I would
> expect a single SQL Statement:
> INSERT INTO Table1 (Name,Id) VALUES ('New Row', 193)
>
> We need CMP to work like that because we like to have
> DB fields that don't allow NULLs.
>
>
> Will these problems be fixed? If yes, when?
>
> Regards
> Gerd
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
