- Josh Turner
- PowerBuilder
- Friday, 27 October 2017 07:13 PM UTC
We have recently imported the PBDOM extension into one of our existing libraries. I feel like I am missing something very basic because our automated builds fail when trying to compile the library stating that the pbdom_document object is an illegal data type. Even though I can physically see the pbdom_document object in the library, the solution has temporarily been to manually import the extension on every environment separately. As far as I can tell there was no difference in the source but something about doing the import causes the compile issues to go away. However, this is not a good solution long term because it happens every time we set up a new environment in source control and sometimes after a GLV in source control. Please help.
pbdom_object C:\Builds\Unit_Testing\Source\reuse\xml\xml.pbl
Library: C:\Builds\Unit_Testing\Source\reuse\xml\xml.pbl
Object: pbdom_object
pbdom_object Class Declaration
(0014): Error C0001: Illegal data type: pbdom_document
pbdom_characterdata C:\Builds\Unit_Testing\Source\reuse\xml\xml.pbl
Library: C:\Builds\Unit_Testing\Source\reuse\xml\xml.pbl
Object: pbdom_characterdata
pbdom_characterdata Class Declaration
(0014): Error C0001: Illegal data type: pbdom_document
pbdom_text C:\Builds\Unit_Testing\Source\reuse\xml\xml.pbl
Library: C:\Builds\Unit_Testing\Source\reuse\xml\xml.pbl
Object: pbdom_text
...
Thanks
Josh Turner
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.