Your answer to your question is correct. :-) "Stephen Haberman" <[EMAIL PROTECTED]> writes:
> Okay, I think I just answered my own question. > > It's so that the jar can have the default classic pipeline in it and > have the class loader find it. Specifying user-defined pipelines just > needs to follow the same format. > > Sorry I didn't look at the source code more closely before posting my > question. > > - Stephen > >> -----Original Message----- >> From: Stephen Haberman [mailto:[EMAIL PROTECTED]] >> Sent: Thursday, May 23, 2002 3:47 PM >> To: [EMAIL PROTECTED] >> Subject: pipeline in the classpath? >> >> Hello, >> >> I've been looking at how Scarab uses Turbine and one thing that caught >> my attention was that the scarab-pipeline.xml is actually in the Java >> source code. This seems a departure from the old standard of having > the > > TurbineResources.properties in the WEB-INF/conf. >> >> I guess it's not overly important, as long as it works, but out of >> curiosity, is there a reason the pipeline descriptor should be loaded >> from the classpath instead of the conf dir? My humble opinion is that >> I'd rather see it back in the conf dir instead of hiding in the source >> code. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
