Handling Differences Between XML and JSP Tags in WebCenter Sites

Sep 12, 2013 11:02:08 AM

By: Darek Blankenbuhler - Application Consultant

sites boxIn WebCenter Sites there is a common issue of using JSP tags that function differently than their XML counterparts, even though the tags share documentation.  This can become a major issue when a developer is required to use JSP, for example when using a custom Java class in the element code.

To counter this issue there is a function in the ics class called RunTag.  This function will run any tag as an XML tag and create all the necessary objects inside the JSP.  The tag is very simple to use.  First the developer needs to identify all of the XML attributes the tag will need.  Keep in mind that some of these attributes will have different names.  Then the developer needs to create an instance of FTValList (found at COM.FutureTense.Interfaces.FTValList).  The FTValList will allow the developer to create a name/value map.  In this case, the developer will want to create the map using the pattern attribute name/attribute value.  Once the FTValList has been created, the developer can run the RunTag function.

Here is an example for running the RunTag function on the proprety:get tag.

FTValList attrs = new FTTValList();




String tagReturns = ics.RunTag(“PROPERTY.GET”, attrs);

The example code is retrieving the property xcelerate.batchpass.  I chose this specific example because this is one of the places where JSP and XML differ.  The JSP version of the PROPERTY.GET tag will not unhash the password, whereas the XML version will.

You may notice that the tag returns a string.  This string will contain any output the tag itself might generate.  Most tags in the system do not generate any output, so most of the time this string will be null.  However, if the tag does output anything, that data will be available in the string.

All in all, it is important to remember to check the Java API section of the tag reference.  WebCenter Sites tags have a great deal of functionality, the RunTag method is just one example.  There are plenty of other methods in the Java API (more specifically the COM.FutureTense.Interfaces package included on each JSP) that will allow for even more control and functionality within any template that is written.

If you are ready to get started with WebCenter Sites, or perhaps need some help on your current project. Feel free to Contact us!

Subscribe by Email

No Comments Yet

Let us know what you think