Menu
▾
▴
springframework-developer — Spring Framework developers list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(55) |
Mar
(100) |
Apr
(203) |
May
(330) |
Jun
(190) |
Jul
(302) |
Aug
(323) |
Sep
(197) |
Oct
(245) |
Nov
(490) |
Dec
(330) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(194) |
Feb
(400) |
Mar
(416) |
Apr
(415) |
May
(359) |
Jun
(381) |
Jul
(491) |
Aug
(311) |
Sep
(291) |
Oct
(273) |
Nov
(355) |
Dec
(266) |
| 2005 |
Jan
(306) |
Feb
(303) |
Mar
(520) |
Apr
(346) |
May
(255) |
Jun
(221) |
Jul
(171) |
Aug
(247) |
Sep
(147) |
Oct
(125) |
Nov
(165) |
Dec
(65) |
| 2006 |
Jan
(90) |
Feb
(53) |
Mar
(121) |
Apr
(103) |
May
(113) |
Jun
(103) |
Jul
(104) |
Aug
(67) |
Sep
(78) |
Oct
(82) |
Nov
(78) |
Dec
(70) |
| 2007 |
Jan
(77) |
Feb
(76) |
Mar
(63) |
Apr
(30) |
May
(47) |
Jun
(41) |
Jul
(44) |
Aug
(44) |
Sep
(49) |
Oct
(33) |
Nov
(25) |
Dec
(21) |
| 2008 |
Jan
(45) |
Feb
(13) |
Mar
(15) |
Apr
(12) |
May
(9) |
Jun
(33) |
Jul
(30) |
Aug
(7) |
Sep
(20) |
Oct
(17) |
Nov
(20) |
Dec
(10) |
| 2009 |
Jan
(8) |
Feb
(5) |
Mar
(12) |
Apr
(17) |
May
(19) |
Jun
(97) |
Jul
(77) |
Aug
(33) |
Sep
(24) |
Oct
(41) |
Nov
(16) |
Dec
(32) |
| 2010 |
Jan
(24) |
Feb
(14) |
Mar
(50) |
Apr
(71) |
May
(70) |
Jun
(64) |
Jul
(45) |
Aug
(62) |
Sep
(32) |
Oct
(4) |
Nov
(12) |
Dec
(2) |
| 2011 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(3) |
May
(6) |
Jun
(1) |
Jul
(4) |
Aug
(3) |
Sep
(4) |
Oct
(6) |
Nov
(3) |
Dec
(3) |
| 2012 |
Jan
(4) |
Feb
(8) |
Mar
(6) |
Apr
(10) |
May
(2) |
Jun
(3) |
Jul
(11) |
Aug
(10) |
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(4) |
Feb
(1) |
Mar
(9) |
Apr
(1) |
May
(8) |
Jun
(2) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(10) |
Dec
(8) |
| 2014 |
Jan
(3) |
Feb
(12) |
Mar
(9) |
Apr
(12) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(9) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(7) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2016 |
Jan
(7) |
Feb
(5) |
Mar
(5) |
Apr
(5) |
May
(8) |
Jun
(4) |
Jul
(5) |
Aug
(4) |
Sep
(6) |
Oct
(7) |
Nov
(2) |
Dec
(3) |
| 2017 |
Jan
(7) |
Feb
(8) |
Mar
(7) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(8) |
Sep
(4) |
Oct
(2) |
Nov
(3) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Juergen H. <ju...@in...> - 2005-03-23 17:08:43
|
That's interesting... OK, so I guess I should add "dataAccessResourceFailureCodes" again, and register 17002 there for Oracle. Convinced :-) Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of tho...@tr... Sent: Wednesday, March 23, 2005 4:22 PM To: spr...@li... Subject: Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException Oracle must have that built into the driver: Translating SQLException with SQLState 'null' and errorCode '17002' and message [Io exception: Connection reset]; Thomas Quoting Juergen Hoeller <ju...@in...>: > I've prototypically added such an InvalidResultSetAccessException with > corresponding "invalidResultAccessCodes" on SQLErrorCodes, and added 17003 > as such an error code for Oracle. Of course, we can still rework this if we > decide on some other solution. > > Regarding DataAccessResourceFailureException: Indeed, resource failure can > happen during JDBC access too. But can we identify it through a SQL error > code? I think we can't: that error code usually comes from the database, and > the very point of DataAccessResourceFailureException is that we couldn't > access the database... > > Juergen > > > -----Original Message----- > From: Juergen Hoeller [mailto:ju...@in...] > Sent: Wednesday, March 23, 2005 2:56 PM > To: spr...@li... > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > OK, worth a reconsideration, I guess :-) > > DataRetrievalFailureException is maybe too generic for associating it with > SQL error codes. It's mainly meant to be thrown by ORM tools or specific > DAOs, where domain entities with specific ids could not be found. > > Maybe we should add a specific exception class that says "ResultSet access > failed", like "InvalidResultSetAccessException"? Such an exception should > probably be a subclass of InvalidDataAccessResourceUsageException, not of > DataRetrievalFailureException. > > After all, such a failure is somewhat similar to BadSqlGrammarException: the > user probably specified an invalid column index or name, just like bad SQL > is probably the result of a user error too (selecting invalid columns or the > like). > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On Behalf > Of Thomas Risberg > Sent: Wednesday, March 23, 2005 5:52 AM > To: spr...@li...; Thomas Risberg > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > If we decide to keep DataRetrievalFailureException -- one code for > Oracle is '17003' [Invalid column index]. > > Thomas > > On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > > > I think removing most of these are OK. > > > > Except, > > > > DataAccessResourceFailureException - is possible, I think. Connection > > could be lost during execution of a query. Reconnect and execute the > > query again is a possibility here. > > > > DataRetrievalFailureException indicates some kind of error retrieving > > column values - bad column index or column has been removed or > > renamed. Not recoverable, but could be worth reporting with this > > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > > This is especially true when calling stored procedures where you don't > > specify the sql for the resultset that is generated. > > > > I think the above categories are worth keeping and we should gather > > error codes that represent these failures. If I could only have one > > of them, then DataRetrievalFailureException would be the one. > > > > Thomas > > > > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > > > >> Thomas, > >> > >> I've cleaned up the SQLErrorCodes class a little bit: there are no > >> categories for OptimisticLockingFailureException, > >> DataRetrievalFailureException and DataAccessResourceFailureException > >> anymore. None of those should be caused by SQL error codes, but only > >> by > >> conditions at the ORM/DAO higher level (respectively connect failure > >> in case > >> of DataAccessResourceFailureException, which isn't indicated by a SQL > >> error > >> code either). > >> > >> I've also removed the category for > >> PessimisticLockingFailureException. We > >> generally don't offer fields for exception base classes in > >> SQLErrorCodes but > >> rather encourage specifying codes for fine-grained exception > >> subclasses. We > >> have fields for all three subclasses here: CannotAcquireLockException, > >> DeadlockLoserDataAccessException (I've renamed the associated field > >> to the > >> shortened "deadlockLoserCodes") and > >> CannotSerializeTransactionException. > >> > >> BTW, the latter exception isn't thrown anywhere currently. All others > >> that > >> we offer fields in SQLErrorCodes for are mapped for at least one > >> database in > >> the meantime. > >> > >> Strictly speaking, removing the SQLErrorCodes fields for those > >> exceptions is > >> not backwards-compatible. However, as we can't figure out how a > >> database > >> could cause them through error codes, this shouldn't matter; I think > >> it's > >> more important to offer a set of meaningful exception categories > >> there. This > >> should be acceptable for 1.2. And if someone unexpectedly found an > >> error > >> code for such a condition, it wouldn't be a bad thing to hear about > >> it :-) > >> > >> Juergen > >> > >> > >> > >> -----Original Message----- > >> From: spr...@li... > >> [mailto:spr...@li...]On > >> Behalf > >> Of tho...@tr... > >> Sent: Monday, March 21, 2005 4:22 PM > >> To: spr...@li... > >> Subject: Re: [Springframework-developer] > >> DeadlockLoserDataAccessException vs CannotAcquireLockException > >> > >> > >> > >> I'm OK with PessimisticLockingFailureException as the superclass name. > >> > >> I wasn't questioning the existence of > >> OptimisticLockingFailureException, I > >> just > >> can't come up with any SQLException error codes that would translate > >> into > >> it - > >> it's not a SQL/Database error. It is definitely thrown by the > >> ORM/DAO code. > >> > >> I can add this in later today, so we could make 1.2RC1. > >> > >> Thomas > >> > >> > >> Quoting Juergen Hoeller <ju...@in...>: > >> > >>> FYI, we already do throw OptimisticLockingFailureException for > >>> Hibernate > >> and > >>> JDO since the beginning of time :-) > >>> > >>> PessimisticLockingFailureException as superclass for > >>> CannotAcquireLockException and co sounds appropriate to me. Do we > >>> want to > >>> include this in 1.2 RC1, which was originally scheduled for today? > >>> ;-) It > >>> looks like 1.2 RC1 won't be released before Wednesday anyway. > >>> > >>> Juergen > >>> > >>> > >>> -----Original Message----- > >>> From: spr...@li... > >>> [mailto:spr...@li...]On > >>> Behalf > >>> Of Rod Johnson > >>> Sent: Monday, March 21, 2005 3:00 PM > >>> To: spr...@li... > >>> Subject: Re: [Springframework-developer] > >>> DeadlockLoserDataAccessException vs CannotAcquireLockException > >>> > >>> > >>> Thomas > >>> > >>>> ConcurrencyFailureException > >>>> '- TransactionLockingFailureException [X] > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> '- OptimisticLockingFailureException [X?] > >>>> > >>>> The [X] indicates that I think we should provide the option for > >>>> separate > >>>> categories in sql-error-codes.xml for this exception. Some of the > >>>> lower > >>>> exception classes might not make sense for all databases, but > >>>> TransactionLockingFailure and OptimisticLockingFailure will provide > >>>> enough information to retry the transaction if the app developer > >>>> want to > >>>> do that. > >>> > >>> I like this proposal. Though should it ben > >>> PessimisticLockingFailureException to match > >>> OptimisticLockingFailureException? Yes, the latter is intended to be > >>> thrown by ORM tools, not JDBC-level operations. So we could convert > >>> from > >>> whatever the ORM tool throws. Or developers could throw it > >>> themselves, > >>> still allowing for consistent handling within Spring's DAO > >>> abstraction. > >>> > >>> R > >>>> > >>>> Oracle might have these categories defined: > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> > >>>> while MySQL might have this > >>>> '- TransactionLockingFailureException [X] > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >> > >> > >> > >> > >> > >> ------------------------------------------------------- > >> SF email is sponsored by - The IT Product Guide > >> Read honest & candid reviews on hundreds of IT Products from real > >> users. > >> Discover which products truly live up to the hype. Start reading now. > >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: 2005 Windows Mobile Application > >> Contest > >> Submit applications for Windows Mobile(tm)-based Pocket PCs or > >> Smartphones > >> for the chance to win $25,000 and application distribution. Enter > >> today at > >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Rob H. <ro...@ca...> - 2005-03-23 17:07:12
|
I agree with that. In the final release we should probably change to using MX4J rather than the Sun RI for our JMX dist. ROb Juergen Hoeller wrote: >The reason why I've removed jmx-tools.jar is that I've moved the JMX >AdapterHost stuff back to the sandbox for 1.2 RC1 (and commented out the >jmx-tools dependency). It currently just served as a wrapper around Sun's >old JMX RI HtmlAdaptor, which dates back to 2002 and seems to have been >abandoned, so I guess we shouldn't ship it unless someone asks for it. > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf >Of Juergen Hoeller >Sent: Wednesday, March 23, 2005 5:44 PM >To: spr...@li... >Subject: RE: [Springframework-developer] Missing JARS > > >I've moved rowset.jar and removed jmx-tools.jar for 1.2 RC1, which probably >just needs to be reflected in the Eclipse classpath file. > >Juergen > > >-----Original Message----- >From: spr...@li... >[mailto:spr...@li...]On Behalf >Of Rod Johnson >Sent: Tuesday, March 22, 2005 1:14 PM >To: spr...@li... >Subject: [Springframework-developer] Missing JARS > > >I'm seeing rowset.jar and jmx-tools.jar missing in CVS. > >R > > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > >------------------------------------------------------- >This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 >Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows >Embedded(r) & Windows Mobile(tm) platforms, applications & content. >Register >by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > >------------------------------------------------------- >This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 >Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows >Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register >by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click >_______________________________________________ >Springframework-developer mailing list >Spr...@li... >https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > |
|
From: Juergen H. <ju...@in...> - 2005-03-23 17:04:32
|
Yes, I guess I'll change the exceptions there to InvalidResultSetAccessException too. A subclass of InvalidDataAccessResourceUsageException seems appropriate there. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of tho...@tr... Sent: Wednesday, March 23, 2005 5:04 PM To: spr...@li... Subject: Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException That's fine - we should probably coordinate these changes with the exceptions thrown by the new SqlRowSet - it currently throws DataRetrievalFailureExeceptions when accessing row data like getString(3). Thomas Quoting Juergen Hoeller <ju...@in...>: > OK, worth a reconsideration, I guess :-) > > DataRetrievalFailureException is maybe too generic for associating it with > SQL error codes. It's mainly meant to be thrown by ORM tools or specific > DAOs, where domain entities with specific ids could not be found. > > Maybe we should add a specific exception class that says "ResultSet access > failed", like "InvalidResultSetAccessException"? Such an exception should > probably be a subclass of InvalidDataAccessResourceUsageException, not of > DataRetrievalFailureException. > > After all, such a failure is somewhat similar to BadSqlGrammarException: the > user probably specified an invalid column index or name, just like bad SQL > is probably the result of a user error too (selecting invalid columns or the > like). > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On Behalf > Of Thomas Risberg > Sent: Wednesday, March 23, 2005 5:52 AM > To: spr...@li...; Thomas Risberg > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > If we decide to keep DataRetrievalFailureException -- one code for > Oracle is '17003' [Invalid column index]. > > Thomas > > On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > > > I think removing most of these are OK. > > > > Except, > > > > DataAccessResourceFailureException - is possible, I think. Connection > > could be lost during execution of a query. Reconnect and execute the > > query again is a possibility here. > > > > DataRetrievalFailureException indicates some kind of error retrieving > > column values - bad column index or column has been removed or > > renamed. Not recoverable, but could be worth reporting with this > > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > > This is especially true when calling stored procedures where you don't > > specify the sql for the resultset that is generated. > > > > I think the above categories are worth keeping and we should gather > > error codes that represent these failures. If I could only have one > > of them, then DataRetrievalFailureException would be the one. > > > > Thomas > > > > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > > > >> Thomas, > >> > >> I've cleaned up the SQLErrorCodes class a little bit: there are no > >> categories for OptimisticLockingFailureException, > >> DataRetrievalFailureException and DataAccessResourceFailureException > >> anymore. None of those should be caused by SQL error codes, but only > >> by > >> conditions at the ORM/DAO higher level (respectively connect failure > >> in case > >> of DataAccessResourceFailureException, which isn't indicated by a SQL > >> error > >> code either). > >> > >> I've also removed the category for > >> PessimisticLockingFailureException. We > >> generally don't offer fields for exception base classes in > >> SQLErrorCodes but > >> rather encourage specifying codes for fine-grained exception > >> subclasses. We > >> have fields for all three subclasses here: CannotAcquireLockException, > >> DeadlockLoserDataAccessException (I've renamed the associated field > >> to the > >> shortened "deadlockLoserCodes") and > >> CannotSerializeTransactionException. > >> > >> BTW, the latter exception isn't thrown anywhere currently. All others > >> that > >> we offer fields in SQLErrorCodes for are mapped for at least one > >> database in > >> the meantime. > >> > >> Strictly speaking, removing the SQLErrorCodes fields for those > >> exceptions is > >> not backwards-compatible. However, as we can't figure out how a > >> database > >> could cause them through error codes, this shouldn't matter; I think > >> it's > >> more important to offer a set of meaningful exception categories > >> there. This > >> should be acceptable for 1.2. And if someone unexpectedly found an > >> error > >> code for such a condition, it wouldn't be a bad thing to hear about > >> it :-) > >> > >> Juergen > >> > >> > >> > >> -----Original Message----- > >> From: spr...@li... > >> [mailto:spr...@li...]On > >> Behalf > >> Of tho...@tr... > >> Sent: Monday, March 21, 2005 4:22 PM > >> To: spr...@li... > >> Subject: Re: [Springframework-developer] > >> DeadlockLoserDataAccessException vs CannotAcquireLockException > >> > >> > >> > >> I'm OK with PessimisticLockingFailureException as the superclass name. > >> > >> I wasn't questioning the existence of > >> OptimisticLockingFailureException, I > >> just > >> can't come up with any SQLException error codes that would translate > >> into > >> it - > >> it's not a SQL/Database error. It is definitely thrown by the > >> ORM/DAO code. > >> > >> I can add this in later today, so we could make 1.2RC1. > >> > >> Thomas > >> > >> > >> Quoting Juergen Hoeller <ju...@in...>: > >> > >>> FYI, we already do throw OptimisticLockingFailureException for > >>> Hibernate > >> and > >>> JDO since the beginning of time :-) > >>> > >>> PessimisticLockingFailureException as superclass for > >>> CannotAcquireLockException and co sounds appropriate to me. Do we > >>> want to > >>> include this in 1.2 RC1, which was originally scheduled for today? > >>> ;-) It > >>> looks like 1.2 RC1 won't be released before Wednesday anyway. > >>> > >>> Juergen > >>> > >>> > >>> -----Original Message----- > >>> From: spr...@li... > >>> [mailto:spr...@li...]On > >>> Behalf > >>> Of Rod Johnson > >>> Sent: Monday, March 21, 2005 3:00 PM > >>> To: spr...@li... > >>> Subject: Re: [Springframework-developer] > >>> DeadlockLoserDataAccessException vs CannotAcquireLockException > >>> > >>> > >>> Thomas > >>> > >>>> ConcurrencyFailureException > >>>> '- TransactionLockingFailureException [X] > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> '- OptimisticLockingFailureException [X?] > >>>> > >>>> The [X] indicates that I think we should provide the option for > >>>> separate > >>>> categories in sql-error-codes.xml for this exception. Some of the > >>>> lower > >>>> exception classes might not make sense for all databases, but > >>>> TransactionLockingFailure and OptimisticLockingFailure will provide > >>>> enough information to retry the transaction if the app developer > >>>> want to > >>>> do that. > >>> > >>> I like this proposal. Though should it ben > >>> PessimisticLockingFailureException to match > >>> OptimisticLockingFailureException? Yes, the latter is intended to be > >>> thrown by ORM tools, not JDBC-level operations. So we could convert > >>> from > >>> whatever the ORM tool throws. Or developers could throw it > >>> themselves, > >>> still allowing for consistent handling within Spring's DAO > >>> abstraction. > >>> > >>> R > >>>> > >>>> Oracle might have these categories defined: > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> > >>>> while MySQL might have this > >>>> '- TransactionLockingFailureException [X] > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >> > >> > >> > >> > >> > >> ------------------------------------------------------- > >> SF email is sponsored by - The IT Product Guide > >> Read honest & candid reviews on hundreds of IT Products from real > >> users. > >> Discover which products truly live up to the hype. Start reading now. > >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: 2005 Windows Mobile Application > >> Contest > >> Submit applications for Windows Mobile(tm)-based Pocket PCs or > >> Smartphones > >> for the chance to win $25,000 and application distribution. Enter > >> today at > >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Juergen H. <ju...@in...> - 2005-03-23 17:02:06
|
The reason why I've removed jmx-tools.jar is that I've moved the JMX AdapterHost stuff back to the sandbox for 1.2 RC1 (and commented out the jmx-tools dependency). It currently just served as a wrapper around Sun's old JMX RI HtmlAdaptor, which dates back to 2002 and seems to have been abandoned, so I guess we shouldn't ship it unless someone asks for it. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Juergen Hoeller Sent: Wednesday, March 23, 2005 5:44 PM To: spr...@li... Subject: RE: [Springframework-developer] Missing JARS I've moved rowset.jar and removed jmx-tools.jar for 1.2 RC1, which probably just needs to be reflected in the Eclipse classpath file. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Rod Johnson Sent: Tuesday, March 22, 2005 1:14 PM To: spr...@li... Subject: [Springframework-developer] Missing JARS I'm seeing rowset.jar and jmx-tools.jar missing in CVS. R ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Alexandru P. <the...@ez...> - 2005-03-23 17:01:21
|
Thanks everybody for your answers. My case is pretty uncommon: i am trying to integrate the H3 support into the existing stable 1.1.5 version. You may ask why this? I need some of the features from H3 (simple, ain't it :-) ). So, being a week old Spring user (in fact i haven't write a single line of code, so I would say Spring researcher) I thought it would be a good idea to ask the developers if my feeling was right. -- :alex |.::the_mindstorm::.| [quote Mark St Godard::on 3/23/2005 5:23 PM] > > > > Yeah Alex, > > For me (as an Eclipse user) it was just an exercise in CTRL-Shift-O to > reference the new APIs... and to also change > the applicationContext XML to reference the new LocalSessionFactoryBean... > > Note: I was not using Annotations at this point on this current project... > so it was pretty straightforward > > Cheers > Mark > > > > Colin Sampaleanu > <col...@ex... > m> To > Sent by: spr...@li... > springframework-d rceforge.net > eveloper-admin@li cc > sts.sourceforge.n > et Subject > Re: [Springframework-developer] > Hibernate3 vs Hibernate2 > 03/23/2005 09:10 > AM > > > Please respond to > springframework-d > eveloper > > > > > > > Alexandru Popescu wrote: > >>Hi! >> >>I saw in the ML that the Hibernate3 support is in CVS HEAD already. Can > you point me to the main >>changes provided in the Spring support for Hibernate3 vs Hibernate2? (i > expected there where changes >>required by the changes (from check to unchecked) exceptions in Hibernate3 > and for supporting the >>new features, but it will be more easy for me to have a Spring expert > opinion on this). >> >> > Alex, > > Juergen did the actual conversion, so is the final authority, but the > port is mostly a straight port of the existing classes to reflect the > new packages used by Hibernate 3. One difference in Hibernate 3 is that > Hibernate 3 does throw unchecked exceptions instead of checked > exceptions, but Spring users should actually be insulated from that, as > they would have normally be catching Spring's own unchcked > DataAccessExceptionHierarchy. Spring's HibernateTemplate class for > Hibernate v3 does add the important methods added to v3's Session, such > as the 'load()' variants which take an entityName, e.g.: > http://www.hibernate.org/hib_docs/v3/api/ > > Generally, you should be able to take existing Spring-based code using > the Hibernate 2 support, and convert it to using the Hibernate 3 > support, by just changing all org.springframework.hibernate.* package > names to org.springframework.hibernate3.*. Any breakage (not that you > should generally expect any) should generally be from changes in > Hibernate itself between versions, and not the Spring support code. Note > that Hibernate has actually deprecated a few methods on the Session > interface (they are only available now as part of the > org.hibernate.classic.Session interface. I believe HibernateTemplate has > also removed some of the methods which were directly exposed and are now > deprecated. > > Colin > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Juergen H. <ju...@in...> - 2005-03-23 16:44:49
|
I've moved rowset.jar and removed jmx-tools.jar for 1.2 RC1, which probably just needs to be reflected in the Eclipse classpath file. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Rod Johnson Sent: Tuesday, March 22, 2005 1:14 PM To: spr...@li... Subject: [Springframework-developer] Missing JARS I'm seeing rowset.jar and jmx-tools.jar missing in CVS. R ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: <tho...@tr...> - 2005-03-23 16:42:37
|
rowset.jar was moved to the lib/j2ee directory. Don't know about the jmx-tools.jar. Thomas Quoting Rod Johnson <ro...@in...>: > I'm seeing rowset.jar and jmx-tools.jar missing in CVS. > > R > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: <tho...@tr...> - 2005-03-23 16:03:48
|
That's fine - we should probably coordinate these changes with the exceptions thrown by the new SqlRowSet - it currently throws DataRetrievalFailureExeceptions when accessing row data like getString(3). Thomas Quoting Juergen Hoeller <ju...@in...>: > OK, worth a reconsideration, I guess :-) > > DataRetrievalFailureException is maybe too generic for associating it with > SQL error codes. It's mainly meant to be thrown by ORM tools or specific > DAOs, where domain entities with specific ids could not be found. > > Maybe we should add a specific exception class that says "ResultSet access > failed", like "InvalidResultSetAccessException"? Such an exception should > probably be a subclass of InvalidDataAccessResourceUsageException, not of > DataRetrievalFailureException. > > After all, such a failure is somewhat similar to BadSqlGrammarException: the > user probably specified an invalid column index or name, just like bad SQL > is probably the result of a user error too (selecting invalid columns or the > like). > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On Behalf > Of Thomas Risberg > Sent: Wednesday, March 23, 2005 5:52 AM > To: spr...@li...; Thomas Risberg > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > If we decide to keep DataRetrievalFailureException -- one code for > Oracle is '17003' [Invalid column index]. > > Thomas > > On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > > > I think removing most of these are OK. > > > > Except, > > > > DataAccessResourceFailureException - is possible, I think. Connection > > could be lost during execution of a query. Reconnect and execute the > > query again is a possibility here. > > > > DataRetrievalFailureException indicates some kind of error retrieving > > column values - bad column index or column has been removed or > > renamed. Not recoverable, but could be worth reporting with this > > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > > This is especially true when calling stored procedures where you don't > > specify the sql for the resultset that is generated. > > > > I think the above categories are worth keeping and we should gather > > error codes that represent these failures. If I could only have one > > of them, then DataRetrievalFailureException would be the one. > > > > Thomas > > > > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > > > >> Thomas, > >> > >> I've cleaned up the SQLErrorCodes class a little bit: there are no > >> categories for OptimisticLockingFailureException, > >> DataRetrievalFailureException and DataAccessResourceFailureException > >> anymore. None of those should be caused by SQL error codes, but only > >> by > >> conditions at the ORM/DAO higher level (respectively connect failure > >> in case > >> of DataAccessResourceFailureException, which isn't indicated by a SQL > >> error > >> code either). > >> > >> I've also removed the category for > >> PessimisticLockingFailureException. We > >> generally don't offer fields for exception base classes in > >> SQLErrorCodes but > >> rather encourage specifying codes for fine-grained exception > >> subclasses. We > >> have fields for all three subclasses here: CannotAcquireLockException, > >> DeadlockLoserDataAccessException (I've renamed the associated field > >> to the > >> shortened "deadlockLoserCodes") and > >> CannotSerializeTransactionException. > >> > >> BTW, the latter exception isn't thrown anywhere currently. All others > >> that > >> we offer fields in SQLErrorCodes for are mapped for at least one > >> database in > >> the meantime. > >> > >> Strictly speaking, removing the SQLErrorCodes fields for those > >> exceptions is > >> not backwards-compatible. However, as we can't figure out how a > >> database > >> could cause them through error codes, this shouldn't matter; I think > >> it's > >> more important to offer a set of meaningful exception categories > >> there. This > >> should be acceptable for 1.2. And if someone unexpectedly found an > >> error > >> code for such a condition, it wouldn't be a bad thing to hear about > >> it :-) > >> > >> Juergen > >> > >> > >> > >> -----Original Message----- > >> From: spr...@li... > >> [mailto:spr...@li...]On > >> Behalf > >> Of tho...@tr... > >> Sent: Monday, March 21, 2005 4:22 PM > >> To: spr...@li... > >> Subject: Re: [Springframework-developer] > >> DeadlockLoserDataAccessException vs CannotAcquireLockException > >> > >> > >> > >> I'm OK with PessimisticLockingFailureException as the superclass name. > >> > >> I wasn't questioning the existence of > >> OptimisticLockingFailureException, I > >> just > >> can't come up with any SQLException error codes that would translate > >> into > >> it - > >> it's not a SQL/Database error. It is definitely thrown by the > >> ORM/DAO code. > >> > >> I can add this in later today, so we could make 1.2RC1. > >> > >> Thomas > >> > >> > >> Quoting Juergen Hoeller <ju...@in...>: > >> > >>> FYI, we already do throw OptimisticLockingFailureException for > >>> Hibernate > >> and > >>> JDO since the beginning of time :-) > >>> > >>> PessimisticLockingFailureException as superclass for > >>> CannotAcquireLockException and co sounds appropriate to me. Do we > >>> want to > >>> include this in 1.2 RC1, which was originally scheduled for today? > >>> ;-) It > >>> looks like 1.2 RC1 won't be released before Wednesday anyway. > >>> > >>> Juergen > >>> > >>> > >>> -----Original Message----- > >>> From: spr...@li... > >>> [mailto:spr...@li...]On > >>> Behalf > >>> Of Rod Johnson > >>> Sent: Monday, March 21, 2005 3:00 PM > >>> To: spr...@li... > >>> Subject: Re: [Springframework-developer] > >>> DeadlockLoserDataAccessException vs CannotAcquireLockException > >>> > >>> > >>> Thomas > >>> > >>>> ConcurrencyFailureException > >>>> '- TransactionLockingFailureException [X] > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> '- OptimisticLockingFailureException [X?] > >>>> > >>>> The [X] indicates that I think we should provide the option for > >>>> separate > >>>> categories in sql-error-codes.xml for this exception. Some of the > >>>> lower > >>>> exception classes might not make sense for all databases, but > >>>> TransactionLockingFailure and OptimisticLockingFailure will provide > >>>> enough information to retry the transaction if the app developer > >>>> want to > >>>> do that. > >>> > >>> I like this proposal. Though should it ben > >>> PessimisticLockingFailureException to match > >>> OptimisticLockingFailureException? Yes, the latter is intended to be > >>> thrown by ORM tools, not JDBC-level operations. So we could convert > >>> from > >>> whatever the ORM tool throws. Or developers could throw it > >>> themselves, > >>> still allowing for consistent handling within Spring's DAO > >>> abstraction. > >>> > >>> R > >>>> > >>>> Oracle might have these categories defined: > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> > >>>> while MySQL might have this > >>>> '- TransactionLockingFailureException [X] > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >> > >> > >> > >> > >> > >> ------------------------------------------------------- > >> SF email is sponsored by - The IT Product Guide > >> Read honest & candid reviews on hundreds of IT Products from real > >> users. > >> Discover which products truly live up to the hype. Start reading now. > >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: 2005 Windows Mobile Application > >> Contest > >> Submit applications for Windows Mobile(tm)-based Pocket PCs or > >> Smartphones > >> for the chance to win $25,000 and application distribution. Enter > >> today at > >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Mark St G. <stg...@ca...> - 2005-03-23 15:23:57
|
Yeah Alex,
For me (as an Eclipse user) it was just an exercise in CTRL-Shift-O to
reference the new APIs... and to also change
the applicationContext XML to reference the new LocalSessionFactoryBean...
Note: I was not using Annotations at this point on this current project...
so it was pretty straightforward
Cheers
Mark
Colin Sampaleanu
<col...@ex...
m> To
Sent by: spr...@li...
springframework-d rceforge.net
eveloper-admin@li cc
sts.sourceforge.n
et Subject
Re: [Springframework-developer]
Hibernate3 vs Hibernate2
03/23/2005 09:10
AM
Please respond to
springframework-d
eveloper
Alexandru Popescu wrote:
>Hi!
>
>I saw in the ML that the Hibernate3 support is in CVS HEAD already. Can
you point me to the main
>changes provided in the Spring support for Hibernate3 vs Hibernate2? (i
expected there where changes
>required by the changes (from check to unchecked) exceptions in Hibernate3
and for supporting the
>new features, but it will be more easy for me to have a Spring expert
opinion on this).
>
>
Alex,
Juergen did the actual conversion, so is the final authority, but the
port is mostly a straight port of the existing classes to reflect the
new packages used by Hibernate 3. One difference in Hibernate 3 is that
Hibernate 3 does throw unchecked exceptions instead of checked
exceptions, but Spring users should actually be insulated from that, as
they would have normally be catching Spring's own unchcked
DataAccessExceptionHierarchy. Spring's HibernateTemplate class for
Hibernate v3 does add the important methods added to v3's Session, such
as the 'load()' variants which take an entityName, e.g.:
http://www.hibernate.org/hib_docs/v3/api/
Generally, you should be able to take existing Spring-based code using
the Hibernate 2 support, and convert it to using the Hibernate 3
support, by just changing all org.springframework.hibernate.* package
names to org.springframework.hibernate3.*. Any breakage (not that you
should generally expect any) should generally be from changes in
Hibernate itself between versions, and not the Spring support code. Note
that Hibernate has actually deprecated a few methods on the Session
interface (they are only available now as part of the
org.hibernate.classic.Session interface. I believe HibernateTemplate has
also removed some of the methods which were directly exposed and are now
deprecated.
Colin
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: <tho...@tr...> - 2005-03-23 15:22:31
|
Oracle must have that built into the driver: Translating SQLException with SQLState 'null' and errorCode '17002' and message [Io exception: Connection reset]; Thomas Quoting Juergen Hoeller <ju...@in...>: > I've prototypically added such an InvalidResultSetAccessException with > corresponding "invalidResultAccessCodes" on SQLErrorCodes, and added 17003 > as such an error code for Oracle. Of course, we can still rework this if we > decide on some other solution. > > Regarding DataAccessResourceFailureException: Indeed, resource failure can > happen during JDBC access too. But can we identify it through a SQL error > code? I think we can't: that error code usually comes from the database, and > the very point of DataAccessResourceFailureException is that we couldn't > access the database... > > Juergen > > > -----Original Message----- > From: Juergen Hoeller [mailto:ju...@in...] > Sent: Wednesday, March 23, 2005 2:56 PM > To: spr...@li... > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > OK, worth a reconsideration, I guess :-) > > DataRetrievalFailureException is maybe too generic for associating it with > SQL error codes. It's mainly meant to be thrown by ORM tools or specific > DAOs, where domain entities with specific ids could not be found. > > Maybe we should add a specific exception class that says "ResultSet access > failed", like "InvalidResultSetAccessException"? Such an exception should > probably be a subclass of InvalidDataAccessResourceUsageException, not of > DataRetrievalFailureException. > > After all, such a failure is somewhat similar to BadSqlGrammarException: the > user probably specified an invalid column index or name, just like bad SQL > is probably the result of a user error too (selecting invalid columns or the > like). > > Juergen > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On Behalf > Of Thomas Risberg > Sent: Wednesday, March 23, 2005 5:52 AM > To: spr...@li...; Thomas Risberg > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > If we decide to keep DataRetrievalFailureException -- one code for > Oracle is '17003' [Invalid column index]. > > Thomas > > On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > > > I think removing most of these are OK. > > > > Except, > > > > DataAccessResourceFailureException - is possible, I think. Connection > > could be lost during execution of a query. Reconnect and execute the > > query again is a possibility here. > > > > DataRetrievalFailureException indicates some kind of error retrieving > > column values - bad column index or column has been removed or > > renamed. Not recoverable, but could be worth reporting with this > > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > > This is especially true when calling stored procedures where you don't > > specify the sql for the resultset that is generated. > > > > I think the above categories are worth keeping and we should gather > > error codes that represent these failures. If I could only have one > > of them, then DataRetrievalFailureException would be the one. > > > > Thomas > > > > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > > > >> Thomas, > >> > >> I've cleaned up the SQLErrorCodes class a little bit: there are no > >> categories for OptimisticLockingFailureException, > >> DataRetrievalFailureException and DataAccessResourceFailureException > >> anymore. None of those should be caused by SQL error codes, but only > >> by > >> conditions at the ORM/DAO higher level (respectively connect failure > >> in case > >> of DataAccessResourceFailureException, which isn't indicated by a SQL > >> error > >> code either). > >> > >> I've also removed the category for > >> PessimisticLockingFailureException. We > >> generally don't offer fields for exception base classes in > >> SQLErrorCodes but > >> rather encourage specifying codes for fine-grained exception > >> subclasses. We > >> have fields for all three subclasses here: CannotAcquireLockException, > >> DeadlockLoserDataAccessException (I've renamed the associated field > >> to the > >> shortened "deadlockLoserCodes") and > >> CannotSerializeTransactionException. > >> > >> BTW, the latter exception isn't thrown anywhere currently. All others > >> that > >> we offer fields in SQLErrorCodes for are mapped for at least one > >> database in > >> the meantime. > >> > >> Strictly speaking, removing the SQLErrorCodes fields for those > >> exceptions is > >> not backwards-compatible. However, as we can't figure out how a > >> database > >> could cause them through error codes, this shouldn't matter; I think > >> it's > >> more important to offer a set of meaningful exception categories > >> there. This > >> should be acceptable for 1.2. And if someone unexpectedly found an > >> error > >> code for such a condition, it wouldn't be a bad thing to hear about > >> it :-) > >> > >> Juergen > >> > >> > >> > >> -----Original Message----- > >> From: spr...@li... > >> [mailto:spr...@li...]On > >> Behalf > >> Of tho...@tr... > >> Sent: Monday, March 21, 2005 4:22 PM > >> To: spr...@li... > >> Subject: Re: [Springframework-developer] > >> DeadlockLoserDataAccessException vs CannotAcquireLockException > >> > >> > >> > >> I'm OK with PessimisticLockingFailureException as the superclass name. > >> > >> I wasn't questioning the existence of > >> OptimisticLockingFailureException, I > >> just > >> can't come up with any SQLException error codes that would translate > >> into > >> it - > >> it's not a SQL/Database error. It is definitely thrown by the > >> ORM/DAO code. > >> > >> I can add this in later today, so we could make 1.2RC1. > >> > >> Thomas > >> > >> > >> Quoting Juergen Hoeller <ju...@in...>: > >> > >>> FYI, we already do throw OptimisticLockingFailureException for > >>> Hibernate > >> and > >>> JDO since the beginning of time :-) > >>> > >>> PessimisticLockingFailureException as superclass for > >>> CannotAcquireLockException and co sounds appropriate to me. Do we > >>> want to > >>> include this in 1.2 RC1, which was originally scheduled for today? > >>> ;-) It > >>> looks like 1.2 RC1 won't be released before Wednesday anyway. > >>> > >>> Juergen > >>> > >>> > >>> -----Original Message----- > >>> From: spr...@li... > >>> [mailto:spr...@li...]On > >>> Behalf > >>> Of Rod Johnson > >>> Sent: Monday, March 21, 2005 3:00 PM > >>> To: spr...@li... > >>> Subject: Re: [Springframework-developer] > >>> DeadlockLoserDataAccessException vs CannotAcquireLockException > >>> > >>> > >>> Thomas > >>> > >>>> ConcurrencyFailureException > >>>> '- TransactionLockingFailureException [X] > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> '- OptimisticLockingFailureException [X?] > >>>> > >>>> The [X] indicates that I think we should provide the option for > >>>> separate > >>>> categories in sql-error-codes.xml for this exception. Some of the > >>>> lower > >>>> exception classes might not make sense for all databases, but > >>>> TransactionLockingFailure and OptimisticLockingFailure will provide > >>>> enough information to retry the transaction if the app developer > >>>> want to > >>>> do that. > >>> > >>> I like this proposal. Though should it ben > >>> PessimisticLockingFailureException to match > >>> OptimisticLockingFailureException? Yes, the latter is intended to be > >>> thrown by ORM tools, not JDBC-level operations. So we could convert > >>> from > >>> whatever the ORM tool throws. Or developers could throw it > >>> themselves, > >>> still allowing for consistent handling within Spring's DAO > >>> abstraction. > >>> > >>> R > >>>> > >>>> Oracle might have these categories defined: > >>>> '- CannotAquireLockException [X] > >>>> '- CannotSerializeTransactionException [X] > >>>> '- DeadlockLoserDataAccessException [X] > >>>> > >>>> while MySQL might have this > >>>> '- TransactionLockingFailureException [X] > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >>> > >>> > >>> ------------------------------------------------------- > >>> SF email is sponsored by - The IT Product Guide > >>> Read honest & candid reviews on hundreds of IT Products from real > >>> users. > >>> Discover which products truly live up to the hype. Start reading now. > >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >>> _______________________________________________ > >>> Springframework-developer mailing list > >>> Spr...@li... > >>> https://lists.sourceforge.net/lists/listinfo/springframework- > >>> developer > >>> > >> > >> > >> > >> > >> > >> ------------------------------------------------------- > >> SF email is sponsored by - The IT Product Guide > >> Read honest & candid reviews on hundreds of IT Products from real > >> users. > >> Discover which products truly live up to the hype. Start reading now. > >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.net email is sponsored by: 2005 Windows Mobile Application > >> Contest > >> Submit applications for Windows Mobile(tm)-based Pocket PCs or > >> Smartphones > >> for the chance to win $25,000 and application distribution. Enter > >> today at > >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > >> _______________________________________________ > >> Springframework-developer mailing list > >> Spr...@li... > >> https://lists.sourceforge.net/lists/listinfo/springframework-developer > >> > >> > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones > for the chance to win $25,000 and application distribution. Enter today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Juergen H. <ju...@in...> - 2005-03-23 15:15:39
|
Wow, that took a long time. I sent this more than a day ago... Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Juergen Hoeller Sent: Tuesday, March 22, 2005 9:52 PM To: spr...@li... Subject: Re: [Springframework-developer] Multiple schedulers I got it to work in the mean time with a recreated file that contains multiple scheduler definitions. Quartz initialization is a beast, it really is. Never trust Quartz API - always look at the implementation. I can commit the recreated file, if you want... Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Juergen Hoeller Sent: Tuesday, March 22, 2005 9:07 PM To: spr...@li... Subject: [Springframework-developer] Multiple schedulers Alef, I've seen that you've committed support for multiple Quartz schedulers in the same application context. However, one file seems to be missing: "multiple-schedulers.xml" in the test package. BTW, pleeeeeeeeeeaaaaaaaaaaase use tabs. Tabs, tabs, tabs. I've recently asked for tabs too, after reformatting some freshly committed spaces-based code. Sometimes I feel like the cleanup maid here. Juergen ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Colin S. <col...@ex...> - 2005-03-23 15:10:28
|
Alexandru Popescu wrote: >Hi! > >I saw in the ML that the Hibernate3 support is in CVS HEAD already. Can you point me to the main >changes provided in the Spring support for Hibernate3 vs Hibernate2? (i expected there where changes >required by the changes (from check to unchecked) exceptions in Hibernate3 and for supporting the >new features, but it will be more easy for me to have a Spring expert opinion on this). > > Alex, Juergen did the actual conversion, so is the final authority, but the port is mostly a straight port of the existing classes to reflect the new packages used by Hibernate 3. One difference in Hibernate 3 is that Hibernate 3 does throw unchecked exceptions instead of checked exceptions, but Spring users should actually be insulated from that, as they would have normally be catching Spring's own unchcked DataAccessExceptionHierarchy. Spring's HibernateTemplate class for Hibernate v3 does add the important methods added to v3's Session, such as the 'load()' variants which take an entityName, e.g.: http://www.hibernate.org/hib_docs/v3/api/ Generally, you should be able to take existing Spring-based code using the Hibernate 2 support, and convert it to using the Hibernate 3 support, by just changing all org.springframework.hibernate.* package names to org.springframework.hibernate3.*. Any breakage (not that you should generally expect any) should generally be from changes in Hibernate itself between versions, and not the Spring support code. Note that Hibernate has actually deprecated a few methods on the Session interface (they are only available now as part of the org.hibernate.classic.Session interface. I believe HibernateTemplate has also removed some of the methods which were directly exposed and are now deprecated. Colin |
|
From: Mark St G. <stg...@ca...> - 2005-03-23 15:05:09
|
Alex,
I have been using the HEAD with Hibernate3 support.... things that I
noted....
- all Spring hibernate 3 packages are under a new package (which will
affect your DAOs... and config)
i.e. org.springframework.orm.hibernate3
<!-- Hibernate SessionFactory -->
<bean id="sessionFactory" class=
"org.springframework.orm.hibernate3.LocalSessionFactoryBean">
<property name="dataSource">
<ref local="dataSource" />
</property>
- Hibernate3 changed their top level package from net.sf.hibernate ->
org.hibernate
So I had to change some of my DAOs to use the new API (org.hibernate)....
as well as use the new HibernateDaoSupport
(org.springframework.orm.hibernate3)
for example...
import org.hibernate.HibernateException;
import org.springframework.orm.hibernate3.support.HibernateDaoSupport;
and yes... Hibernate3 is now using a runtime exception for
org.hibernate.HibernateException ... ahhh....
Cheers
Mark
Alexandru Popescu
<the_mindstorm@ez
legacy.com> To
Sent by: spr...@li...
springframework-d rceforge.net
eveloper-admin@li cc
sts.sourceforge.n
et Subject
[Springframework-developer]
Hibernate3 vs Hibernate2
03/22/2005 06:52
PM
Please respond to
springframework-d
eveloper
Hi!
I saw in the ML that the Hibernate3 support is in CVS HEAD already. Can you
point me to the main
changes provided in the Spring support for Hibernate3 vs Hibernate2? (i
expected there where changes
required by the changes (from check to unchecked) exceptions in Hibernate3
and for supporting the
new features, but it will be more easy for me to have a Spring expert
opinion on this).
many thanks in advance,
--
:alex |.::the_mindstorm::.|
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer
|
|
From: Juergen H. <ju...@in...> - 2005-03-23 14:49:54
|
Hi everybody, I've just finished the last planned features for 1.2 RC1, namely a couple of XML bean definition improvements: * shortcut attributes for "ref" and "value" on "property" and "constructor-arg" * maps can be defined with non-String keys (through a <key> subelement) * String values can be typed, for example collection elements (<value type="...">) See the following issues for details: http://opensource.atlassian.com/projects/spring/browse/SPR-379 http://opensource.atlassian.com/projects/spring/browse/SPR-392 http://opensource.atlassian.com/projects/spring/browse/SPR-542 This should allow us to proceed with the actual 1.2 RC1 release now... I expect the release to happen tomorrow (finally!). Juergen |
|
From: Juergen H. <ju...@in...> - 2005-03-23 14:11:29
|
I've prototypically added such an InvalidResultSetAccessException with corresponding "invalidResultAccessCodes" on SQLErrorCodes, and added 17003 as such an error code for Oracle. Of course, we can still rework this if we decide on some other solution. Regarding DataAccessResourceFailureException: Indeed, resource failure can happen during JDBC access too. But can we identify it through a SQL error code? I think we can't: that error code usually comes from the database, and the very point of DataAccessResourceFailureException is that we couldn't access the database... Juergen -----Original Message----- From: Juergen Hoeller [mailto:ju...@in...] Sent: Wednesday, March 23, 2005 2:56 PM To: spr...@li... Subject: Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException OK, worth a reconsideration, I guess :-) DataRetrievalFailureException is maybe too generic for associating it with SQL error codes. It's mainly meant to be thrown by ORM tools or specific DAOs, where domain entities with specific ids could not be found. Maybe we should add a specific exception class that says "ResultSet access failed", like "InvalidResultSetAccessException"? Such an exception should probably be a subclass of InvalidDataAccessResourceUsageException, not of DataRetrievalFailureException. After all, such a failure is somewhat similar to BadSqlGrammarException: the user probably specified an invalid column index or name, just like bad SQL is probably the result of a user error too (selecting invalid columns or the like). Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Thomas Risberg Sent: Wednesday, March 23, 2005 5:52 AM To: spr...@li...; Thomas Risberg Subject: Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException If we decide to keep DataRetrievalFailureException -- one code for Oracle is '17003' [Invalid column index]. Thomas On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > I think removing most of these are OK. > > Except, > > DataAccessResourceFailureException - is possible, I think. Connection > could be lost during execution of a query. Reconnect and execute the > query again is a possibility here. > > DataRetrievalFailureException indicates some kind of error retrieving > column values - bad column index or column has been removed or > renamed. Not recoverable, but could be worth reporting with this > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > This is especially true when calling stored procedures where you don't > specify the sql for the resultset that is generated. > > I think the above categories are worth keeping and we should gather > error codes that represent these failures. If I could only have one > of them, then DataRetrievalFailureException would be the one. > > Thomas > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > >> Thomas, >> >> I've cleaned up the SQLErrorCodes class a little bit: there are no >> categories for OptimisticLockingFailureException, >> DataRetrievalFailureException and DataAccessResourceFailureException >> anymore. None of those should be caused by SQL error codes, but only >> by >> conditions at the ORM/DAO higher level (respectively connect failure >> in case >> of DataAccessResourceFailureException, which isn't indicated by a SQL >> error >> code either). >> >> I've also removed the category for >> PessimisticLockingFailureException. We >> generally don't offer fields for exception base classes in >> SQLErrorCodes but >> rather encourage specifying codes for fine-grained exception >> subclasses. We >> have fields for all three subclasses here: CannotAcquireLockException, >> DeadlockLoserDataAccessException (I've renamed the associated field >> to the >> shortened "deadlockLoserCodes") and >> CannotSerializeTransactionException. >> >> BTW, the latter exception isn't thrown anywhere currently. All others >> that >> we offer fields in SQLErrorCodes for are mapped for at least one >> database in >> the meantime. >> >> Strictly speaking, removing the SQLErrorCodes fields for those >> exceptions is >> not backwards-compatible. However, as we can't figure out how a >> database >> could cause them through error codes, this shouldn't matter; I think >> it's >> more important to offer a set of meaningful exception categories >> there. This >> should be acceptable for 1.2. And if someone unexpectedly found an >> error >> code for such a condition, it wouldn't be a bad thing to hear about >> it :-) >> >> Juergen >> >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...]On >> Behalf >> Of tho...@tr... >> Sent: Monday, March 21, 2005 4:22 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] >> DeadlockLoserDataAccessException vs CannotAcquireLockException >> >> >> >> I'm OK with PessimisticLockingFailureException as the superclass name. >> >> I wasn't questioning the existence of >> OptimisticLockingFailureException, I >> just >> can't come up with any SQLException error codes that would translate >> into >> it - >> it's not a SQL/Database error. It is definitely thrown by the >> ORM/DAO code. >> >> I can add this in later today, so we could make 1.2RC1. >> >> Thomas >> >> >> Quoting Juergen Hoeller <ju...@in...>: >> >>> FYI, we already do throw OptimisticLockingFailureException for >>> Hibernate >> and >>> JDO since the beginning of time :-) >>> >>> PessimisticLockingFailureException as superclass for >>> CannotAcquireLockException and co sounds appropriate to me. Do we >>> want to >>> include this in 1.2 RC1, which was originally scheduled for today? >>> ;-) It >>> looks like 1.2 RC1 won't be released before Wednesday anyway. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...]On >>> Behalf >>> Of Rod Johnson >>> Sent: Monday, March 21, 2005 3:00 PM >>> To: spr...@li... >>> Subject: Re: [Springframework-developer] >>> DeadlockLoserDataAccessException vs CannotAcquireLockException >>> >>> >>> Thomas >>> >>>> ConcurrencyFailureException >>>> '- TransactionLockingFailureException [X] >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> '- OptimisticLockingFailureException [X?] >>>> >>>> The [X] indicates that I think we should provide the option for >>>> separate >>>> categories in sql-error-codes.xml for this exception. Some of the >>>> lower >>>> exception classes might not make sense for all databases, but >>>> TransactionLockingFailure and OptimisticLockingFailure will provide >>>> enough information to retry the transaction if the app developer >>>> want to >>>> do that. >>> >>> I like this proposal. Though should it ben >>> PessimisticLockingFailureException to match >>> OptimisticLockingFailureException? Yes, the latter is intended to be >>> thrown by ORM tools, not JDBC-level operations. So we could convert >>> from >>> whatever the ORM tool throws. Or developers could throw it >>> themselves, >>> still allowing for consistent handling within Spring's DAO >>> abstraction. >>> >>> R >>>> >>>> Oracle might have these categories defined: >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> >>>> while MySQL might have this >>>> '- TransactionLockingFailureException [X] >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: 2005 Windows Mobile Application >> Contest >> Submit applications for Windows Mobile(tm)-based Pocket PCs or >> Smartphones >> for the chance to win $25,000 and application distribution. Enter >> today at >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Juergen H. <ju...@in...> - 2005-03-23 13:59:23
|
Well, backwards compatibility just affects the Hibernate 2.x version. The Hibernate3 version was migrated straight from that. We could add the owner object in the Hibernate3 version; after all, we haven't officially release the Hibernate3 support yet, so are not constrained by backwards compatibility there. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Washusen, Dan Sent: Tuesday, March 22, 2005 11:39 PM To: spr...@li... Subject: RE: [Springframework-developer] AbstractLobType#nullSafeGetInternal((ResultSet, int, LobHandler) is missing a parameter... Hi Juergen, The version I was looking at (hibernate3) has a since of 1.2. I mistakenly presumed it was new; backward-compatibility is a very good reason not to change it... I was trying to make an implementation of AbstractLobType that didn't read everything into memory. The code is available here (http://forum.springframework.org/viewtopic.php?t=4237). I was going to use the owner to generate a hash to use as a temporary file name. I guess I'll re-implement the logic in AbstractLobType. Cheers, Dan ---------------------------------------------------------------------------- -- From: spr...@li... [mailto:spr...@li...] On Behalf Of Juergen Hoeller Sent: Tuesday, 22 March 2005 5:32 PM To: spr...@li... Subject: Re: [Springframework-developer] AbstractLobType#nullSafeGetInternal((ResultSet, int, LobHandler) is missing a parameter... Hi Dan, I guess there simply hasn't been a need to access the owner object in one of the subclasses yet. AbstractLobType mainly serves as base class for the concrete LOB types that we ship in Spring, which don't need owner access. The problem is that the "nullSafeGetInternal" method would have to change in a non-backwards-compatible fashion to expose the owner, so I'm reluctant to change this without a compelling reason. Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Washusen, Dan Sent: Tuesday, March 22, 2005 4:05 AM To: spr...@li... Subject: [Springframework-developer] AbstractLobType#nullSafeGetInternal((ResultSet, int, LobHandler) is missing a parameter... Hey guys, I'm trying to use the new org.springframework.orm.hibernate3.support.AbstractLobType and I'm wondering why the nullSafeGet implementation doesn't pass the owner parameter to the abstract nullSafeGetInternal method. Should I raise a Jira issue? Cheers, Dan www.about.sensis.com.auA leading Australian advertising, information and directories business.www.sensis.com.auwww.yellowpages.com.auwww.whitepages.com.auwww.cit ysearch.com.auwww.whereis.com.auwww.telstra.com.auwww.tradingpost.com.auThis email and any attachments are intended only for the use of the recipient and may be confidential and/or legally privileged.Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss and/or damage arising from using, opening or transmitting this email.If you are not the intended recipient you must not use, interfere with, disclose, copy or retain this email and you should notify the sender immediately by return email or by contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000] www.about.sensis.com.au A leading Australian advertising, information and directories business. www.sensis.com.au www.yellowpages.com.au www.whitepages.com.au www.citysearch.com.au www.whereis.com.au www.telstra.com.au www.tradingpost.com.au This email and any attachments are intended only for the use of the recipient and may be confidential and/or legally privileged. Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss and/or damage arising from using, opening or transmitting this email. If you are not the intended recipient you must not use, interfere with, disclose, copy or retain this email and you should notify the sender immediately by return email or by contacting Sensis Pty Ltd by telephone on [+61 3 8653 5000] |
|
From: Juergen H. <ju...@in...> - 2005-03-23 13:56:44
|
OK, worth a reconsideration, I guess :-) DataRetrievalFailureException is maybe too generic for associating it with SQL error codes. It's mainly meant to be thrown by ORM tools or specific DAOs, where domain entities with specific ids could not be found. Maybe we should add a specific exception class that says "ResultSet access failed", like "InvalidResultSetAccessException"? Such an exception should probably be a subclass of InvalidDataAccessResourceUsageException, not of DataRetrievalFailureException. After all, such a failure is somewhat similar to BadSqlGrammarException: the user probably specified an invalid column index or name, just like bad SQL is probably the result of a user error too (selecting invalid columns or the like). Juergen -----Original Message----- From: spr...@li... [mailto:spr...@li...]On Behalf Of Thomas Risberg Sent: Wednesday, March 23, 2005 5:52 AM To: spr...@li...; Thomas Risberg Subject: Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException If we decide to keep DataRetrievalFailureException -- one code for Oracle is '17003' [Invalid column index]. Thomas On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > I think removing most of these are OK. > > Except, > > DataAccessResourceFailureException - is possible, I think. Connection > could be lost during execution of a query. Reconnect and execute the > query again is a possibility here. > > DataRetrievalFailureException indicates some kind of error retrieving > column values - bad column index or column has been removed or > renamed. Not recoverable, but could be worth reporting with this > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > This is especially true when calling stored procedures where you don't > specify the sql for the resultset that is generated. > > I think the above categories are worth keeping and we should gather > error codes that represent these failures. If I could only have one > of them, then DataRetrievalFailureException would be the one. > > Thomas > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > >> Thomas, >> >> I've cleaned up the SQLErrorCodes class a little bit: there are no >> categories for OptimisticLockingFailureException, >> DataRetrievalFailureException and DataAccessResourceFailureException >> anymore. None of those should be caused by SQL error codes, but only >> by >> conditions at the ORM/DAO higher level (respectively connect failure >> in case >> of DataAccessResourceFailureException, which isn't indicated by a SQL >> error >> code either). >> >> I've also removed the category for >> PessimisticLockingFailureException. We >> generally don't offer fields for exception base classes in >> SQLErrorCodes but >> rather encourage specifying codes for fine-grained exception >> subclasses. We >> have fields for all three subclasses here: CannotAcquireLockException, >> DeadlockLoserDataAccessException (I've renamed the associated field >> to the >> shortened "deadlockLoserCodes") and >> CannotSerializeTransactionException. >> >> BTW, the latter exception isn't thrown anywhere currently. All others >> that >> we offer fields in SQLErrorCodes for are mapped for at least one >> database in >> the meantime. >> >> Strictly speaking, removing the SQLErrorCodes fields for those >> exceptions is >> not backwards-compatible. However, as we can't figure out how a >> database >> could cause them through error codes, this shouldn't matter; I think >> it's >> more important to offer a set of meaningful exception categories >> there. This >> should be acceptable for 1.2. And if someone unexpectedly found an >> error >> code for such a condition, it wouldn't be a bad thing to hear about >> it :-) >> >> Juergen >> >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...]On >> Behalf >> Of tho...@tr... >> Sent: Monday, March 21, 2005 4:22 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] >> DeadlockLoserDataAccessException vs CannotAcquireLockException >> >> >> >> I'm OK with PessimisticLockingFailureException as the superclass name. >> >> I wasn't questioning the existence of >> OptimisticLockingFailureException, I >> just >> can't come up with any SQLException error codes that would translate >> into >> it - >> it's not a SQL/Database error. It is definitely thrown by the >> ORM/DAO code. >> >> I can add this in later today, so we could make 1.2RC1. >> >> Thomas >> >> >> Quoting Juergen Hoeller <ju...@in...>: >> >>> FYI, we already do throw OptimisticLockingFailureException for >>> Hibernate >> and >>> JDO since the beginning of time :-) >>> >>> PessimisticLockingFailureException as superclass for >>> CannotAcquireLockException and co sounds appropriate to me. Do we >>> want to >>> include this in 1.2 RC1, which was originally scheduled for today? >>> ;-) It >>> looks like 1.2 RC1 won't be released before Wednesday anyway. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...]On >>> Behalf >>> Of Rod Johnson >>> Sent: Monday, March 21, 2005 3:00 PM >>> To: spr...@li... >>> Subject: Re: [Springframework-developer] >>> DeadlockLoserDataAccessException vs CannotAcquireLockException >>> >>> >>> Thomas >>> >>>> ConcurrencyFailureException >>>> '- TransactionLockingFailureException [X] >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> '- OptimisticLockingFailureException [X?] >>>> >>>> The [X] indicates that I think we should provide the option for >>>> separate >>>> categories in sql-error-codes.xml for this exception. Some of the >>>> lower >>>> exception classes might not make sense for all databases, but >>>> TransactionLockingFailure and OptimisticLockingFailure will provide >>>> enough information to retry the transaction if the app developer >>>> want to >>>> do that. >>> >>> I like this proposal. Though should it ben >>> PessimisticLockingFailureException to match >>> OptimisticLockingFailureException? Yes, the latter is intended to be >>> thrown by ORM tools, not JDBC-level operations. So we could convert >>> from >>> whatever the ORM tool throws. Or developers could throw it >>> themselves, >>> still allowing for consistent handling within Spring's DAO >>> abstraction. >>> >>> R >>>> >>>> Oracle might have these categories defined: >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> >>>> while MySQL might have this >>>> '- TransactionLockingFailureException [X] >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: 2005 Windows Mobile Application >> Contest >> Submit applications for Windows Mobile(tm)-based Pocket PCs or >> Smartphones >> for the chance to win $25,000 and application distribution. Enter >> today at >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > ------------------------------------------------------- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Thomas R. <tho...@tr...> - 2005-03-23 13:53:41
|
Not sure whether this message ever made it to the list so here it is again: I think removing most of these are OK. Except, DataAccessResourceFailureException - is possible, I think. Connection could be lost during execution of a query. Reconnect and execute the query again is a possibility here. DataRetrievalFailureException indicates some kind of error retrieving column values - bad column index or column has been removed or renamed. Not recoverable, but could be worth reporting with this exception. It's not BadSqlGrammar and not DataIntegrityViolation. This is especially true when calling stored procedures where you don't specify the sql for the resultset that is generated. I think the above categories are worth keeping and we should gather error codes that represent these failures. If I could only have one of them, then DataRetrievalFailureException would be the one. Thomas On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > I think removing most of these are OK. > > Except, > > DataAccessResourceFailureException - is possible, I think. Connection > could be lost during execution of a query. Reconnect and execute the > query again is a possibility here. > > DataRetrievalFailureException indicates some kind of error retrieving > column values - bad column index or column has been removed or > renamed. Not recoverable, but could be worth reporting with this > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > This is especially true when calling stored procedures where you don't > specify the sql for the resultset that is generated. > > I think the above categories are worth keeping and we should gather > error codes that represent these failures. If I could only have one > of them, then DataRetrievalFailureException would be the one. > > Thomas > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > >> Thomas, >> >> I've cleaned up the SQLErrorCodes class a little bit: there are no >> categories for OptimisticLockingFailureException, >> DataRetrievalFailureException and DataAccessResourceFailureException >> anymore. None of those should be caused by SQL error codes, but only >> by >> conditions at the ORM/DAO higher level (respectively connect failure >> in case >> of DataAccessResourceFailureException, which isn't indicated by a SQL >> error >> code either). >> >> I've also removed the category for >> PessimisticLockingFailureException. We >> generally don't offer fields for exception base classes in >> SQLErrorCodes but >> rather encourage specifying codes for fine-grained exception >> subclasses. We >> have fields for all three subclasses here: CannotAcquireLockException, >> DeadlockLoserDataAccessException (I've renamed the associated field >> to the >> shortened "deadlockLoserCodes") and >> CannotSerializeTransactionException. >> >> BTW, the latter exception isn't thrown anywhere currently. All others >> that >> we offer fields in SQLErrorCodes for are mapped for at least one >> database in >> the meantime. >> >> Strictly speaking, removing the SQLErrorCodes fields for those >> exceptions is >> not backwards-compatible. However, as we can't figure out how a >> database >> could cause them through error codes, this shouldn't matter; I think >> it's >> more important to offer a set of meaningful exception categories >> there. This >> should be acceptable for 1.2. And if someone unexpectedly found an >> error >> code for such a condition, it wouldn't be a bad thing to hear about >> it :-) >> >> Juergen >> >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...]On >> Behalf >> Of tho...@tr... >> Sent: Monday, March 21, 2005 4:22 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] >> DeadlockLoserDataAccessException vs CannotAcquireLockException >> >> >> >> I'm OK with PessimisticLockingFailureException as the superclass name. >> >> I wasn't questioning the existence of >> OptimisticLockingFailureException, I >> just >> can't come up with any SQLException error codes that would translate >> into >> it - >> it's not a SQL/Database error. It is definitely thrown by the >> ORM/DAO code. >> >> I can add this in later today, so we could make 1.2RC1. >> >> Thomas >> >> >> Quoting Juergen Hoeller <ju...@in...>: >> >>> FYI, we already do throw OptimisticLockingFailureException for >>> Hibernate >> and >>> JDO since the beginning of time :-) >>> >>> PessimisticLockingFailureException as superclass for >>> CannotAcquireLockException and co sounds appropriate to me. Do we >>> want to >>> include this in 1.2 RC1, which was originally scheduled for today? >>> ;-) It >>> looks like 1.2 RC1 won't be released before Wednesday anyway. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...]On >>> Behalf >>> Of Rod Johnson >>> Sent: Monday, March 21, 2005 3:00 PM >>> To: spr...@li... >>> Subject: Re: [Springframework-developer] >>> DeadlockLoserDataAccessException vs CannotAcquireLockException >>> >>> >>> Thomas >>> >>>> ConcurrencyFailureException >>>> '- TransactionLockingFailureException [X] >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> '- OptimisticLockingFailureException [X?] >>>> >>>> The [X] indicates that I think we should provide the option for >>>> separate >>>> categories in sql-error-codes.xml for this exception. Some of the >>>> lower >>>> exception classes might not make sense for all databases, but >>>> TransactionLockingFailure and OptimisticLockingFailure will provide >>>> enough information to retry the transaction if the app developer >>>> want to >>>> do that. >>> >>> I like this proposal. Though should it ben >>> PessimisticLockingFailureException to match >>> OptimisticLockingFailureException? Yes, the latter is intended to be >>> thrown by ORM tools, not JDBC-level operations. So we could convert >>> from >>> whatever the ORM tool throws. Or developers could throw it >>> themselves, >>> still allowing for consistent handling within Spring's DAO >>> abstraction. >>> >>> R >>>> >>>> Oracle might have these categories defined: >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> >>>> while MySQL might have this >>>> '- TransactionLockingFailureException [X] >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: 2005 Windows Mobile Application >> Contest >> Submit applications for Windows Mobile(tm)-based Pocket PCs or >> Smartphones >> for the chance to win $25,000 and application distribution. Enter >> today at >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > |
|
From: Alexandru P. <the...@ez...> - 2005-03-23 10:01:22
|
Hi! I saw in the ML that the Hibernate3 support is in CVS HEAD already. Can you point me to the main changes provided in the Spring support for Hibernate3 vs Hibernate2? (i expected there where changes required by the changes (from check to unchecked) exceptions in Hibernate3 and for supporting the new features, but it will be more easy for me to have a Spring expert opinion on this). many thanks in advance, -- :alex |.::the_mindstorm::.| |
|
From: David H. <dh...@ob...> - 2005-03-23 09:30:32
|
I=20have=20a=20couple=20of=20comments=20about=20Webflow=20based=20on=20my=20= usage=20in=20a=20current=20application. =20 Firstly,=20FlowController=20is=20responsible=20for=20creating=20its=20own=20= HttpFlowExecutionManager=20-=20I=20guess=20I=20don't=20understand=20why=20= this=20isn't=20a=20dependency=20that's=20injected=20in=20the=20traditional= =20way.=20I=20had=20to=20subclass=20the=20existing=20flow=20execution=20ma= nager=20to=20get=20some=20behaviour=20I=20desired=20(storing=20flow=20exec= utions=20in=20the=20servlet=20context,=20rather=20than=20the=20session),=20= and=20the=20current=20structure=20meant=20I=20also=20had=20to=20subclass=20= FlowController.=20 =20 Secondly,=20it=20would=20be=20nice=20if=20the=20exceptions=20thrown=20to=20= indicate=20missing=20state=20or=20actions=20actually=20provided=20accessor= s=20to=20expose=20which=20state/action=20was=20missing.=20Currently=20I=20= have=20immplemented=20fallback=20logic=20such=20that=20if=20an=20action=20= is=20not=20found=20in=20the=20current=20flow,=20I=20can=20check=20in=20the= =20parent=20flow(s)=20and=20handle=20back=20button=20issues=20with=20subfl= ows=20quite=20elegantly.=20My=20logic=20would=20have=20been=20simpler=20if= =20the=20caught=20exception=20indicated=20the=20state/action=20that=20was=20= the=20problem. =20 Thanks, -Dave=20 ________________________________ From:=20s...@li...=20on=20behal= f=20of=20Erwin=20Vervaet Sent:=20Tue=2022/03/2005=2020:22 To:=20s...@li... Subject:=20[Springframework-developer]=20Web=20Flow=20progress All, We've=20been=20making=20very=20good=20progress=20on=20the=20web=20flow=20s= ystem=20the=20last=20few days.=20Things=20are=20shaping=20up=20for=20a=20preview=20release=20that=20= might=20come=20as=20soon=20as next=20weekend! The=20code=20is=20in=20good=20shape=20again=20and=20all=20JavaDoc=20is=20u= p-to-date.=20All=20samples are=20also=20working=20again. For=20those=20with=20an=20interest=20in=20web=20flows,=20I=20fully=20recom= mend=20that=20you=20take=20a look=20at=20the=20code=20that=20is=20in=20CVS=20right=20now (http://cvs.sourceforge.net/viewcvs.py/springframework/spring/sandbox/src/= org/springframework/web/flow/) and=20let=20us=20know=20what=20you=20think!=20Any=20input=20would=20be=20a= ppreciated! Issues=20left=20to=20work=20out=20(not=20necessarily=20for=20the=20preview= =20release=20:): *=20Conditional=20transitions:=20basic=20support=20is=20there=20(via=20Tra= nsitionCriteria interface=20and=20a=20simple=20OgnlTransitionCriteria=20implementation),=20= but=20details have=20to=20be=20worked=20out: =20=20=20=20-=20how=20to=20integrate=20this=20into=20XML=20flow=20definiti= ons? =20=20=20=20-=20scope=20precedence?=20or=20should=20all=20scopes=20be=20me= rged=20before=20being evaluated=20by=20the=20expression? *=20Token=20based=20transitions=20(e.g.=20<transition=20on=3D"countrySelec= ted" to=3D"register.${request.country}"/>):=20do=20we=20need=20this?=20There=20= is=20no=20support for=20this=20at=20the=20moment. *=20Does=20the=20RequestContext=20need=20to=20keep=20track=20of=20a=20hist= ory=20of=20events=20signaled during=20its=20lifecycle?=20It's=20not=20the=20case=20for=20the=20moment=20= but=20would=20be=20simple to=20implement.=20Also,=20do=20we=20need=20a=20query=20interface=20to=20fi= nd=20an=20event=20parameter across=20all=20signaled=20events=20for=20a=20particular=20request?=20Are=20= there=20any=20good use-cases=20for=20this? *=20Do=20we=20need=20some=20convenience=20accessor=20on=20the=20RequestCon= text=20to=20find attributes=20in=20any=20scope:=20try=20request=20scope=20first,=20then=20f= all=20back=20on=20flow scope?=20This=20would=20be=20simple=20to=20add. Erwin=20Vervaet erw...@er... ------------------------------------------------------- This=20SF.net=20email=20is=20sponsored=20by:=202005=20Windows=20Mobile=20A= pplication=20Contest Submit=20applications=20for=20Windows=20Mobile(tm)-based=20Pocket=20PCs=20= or=20Smartphones for=20the=20chance=20to=20win=20$25,000=20and=20application=20distribution= .=20Enter=20today=20at http://ads.osdn.com/?ad_id=3D6882&alloc_id=3D15148&op=3Dclick _______________________________________________ Springframework-developer=20mailing=20list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer ________________________________________________________________________ This=20e-mail=20has=20been=20scanned=20for=20all=20viruses=20by=20Star.=20= The service=20is=20powered=20by=20MessageLabs.=20For=20more=20information=20on= =20a=20proactive anti-virus=20service=20working=20around=20the=20clock,=20around=20the=20gl= obe,=20visit: http://www.star.net.uk ________________________________________________________________________ ________________________________________________________________________ This=20e-mail=20has=20been=20scanned=20for=20all=20viruses=20by=20Star.=20= The service=20is=20powered=20by=20MessageLabs.=20For=20more=20information=20on= =20a=20proactive anti-virus=20service=20working=20around=20the=20clock,=20around=20the=20gl= obe,=20visit: http://www.star.net.uk ________________________________________________________________________ |
|
From: Thomas R. <tho...@tr...> - 2005-03-23 04:52:41
|
If we decide to keep DataRetrievalFailureException -- one code for Oracle is '17003' [Invalid column index]. Thomas On Mar 22, 2005, at 11:29 PM, Thomas Risberg wrote: > I think removing most of these are OK. > > Except, > > DataAccessResourceFailureException - is possible, I think. Connection > could be lost during execution of a query. Reconnect and execute the > query again is a possibility here. > > DataRetrievalFailureException indicates some kind of error retrieving > column values - bad column index or column has been removed or > renamed. Not recoverable, but could be worth reporting with this > exception. It's not BadSqlGrammar and not DataIntegrityViolation. > This is especially true when calling stored procedures where you don't > specify the sql for the resultset that is generated. > > I think the above categories are worth keeping and we should gather > error codes that represent these failures. If I could only have one > of them, then DataRetrievalFailureException would be the one. > > Thomas > > > On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > >> Thomas, >> >> I've cleaned up the SQLErrorCodes class a little bit: there are no >> categories for OptimisticLockingFailureException, >> DataRetrievalFailureException and DataAccessResourceFailureException >> anymore. None of those should be caused by SQL error codes, but only >> by >> conditions at the ORM/DAO higher level (respectively connect failure >> in case >> of DataAccessResourceFailureException, which isn't indicated by a SQL >> error >> code either). >> >> I've also removed the category for >> PessimisticLockingFailureException. We >> generally don't offer fields for exception base classes in >> SQLErrorCodes but >> rather encourage specifying codes for fine-grained exception >> subclasses. We >> have fields for all three subclasses here: CannotAcquireLockException, >> DeadlockLoserDataAccessException (I've renamed the associated field >> to the >> shortened "deadlockLoserCodes") and >> CannotSerializeTransactionException. >> >> BTW, the latter exception isn't thrown anywhere currently. All others >> that >> we offer fields in SQLErrorCodes for are mapped for at least one >> database in >> the meantime. >> >> Strictly speaking, removing the SQLErrorCodes fields for those >> exceptions is >> not backwards-compatible. However, as we can't figure out how a >> database >> could cause them through error codes, this shouldn't matter; I think >> it's >> more important to offer a set of meaningful exception categories >> there. This >> should be acceptable for 1.2. And if someone unexpectedly found an >> error >> code for such a condition, it wouldn't be a bad thing to hear about >> it :-) >> >> Juergen >> >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...]On >> Behalf >> Of tho...@tr... >> Sent: Monday, March 21, 2005 4:22 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] >> DeadlockLoserDataAccessException vs CannotAcquireLockException >> >> >> >> I'm OK with PessimisticLockingFailureException as the superclass name. >> >> I wasn't questioning the existence of >> OptimisticLockingFailureException, I >> just >> can't come up with any SQLException error codes that would translate >> into >> it - >> it's not a SQL/Database error. It is definitely thrown by the >> ORM/DAO code. >> >> I can add this in later today, so we could make 1.2RC1. >> >> Thomas >> >> >> Quoting Juergen Hoeller <ju...@in...>: >> >>> FYI, we already do throw OptimisticLockingFailureException for >>> Hibernate >> and >>> JDO since the beginning of time :-) >>> >>> PessimisticLockingFailureException as superclass for >>> CannotAcquireLockException and co sounds appropriate to me. Do we >>> want to >>> include this in 1.2 RC1, which was originally scheduled for today? >>> ;-) It >>> looks like 1.2 RC1 won't be released before Wednesday anyway. >>> >>> Juergen >>> >>> >>> -----Original Message----- >>> From: spr...@li... >>> [mailto:spr...@li...]On >>> Behalf >>> Of Rod Johnson >>> Sent: Monday, March 21, 2005 3:00 PM >>> To: spr...@li... >>> Subject: Re: [Springframework-developer] >>> DeadlockLoserDataAccessException vs CannotAcquireLockException >>> >>> >>> Thomas >>> >>>> ConcurrencyFailureException >>>> '- TransactionLockingFailureException [X] >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> '- OptimisticLockingFailureException [X?] >>>> >>>> The [X] indicates that I think we should provide the option for >>>> separate >>>> categories in sql-error-codes.xml for this exception. Some of the >>>> lower >>>> exception classes might not make sense for all databases, but >>>> TransactionLockingFailure and OptimisticLockingFailure will provide >>>> enough information to retry the transaction if the app developer >>>> want to >>>> do that. >>> >>> I like this proposal. Though should it ben >>> PessimisticLockingFailureException to match >>> OptimisticLockingFailureException? Yes, the latter is intended to be >>> thrown by ORM tools, not JDBC-level operations. So we could convert >>> from >>> whatever the ORM tool throws. Or developers could throw it >>> themselves, >>> still allowing for consistent handling within Spring's DAO >>> abstraction. >>> >>> R >>>> >>>> Oracle might have these categories defined: >>>> '- CannotAquireLockException [X] >>>> '- CannotSerializeTransactionException [X] >>>> '- DeadlockLoserDataAccessException [X] >>>> >>>> while MySQL might have this >>>> '- TransactionLockingFailureException [X] >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: 2005 Windows Mobile Application >> Contest >> Submit applications for Windows Mobile(tm)-based Pocket PCs or >> Smartphones >> for the chance to win $25,000 and application distribution. Enter >> today at >> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > |
|
From: Thomas R. <tho...@tr...> - 2005-03-23 04:29:54
|
I think removing most of these are OK. Except, DataAccessResourceFailureException - is possible, I think. Connection could be lost during execution of a query. Reconnect and execute the query again is a possibility here. DataRetrievalFailureException indicates some kind of error retrieving column values - bad column index or column has been removed or renamed. Not recoverable, but could be worth reporting with this exception. It's not BadSqlGrammar and not DataIntegrityViolation. This is especially true when calling stored procedures where you don't specify the sql for the resultset that is generated. I think the above categories are worth keeping and we should gather error codes that represent these failures. If I could only have one of them, then DataRetrievalFailureException would be the one. Thomas On Mar 22, 2005, at 5:25 PM, Juergen Hoeller wrote: > Thomas, > > I've cleaned up the SQLErrorCodes class a little bit: there are no > categories for OptimisticLockingFailureException, > DataRetrievalFailureException and DataAccessResourceFailureException > anymore. None of those should be caused by SQL error codes, but only by > conditions at the ORM/DAO higher level (respectively connect failure > in case > of DataAccessResourceFailureException, which isn't indicated by a SQL > error > code either). > > I've also removed the category for PessimisticLockingFailureException. > We > generally don't offer fields for exception base classes in > SQLErrorCodes but > rather encourage specifying codes for fine-grained exception > subclasses. We > have fields for all three subclasses here: CannotAcquireLockException, > DeadlockLoserDataAccessException (I've renamed the associated field to > the > shortened "deadlockLoserCodes") and > CannotSerializeTransactionException. > > BTW, the latter exception isn't thrown anywhere currently. All others > that > we offer fields in SQLErrorCodes for are mapped for at least one > database in > the meantime. > > Strictly speaking, removing the SQLErrorCodes fields for those > exceptions is > not backwards-compatible. However, as we can't figure out how a > database > could cause them through error codes, this shouldn't matter; I think > it's > more important to offer a set of meaningful exception categories > there. This > should be acceptable for 1.2. And if someone unexpectedly found an > error > code for such a condition, it wouldn't be a bad thing to hear about it > :-) > > Juergen > > > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...]On Behalf > Of tho...@tr... > Sent: Monday, March 21, 2005 4:22 PM > To: spr...@li... > Subject: Re: [Springframework-developer] > DeadlockLoserDataAccessException vs CannotAcquireLockException > > > > I'm OK with PessimisticLockingFailureException as the superclass name. > > I wasn't questioning the existence of > OptimisticLockingFailureException, I > just > can't come up with any SQLException error codes that would translate > into > it - > it's not a SQL/Database error. It is definitely thrown by the ORM/DAO > code. > > I can add this in later today, so we could make 1.2RC1. > > Thomas > > > Quoting Juergen Hoeller <ju...@in...>: > >> FYI, we already do throw OptimisticLockingFailureException for >> Hibernate > and >> JDO since the beginning of time :-) >> >> PessimisticLockingFailureException as superclass for >> CannotAcquireLockException and co sounds appropriate to me. Do we >> want to >> include this in 1.2 RC1, which was originally scheduled for today? >> ;-) It >> looks like 1.2 RC1 won't be released before Wednesday anyway. >> >> Juergen >> >> >> -----Original Message----- >> From: spr...@li... >> [mailto:spr...@li...]On >> Behalf >> Of Rod Johnson >> Sent: Monday, March 21, 2005 3:00 PM >> To: spr...@li... >> Subject: Re: [Springframework-developer] >> DeadlockLoserDataAccessException vs CannotAcquireLockException >> >> >> Thomas >> >>> ConcurrencyFailureException >>> '- TransactionLockingFailureException [X] >>> '- CannotAquireLockException [X] >>> '- CannotSerializeTransactionException [X] >>> '- DeadlockLoserDataAccessException [X] >>> '- OptimisticLockingFailureException [X?] >>> >>> The [X] indicates that I think we should provide the option for >>> separate >>> categories in sql-error-codes.xml for this exception. Some of the >>> lower >>> exception classes might not make sense for all databases, but >>> TransactionLockingFailure and OptimisticLockingFailure will provide >>> enough information to retry the transaction if the app developer >>> want to >>> do that. >> >> I like this proposal. Though should it ben >> PessimisticLockingFailureException to match >> OptimisticLockingFailureException? Yes, the latter is intended to be >> thrown by ORM tools, not JDBC-level operations. So we could convert >> from >> whatever the ORM tool throws. Or developers could throw it themselves, >> still allowing for consistent handling within Spring's DAO >> abstraction. >> >> R >>> >>> Oracle might have these categories defined: >>> '- CannotAquireLockException [X] >>> '- CannotSerializeTransactionException [X] >>> '- DeadlockLoserDataAccessException [X] >>> >>> while MySQL might have this >>> '- TransactionLockingFailureException [X] >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > This SF.net email is sponsored by: 2005 Windows Mobile Application > Contest > Submit applications for Windows Mobile(tm)-based Pocket PCs or > Smartphones > for the chance to win $25,000 and application distribution. Enter > today at > http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Alexandru P. <the...@ez...> - 2005-03-23 00:54:07
|
Hi! I saw in the ML that the Hibernate3 support is in CVS HEAD already. Can you point me to the main changes provided in the Spring support for Hibernate3 vs Hibernate2? (i expected there where changes required by the changes (from check to unchecked) exceptions in Hibernate3 and for supporting the new features, but it will be more easy for me to have a Spring expert opinion on this). many thanks in advance, -- :alex |.::the_mindstorm::.| |
|
From: Darren D. <da...@sh...> - 2005-03-23 00:32:04
|
1111537906
FAILED
[junit] Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 0,526 sec
[junit] Testcase: testSchedulerFactoryBean took 0,382 sec
[junit] Testcase: testSchedulerFactoryBeanWithListeners took 0,028 sec
[junit] Testcase: testSchedulerFactoryBeanWithPlainQuartzObjects took 0,007 sec
[junit] Testcase: testSchedulerFactoryBeanWithApplicationContext took 0,002 sec
[junit] Testcase: testJobDetailBeanWithApplicationContext took 0,001 sec
[junit] Testcase: testJobDetailBeanWithListenerNames took 0 sec
[junit] Testcase: testCronTriggerBeanWithListenerNames took 0,001 sec
[junit] Testcase: testSimpleTriggerBeanWithListenerNames took 0 sec
[junit] Testcase: testMultipleSchedulers took 0,038 sec
[junit] Caused an ERROR
[junit] IOException parsing XML document from class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml]; nested exception is java.io.FileNotFoundException: class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml] cannot be opened because it does not exist
[junit] org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml]; nested exception is java.io.FileNotFoundException: class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml] cannot be opened because it does not exist
[junit] java.io.FileNotFoundException: class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml] cannot be opened because it does not exist
[junit] at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:127)
[junit] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:144)
[junit] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:99)
[junit] at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:102)
[junit] at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:70)
[junit] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:87)
[junit] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:262)
[junit] at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:80)
[junit] at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:65)
[junit] at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:56)
[junit] at org.springframework.scheduling.quartz.QuartzSupportTests.testMultipleSchedulers(QuartzSupportTests.java:423)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.
See http://springframework.sourceforge.net/test/ for further
information.
|
|
From: Darren D. <da...@sh...> - 2005-03-22 23:30:22
|
1111534202
FAILED
[junit] Tests run: 9, Failures: 0, Errors: 1, Time elapsed: 0,548 sec
[junit] Testcase: testSchedulerFactoryBean took 0,446 sec
[junit] Testcase: testSchedulerFactoryBeanWithListeners took 0,017 sec
[junit] Testcase: testSchedulerFactoryBeanWithPlainQuartzObjects took 0,005 sec
[junit] Testcase: testSchedulerFactoryBeanWithApplicationContext took 0,002 sec
[junit] Testcase: testJobDetailBeanWithApplicationContext took 0,001 sec
[junit] Testcase: testJobDetailBeanWithListenerNames took 0 sec
[junit] Testcase: testCronTriggerBeanWithListenerNames took 0,001 sec
[junit] Testcase: testSimpleTriggerBeanWithListenerNames took 0 sec
[junit] Testcase: testMultipleSchedulers took 0,043 sec
[junit] Caused an ERROR
[junit] IOException parsing XML document from class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml]; nested exception is java.io.FileNotFoundException: class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml] cannot be opened because it does not exist
[junit] org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml]; nested exception is java.io.FileNotFoundException: class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml] cannot be opened because it does not exist
[junit] java.io.FileNotFoundException: class path resource [org/springframework/scheduling/quartz/multiple-schedulers.xml] cannot be opened because it does not exist
[junit] at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:127)
[junit] at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:144)
[junit] at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:99)
[junit] at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:102)
[junit] at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:70)
[junit] at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:87)
[junit] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:262)
[junit] at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:80)
[junit] at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:65)
[junit] at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:56)
[junit] at org.springframework.scheduling.quartz.QuartzSupportTests.testMultipleSchedulers(QuartzSupportTests.java:423)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
This is an automated mail from one of the SF Compile Farm machines.
The machine name noted in the subject encountered a failure building
or running the Spring test suite. The last few lines of the output
were included for info.
NB: No further mail will be sent from this machine until a
manual reset occurs on the cf-shell machine, although builds will
continue as scheduled.
See http://springframework.sourceforge.net/test/ for further
information.
|
1239 messages has been excluded from this view by a project administrator.
