|
In a whiteboarding scenario, placing images on the
whiteboard is tough because you have to upload the XML element and the file.
We have been sending the file first, then the image element. This way, the
image element resolves properly because the referenced file is already there.
The drawback? During the time it takes for the file to upload, other users can
manipulate the document by adding/updating other elements. When the image
element arrives, it won’t end up in the originally intended place. That’s a little vague, but here’s the technical
problem I’m trying to overcome: An image element is placed and the xlink:href points to a
non-existant file. The standard “broken image” image appears on
the JSVGCanvas instead, per Batik. Next, the correct file appears in the
correct place. How do I tell Batik to try and resolve that again?
JSVGCanvas.setDocument(…) doesn’t seem to have an effect, the image
still appears broken. Michael Bishop |
Resolving xlink:href at a later time?
Bishop, Michael W. CONTR J9C880 Thu, 12 Oct 2006 14:07:50 -0700
- Resolving xlink:href at a later time? Bishop, Michael W. CONTR J9C880
- Re: Resolving xlink:href at a later t... thomas . deweese
- RE: Resolving xlink:href at a later t... Bishop, Michael W. CONTR J9C880
- RE: Resolving xlink:href at a lat... thomas . deweese
- RE: Resolving xlink:href at a later t... Bishop, Michael W. CONTR J9C880
- RE: Resolving xlink:href at a lat... thomas . deweese
- RE: Resolving xlink:href at a later t... Bishop, Michael W. CONTR J9C880
- RE: Resolving xlink:href at a later t... Bishop, Michael W. CONTR J9C880
- RE: Resolving xlink:href at a lat... thomas . deweese
- RE: Resolving xlink:href at a lat... thomas . deweese
- RE: Resolving xlink:href at a later t... Bishop, Michael W. CONTR J9C880
