Congrats on getting it rolled out... I'm still digging around, getting a
feel for it. I haven't seen evidence yet of how to show block-to-block
dependencies, but if there's javadoc for it, I'll find it no problem.
Everything else I've looked at seems sensible enough...
Something that came up in connection with web start... that program is
kind of pissing me off. Turns out that when jarsigner does its thing,
it only attaches sig info (the md5 digest I suppose) to the Name:
sections that are associated with files. WebStart insists that every
single Name: section be signed, or it considers the jar incorrectly
signed and won't load it. So any required entries in the manifest that
do not directly correspond to a file automatically break Web Start. I
submitted a bug report, but Web Start releases are only every six months
to a year. There are open source implementations but they aren't very
complete. Urk.
So anyway, the obvious question, is the Avalon-Block header needed?
It occurs to me that I can simply create a file called Avalon-Block!!!
Urk...
Gary
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
