[JBoss-user] [EJB/JBoss] - Re: How to keep Connection/ResultSet open across EJB methods
Thanks for the information about the solution. Your response with the solution arrived even before I could respond to your original post -- which wouldn't have helped you much, because I only had a hack of a work around. The solution that you've found works much better and is much easier to implement. I never would have thought that almost a year and a half later that I'd find a solution. That's awesome! Thanks. Cheers, Kyley View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=3913214#3913214 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3913214 --- 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://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - How to keep Connection/ResultSet open across EJB methods
Within my application, there is a query that potentially can return large amounts of data. In order to display this data in the client app without freezing the UI waiting for the entire data set, we have three EJB methods to get the data. 1) Do the query and store the ResultSet 2) Get a specified number of the data 3) close the ResultSet. My initial thought would be that I would get an Error such as fetch sequence out of bounds or connection closed. However with JBoss 3.2.3 and earlier it works fine. In the first method I get a Connection and query for the ResultSet (which is a class variable). Then the second method is called iteratively until the entire ResultSet is returned. The third method is called to close the ResultSet. When my EJB is deployed in JBoss 4.0, after retuning from the first method, because the Connection is closed the ResultSet is closed too -- thus causing an Exception when trying to iterator over a closed ResultSet. I thought that by changing my client to handle the transactions that I would be able to keep the ResultSet open. But that doesn't seem to work. So, my questions are if what I have been doing should/could work? Are there deployment settings that need to changed to allow for the ResultSet to remain open across EJB method calls? Am I correct in my thinking that if the client handle the transactions that the ResultSet could remain open? Any help would be appreciated in figuring out whether my application is not adhering to the J2EE EJB specs or if there is a problem with JBoss 4.0. Cheers! Kyley View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3847840#3847840 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3847840 --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - EJB Deployment Error
Upon the release of JBoss 4.0 RC2, I've downloaded and deployed my EJBs that worked with 3.2.3 into 4.0, but I get the following error: Failed to setup client ENC; - nested throwable: (org.jboss.deployment.DeploymentException: ejb-ref ejb/jdelphi-utility, expected either ejb-link in ejb-jar.xml or jndi-name in jboss.xml) I'm not quite sure what that means and if it is correct because I have the jndi-name defined in the jboss.xml already. And by adding the ejb-link to the ejb-jar.xml it doesn't change the error. Any ideas? Is this error correct? or am I missing something else that was added to change the behavior from 3.2.3 to 4.0 RC2? Cheers! Kyley View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3847583#3847583 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3847583 --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047alloc_id=10808op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [EJB/JBoss] - Re: EJB Deployment Error
Is this something that is new to 4.0 (because I notice there exists a 3_2.dtd and 4_0.dtd) or did the dependency on this change. Thanks for your reply -- I'll give it a try. Cheers! Kyley View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3847586#3847586 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3847586 --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047alloc_id=10808op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
