Re: [JXTA discuss] problems in parsing XML profile??

Hey Michele, et al -

  I have just submitted a patch that should resolve this issue such that
  one does not have to perform the work around of specifying a fully qualified
  InetAddress:

     http://platform.jxta.org/issues/show_bug.cgi?id=1375

     note: more use case info included in the issue db

  Unit tests are included as well:

    http://wiki.java.net/bin/view/Jxta/BuildingJXTA

    % cd platform/binding/java
    % ant runtestui

  I appreciate folks testing this patch so that we can resolve the
  issue for all.

  hth,

- 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 


James Todd wrote:
> 
> Hey Michele -
> 
>  Alex and I have been discussing this issue:
> 
>    http://platform.jxta.org/issues/show_bug.cgi?id=1375
> 
>  The work around is to specify a fully qualified address, even the any/all
>  address, when one wants to change the default port. The real fix will
>  (likely) entail getting support back in for the address "template/macro"
>  logic so that a URI fragment can be provieded, eg:
> 
>    http://:9901
> 
>  to which ext:config will expand as needed. In this case:
> 
>    http://0.0.0.0:9901 for ipv4
>    http://[::]:9901 for ipv6
> 
>  Please feel free to comment against all ext:config issues so that we
>  can work towards resolution. At present, I have the following 4 issues
>  that are ready for review and I would very much like to close them by
>  weeks end:
> 
>    http://platform.jxta.org/issues/show_bug.cgi?id=1373 - jxta home
>    http://platform.jxta.org/issues/show_bug.cgi?id=1374 - null relay 
> bootstrap
>    http://platform.jxta.org/issues/show_bug.cgi?id=1368 - simplify AbsConf
>    http://platform.jxta.org/issues/show_bug.cgi?id=1364 - edge optimizer
> 
>  With the above resolved I'd like to go after 1375 which was supported at
>  one time, for obvious reason, at which point the concern you have raised
>  will be addressed.
> 
>  hth,
> 
> - 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
> 
> Michele Amoretti wrote:
> 
>> Hello,
>> I found a probable BUG in the autoconfiguration phase...
>>
>> This is part of the profile for a rendezvous:
>>
>> .........
>>   <transport>
>>     <tcp enabled="true">
>>       <address range="1">
>>         <multicast enabled="false"/>
>>         tcp://:9901
>>       </address>
>>       <publicAddress>tcp://:9901</publicAddress>
>>       <proxy enabled="false"/>
>>     </tcp>
>> .........
>>
>> I want the RendezVousService can be reached only on port 9901.
>>
>> I publish a list of rendezvous in which the port is said to be 9701. 
>> Nevertheless, edges are able to find the rendezvous!
>>
>> In fact, searching in the PlatformConfig of the rdv, I find that:
>>
>>                                  <Port start="9701" end="9702">
>>                                         9701
>>                                 </Port>
>>
>> thus the "9901" setting is completely IGNORED.
>>
>> The same setting, from the GUI, is correctly translated in the 
>> PlatformConfig...
>>
>>
>>
>> Another problem of XML profiles:
>>
>> a local "bootstrap" rdv list is correctly read IF AND ONLY IF the 
>> absolute path is provided... relative paths are not correctly parsed
>>
>>
>>
>>  Thanks
>>
>>
>