Has anyone tried this? I'm using JRun 3.1 on Win2000 server, connecting to an Oracle datasource via thin driver, and have encountered the bug #26844 -- when doing UPDATE queries using the jrun:sql tag I get an OutOfMemory exception. Naturally everything worked with a MS SQL Server dev data source, both in JRun 3.0 and after upgrading to 3.1 (albeit with much pain due to changes in the jrun tags lib). Has anyone tried using the 3.0 custom tag library with JRun 3.1? It seems like less work than blowing away my 3.1 install and going back to 3.0SP2. If anyone _has_ done this successfully, did you just drag out the newer jruntags.jar and /exception dir from servers/lib and drag the old jruntags.jar file back in? (restarting JRun in Services, etc., of course) If not, any other words of advice? My advice to others: avoid the JRun custom tag library & write your own, find another or do without. If you're using it successfully, do not upgrade. I expect mixing versions is not a config supported by Macromedia/Allaire but I'm not having any luck with 3.1 itself and it seems 3.1 SP1 is not due soon. -- Laurence Laurence Middleton code wrangler ecentricarts inc. 416 644-5000 ext.225 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
