fatal error due to </ in the value

[Former Member]

Hi XI Gurus

I have follwing scenario:

Mail ---> XI ---> R-3

In the few mails, i am receiving the <b></</b> as a part of node value.

For ex.

<Root>

<Child>4534DECEFFDA1911E1</font>

</Child>

</Root>

Please guide me to sort out this issue.

Regards

Piyush

[Former Member · Accepted solution]

Hi,

Please check if this URL helps:

Regards

Vijaya

[Former Member · Accepted solution]

Hi vijaya,

Thanks for the prompt response.

I went through the whole post and i realized that shai is looking for the value of one paricular node to pass further.

In my case, i want to pass the whole content....but it has <b>"</" </b>

So please share some idea, how can i handle this?

In whole message only one tag has this issue..

Piyush

[Former Member · Accepted solution]

Hi Piyush,

one option would be to write a module at sender adapter to replace the '<' character with corresponding escape character '&lt;'and '>' by '&gt;'(without quotes) in the node value.

Regards,

Sudharshan

[bhavesh_kantilal · Accepted solution]

Piyush,

Can you give more details,.

1. What is the mapping you are using?

2. What is the source and what is the target? with an example?

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi All,

In my scenario,

Source Structure is

<Root>

<Child>

NodeValue

</Child>

</Root>

As <b>"</"</b> is present in the NodeValue, the input xml becomes invalid and it throws the fatal error.

It is not reaching mapping part at all due to improper source xml.

Parser will also fail due to this.

Please let me know how to handle this.

Regards

Piyush

[bhavesh_kantilal · Accepted solution]

Piyush,

One option is to ask the source system to replace this </ as <b></</b>. If the source system cannot do this , then another options is to use multiple mappings inside the Interface Mappings.

1. The first mapping will be a java mapping that will replace the </ with &lt; and then send the source as the output.

2. The second mapping will be the actual graphical mapping and as it has been replaced by </ I dont think graphical mapping will cause any issues in this case.

Regards,

Bhavesh