cancel
Showing results for 
Search instead for 
Did you mean: 

Exception in XML Parser

Former Member
0 Kudos

Hi all,

I have a file-XI-file scenario.

In this scenario the Transport Protocol used is FTP.

The remote sender and the receiver system have Golden FTP server installed.

The xml file is getting properly picked from the sender system. The format of this file is:

<?xml version="1.0" encoding="UTF-8" ?>

<ns:file_mt xmlns:ns="http://namespace4BPM1">

<file_type>binary</file_type>

<file_name>input</file_name>

<file_ext>txt</file_ext>

<content_dt>

<firstname>neetu</firstname>

<middlename>k</middlename>

<lastname>gupta</lastname>

</content_dt>

</ns:file_mt>

But the reciever file adapter is giving the following error:

Receiver Adapter v1027 for Party '', Service 'Receiver_Service':

Configured at 10:21:05 2006-06-05

Last message processing started 10:21:35 2006-06-05, Error: Message processing failed with java.lang.Throwable: ftp access error: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns:file_mt' found in document', probably configuration error in file adapter (XML parser error)'

The parameters specified in the receiver adapter are:

Connect mode: per file transfer

Transfer mode: Binary

put file: directly

file type : binary

I also tried sending the file after removing the structure 'ns:file_mt', but it gave the structure missing error message.

Pls if anybody could guide me as to what should be done.

Thanks in advance.

Regards

Neetu

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hey,

just try removing the namespace from the message type by deleting the value in XML NameSpace field while creating the message type.

Or check whether the message type given in the file adapter matches with the message type given in the xml file.

regards

jithesh

Former Member
0 Kudos

Thanks for the replies.

The scenario is working fine now.

Actually the message protocol in the reciever adapter should have parameter File.

By mistake i had mentioned File Content Conversion.

Regards

Neetu

Shabarish_Nair
Active Contributor
0 Kudos

just try with file_mt instead of ns:file_mt. Remember to edit the </ns:file_mt> also.

STALANKI
Active Contributor
0 Kudos

check the document name in file adapter configuration channel and message type name of the interface and name space..both should have same name...

check thz blog for more inputs

/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1

/people/venkat.donela/blog/2005/03/03/introduction-to-simple-file-xi-filescenario-and-complete-walk-through-for-starterspart2

Go through them and cross check ur config..