Only bad in that things can be deleted, renamed, refactored or moved around without notice.
On Thu, Jul 15, 2010 at 3:07 PM, Pierce Wetter <pie...@paceap.com> wrote: > Background: I ported part of tapestry-hibernate to tapestry-jpa, which lives > over at tynamo.org. When I did that, I mostly just cribbed directly from > tapestry-hibernate. tapestry-hibernate uses some internal stuff though, so > this morning, all my apps broke because T5.2 deleted Defense in favor of > plain asserts. > > Fair enough. I've fixed it in the meantime, but I wasn't able to scrub all of > the references to internal stuff. Specifically: > > import org.apache.tapestry5.ioc.internal.util.MessagesImpl; > > import > org.apache.tapestry5.internal.services.AbstractSessionPersistentFieldStrategy; > > Should I worry about these? I'm sort of making the assumption here that its > "bad" to use things that are "internal", but tapestry-hibernate seems to be > inside the kimono, so its allowed to... > > Pierce > > > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
