Good catch on the message in BaseContext. But, I intended for the message
not to change in DataContext. Changing the message thrown is itself a
backwards incompatible change. Perhaps someone has a logging tool that
greps for that statement or worse, code that looks for it. In any event, I
think it should still say DataContext from the deprecated method and
ObjectContext from the new one.
--
Kevin
> /**
> * The most common implementation of [EMAIL PROTECTED] ObjectContext}.
> DataContext is
> an isolated
> * container of an object graph, in a sense that any uncommitted changes to
> persistent
> @@ -93,12 +126,7 @@
> * @deprecated since 3.0, replaced by
> BaseContex#getThreadObjectContext().
> */
> public static DataContext getThreadDataContext() throws
> IllegalStateException {
> - try {
> - return (DataContext) BaseContext.getThreadObjectContext();
> - }
> - catch(final IllegalStateException ex) {
> - throw new IllegalStateException("Current thread has no bound
> DataContext.");
> - }
> + return (DataContext) BaseContext.getThreadObjectContext();
> }
>
> /**
>
>
>
