Re: Problem with net.jxta.ext.config.Configurator

hmmmmmmmmmm ...

createPlatformConfig() will not be called only in the event a 
PlatformConfig already
exhists.

Can you try the following:

  create and register an AbsoluteConfigurator

  in createPlatformConfig(Configurator c), the only method one must 
implement, simply echo
  out c.getJxtaHome() and exit

  then, on the commandline, go to that directory and see if a 
PlatformConfig already exhists

If a valid PlatformConfig does not exist *and* createPlatformConfig() is 
not invoked then that is
a bug.

- james

--

James Todd :: blogs.sun.com/gonzo | weblogs.java.net/blog/gonzo

MyJXTA :: use it - learn it - do it

Java == platform independence
XML  == application independence
JXTA == network independence

Secure End-to-End Computing 



Marco Marconi wrote:

>On Mon, 29 Aug 2005 00:11:35 -0700
>James Todd <[email protected]> wrote:
>
>  
>
>>  I don't think you will want to "re-create" a JXTA configuration each
>>  
>>time your application starts
>>  up. Have you considered AbstactConfigurator? With this class, your 
>>"create configuration" impl
>>  will be invoked only when needed and you can, optionally, get a 
>>callback each time the platform
>>  starts up, so you can tune the configuration as applicable.
>>    
>>
>
>thank you, I tried to use AbstractConfigurator, In the subclass I
>overidded the methods createPlatformConfig and updatePlatformConfig, but
>when I lauch the app only the update is only called! Even if I remove
>the .jxta directory...
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>
>  
>