However, what's the trick to having a servlet with different
parameters in its URL with NetworkLinkControls to modify content.
Suppose the initial load creates a NetworkLink:
<kml xmlns="http://www.opengis.net/kml/2.2">
<NetworkLink>
<Link>
<href>http://localhost:8080/testServlet</href>
<httpQuery>fetch=kml&otherparameters...</httpQuery>
</Link>
</NetworkLink>
</kml>
Receiving the parameters loads the initial KML content:
<kml xmlns="http://www.opengis.net/kml/2.2">
<Placemark id="pm123">
<name>Placemark</name>
<description><![CDATA[Click <A href="http://localhost:
8080/testServlet?action=move">here</a> to move location
]]></description>
<Point>
<coordinates>...</coordinates>
</Point>
</Placemark>
</kml>
Now a move action generates this KML:
<kml xmlns="http://www.opengis.net/kml/2.2">
<NetworkLinkControl>
<Update>
<targetHref>http://localhost:8080/testServlet</targetHref>
<Change>
<Placemark targetId="pm123">
<name>Name changed by Update Change</name>
<Snippet>Snippet added by Update Change</Snippet>
</Placemark>
</Change>
</Update>
</NetworkLinkControl>
</kml>
But the original KML is unchanged..
Likewise, tried targetHref as http://localhost:8080/testServlet?fetch=kml&otherparameters..
to match the URL as would be modified via the HttpQuery parameter.
> Likewise, tried targetHref ashttp://localhost:8080/testServlet?fetch=kml&otherparameters..