Hello Thomas,
here's the stack trace as given by the dialog:
org.apache.batik.bridge.BridgeException: null: -1
Cannot find the referenced element: "#Solar"
specified on the element <use> - may be a problem of id
at org.apache.batik.bridge.BridgeContext.getReferencedElement(Unknown
Source)
at
org.apache.batik.bridge.SVGUseElementBridge.buildCompositeGraphicsNode(Unknown
Source)
at
org.apache.batik.bridge.SVGUseElementBridge.createGraphicsNode(Unknown
Source)
at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildGraphicsNode(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.buildComposite(Unknown Source)
at org.apache.batik.bridge.GVTBuilder.build(Unknown Source)
at org.apache.batik.swing.svg.GVTTreeBuilder.run(Unknown Source)
I am using the Batik 1.6 on a Java 5 Update 4 virtual machine running on
Windows XP service pack 2. The batik .jars are taken directly from the
distribution.
If it will further your assessment of the situation, I could recompile
batik with debug information and resend the stack trace. Just give me
the word.
Good bye
-Urs
Thomas DeWeese wrote:
Hi Urs,
This is a bug, can you provide a full stack trace?
So I can tell who is getting it wrong?
Urs Reupke wrote:
Greetings,
Tonny Kohar wrote:
On Tue, 2005-07-19 at 16:48 +0200, Urs Reupke wrote:
Now, I believe this is a problem with the base URI of the document -
when converting from another XML-implementation, the (which did not
exist in the first place, since the document is created in memory)
URI is lost, thus Batik has no point of reference.
Is this assumption correct?
I am not sure if the error is because the base URI, since the Solar is
embeded within the same doc. It become problem when the referenced
resources is not within/embeded on the same doc
That's what I thought - but for some reason, there's a problem
nonetheless. Maybe there's something wrong with my conversion.
Does anyone here have experience with converting dom4j to w3c.dom?
However, to set the base URI there is two ways (you can choose either
one)
Thanks, for pointing this out. Referring to the my original message,
however, since the documents are created in-memory, there is no valid
URI I want them to have - all references will be to elements within
the document itself.
Regards
-Urs
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
