Skip to Content

If you perform content conversion using the Adapter Module localejbs/AF_Modules/MessageTransformBean (as explained in the “How To Use the Content Conversion Module in JMS Adapter” HowToGuide), especially when going from structured (multi record) flat to XML, you may need an “ignoreRecordsetName” option…

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Hi Alessandro,

    I don’t see any difference between the two XML that was shown here. I guess may be copy-paste error ๐Ÿ™‚

    I am still wondering is there any great value addition because of using this java mapping.
    Generally everyone used to go for ignoreRecordsetName
    create our strucutre with Recordset
    we can always give the Recordset Name in the content conversion paramter if out strucutre demands to have a different name.

    Even if we are not in the situation to use any of these option I feel the same can be achieved with few lines of code using XSLT. Even from performance point of view the java mapping shown here uses DOM. May be Java mapping with String manipulation like replace/substring or SAX would be of better performance.

    Anyways this is just my view, keep posting more blogs ๐Ÿ™‚


    1. Former Member Post author
      Thanks for your correction. Indeed a quick copy-paste did the mistake.

      Actaully the ignoreRecordsetName option was not workin’ for me (SP16), and I had an already used DataType without recordset. That’s why I wrote this java mapping.
      Also, I said explicitely that if anyone knew a std way, I would have been informed…

      Anyway, string manipulation doesn’t fit (no wise guy would do that!)… Maybe SAX, but currently I don’t know exactly how to deal with it.

      You know, I’ve never considered an XML a string.

      1. Yes I do agree string manipulation would not be a great idea while dealing with XML, may be you can try with SAX. But I thought you would be happy with the string manipulation as you had already used string for processing instruction (I mean “xmldecl” in the above code) instead of ProcessingInstruction that is available in DOM. <br/><br/>Anyways here is the code in XSLT to do the same, thought this might help you <br/><br/><br/><?xml version=”1.0″ encoding=”UTF-8″ standalone=”yes” ?> <br/><xsl:stylesheet version=”2.0″ xmlns:xsl=””  xmlns:ns1=”“><br/><xsl:output method=”text/xml” version=”1.0″ encoding=”ISO-8859-1″ indent=”yes”/><br/><xsl:template match=”ns1:MyDocument/Recordset”><br/><ns:MyDocument xmlns:ns=”“><br/><xsl:copy-of select=”child::node()”/><br/></ns:MyDocument><br/></xsl:template><br/></xsl:stylesheet><br/><br/><br/>Regards,<br/>Prakash


Leave a Reply