Running a JSF application as a managed website?

[marcus]

I notice that the sample WCM site has JSP pages that work fine, is it possible to use other servlet technologies in a managed website? I've tried with a very basic JSF hello world that didn't seem to do anything at all, and was wondering if anyone else had tried with any success.

[britt]

I notice that the sample WCM site has JSP pages that work fine, is it possible to use other servlet technologies in a managed website? I've tried with a very basic JSF hello world that didn't seem to do anything at all, and was wondering if anyone else had tried with any success.

In theory, any servlet based technology (that is well behaved) should virtualize.  In practice we haven't had a chance to try out anything more than straight servlets and JSPs.  Explaining 'well behaved' precisely is outside of my expertise, but in general servlet technologies that reach into the file system directly, eg to read specialized configuration files may fail.  We will be working on getting various web-app technologies, JSF, struts, virtualize in the future.

[marcus]

Just bumping this thread to let others know that I've successfully had a simple Wicket (http://wicket.sourceforge.net/) application running as a virtualised app.

[dipu_cs]

Hi Marcus,

We are trying to use Alfresco as Web CMS to maintain one of our Wicket based web apps.

We are not able to get virtulisation working with the wicket app.

We are using the current release community version (2.1.0) and Wicket 1.3.1

Can you please let me know which version of a Wicket and Alfresco are you using.

Kind Regards
Dipu

[marcus]

I think it was 1.2.4 or 1.2.5. It really was a simple hello world style app, and I haven't tried anything more complex.

[marcus]

With the wicket app, I did have to override how the templates are loaded to get it working in the virtual server (but I don't have the code anymore so can't be more helpful than that). Check out http://cwiki.apache.org/WICKET/control-where-html-files-are-loaded-from.html which goes through how template files are loaded; it needs to be modified to use a path can be looked up in the context of the AVM.