"Eric Pugh" <[EMAIL PROTECTED]> writes: > I have made a lot of progress in the conversion process. Obviously > things are done yet, but I would be very curious which services > Scarab and Sourcecast use..
Scarab uses the following services: FactoryService PoolService MimeTypeService SchedulerService UploadService SecurityService GlobalCacheService TemplateService RunDataService LocalizationService PullService IntakeService VelocityService EmailService ScarabSecurity ScarabCache TorqueService DatabaseInitializer EmailService is basically a copy of VelocityService, but we needed a different configuration. I'm hoping that this is something that an Avalon container can help with. The remaining 4 are custom Service implementations used in Scarab. SourceCast uses a similar set (including XML-RPC), also with some of its own custom impls. > One of the services, BSF, I was thinking of ditching, as I can > repackage it, but don't know how to use it.. I think it was a one > off that went no where. Sounds fine to me. > At any rate, if you want to look at the repackage stuff, I wouldn't > mind another set of eyes looking at the code. I'm not particularly fond of the repacking, actually -- it strikes me as unnecessary complexity. However, so long as it doesn't take too much of my time up mucking with the build, I'm not going to complain with you doing so much good work. I'm very happy to see jakarta-turbine-2 using jakarta-turbine-fulcrum. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
