Nested tags are no longer evaluated since sp3

Question

Since the introduction of service pack 3 for WLS6.1, all our custom tags
          have a problem: any tag that is nested inside one of our custom tags is not
          evaluated, but just displayed as text. Before sp3 everything worked just
          fine?
          What happened?
          example:
          public class ExtendedOptionTag extends BodyTagSupport {
          protected static MessageResources messages =
          MessageResources.getMessageResources(
          "com.bmg.view.taghandler.LocalStrings" );
          public static Log log = LogFactory.getLog(
          ExtendedOptionTag.class.getName() );
          protected String text = null;
          protected boolean disabled = false;
          public boolean getDisabled() {
          return ( this.disabled );
          public void setDisabled( boolean disabled ) {
          this.disabled = disabled;
          protected String value = null;
          public String getValue() {
          return ( this.value );
          public void setValue( String value ) {
          this.value = value;
          protected String name = null;
          public String getName() {
          return ( this.name );
          public void setName( String name ) {
          this.name = name;
          protected String property = null;
          public String getProperty() {
          return ( this.property );
          public void setProperty( String property ) {
          this.property = property;
          public int doStartTag() throws JspException {
          // Initialize the placeholder for our body content
          this.text = null;
          return ( EVAL_BODY_TAG );
          public int doAfterBody() throws JspException {
          String text = bodyContent.getString();
          if ( text != null ) {
          text = text.trim();
          if ( text.length() > 0 ) {
          this.text = text;
          return ( SKIP_BODY );
          public int doEndTag() throws JspException {
          // Acquire the select tag we are associated with
          SelectTag selectTag = ( SelectTag ) pageContext.getAttribute(
          Constants.SELECT_KEY );
          if ( selectTag == null ) {
          JspException e = new JspException
          ( messages.getMessage( "optionTag.select" ) );
          RequestUtils.saveException( pageContext, e );
          throw e;
          // Generate an HTML <option> element
          StringBuffer results = new StringBuffer();
          results.append( "<option value=\"" );
          if ( value != null ) {
          results.append( value );
          } else {
          if ( name != null ) {
          Object theBean = RequestUtils.lookup( pageContext, getName(), null );
          log.debug( "The bean class is: " + theBean.getClass().getName() );
          if ( theBean == null ) {
          throw new JspTagException( messages.getMessage(
          "exceptions.nosuchbean", getName() ) );
          if ( property != null ) {
          if ( theBean instanceof
          com.bmg.bbb.business.nettingmgr.rb.NettingCalendarEntryRB ) {
          short variable = ( (
          com.bmg.bbb.business.nettingmgr.rb.NettingCalendarEntryRB )
          theBean ).getCalenderEntrySeqNo();
          value = "" + variable;
          } else {
          try {
          value = BeanUtils.getSimpleProperty( theBean, getName() );
          } catch ( NoSuchMethodException ex ) {
          // TBD GW 3/12/2001 11:34AM: improve exception handling
          throw new JspException( messages.getMessage(
          "exceptions.nosuchproperty", getProperty(), getName() ) );
          } catch ( Exception ex ) {
          throw new JspException( messages.getMessage(
          "exceptions.unsupportedexception", ex.getClass().getName(), "bmg:option",
          ex ) );
          results.append( value );
          } else {
          value = theBean.toString();
          results.append( value );
          } else {
          throw new JspTagException( messages.getMessage(
          "exceptions.exorattribute", "value", "name" ) );
          results.append( "\"" );
          if ( disabled ) {
          results.append( " disabled=\"disabled\"" );
          log.debug( "Match Value: " + value );
          if ( selectTag.isMatched( value ) ) {
          results.append( " selected=\"selected\"" );
          results.append( ">" );
          String text = text();
          if ( text == null ) {
          results.append( value );
          } else {
          results.append( text );
          results.append( "</option>" );
          // Render this element to our writer
          ResponseUtils.write( pageContext, results.toString() );
          // and reset the body text
          text = null;
          // Continue evaluating this page
          return EVAL_PAGE;
          public void release() {
          super.release();
          text = null;
          disabled = false;
          value = null;
          name = null;
          property = null;
          protected String text() throws JspException {
          return this.text;
          Folkert Schram de Jong
          Cap Gemini Ernst & Young
          Financial Services / B71 Java
          Tel. [phone]
          

Answer 1

Hi Marcel,
I haven't tried it with XML file but i hope it may help you.
long back i need to send one field with value null if it doesn't come in source file and if it comes then original value.
What i did, i loaded a file which does not have this field, so in MDM Import Manager, under source hierarchy i created a field say ABC and map this field with target field and its value Null with Null, i also save this property in map using configuration options-->Automap fields when loading map = Yes
So whenever a file come with missing field ABC, automatically this field get created and mapped with target field and its value Null with target Null.  on the other hand, If this field actually comes in Source File(Delimited, Excel) ABC then this field with its original value gets map with target field value. That time it worked fine.
Just try and revert with result if it helps..
Else, using PI is the best option to create that missing segment into the XML message.
Regards,
Mandeep Saini