The security interfaces can easily be moved to the security module, its just legacy that it lives in server. It is correct that this lives outside of the jca layer.
However, there is no dependency between the jca layer and cmp, this is a usecase of the jca connection by cmp that was hacked in by the cmp layer. I don't see why the connection simply isn't cast to a jca WrappedStatement instead of adding this interface. Is there a usecase where the jdbc statement is not coming from the jca layer? xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Brock Sent: Tuesday, February 03, 2004 6:54 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] Bad cross module dependency According to cvs it was a temporary solution that has never been fixed. http://cvs.sourceforge.net/viewcvs.py/jboss/jbosscx/src/main/org/jboss/r esource/adapter/jdbc/Attic/WrappedStatement.jpp?hideattic=0 I guess the problem is that connector depends upon server for things like the security interfaces. But server also includes cmp. There's a similar problem between transaction and server. Regards, Adrian ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
