I was looking at the hibernate booking example, and noticed that not only doesn't it use Entities, it doesn't use Session beans either, yet some of the actions are still annotated with interceptors like @Login (and of course Seam's interceptors). I was under the impression that javax.interceptor only worked on Session and Message-Driven beans, so I'm puzzled how this works. Am I misinformed, or is there extra power in JBoss AOP being leveraged over and above what JEE5 provides?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973671#3973671
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973671
I am using the WebObjects EOF framework for developing my applications I deploy with jboss. This framework uses the data source connection described in my postgres-ds.xml. Since upgrading from jboss-4.0.3.SP1 to jboss-4.0.4.GA I am getting the ResultSet already closed exception. I have seen others say the problem occurs because the ResultSet is being closed AFTER instead of BEFORE the Statement is closed.
Unfortunately for me, this code occurs in the framework and is beyond my control. If jboss insists on throwing an exception in this instance, I am afraid I will be prevented from using jboss-4.0.4 or I will have to start using the framework for creating its own jdbc connections, bypassing the jboss data source connections.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973666#3973666
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973666