I was doing some testing and accidentally discovered a janky workaround... I was thinking that the only difference between the working samples and my application is that mine is built in Eclipse RCP with SWT, using an SWT-AWT bridge to contain the JMap:// Create embedding composite
Composite comp = new Composite(this,SWT.EMBEDDED | SWT.DOUBLE_BUFFERED);
comp.setLayoutData(new GridData(SWT.FILL, SWT.FILL, true, true));
comp.setLayout(new FillLayout());
// Create AWT container
Frame f = SWT_AWT.new_Frame(comp);
JApplet japp = new JApplet();
map = new ArcMap(); // extends JMap
// Add map to container
f.add(japp);
japp.add(map);
f.setVisible(true);
I decided to test my project by simply starting the Local Tiled Layer sample from inside my application. It worked! But all the more interesting... my map also worked! Therefore, somehow, when I start the Local Tiled Layer sample (which runs as a separate JFrame) from inside my application, it lets my JMap work (which is embedded in an SWT-AWT bridge JApplet).// start workaround
LocalTiledLayer.main();
// add map dispose listeners
addDisposeListener(new DisposeListener() {
@Override
public void widgetDisposed(DisposeEvent e) {
map.dispose();
LocalTiledLayer.dispose();
}
});I have no clue whatsoever why this works... but it WORKS! The only modification I made to the Local Tiled Layer sample was to change the instance created by main() to a static attribute and added a static dispose() function to call when my application is done. If the sample application is disposed before my application is complete, my map reverts to spewing errors.@See ESRI 10.2 Sample Code: Local Tiled Layer
