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: Weird issue when calling Prefix external object

Emanuel

Hello everyone.

I need to write a component that calls two different external Java methods (both of thoose will be returning a DOM4J Document).

This is the code of my data section:



  External
    Prefix Object="com.interwoven.livesite.external.impl.LivesiteSiteMap" Method="getSiteMap" Scope="local"/
    Object Scope="local" it.company.external.search.Retriever /Object
    Method>getSearchResults /Method
  /External

i could not get the code tag to work so i stripped all invalid char

The above works perfectly when i try the preview of the single component the iwadmin>main>ls>component section.

However, when i add this component to a .page the same prefix call does not work (no xml is returned and the xslt works on nothing).

Any tips / advices?

Thank you very much.
Emanuel.

Find more posts tagged with

Comments

Binettoid

Are you previewing this in the same Branch as your page? Does your Component containing your Prefix class have access to the data/DCRs in the branch where your page is running?
If you're not seeing errors in servletd_out.log, your Prefix class is simply finding no data.
HTH!

vpatel

When it worked in preview, were you previewing it against the same site as when it fails in your workarea??

Emanuel

Hi Everyone.

Yes i only got one workarea and one site in the current installation (TS 6.7.2 SP 2).

The prefix is working in the component preview but it's failing in the page preview that includes the components.

In other words: the standalone component preview (from the iwadmin/ branch) works, the page preview (from my workarea) fails... the same external definition does works if i declare it as an external instead of a prefix, so the required resources should be 100% available...

: (

AlexC

Do you get anything in the logs when it fails?

Binettoid

Make sure you have submitted all the relevant resources through the PLC.

Emanuel

No log error and everything is both in the workarea and in staging, so since i am using the local preview it should be ok.

On top of that as i said, if i declare the same call as a single external instead of a prefix + other external everything works.

I resolved this few days ago by programmatically (in the single external call) merging the two XML that i needed (the segment sitemap and a few other info), so i managed to achieve the funcionality with a single external call.

Of course this is not pretty due to loss of reusability.

I will try to run a few more tests and see if i can get any followup in case this happens to someone else.

Just an idea, could it be that the signature of the prefix method is different from the external ones and the ootb method "com.interwoven.livesite.external.impl.LivesiteSite.Map.getSitemap" fails?

Thank you for the reply.

Emanuel.

AlexC

The difference in signature is for legacy reasons and works as intended, we have many OOTB components that use prefix and external. In older versions (LS 3.1 and earlier) an external is required or controller/prefix for the component will not execute by itself.

Binettoid

Holy $^% I take it all back! I really thought I knew what I was talking about until yesterday. Now i see Emanuel was talking about something subtly different:

I have a component that is using a generator, 4 prefixes, plus an external and a controller.
It previews ok but requires a bunch of Javascript and CSS to work properly, that is included at the page level. When I add it to my page and preview the page, not all the prefixes execute.
There is nothing helpful in the logs - because the final prefix simply does not execute. I can juggle the order of inclusion around and even swap around externals and prefixes. The final Prefix always fails to execute.

Anyhoooo, I recoded my Java so that I perform 3 former prefix calls in one method. Now I have 2 prefixes, an external and a controller. My second (final in the list of 2) prefix is failing to execute in the page environment.
Maybe it's relevant that the second prefix here is in fact an external that I am simply using like a prefix in this instance. Is this relevant? If so, why?

Please, somebody put me out of my misery.

[HTML]

$PAGE_LINK[worksheet]
$PAGE_LINK[factsheet]
$PAGE_LINK[audiovideo]
$PAGE_LINK[interactive]
$PAGE_LINK[quiz]

UserController
createLesson

Audio/Video
gba1ou4i

Interactive
gba1ou4l

Quiz
gba1ou4p

Worksheet
gba1ou4o

All
*

*
*
*
*

Title
title

Creation Date
creationdate

Ascending
Ascending

Descending
Descending

Top Five
5

Top Ten
10

All
All

LscsMetadataQuery
getDocumentList

[/HTML]

Emanuel

Hello, i find myselft in pain again.

I wrote several "atomic" Java external components that return small dom4j documents, each one of this xml contains several application wide information (such as available product list, user informations etc).

I wrote several externals so that a page only needs to call the externals that provide the information that need to be displayed via xsl -> html.

Being unable to call more than one "xml returning java method" (afaik have to use prefix after you already have one external) in my components is crippling my modular design.

Even now i could only manage to use prefix calls in the component design preview, the same component however, does not execute the prefix when included in a page, this lead to missing data.

The log have no error, it's just like the prefix is simply omissed.

Any help or suggestions?

Emanuel

... My second (final in the list of 2) prefix is failing to execute in the page environment.
Maybe it's relevant that the second prefix here is in fact an external that I am simply using like a prefix in this instance. Is this relevant? If so, why?

This is pretty much the same behaviour i have Smiley Sad

especially the bolded quote, i used an external method as a prefix since the method signature is exactly the same ( at least according to the manuals).


[HTML]
public Document method(RequestContext context) 
{
}
[/HTML]

The (not!) funny part as i already stated is that all of this fails only when the component is included in a page but works in the single component preview.

PS:

Interwoven TeamSite 6.7.2 Service Pack 2

Customers.rptdesign

joe_pat

This is pretty much the same behaviour i have especially the bolded quote, i used an external method as a prefix since the method signature is exactly the same ( at least according to the manuals).
[HTML]
public Document method(RequestContext context) 
{
}
[/HTML]
The (not!) funny part as i already stated is that all of this fails only when the component is included in a page but works in the single component preview.

PS:

Interwoven TeamSite 6.7.2 Service Pack 2

Hello,

we have a component that uses both prefix and external and is works well both in component preview and page preview here the part of content XML

[html]

execute
com.xxxx.livesite.external.xxxx

sites/dice/default.site

com.interwoven.livesite.spring.external.DelegatingExternalProxy
delegate

[/html]

Emanuel

Hi everyone, still TeamSite/LiveSite 6.7.2

I found the bug.

The prefix call that i've added to my component in the iwadmin segment of the content center DOES NOT get imported into the page if i try to update it via the " get latest components".

Get latest components update's into the page everything (datums/external mappings/xsl) but does not bring the prefix statement that, obviously does not get executed when you deploy your page to the production envrionment.

By manually modifiyng the .page i got it to work, too bad this cannot be the final solution due to the overrides that can be done later....

Smiley Sad

tec_iwov

looks like it's a bug and exists in the latest version as well.

please contact support.