AnsweredAssumed Answered

ImportObject.getImportMessages()

Question asked by DanielGates628573 on Feb 27, 2018
Latest reply on Feb 27, 2018 by DanielGates628573

Like • Show 0 Likes0
Comment • 4

Hello,

I have coded a solution to create a client, user, attach agent and import objects from xml.

I am using the getImportMessages() to return the messages when the objects are imported.

In terms of trapping any import errors/issues does anyone have a solution for doing so? Is it just a case of outputting the messages and then looking for keywords e.g. 'skipped'

If I need to check the output messages does anyone else know of any other keywords I should look for?

Cheers,

Dan.

Carsten_Schmitz Feb 27, 2018 10:25 AM

Correct Answer

Ah okay, so more like logical errors that don't get catched by an exception. Sounds good to me, but also sorry: I can't on the fly recall any further keywords.

Just another idea: Do the messages thrown possibly have "U000001"-style prefixes, as most Automic messages have? Maybe you could use those, e.g. treat anything that's not a known benign message code as an error, and narrow it down from there? Message codes would probably be more future proof than keywords, and also mean it potentially works with AEs in foreign translations?

Cheers,
Carsten

See the reply in context

No one else had this question

Outcomes

Carsten_Schmitz Feb 27, 2018 9:53 AM

Hi Dan,

Kudos on your solution!

I'm not much of a Java programmer, but parsing strings for error messages seems fragile and not very future-proof to me.

Doesn't ImportObject() throw exceptions, specificially java.io.IOException and org.xml.sax.SAXException that you could catch instead? This should cover all bases, and if it does not, that'd be a defect in the Automic functions, me thinks?

Best,
Carsten

Actions

DanielGates628573 Feb 27, 2018 10:20 AM

Carsten,

Ha ha .. when I say I have coded a solution I mean i have downloaded all @Brendan Sapience code and extracted out the bits i need :)

I think it will throw an error if something bad happens at the import level, but for example when we imported all objects into a new installation of the engine the SQL backend varas were skipped as our UC_SYSTEM_SETTINGS were different. I was thinking more about trying to catch errors like this really?

Cheers,

Dan

Actions

Carsten_Schmitz Feb 27, 2018 10:25 AM

Actions

DanielGates628573 Feb 27, 2018 10:29 AM

Cheers Carsten I will give it a go :)

Actions

4 Replies

Carsten_Schmitz Feb 27, 2018 9:53 AM
Mark Correct
Correct Answer
Hi Dan,

Kudos on your solution!

I'm not much of a Java programmer, but parsing strings for error messages seems fragile and not very future-proof to me.

Doesn't ImportObject() throw exceptions, specificially java.io.IOException and org.xml.sax.SAXException that you could catch instead? This should cover all bases, and if it does not, that'd be a defect in the Automic functions, me thinks?

Best,
Carsten
Like • Show 1 Like1
Actions
DanielGates628573 Feb 27, 2018 10:20 AM
Mark Correct
Correct Answer
Carsten,

Ha ha .. when I say I have coded a solution I mean i have downloaded all @Brendan Sapience code and extracted out the bits i need :)

I think it will throw an error if something bad happens at the import level, but for example when we imported all objects into a new installation of the engine the SQL backend varas were skipped as our UC_SYSTEM_SETTINGS were different. I was thinking more about trying to catch errors like this really?

Cheers,

Dan
Like • Show 1 Like1
Actions
Carsten_Schmitz Feb 27, 2018 10:25 AM
Unmark Correct
Correct Answer
Ah okay, so more like logical errors that don't get catched by an exception. Sounds good to me, but also sorry: I can't on the fly recall any further keywords.

Just another idea: Do the messages thrown possibly have "U000001"-style prefixes, as most Automic messages have? Maybe you could use those, e.g. treat anything that's not a known benign message code as an error, and narrow it down from there? Message codes would probably be more future proof than keywords, and also mean it potentially works with AEs in foreign translations?

Cheers,
Carsten
Like • Show 0 Likes0
Actions
DanielGates628573 Feb 27, 2018 10:29 AM
Mark Correct
Correct Answer
Cheers Carsten I will give it a go :)
Like • Show 0 Likes0
Actions

ImportObject.getImportMessages()

Outcomes

Related Content

Recommended Content