Right. The issue is we can't have the infinite web of project implementation details leaking to users unncessarily. Hibernate is a little different in that its used both in Java SE and Java EE profiles. My concern is that a pure Java EE client should not care about that antlr happens to be used for the ejb3 query language parser. Antlr should not be a required jar in the jboss client jars for ejb3 usage.
> -----Original Message----- > From: Steve Ebersole > Sent: Wednesday, February 08, 2006 6:52 AM > To: Max Andersen; Scott M Stark; > jboss-development@lists.sourceforge.net; Hibernate development > Subject: RE: [Hibernate] Do antlr exception leak to users? > > Well I think the distinction here is that Hibernate > constitutes a "hard" dependency on Antlr. The users choice > to use Oracle is completely within their control. > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
