topic Re: PageLookup fails in Alfresco Archive

PageLookup fails

sam1980 — Wed, 19 Oct 2011 12:16:19 GMT

I've encountered a problem when deploying my wqs-based webapp to WebLogic 10.3.5. All of a sudden the page lookup mechanism fails. The only other reference I found to this problem is in this spanish forum post: https://forums.alfresco.com/es/viewtopic.php?f=11&t=3634 which also encounted the pro

Re: PageLookup fails

bremmington — Wed, 19 Oct 2011 13:53:30 GMT

Are you deploying your app as a WAR file?

Re: PageLookup fails

sam1980 — Wed, 19 Oct 2011 14:09:04 GMT

Yes, as a WAR

Re: PageLookup fails

bremmington — Wed, 19 Oct 2011 14:14:38 GMT

Hmm. OK. I've seen some similar kinds of issues when deploying as an exploded WAR in JBoss, but not as a WAR.

I'm not sure why that may be happening in WebLogic - it's been a while since I've used WebLogic. I'll ask around here to see if anyone has any ideas. I know that Share works in WebLogic, so it must be achievable.

Re: PageLookup fails

ddraper — Thu, 20 Oct 2011 10:36:05 GMT

If the exactly the same application works on other app servers, and the pages should ultimately be loaded from ClassPathStores (which they almost certainly are) then it's almost certainly a classpath configuration problem with WebLogic. Unfortunately I don't know anything about configuring WebLogic nor very much about WQS (although I know about Spring Surf) but I'm guessing you might need to explicitly configure the Classpath access for the application (?)

You shouldn't need to re-configure the Spring application context that defines the Surf object stores that are used to look up the pages if they are working on other app servers. It doesn't look like the default WQS application overrides any of the Spring Surf defaults. The object stores/persister configuration is quite complex and scattered across several Spring application context configuration files in the Spring Surf and Spring WebScripts JAR files… they in the "org.springframework.extensions.webscripts." and "org.springframework.extensions.surf." packages. There is also an "autowire" service which updates some of the persistence/object store configuration… however, as I said - if it's working on other app servers you really shouldn't need to touch any of that. However, it might be useful as reference for working out how configure your applications Classpath in WebLogic.

Hope this helps, apologies if it's a bit vague but the best I can do without deep WebLogic or WQS knowledge,

Regards,
Dave

Re: PageLookup fails

sam1980 — Fri, 21 Oct 2011 10:37:24 GMT

Thanks for your feedback.

It sure was a classpath problem. The workaround involved reorganising the web app folder strukture in order for surf to pick up the correct places to look for pages, templates and webscripts.

Old:

WEB-INF
—- pages
—- templates
—- webscripts

New:

WEB-INF
—- classes
——– surf
———— site
—————– templates\*.xml
—————– pages
———— templates\*.flt
———— webscripts

Not the most elegant solution, but feasible workaround. We'll just make our own weblogic profile in our maven build that takes care of the reorganizing parts.

For future reference this might be related: http://forum.springsource.org/showthread.php?86713-Surf-autowire-runtime .