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; } } }

Livesite dynamic component

Arundevid

Hi,

we are creating dynamic component.in that component we need filter option Appearance xsl we create drop down box.

selected value we need to pass the parameter to my java class and return value based on my selection.

please any give me some sample code.

Please suggest me on this.

Regards

ArunDevid

Find more posts tagged with

Comments

tec_iwov

your component show a drop down box or you need to have a multipul select value as part of your XML?

Arundevid

Thanks for your reply.

We create two java method in same java class.

please refer my content xml file for more information.

Content xml.
......................

com.interwoven.livesite.sampleTask
method2

com.interwoven.livesite.sampleTask
method1

.............................

if click the preview method1 call it will return value from database,using xsl to asign value to dropdown box. upto this its working fine,if we select the dropdown value call our controller class" Test",once invoke this controller it will call another java method "method2".its returning value from database based on our selected value.
Any suggestions?

regards
Arundevid

tec_iwov

you need to escape your xml or attach it as a file.

Arundevid

Hi,

Actual requirement:-
...........................
Javaclass we have two method which is method1 and method2.method one intially call while preview the component its return value using xsl to asign the value to dropdown box.if we select the value from dropdown again reload the page call my controller method which is method2.mehtod2 just returning value based on parameter passing.

First time its loading its calling java class method1 and return value.if select value again reload page its not invoke method2.

AlexC

Component controllers are only called when you submit to the component and you specify which controller to execute using iwPreAction= parameter.

If you call you page with: http://some.server/my.page?componentId=1234567&iwPreAction=Test it will invoke the controller.

Since you need correct component ID, your component should contain a form submit that is not external which will generate a correct action internally. (See the dev guide of submitting form data from components).

If you need to invoke 2 methods in a row you should use a Prefix which executes an external method(s) before the actual external is executed. The output is also added to the Result XML just like external.

dazzlad

Component controllers are only called when you submit to the component and you specify which controller to execute using iwPreAction= parameter.

If you call you page with: http://some.server/my.page?componentId=1234567&iwPreAction=Test it will invoke the controller.

Since you need correct component ID, your component should contain a form submit that is not external which will generate a correct action internally. (See the dev guide of submitting form data from components).

If you need to invoke 2 methods in a row you should use a Prefix which executes an external method(s) before the actual external is executed. The output is also added to the Result XML just like external.

Hi Alex,

Just wondering you should clear up a couple of points?

In the LS dev guide for LiveSite 3.0 the parameter is doucmented as iwPreActions (plural) and you mention iwPreAction - which is correct?

In the same dev guide componentID is capitalised differently - is this relevant? how should it be capitalsed?

I've previously seen you state on this forum that controllers don't execute in preview mode. Can you clarify - does this mean component preview or in the iw-preview webapp as a whole?

I'm having a great deal of trouble getting a controller to execute.

Thanks.

AlexC

Sorry my typo, iwPreActions is the right one.

The capitalization issue is a result of someone changing the constant without realizing that it was used in more than 1 place and this happened between 3.0 and 3.1 release. componentID is the correct one since 3.1.

The component controller did not execute in the past when there was no external present, so fix it you added an external to the component. As of 7.0 I believe this was made so that the controller executes even if there is no explicit external defined.

AlexC

There is a built-in class in livesite-runtime.jar called SampleControllers (com.interwoven.livesite.runtime.controller.example), controller method called helloWorld can be used for testing. If you do not have SampleControllers, check com.interwoven.livesite.external.runtime.Debugging it has controller sample before it was moved out to its own class long ago.

Check a file in your install called impl.zip it has all this java source code for reference.

dazzlad

Hi Alex,

I created a component with the following content XML:

[PHP]<Data>
<Controllers>
<Controller Name="dump">
<Object>com.interwoven.livesite.runtime.controller.impl.DebugController</Object>
<Method>dumpContext</Method>
</Controller>
</Controllers>
<External>
<Object Scope="local">com.interwoven.livesite.external.runtime.Debugging</Object>
<Method>dumpContext</Method>
</External>
</Data>
[/PHP]

