Generic XML Structure solution/suggestions

Hi,
I am pretty new to XML, so looking for some suggestions.
I want to create an XML structure for following data.
I have Product P1, and Product P2
P1 has following fields: F1,F2,F3,F4
P2 has following fields:F0,F1, F3, F4, F5,F6
You see both the products have some common fields and some extra fields.
I want to make one XML structure (common to P1 and P2)that defines(tag value pair) both.
I dont want something like say: If type == P1 then F5 and F6 field is null.
It should not be defined for P1.
lly F0 and F2 should not be defined for P2.
Can anyone help me to define some common structure to accomplish this.

Unless I'm missing something, what you want to do is set up the structure something like:
<!element products(product*) >
<!element product(f0*, f1*, f2*, f3*, f4* , f5*, f6*) >
<!element f0 (#CDATA) >
<!element f1 (#CDATA) >
<!element f2 (#CDATA) >
<!element f3 (#CDATA) >
<!element f4 (#CDATA) >
<!element f5 (#CDATA) >
<!element f6 (#CDATA) >
Obviously this changes depending on how often the data can recur and type of data, but this will give you an idea of DTD setup. Using schema would also give you the ability to define field length and such. Find a good DTD reference guide either online or from a book and it will give examples of the different recurring notations (*, + and the like). Hope this helps.

Similar Messages

Generating Dynamic UI from XML structure

Hi All,
I have a requirement in which I need to select an entry in the first view and based on this, the second view would come come. But there are 30 different values that can be selected and each of them will have a different set of UI elements in the second screen. So if I go for normal static UI creation, then I need to create 30 odd views which is something we do not want.
The second option is to dynamically generate the UI elements in wdDoModify() method. But for 30 different conditions to check all the time will lead to performance issue.
So we are thinking if there is a way for webdynpro to dynamically read an XML structure that defines attributes and generates a layout for us dynamically.
Please provide your inputs on this. Also kindly suggest any other better ways for the solution.
Thanks and Regards,
Sayan Ghosh

Hello!
I think you should go with second one. But I don't know any "ready to use" solutions, so you have to
- Create your own XML structure, something like
<section type="yourCondition">
<input name="somePropertyName" type="text"/>

</section>
- Parse this XML into Java Model (on application startup for example)
- On user selection choose requred UI Model from memory and pass it to view
- In wdDoModify() build UI(elements, context attributes, mappings etc.) according to this model
It will be rather complicated for huge UI, but possible.
Thanks, Mikhail

More fields in XML structure error in Adapter Monitor

Hi all
I am getting the following error in the adapter monitor
Error: Message processing failed: Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value ' ')', probably configuration error in file adapter (XML parser error)'
I am using FCC in the rx adapter. I have also checked the fields for any extra fields but there isnt any.
kindly suggest what could be throwing the error
regards
krishna

Hi raj
here are the CC parameters.
BEGIN.addHeaderLine     0
BEGIN.fieldFixedLengths     2,1,3,2,4,1,8,12,8,2,307,12,8,12,18
BEGIN.fixedLengthTooShortHandling     Ignore
BEGIN.endSeparator     '0x0D''0x0A'
CLIENT_RECORD.addHeaderLine     0
CLIENT_RECORD.fieldFixedLengths     2,12,9,4,15,15,4,20,12,9,8,1,1,25,10,1,25,10,1,6,1,1,1,1,1,10,8,1,25,2,1,1,1,106,12,38
CLIENT_RECORD.fixedLengthTooShortHandling     Ignore
CLIENT_RECORD.endSeparator     '0x0D''0x0A'
RELATION_RECORD.addHeaderLine     0
RELATION_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,9,8,1,25,10,1,25,10,1,6,1,1,181,12,38
RELATION_RECORD.fixedLengthTooShortHandling     Ignore
RELATION_RECORD.endSeparator     '0x0D''0x0A'
ADDRESS_RECORD.addHeaderLine     0
ADDRESS_RECORD.fieldFixedLengths     2,12,9,4,20,20,2,2,5,6,8,24,24,2,35,15,4,15,4,70,8,8,1,50,12,38
ADDRESS_RECORD.fixedLengthTooShortHandling     Ignore
ADDRESS_RECORD.endSeparator     '0x0D''0x0A'
GIVING_REC.addHeaderLine     0
GIVING_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,1,1,1,1,1,1,1,1,1,1,281,12,38
GIVING_REC.fixedLengthTooShortHandling     Ignore
GIVING_REC.endSeparator     '0x0D''0x0A'
ZIKT_REC.addHeaderLine     0
ZIKT_REC.fieldFixedLengths     2,12,9,4,20,9,2,3,2,8,1,1,277,12,38
ZIKT_REC.fixedLengthTooShortHandling     Ignore
ZIKT_REC.endSeparator     '0x0D''0x0A'
BEPER_REC.addHeaderLine     0
BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,1,1,291,12,38
BEPER_REC.fixedLengthTooShortHandling     Cut
BEPER_REC.endSeparator     '0x0D''0x0A'
SCORE_BEPER_REC.addHeaderLine     0
SCORE_BEPER_REC.fieldFixedLengths     2,12,9,4,20,9,1,3,4,1,1,284,12,38
SCORE_BEPER_REC.fixedLengthTooShortHandling     Ignore
SCORE_BEPER_REC.endSeparator     '0x0D''0x0A'
INDBES_REC.addHeaderLine     0
INDBES_REC.fieldFixedLengths     2,12,9,4,20,9,9,2,2,8,8,8,1,256,12,38
INDBES_REC.fixedLengthTooShortHandling     Ignore
INDBES_REC.endSeparator     '0x0D''0x0A'
FUNCTIONAL_REC.addHeaderLine     0
FUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,8,8,1,4,2,2,1,1,1,1,8,1,1,233,12,38
FUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
FUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ACT_REC.addHeaderLine     0
ACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,8,3,5,1,263,12,38
ACT_REC.fixedLengthTooShortHandling     Ignore
ACT_REC.endSeparator     '0x0D''0x0A'
SCORE_REC.addHeaderLine     0
SCORE_REC.fieldFixedLengths     2,12,9,4,20,9,3,4,1,1,285,12,38
SCORE_REC.fixedLengthTooShortHandling     Ignore
SCORE_REC.endSeparator     '0x0D''0x0A'
ZFUNCTIONAL_REC.addHeaderLine     0
ZFUNCTIONAL_REC.fieldFixedLengths     2,12,9,4,20,9,9,12,3,2,8,8,5,1,8,8,8,4,2,2,1,1,1,1,210,12,38
ZFUNCTIONAL_REC.fixedLengthTooShortHandling     Ignore
ZFUNCTIONAL_REC.endSeparator     '0x0D''0x0A'
ZACT_REC.addHeaderLine     0
ZACT_REC.fieldFixedLengths     2,12,9,4,20,9,9,3,2,3,5,8,8,5,8,1,242,12,38
ZACT_REC.fixedLengthTooShortHandling     Ignore
ZACT_REC.endSeparator     '0x0D''0x0A'
COMMENT.addHeaderLine     0
COMMENT.fieldFixedLengths     2,12,4,140,1,191,12,38
COMMENT.fixedLengthTooShortHandling     Ignore
COMMENT.endSeparator     '0x0D''0x0A'
END_REC.addHeaderLine     0
END_REC.fieldFixedLengths     2,6,6,6,6,6,6,6,6,6,6,6,6,6,6,6,1,257,50
END_REC.fixedLengthTooShortHandling     Ignore
END_REC.endSeparator     '0x0D''0x0A'
REgards
krishna

XML structure - mapping one Oracle column to many XML attributes

Hi,
I need to insert data into EMP table reading from xml file and this is how the file would look like....
<?xml version='1.0'?>
<ROWSET>
<ROW num="1">
<EMPLOYEE_ID>7369</EMPLOYEE_ID>
<LAST_NAME>Smith</LAST_NAME>
<FIRST_NAME>JOHN</FIRST_NAME>
<PHONE> 905000123</PHONE>
<PHONE> 905000456</PHONE>
<PHONE> 905000789</PHONE> ...... n
(There could be many phone numbers in the xml file and I need to concatenate all the numbers and insert in the PHONE column of emp table)
<SALARY>800</SALARY>
</ROW>

</ROWSET>
I am new to XML and would to know the set of lines required to read the data from xml and insert into EMP table. All this is for Oracle 10g R2.
Please let me know solution using XSU if possible.

Hi,
Chk this:
/people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
Re: Conversion of source XML structure to single string using PI 7.1
Thanks
Amit

Convert IDOC XML structure to flat file - and now?

Hi,
we are working with input message ORDERS05 and want to convert it to flat file.
So we used the implementation description from "how to convert an IDOC-XML structure to a flat file....".
Looks like this is a standard procedure described here fitting for all IDOCs.
We followed the guide, making XI ready for Abap-Mapping, implemented the Abap class like described, added an interface mapping with source ORDERS05 to a mess.type dummy destination, added with type Abap-class the class implemented from the guide and completed the Int.Dir. implementation.
For comparism purpose we have two systems as receiver, one with a standard flat file with regular graph.mapping in XI, one with the Abap mapping.
Result:
Error description in SXMB_MONI:
Didn´t expect something like that! The IDOC was delivered successfully to the other simple flat file receiver.
Any idea what we made wrong (we are on SP17) or if there is a standard mistake you can do when following the guide?
Best regards
Dirk

Hi,
I've got the same problem. He the solution in my case:
The problem is:
My IDOC has no element <STDMES>, but the method IF_MAPPING~EXECUTE from the 'HOW-TO Guide' does not check this situation:
el_element = idocument->find_from_name('STDMES').
ls_edidc-stdmes = el_element->get_value().
thows the exception.
Solution:
make shure that the field STDMESis set or change the method to:
el_element = idocument->find_from_name('STDMES').
if not el_element is initial.
ls_edidc-stdmes = el_element->get_value().
endif.
Best regards
Dieter

XML gateway with multiple XML structures??

Hi,
I have a requirement to import data using XML gateway with different XML structures. Third party system sometimes will not provide certain tags itself if there is no data for the tag like contacts in below sample xmls. In that case we need to ignore those tags (CONTACTS in below sample). As per my understanding, we must have tag in XML though it may not have any value.
We have 2 XMLs
XML1 for supplier with contacts
<SUPPLIER>
<NAMES>
<NAME1>XYZ </NAME1>
<NAME2>ABC</NAME2>
</NAMES>
<SITE>
<SITE1>XYZ </SITE1>
<SITE2>ABC</SITE2>
</SITE>
<CONTACT>
<CONTACT1>XYZ </CONTACT1>
<CONTACT2>ABC</CONTACT2>
</CONTACT>
</SUPPLIER>
XML2 for supplier without contacts
XML1
<SUPPLIER>
<NAMES>
<NAME1>XYZ1 </NAME1>
<NAME2>ABC1</NAME2>
</NAMES>
<SITE>
<SITE1>XYZ1 </SITE1>
<SITE2>ABC1</SITE2>
</SITE>
</SUPPLIER>
Can we upload data in both these xmls using only one generic dtd and xgm using XML gateway which will skip any missing tag.
Thanks
Rishi

Hi, you can FOR XML PATH for a finer degree of control over your XML. Use the @ symbol to create attributes. Here's a simple example:
DECLARE @t TABLE ( rowId INT IDENTITY PRIMARY KEY, [address] VARCHAR(50), city VARCHAR(30), floor INT, suite INT, doorType VARCHAR(20) )
INSERT INTO @t VALUES
( '123 Fake St', 'Springfield', 10, 512, 'Metal' )
SELECT
[address] AS "Address",
city AS City,
[floor] AS "Location/@Floor",
suite AS "Location/@Suite",
doorType AS "Location/@DoorType"
FROM @t
FOR XML PATH ('Company'), ROOT ('Companies'), ELEMENTS;

Xml structure being ignored

XML structure in "Bus Card Order Form" created in inDesign is being ignored by Acrobat>Tools>Forms>More Form Options>Export Data.
inDesign form also has DTD.
1. inDesign "BC Order Form" is output to interactive pdf fillable form
2. pdf filled form is then saved.
3. XML is then exported per above, however XML structure does not match. Rather, root is redefined as "fields' and all fields are listed alphabetically.
4. xml data does not flow into fields in BC template.
Both "Bus Card Order Form' and 'BC Template' have matching xml structure.
What am I doing wrong?

Nevermind my previous post; I see the error in our own code. You're
right; the file isn't being used. This will be fixed in our 2.5 final
release. Sorry!
In the meantime, I suggest you continue to use the 2.4
kodo-reverse-schema.jar

Database data to nested xml structure

Hi All,
I need to convert the data in the oracle database to nested xml tree structure as below:
Data in the database is in the following structure:
1     branch1     13-JAN-11     a.txt
1     branch1     25-JAN-11     b.txt
1     branch1     25-JAN-11     c.txt
1     branch2     20-JAN-11     d.txt
2
XML for the above data should be in the format:
<Root>
<Account_no value="1">
<Desc value="branch1">
<Date value="13-JAN-11">
<Name value="a.txt"/>
</Date>
<Date value="25-JAN-11">
<Name value="b.txt"/>
<Name value="c.txt"/>
</Date>
</Desc>
<Desc value="branch2">
<Date value="20-JAN-11">
<Name value="d.txt"/>
</Date>
</Desc>
</Account_no>
<Account_no value="2">
</Account_no>
</Root>
I am able to get this kind of xml structure using java after storing the database data in a n-ary tree. But it takes more time to execute.
Can this kind of same xml format be achieved using pl/sql programming?
Please help me with your valuable insights.
Thanks,
Alagappan

Hi,
Please always mention your db version (select * from v$version).
Here's one solution using SQL/XML functions :
Sample data used :
create table sample_data
account_no number,
description varchar2(30),
dt          date,
name        varchar2(30)
insert into sample_data values(1, 'branch1', to_date('13-JAN-11','DD-MON-RR'), 'a.txt');
insert into sample_data values(1, 'branch1', to_date('25-JAN-11','DD-MON-RR'), 'b.txt');
insert into sample_data values(1, 'branch1', to_date('25-JAN-11','DD-MON-RR'), 'c.txt');
insert into sample_data values(1, 'branch2', to_date('20-JAN-11','DD-MON-RR'), 'd.txt');
insert into sample_data values(2, 'branch3', to_date('20-JAN-11','DD-MON-RR'), 'e.txt');Query :
SELECT xmlserialize(document
         xmlelement("Root",
           xmlagg(
             xmlelement("Account_no", xmlattributes(account_no as "value"),
               xmlagg(
                 xmlelement("Desc", xmlattributes(description as "value"), dt)
                 order by description
             ) order by account_no
       as clob indent ) doc
FROM (
SELECT account_no, description,
         xmlagg(
           xmlelement("Date", xmlattributes(to_char(dt,'DD-MON-RR') as "value"), name)
           order by dt
         ) dt
FROM (
    SELECT account_no, description, dt,
           xmlagg(
             xmlelement("Name", xmlattributes(name as "value"))
             order by name
           ) name
    FROM sample_data
    GROUP BY account_no, description, dt
GROUP BY account_no, description
GROUP BY account_no
DOC
<Root>
<Account_no value="1">
    <Desc value="branch1">
      <Date value="13-JAN-11">
        <Name value="a.txt"/>
      </Date>
      <Date value="25-JAN-11">
        <Name value="b.txt"/>
        <Name value="c.txt"/>
      </Date>
    </Desc>
    <Desc value="branch2">
      <Date value="20-JAN-11">
        <Name value="d.txt"/>
      </Date>
    </Desc>
</Account_no>
<Account_no value="2">
    <Desc value="branch3">
      <Date value="20-JAN-11">
        <Name value="e.txt"/>
      </Date>
    </Desc>
</Account_no>
</Root>
Here, I used XMLSerialize function with indent option to format the output (available starting with 11g).

XML structure validation by javascript

Hi All,
I’m trying to find solution for XML structure validation on opening the indesign document.
Is this possible by javascript.
by
hasvi

Or you could go directly to the source.
http://help.sap.com/saphelp_nw70/helpdata/en/c4/e1343e8c7f6329e10000000a114084/frameset.htm
Regards,
Henrique.

CDATA and XML structure

Hej!
I am trying to but an entire XML structure into a CDATA-tag. But have not been successful.
Im using Xquery and trying to somthing like this:
I have an variable $example which contains a XML structure. For example:
$example = <elementA><A1>valueA1</A1><A2><A2a>text2a</A2a><A2b>text2b</A2b></A2><A3>valueA3</A3></elementA>
I want to something like this <![CDATA[$example]]> to be expanded to <![CDATA[<elementA><A1>valueA1</A1><A2><A2a>text2a</A2a><A2b>text2b</A2b></A2><A3>valueA3</A3></elementA>]]>
I have tried in many ways (eg by doing concat("<![CDATA[", $example, "]]>") ) and ended up with a CDATA tag that contains only the value of the elements in the tags of A1, A2 and A3. for example the CDATA that is created looks something like this:
<![CDATA[valueA1text2atext2bvalueA3]]>
instead of
<![CDATA[<elementA><A1>valueA1</A1><A2><A2a>text2a</A2a><A2b>text2b</A2b></A2><A3>valueA3</A3</elementA>]]>
I would really be grateful for any suggestions or tips and pointers on how to solve this.
Best Regards
Ninib
Edited by: NinibEDB on 2010-nov-09 17:35

Hi,
Which XQuery processor are you using?
According to the W3C specifications, the output of CDATA section is part of the serialization process, not the XQuery evaluation. So it's up to the implementor to provide the necessary options.
The option we need here is the "cdata-section-elements" parameter :
http://www.w3.org/TR/xslt-xquery-serialization/#XML_CDATA-SECTION-ELEMENTS
For example, using the Saxon XQuery processor :
declare option saxon:output "omit-xml-declaration=yes";
declare option saxon:output "cdata-section-elements=test";
let $example := "<elementA><A1>valueA1</A1><A2><A2a>text2a</A2a><A2b>text2b</A2b></A2><A3>valueA3</A3></elementA>"
return <test>{$example}</test>which gives :
<test><![CDATA[<elementA><A1>valueA1</A1><A2><A2a>text2a</A2a><A2b>text2b</A2b></A2><A3>valueA3</A3></elementA>]]></test>

Nested XML structure from Oracle

Using the SQL Adapter i BizTalk, calling a SQL Stored procedure on a MS SQL DB, I can get a nice nested XML structure using p JOIN ii and FOR XML AUTO, like this
<p code="DK003">
<ii stamp="2013-01-14T10:27:38.790"value="180.702052"price="184.000000">
<d Dividend="2.50"DividendDate="2012-03-29T00:00:00" />
</ii>
<ii stamp="2013-01-14T10:27:38.790"value="181.702052"price="14.000000">
<d Dividend="2.50"DividendDate="2012-03-29T00:00:00" />
</ii>
</p>
How can I get the same on Oracle ??

Hi E.,
I guess this an XML namespace issue. I'm creating XmlForms-style documents and had to add an XML namespace to my root element to make them visible as such:
Namespace xf = Namespace.getNamespace("xf", "http://www.sapportals.com/wcm/app/xmlforms");
root.addNamespaceDeclaration(xf);
So what I'd suggest to you is reading out the IResource and treating the content as XML:
Document document = new SAXBuilder().build(content.getInputStream());
Element root = document.getRootElement();
Namespace xf = Namespace.getNamespace("xf", "http://www.sapportals.com/wcm/app/xmlforms");
root.removeNamespaceDeclaration(xf);
Hope this helps!
regards,
Christian

Passing XML structures

Dear All,
We have got a problem trying to pass structured XML string to BPEL via JMS. The partner process just computes the result (an XML string) and sends it to a JMS queue. The JMS content contains the XML structure (string) that we want to pass. When we try to assign the JMS content to the BPEL variable it seems to work but, when we try to address an element, the process fails.
In my opinion this behaviour is due to the forced assignment of an XML formatted string to a BPEL XML object. So we tried to find samples on this topic. Any help is welcomed. Thanks and Regards,

You can't execute xpath query on a string, i would suggest converting that xml string into dom element and set the variable. there is an easy way to achieve this bpel.
Use the parseEscapedXML('xml-string') xpath function, you can look at [orabpel-home]/samples/references/XPathFunction sample on how its getting used.
In your case,you might need to use getVariableData() to get the xml string content and use this parseEscapedXML() to convert to element. like below:
<copy>
<from expression="ora:parseEscapedXML(string(bpws:getVariableData('your-variable', 'part', '/a/b'))))"/>
<to variable="your-variable" part="part", query="/a/b/c"/>
</copy>

XML structure inside WS string response

Hi all,
I have a PI scenario and I can find a solution.
The scenario is a ABAP PROXY that consume a WS, this is no problem, the problem is that the web service returns a string parameter, and inside the string parameter there is a XML structure.
My doubt is, how can mapping it to get the response in a structured data type instead of a string??
Thanks a lot
Raú

Hi ,
Is the return type is an XML structure? Then use java mapping using DOM parser to extract the string from response. Then the mapping program can generate the required target structure from the string.
you can if possible let the forum members know, the response xml message and the structure of target XML as per your requirement. Finally also the version of PI you are working is also important as java mapping procedure is different for PI7.0 and PI 7.1.
As Stefan has pointed out without java mapping it will be almost impossible to extract the target XML from String. Still you can try out with XSLT mapping, but I don't think that will be easy task to do. Java mapping is the correct procedure to solve your problem. Finally forum members will be able to assist you if you provide complete source and target XML structure alog with sample string response. you can reuse java mapping code for multiple interfaces within same SWCV. The part or module which will be calling the common code with different input parameters will vary accross interfaces depending on your need.
regards
Anupam
Edited by: anupamsap on Sep 29, 2011 1:55 PM
Edited by: anupamsap on Sep 29, 2011 2:21 PM

How to modify Source XML Structure as it is getting Fail in message Mapping

From Client , I am Gettin Such XML Structure in XML File ...But it is getting failed in Message Mapping ,.,,
<?xml version="1.0"?>
<invoice>
   <Header>
      <DOCID>0001</DOCID>
      <DOCNO>0001</DOCNO>
      <INVAMT>1000</INVAMT>
   </Header>
</invoice>
I tried to find out few things ...
On test of mesage mapping
<?xml version="1.0" encoding="UTF-8"?>
<ns0:invoice xmlns:ns0="urn:sample.com:file:file">
   <Header>
      <DOCID>0001</DOCID>
      <DOCNO>0001</DOCNO>
      <INVAMT>1000</INVAMT>
   </Header>
</ns0:invoice>
This mapping is getting successful.
So Problem I found Is difference in Sender File Structure from autogenrated Source Structure in Test tab :
</invoice>
and
<ns0:invoice xmlns:ns0="urn:sample.com.com:Invoice:DB">
Please Suggest : What to do ?
How to add this ns0: before INVOICE and :ns0="urn:sample.com.com:Invoice:DB" after INVOICE in Source Structure.
I am using PI 7.0
regards
Prabhat

Hi Prabhat,
the easiest way is to make the field XML Namespace of the source Message Type blank.
Regards,
Udo

How can I get the XML structure from a flat structure?

Hi all,
in my XI SP 12 I use a JMS adapter to read information using the WebSphereMQ transport protocol.
The structure that I receive have this format:
<Name_A.KeyFieldValue><Name_A.fieldName_A1_Value>...<Name_A.fieldName_AN_Value>
<NumberRecordType_B><NumberRecordType_c>
<Name_B.KeyFieldValue><Name_B.fieldName_B1_Value>...<Name_B.fieldName_BN_Value>
<Name_B.KeyFieldValue><Name_B.fieldName_B1_Value>...<Name_B.fieldName_BN_Value>
<Name_C.KeyFieldValue><Name_C.fieldName_C1_Value>...<Name_C.fieldName_CN_Value>
<Name_C.KeyFieldValue><Name_C.fieldName_C1_Value>...<Name_C.fieldName_CN_Value>
the problem is that in this structure each line is not separated by a carriage return or a comma, I have all the information in a single line:
<Name_A.KeyFieldValue><Name_A.fieldName_A1_Value>...<Name_A.fieldName_AN_Value><NumberRecordType_B><NumberRecordType_c><Name_B.KeyFieldValue><Name_B.fieldName_B1_Value>...<Name_B.fieldName_BN_Value>...<Name_B.KeyFieldValue><Name_B.fieldName_B1_Value>...<Name_B.fieldName_BN_Value><Name_C.KeyFieldValue><Name_C.fieldName_C1_Value>...<Name_C.fieldName_CN_Value>...<Name_C.KeyFieldValue><Name_C.fieldName_C1_Value>...<Name_C.fieldName_CN_Value>
and the customer don't want to insert a line separator.
Then, the question is:
How can I get the XML structure from this structure?
If possible, I don't want to develop new Module and add it in the JMS Module Sequence.
PS I have already read the article "How to Use the Content Conversion Module with the XI 3 J2EE JMS Adapter.pdf" and it doesn't seem to help me.
Best Regards,
Paolo

To get context parameters from your web.xml file you can simply get the ActionServlet object from an implementing action object class. In the perform (or execute) method make the following call.
ServletContext context = getServlet().getServletContext();
String tempContextVar =
context.getInitParameter("<your context param >");

Generic XML Structure solution/suggestions

Similar Messages

Maybe you are looking for