Facing problem in rendering a DCT using inline with a datasource

amitsb

Hi,

 

My requirement is to dynamically generate a DCT using XMLs that will be aggregated in the server using xincludes. I plan to use datasource feature in inline for which I started with a simple code to first render an item but I am unable to figure out why it does not work.

 

Java code:

 

import java.util.Map;
import com.interwoven.datasource.*;

public class DatasourceTest implements SimpleDataSource{

	public String execute(String sessionId, String context, Map param){
	return("<substitution><item name='testItem' pathid='@testPath'><label>From Datasource</label><textarea /></item></substitution>");	
	}

}

 

 

Entry in DataSourceConfig.xml -

 

<datasource>
  <name>TestDS</name>
  <classname>DatasourceTest</classname>
  <param name="servername">SDW486</param>
</datasource>

 

Entry in DCT-

 

 

 <tab name="Additional attributes">

      <item name="Users" pathid="@Users"&gt;
        <label>Author</label>
        <description>Select a user who is a TeamSite author</description>
        <textarea required="t"/>
      </item>

      <inline command="Datasource:executeComponent:TestDS:Role=author"/>


        <item name="crm_ref" pathid="crm_ref" required="f">
          <label>CRM lead ID</label>
          <text/>
        </item>
.
.
.
.
.

 

Error in logs -

 

com.interwoven.ui.datacapture.external.InvalidDCTException: com.interwoven.ui.datacapture.external.InvalidDCTException: Invalid Element: option cannot appear at this level.

 

Appreciate if anybody can throw some light on what possible could be the issue.

 

 

Adam Stoller

Caveat: I have done extremely little with DataSources; I have never tried to create one for an inline process to construct part of a DCT.

 

With that in mind - have you tried changing your code from:

  public String execute(...) {
return("...");
  }

 

to:

  public String execute(...) {
System.out.println("...");
  }

 

I'm just thinking that a Perl inline script sends the text to STDOUT, so presumably a Java DataSource inline script should do the same, and the fact that it isn't currently doing that might lead the system to thinking you're trying to include something that doesn't belong there.

 

Also - you might consider adding some diagnostic logging to your code before / after the println() function so that you can verify whether your code is actually running...