I recently took up the task of getting slide to work on weblogic 6.1. I have everything up and working fine, but now I have one small bug/change request.
org.apache.slide.common.Domain.java around line 660 replace: FileInputStream is = new FileInputStream(fileName); with InputStream is = Domain.class.getClassLoader().getResourceAsStream(fileName); with this done, weblogic has no problem finding the Domain.xml file when it is included in a war at WEB-INF\classes. Before I made this change, there was nowhere I could put the Domain.xml file for weblogic to find it. I don't have Tomcat set up, so I wasn't able to validate whether or not the change affects the typical deployment. If it does, I'd suggest trying the FileInputStream, checking for an error, and then trying the ResourceAsStream method. Should I submit this as a bug as well? Now that I have it up and running, my next task is going to be to get it to be part of a clustered environment. My three options seem to be: 1) Find all references to the cache and allow it to be turned off. 2) Implement some sort of timestamp on each Node and make sure that whichever layer does the caching checks this before returning the contents 3) Allow only one slide instance to be running at any point in time, and create a heartbeat with a slave so that if the first instance crashes, the second takes over. Any thoughts or suggestions? I'll be more than happy to feed back any of the work I do into the project. Thanks, Ryan Barrows
