Thanks Tom, I want to give kudos to the jBoss team for their CVS distribution. I grabbed the latest source and ran build. Worked like a charm, the first time! Distributing all of the necessary jar files with the distribution makes this very easy for newbies. I then took my distribution and started to modify those configuration files. As expected, there were some changes, but nothing too challenging. I was even pleased to see that we no longer have to include the jdbc.driver statement in jboss.properties any longer. One less configuration to make. My existing beans deployed without incident, although my client started throwing a CommunicationException. It was totally my fault, as a jar file from the 2.0 FINAL was still in my classpath. 2.1 appears much more stable than 2.0. Thanks to everyone for the directions. jim ----- Original Message ----- From: "Tom Cook" <[EMAIL PROTECTED]> To: "JBoss-User" <[EMAIL PROTECTED]> Sent: Thursday, March 08, 2001 5:43 PM Subject: Re: [jBoss-User] Bug: EJBException does not result in atransaction rollback > On Thu, 8 Mar 2001, James Cook wrote: > > Sorry to disappoint - the config files have changed considerably since > then, and are pretty much completely incompatible (not quite true, I > don't think, but near as dammit). > > Tom > > > I need to gauge whether I want to try working with 2.1. It took me quite a while > > to figure out how to modify the conf files for 2.0. What's your gut assessment > > on how much the conf files (all of them) have changed between 2.0 to 2.1. If it > > is "very little" I will probably grab 2.1. > > > > thanks, > > jim > > > > ----- Original Message ----- > > From: "danch" <[EMAIL PROTECTED]> > > To: "JBoss-User" <[EMAIL PROTECTED]> > > Sent: Thursday, March 08, 2001 3:40 PM > > Subject: Re: [jBoss-User] Bug: EJBException does not result in atransaction > > rollback > > > > > > > There was a bug in 2.0 and up to several weeks ago where any runtime > > > exception (including EJBException) from ejbStore would fail this way. It > > > is fixed in 2.1 at this time. > > > > > > Jim Archer wrote: > > > > > > > > Hi Jim... > > > > > > > > I agree, the spec says that all non-application exceptions should cause a > > > > rollback and EJBException qualifies! > > > > > > > > Just so we know what to watch out for, which version of jBoss are you > > > > seeing this in? > > > > > > > > Thanks! > > > > > > > > Jim > > > > > > > > --On Thursday, March 08, 2001 11:15 AM -0500 James Cook <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > In my ejbStore() I am throwing an EJBException and it is not causing a > > > > > transaction rollback. Because the transacation stalls, the container > > > > > actually appears to lock up in these cases. The client also stalls. > > > > > > > > > > If I change the exception to RemoteException, all works as expected. The > > > > > transaction is aborted. According to the spec all non-application > > > > > exceptions should cause an automatic rollback. I believe that > > > > > EJBException should be considered a non-application exception. > > > > > > > > > > jim > > > > > > > > > > > > > > > > > > > > -- > > > > > -------------------------------------------------------------- > > > > > To subscribe: [EMAIL PROTECTED] > > > > > To unsubscribe: [EMAIL PROTECTED] > > > > > > > > -- > > > > -------------------------------------------------------------- > > > > To subscribe: [EMAIL PROTECTED] > > > > To unsubscribe: [EMAIL PROTECTED] > > > > > > > > > -- > > > -------------------------------------------------------------- > > > To subscribe: [EMAIL PROTECTED] > > > To unsubscribe: [EMAIL PROTECTED] > > > > > > > > > > > > > > -- > > -------------------------------------------------------------- > > To subscribe: [EMAIL PROTECTED] > > To unsubscribe: [EMAIL PROTECTED] > > > > > > -- > "If you mess with something for long enough it will break." - Schmidt > > > > -- > -------------------------------------------------------------- > To subscribe: [EMAIL PROTECTED] > To unsubscribe: [EMAIL PROTECTED] > > -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED]
