How to Eliminate empty tags in target XML in XSLT


To exclude empty tag in output XML from transformation apply below condition in transformation

<xsl:if test="(client:result3 != not(string(.)))">
      <client:result3>
        <xsl:value-of select="/client:process/client:input3"/>
      </client:result3>
      </xsl:if>

Comments

Post a Comment

Popular posts from this blog

How to get only numbers from string in XSLT

Image
To get only numeric value from input string we can use translate  function in XSLT.   <ns0:result>             <xsl:value-of select="translate ( /ns0:process/ns0:input , translate ( /ns0:process/ns0:input , '0123456789', '' ), '')"/>                  </ns0:result> /ns0:process/ns0:input is having string  from which numeric value should be get. nested translate function will work as below.  Inner translate(). This produces all characters of the string, except digits.  Outer translate(). This deletes from the string all characters produced by the inner translate(). What remains is just the wanted characters (the digits).
Read more

SOA interview questions

Question 1. What Is Bpel? Answer : Within the enterprise, BPEL is used to standardize enterprise application integration as well as to extend the integration to previously isolated systems. Between enterprises, BPEL enables easier and more effective integration with business partners. BPEL stimulates enterprises to further define their business processes, which in turn leads to business process optimization, reengineering, and the selection of the most appropriate processes, thus further optimizing the organization. Definitions of business processes described in BPEL do not affect existing systems, thereby stimulating upgrades. BPEL is the key technology in environments where functionalities are already or will be exposed via Web services. With increases in the use of Web services, the importance of BPEL will increase as well. BPEL represents a convergence of two early workflow languages; Web Services Flow Language (WSFL) and XLANG. WSFL was designed by IBM and is based on the...
Read more

[JMSClientExceptions:055144]Destination must be a topic

ERROR:- <Error> <oracle.soa.bpel.engine.ws> <BEA-000000> <got FabricInvocationException weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055144]Destination must be a topic, JMSModule!mycompany.dev.queue.Process.ErrorMessage.Routing CAUSE:-  The issue occurred due to incorrect setting of JMS Adapter Outbound Connection Pool. "mycompany.dev.queue.Process.ErrorMessage.Routing" is a queue created in JMSModule. However the outbound connection pool created at JMS Adapter to interact with this queue has IsTopic set as TRUE. This means it is searching for a TOPIC by the name "mycompany.dev.queue.Process.ErrorMessage.Routing" and not a queue. SOLUTION:-  If you are creating JMS Adapter Outbound Connection Pool for QUEUE, set isTopic= FALSE. If you are creating JMS Adapter Outbound Connection Pool for TOPIC, set isTopic= TRUE.
Read more