I can see that in this case since the resource in question is unique to the task, it should be sufficient to assume that a nested resource is a stylesheet.
The real requirement that will necessitate the attribute syntax, as I see it, is enforcing that a single resource be specified as the output destination for a given task. :) -Matt --- Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: > Matt, > > I plan to use the bug report : > > <http://issues.apache.org/bugzilla/show_bug.cgi?id=39407>. > which contains an attachment where the resource is > instantiated using the URL schemes. > > I did not test it though to make sure that it does > work with a jar:file: URL (not sure what the exact > syntax is). > > :-) > > Regards, > > Antoine > > > Matt Benson wrote: > > Antoine: Does this put us back to needing a > "scheme" > > to translate a string (attribute value) to a > Resource? > > > > -Matt > > > > --- Antoine Levy-Lambert <[EMAIL PROTECTED]> wrote: > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
