+10000 to get rid off the file system.
Turbine should realy turn on ALL application server...I've not spent time to scan all the sources to get an idea of all the file system dependencies. Perhaps a turbine dev could give us his opinion on this? Blair Martin a �crit : > > Hi. I'm new to Turbine and this list. > > I'm trying to deploy my Turbine based app on an app server (Iona iPortal). > This means that all files are packed in a WAR file which is in turn packed > in a EAR file and _apparently_ the EAR file is loaded into memory. In other > words things aren't available in a regular file structure. Well, things > grind to a halt early because Turbine can't find it's properties file. > > Scanning the archives I see "Turbine 2.x apps are fully WAR compliant. You > just have to make sure your app server unpacks the war file...". > > How is Turbine "WAR compliant" if it never encounters WAR files (the app/web > server unpacks them)? > > I also read that Turbine only works in a "live" file system. This applies to > 2.x and 3.x. Is there not enough demand for Turbine to work with in-memory > deployments? Seems odd... > > I hope I can figure out how to get iPortal to deploy a live file system > (anyone know?). Modifying Turbine could also be an option but the fact that > it hasn't been done yet leads me to believe that that would be non-trivial. > I got Velocity working in this scheme using > ServletContext.getResourceAsStream(filename) to load the properties. Maybe I > can do something similar with Turbine.... > > blair > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
