Hello, after some investigations I found out why the decoupled fulcrum localization service does�nt work:
The interface class "Localization" referes the old TurbineLocalizationService. So, when starting decoupled fulcrum all services will be initialized by an object of class Fulcrum. Later, when calling the Localization service via "org.apache.fulcrum.localization.Localization" it tries to get an instance of the service by the singleton class TurbineServices. This class is uninitalized and so returns "service not found". ==> and that�s it In fulcrum3.0-b1 I found no possibility to get a reference to the service because the class Fulcrum has no method to get a service. So suspected with fulcrum3.0-b1 the services could not be called from turbine. in fulcrum3.0-b2 there is a new method getService() but in the existing class Localization the old TurbineServices is called. So when using it with the fulcrum3.0-b2 you have to get the service with something like Fulcrum.getService(LocalizationService.SERVICE_NAME); In a released version of fulcrum I think all these fragments which rely on the old turbine-version will be removed. Meanwhile: be careful ... ;-)) (Thanks bart for your help, but at least I have�nt got it running so I switched of the fulcrum services. I am a little bit under pressure to get my application released for testing ) Uwe -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
