# Java method behind 'Copy XML to Clipboard'

**URL:** <https://forum.inductiveautomation.com/t/java-method-behind-copy-xml-to-clipboard/48082>\
**Category:** Ignition\
**Tags:** ignition80, vision, scripting\
**Created:** [June 22, 2021, 9:09pm UTC](https://forum.inductiveautomation.com/t/java-method-behind-copy-xml-to-clipboard/48082 "2021-06-22T21:09:02Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![zacht](https://avatars.discourse-cdn.com/v4/letter/z/ea5d25/32.png) [@zacht](https://forum.inductiveautomation.com/u/zacht)\
**Post date:** [February 28, 2022, 4:14pm UTC](https://forum.inductiveautomation.com/t/java-method-behind-copy-xml-to-clipboard/48082/8 "2022-02-28T16:14:10Z")

</div>

That isn't how I got the designer context. I used some code from [this forum post](https://forum.inductiveautomation.com/t/how-to-get-project-object-using-script/7472/3).

As `pturmel` noted,

> [@pturmel](#):
>
> Working with contexts is totally unsupported, of course.

so tread carefully and probably don't use this in a production setting. I used it to partially automate some mass tag renaming I was very closely supervising. I wouldn't trust it for much more than that, and I certainly wouldn't trust it across Ignition versions.

In the forum thread I linked you will also see @Robert.McKenzie warn against relying on this sort of implementation, so consider this a double warning.

---

_[View the full topic](https://forum.inductiveautomation.com/t/java-method-behind-copy-xml-to-clipboard/48082)._