nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

WebTask.do in LiveSite workflow

Parag

Hi all,

We want to create a workflow based on LiveSite Content Publishing workflow, I gone thru the Publish LiveSite Content.ipm file. For the deployment task it has a property as CGIScriptName and value as "/iw-cc/Workflow/WebTask.do".

All the similar tasks are handled by same servlet only the parameters differs.

Can anyone please tell me where this servlet(WebTask.do) is placed? as well if we want to create user defined classes then where should be it placed?

Thanks,
-Parag
TS 6.7.1 LS 3.0
Unix
Reply With Quote

Find more posts tagged with

Comments

RajatChopra

Hi,
Can someone shed some more light on this? I want to create a similar workflow using my own custom code.

Any idea where the entry for this mapping is?

Thanks,
Rajat

Faizi

Hi,
Can someone shed some more light on this? I want to create a similar workflow using my own custom code.

Any idea where the entry for this mapping is?

Thanks,
Rajat

Hi Rajat,

As you know TS is a J2EE application and architecture based on Struts. So if you have any idea about these technologies you understand better.

As the question is regarding Publish LiveSite Content Workflow, you can find complete information regarding beans and classes used for different task in this file:
\\iw-home\httpd\webapps\content_center\WEB-INF\conf\livesite\resources\workflow-resource-config.xml

If you want to create you custom code then change all the customization from \\iw-home\local\config\lib\content_center\livesite_customer_src folder. For more information on customization go through Customiztion Guide.

Hope this helps.
Thanks,

Migrateduser

Looks like no one has any clue about this.

vpatel

<action path="/Workflow/WebTask" type="org.springframework.web.struts.DelegatingActionProxy" scope="request"/>

Usually when you use this OOTB "WebTask.do", you also pass a parameter "TaskBeanId" with a value that points to whatever Java class you have written (i.e. com.custom.workflow.MyClass).

Basically this is strut framework. Any incoming requests are passed onto the Java class (DelegatingActionProxy) along with any parameters (i.e. your BeanId) -- utlimately your bean gets executed.

HTH!