inline command not working

vini_mysuru

We are in process of replacing .Net console programs by java utiltities as part of a redesign program.

 

Eariler dropdowns in DCTs were sourcing data from .Net exe.I  have setup a DataSource for a drop down and got it to work with the DCT. This Datasource returns a string which is an XML containing option list values for the drop down. No issues with this.

<description>Select disclosure type</description>
<select>
<inline command="Datasource:executeComponent:FileDataSource:fileName=lpDisclosure"/>
</select>

 

There is another inline commad in the DCT to get XML to construct the metadata tab in the DCT. The .exe program is reading XML content from a file and substituting in DCT.

 

<root-container name="ContentDataRecord" location="ContentDataRecord">
<tab name="Details">
<container combination="and" name="content" location="content">
.
.
.

</container>
</tab>
<inline command="D:\Interwoven\TeamSite\local\bin\TSAdmin_Util_commercial\TSAdmin.exe -dct IncludeDCTModule genericMetadata"/>
</root-container>

 

I read  in the documentation that  <inline> is supported only for dropdowns, checkbox list and radio list. I am confused because I am not able to fugure out how it is working currently to get a whole <tab> element. It will be great if someone can help me find a way to replace this 'exe' using Java.

 

My queries:

1. Does <inline> work for items other than dropdown, radio & checkbox at all? If so, should it return <substitution> element as root?

2. If answer to previous query is 'no', hwo is it working with that exe?

3. If answer to previous query is 'no', what is the best way to reuse metadata <tab> content in a file to load the metadata tab in multiple DCTs

 

Thanks,

Vinay.

 

Adam Stoller

Inlines can actually work almost anywhere within a DCT as long as they result in syntactially correct DCT code because they are part of the pre-processing step of the DCT (but once processed they do not get re-pre-processed, which is why you cannot have an inline returned as part of the inline code - unless you write your own processor to handle it).  The DTD and associated documentation regarding inlines tend to "simplify" the use-cases for where / when inlines can be used.