>> I
>> thought that it made sense to use them directly instead of using a lot
>> of Url.toString() and new URL(String) calls
>
>I think that all we are doing is shifting the "new URL(String)" calls
>from the processor to the application.
I think this is right - the "application" is going to have to do a lot of
additional testing for semantic validity. XLL is full of this problem. So I
think it will be very valuable to have *generic* modules that can be used
for this sort of thing. I see some of these as coming in a post-parser
(i.e. post-processor) and pre-application area. For example, it's
reasonable that an application shouldn't get passed:
<A XML-LINK="SIMPLE" HREF="htpp://www.some.where/myfile.xml" SHOW="Embed"
ACTUATE="New" behaviour="DISPLAY">My XML file</A>
This is a WF element, but contains a number of semantic errors (at least if
the application wishes to validate it against the XLL spec :-).
java.net.URL would catch one of them :-)
P.
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
net connection
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
http://www.venus.co.uk/vhg