If I place it on a page I now expect to be able to hit:

http://myhost/iw-preview/Darren/Ferg.page?iwPreActions=dump&componentID=1279614689205

and see the output from the dumpContext controller.

Am I missing something? It doesn't work.

Thanks.

AlexC

There are 2 requirements for components to re-execute:

componentID to match the component in question
submit=[somevalue] to be present

Add &submit=true
That should force component exection, the submit is part of the generated form and required.

dazzlad

There are 2 requirements for components to re-execute:

componentID to match the component in question
submit=[somevalue] to be present

Add &submit=true
That should force component exection, the submit is part of the generated form and required.

AlexC

None of those URLs are valid... some have iwPreAction instead of iwPreActions and they do not have the page path, just server and query string...

SwitchingCSVFilesForChart.zip

dazzlad

None of those URLs are valid... some have iwPreAction instead of iwPreActions and they do not have the page path, just server and query string...

AlexC

Can you set logging to DEBUG and execute one URL and paste the log, there is probably something subtle.

dazzlad

I've had to attach as two files due to size restrictions.

Thanks for looking at this - very much appreciated.

dazzlad

I can see this in the log:

RuntimeController.execute: Component not found on page

AlexC

Open the .page file and look at all the component IDs present. Where is that componentID coming from? Are you redirecting a submit from one page to another?

dazzlad

Open the .page file and look at all the component IDs present. Where is that componentID coming from? Are you redirecting a submit from one page to another?

Component 1279728179694 is the only component present on the page. I'm not doing any redirecting - just hitting the page directly with the URLs I specified.

The .page file is attached.

AlexC

What does the following URL give you:


http://localhost:1776/index.page?componentID=1279728179694&submit=true&iwPreActions=dump

Is there anything in the logs under DEBUG (can you paste everything that gets logged from the time you submit that URL?

dazzlad

What does the following URL give you:
http://localhost:1776/index.page?componentID=1279728179694&submit=true&iwPreActions=dump
Is there anything in the logs under DEBUG (can you paste everything that gets logged from the time you submit that URL?

I've attached the log resulting from that URL in the attached zip (I can't post it inline or attach it as a text file as the forum complains about sizes.

I still get the same error with that URL:

2010-07-21 20:52:10,859 DEBUG [com.interwoven.livesite.runtime.controller.RuntimeControllerExecutor] RuntimeController.execute: Component not found on page.

But I can't see anything else significant.

dazzlad

Looking at it with JAD the message seems to originate from

[PHP]Component component = context.getPage().getComponent(context);
if(null == component)
{
if(LOGGER.isDebugEnabled())
LOGGER.debug("RuntimeController.execute: Component not found on page.");
return false;
}
[/PHP]
in RuntimeControllerExecutor

I'll dig deeper tomorrow, but it is after 9 here and I must call it a night.
Thanks for your time today Alex.

AlexC

This is odd, based on that message this is probably Livesite 3.0.x since the current code actually lists the component id it was looking for. Essentially when that error occurs the component id was probably not found, I know there was a bug long ago about componentID or ComponentID or componentId or ComponentId and I forget which used to be checked along with the correct one which is componentID. So if you don't mind doing the 4 URL test and try each of the componentID versions above you can determine which was the one that was incorrectly used in 3.0.x and since fixed.

dazzlad

This is odd, based on that message this is probably Livesite 3.0.x since the current code actually lists the component id it was looking for. Essentially when that error occurs the component id was probably not found, I know there was a bug long ago about componentID or ComponentID or componentId or ComponentId and I forget which used to be checked along with the correct one which is componentID. So if you don't mind doing the 4 URL test and try each of the componentID versions above you can determine which was the one that was incorrectly used in 3.0.x and since fixed.

Thanks! problem solved it needs to be "ComponentID". We are running 3.0 BTW.

Really appreciate all of your help.

AlexC

Glad it was resolved, the ComponentID was used in 3.0 and was a bug, it was fixed about 3 years ago when 3.0.2 came out if I remember correctly.