LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Parse XML string NXG4

Dear Community members

 

I am in the process to use NXG more and more (NXG 4) 

Now I had to convert some code where I used the parse XML features from LabVIEW 20xx.

 

I there any equivalent to parse XML in NXG 4. The code conversion tool was not able to do anything with this sub vi's.

 

Thank you for any input

Gernot Hanel
IONICON Analytik Gesellschaft m.b.H.
0 Kudos
Message 1 of 9
(4,815 Views)

This will not help you a lot but, I asked JKI (on their forum) they intend to publish thier XML tools for NXG in 2020. I know... that's a bit vague. Until then, I don't know what to suggest.

Good luck!


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

0 Kudos
Message 2 of 9
(4,806 Views)

I have no confidence this step helps you. We can use following example to read xml fast.

Libxml2: Parsing XML in LabVIEW is too slow... or is it?

 

The components call dll. NXG 4.0 also can. Can we convert the example to NXG version?

Certified LabVIEW Developer
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

GCentral
Message 3 of 9
(4,789 Views)

I have already fighted with libxml2 a few years ago. There was a problem with 64bit compatibility.

So I went to use the .NET xDocument solution which worked fine.

Sorry but I don't want to start again with the libxml solution.

 

Thank you for your suggestion

Gernot Hanel
IONICON Analytik Gesellschaft m.b.H.
0 Kudos
Message 4 of 9
(4,728 Views)

Hi Gernot,

 

We have not yet migrated the native XML API but at least adding the flatten/unflatten VIs is on our roadmap. As mentioned above we'll be working with JKI to support their add-on migration for additional functionality over the coming year.

Deborah Burke
NI Hardware and Drivers Product Manager
Certified LabVIEW Architect
0 Kudos
Message 5 of 9
(4,682 Views)

Any news about migrating native XML to NXG now, Deborah? Will it be included in version 5.1 or 6? I think it is quite strange not to have XML support in a common programming tool. We have been using the XML parser in LabVIEW for many years, in fact since the Internet Toolkit was introduced, so lack of support for XML is really a problem for us when we consider switching to NXG. And the proprietary toolkit from JKI is not a replacement.

0 Kudos
Message 6 of 9
(4,176 Views)

@perj wrote:

Any news about migrating native XML to NXG now, Deborah? Will it be included in version 5.1 or 6? I think it is quite strange not to have XML support in a common programming tool. We have been using the XML parser in LabVIEW for many years, in fact since the Internet Toolkit was introduced, so lack of support for XML is really a problem for us when we consider switching to NXG. And the proprietary toolkit from JKI is not a replacement.


I advise to read the sticky posts at the top of the forum.  LabVIEW NXG is being discontinued.  The last version will be 5.1, due next year.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 7 of 9
(4,158 Views)

Hello,

We have a requirement to parse an XML String to a complex business object.

Scenario : XML String was formed as a result of conversion of my complex business object. After changing values of some variables (to rectify application error), we need to parse this XML String back to the same complex business object.

Could someone provide your inputs on how to get this done using IBM BPM 8.5.x?

 

 

 

myccpay

0 Kudos
Message 8 of 9
(4,085 Views)

@nottilie FaceTime wrote:

Dear Community members

 

I am in the process to use NXG more and more (NXG 4) 

Now I had to convert some code where I used the parse XML features from LabVIEW 20xx.

 

I there any equivalent to parse XML in NXG 4. The code conversion tool was not able to do anything with this sub vi's.

 

Thank you for any input


There was an issue with 64bit similarity. So I went to utilize the .NET xDocument arrangement which turned out great.

0 Kudos
Message 9 of 9
(4,083 Views)