Hi,
I'm sorry to raise this issue again but after I checked out the latest jBoss
and carried out the build (which was very fast and smooth - great work
guys!) I started the server and couldn't wait to check that
JAWSPersistenceManager bug fix at work. Just to find the following (as a
result of create(..) followed by set...(...)) :
[JAWS] Create entity
[JAWS] Create, id is 8
[JAWS] Insert
[JAWS] Executing:INSERT INTO exchange (rate,id,currencySymbol) VALUES
(?,?,?)
[ExchangeRateBean EJB] RMI TCP Connection(11)-130.205.88.207 INSERT INTO
exchang
e ( rate , id , currencySymbol ) VALUES ( 0.0 , 8 , NULL )
[JAWS] Load SQL:SELECT rate,id,currencySymbol FROM exchange WHERE id=?
[Default] RMI TCP Connection(11)-130.205.88.207 SELECT rate , id ,
currencySymbo
l FROM exchange WHERE id = 8
at
org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.storeEntity(JAWSPer
sistenceManager.java:732)
at
org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invoke(EntityS
ynchronizationInterceptor.java:250)
at
org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.
java:82)
at
org.jboss.ejb.plugins.EntityInstanceInterceptor.invoke(EntityInstance
Interceptor.java:88)
at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:151)
at
org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPCon
tainerInvoker.java:129)
at java.lang.reflect.Method.invoke(Native Method)
at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241)
at sun.rmi.transport.Transport$1.run(Transport.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:139)
at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:4
43)
at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport
.java:643)
at java.lang.Thread.run(Thread.java:484)
[Default] java.rmi.ServerException: Store failed; nested exception is:
java.lang.ClassCastException:
org.jboss.ejb.plugins.jaws.JAWSPersistence
Manager$PersistenceContext
[Default] java.lang.ClassCastException:
org.jboss.ejb.plugins.jaws.JAWSPersisten
ceManager$PersistenceContext
Where did I go wrong now? I'd appreciate your kind advice/hint on how to
overcome this problem.
Ina
>From: Rickard �berg <[EMAIL PROTECTED]>
>Reply-To: "jBoss" <[EMAIL PROTECTED]>
>To: jBoss <[EMAIL PROTECTED]>
>Subject: Re: [jBoss-User] JAWS O>R problem *** Rickard, are you there? ***
>Date: Tue, 23 May 2000 18:26:46 +0200
>
>Hey
>
>Fredrik Borgh wrote:
> > I'm sorry to bother you with this again, but I want to understand this
> > fully. Looking at your code again a little more thorough, a questions
> > arises. The if-statments - both of them as they are identical - does not
> > allow an update if currentState[i] is null, i.e. if the field has been
> > changed to (or still is) null. Shouldn't it be possible to set a field
>to
> > null after being "not-null" (oldState[i] being non-null)??? As far as I
>can
> > see, your code does not permit this. Have I missed something??
>
>Yep. It works :-) Look harder...
>
>/Rickard
>
>--
>Rickard �berg
>
>@home: +46 13 177937
>Email: [EMAIL PROTECTED]
>http://www.telkel.com
>http://www.jboss.org
>http://www.dreambean.com
>
>
>--
>--------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Problems?: [EMAIL PROTECTED]
>
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
