Hi,
No transaction - no commit, as easy as that. Working on Sun: I would call
that a(nother) bug in Sun.
Burkhard
----- Original Message -----
From: "ralph" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 17, 2001 7:42 AM
Subject: Re: [JBoss-user] cloudscape only
> Very good. Thank you.
>
> All business methods had the 'Required' attribute, but all home interface
> methods - including the offending create() method - had the attribute
> 'NotSupported'. A long time ago I thought it should be that way and it
> always worked with the Sun platform. After I changed the TX attribute of
> the create method to 'Required' the record showed up immediately.
>
> But:
> Why - in the original case - did the record not show up even after
shutting
> down jBoss? As the record had been created - transaction or not - it
should
> show up some time in the database and not disappear with the jBoss server.
> That should also happen independent of commit options - or not?
>
> Why did the 'NotSupported' ejbCreate(...) version work with Sun's
> implementation ? Is there some flexibility how this situation can be
> implemented? Some configuration setting which would cause jBoss to write
> the record to the database when shutting down?
> Is this a jBoss bug?
>
> Ralph
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
