Re: [Hypercontent-users] CASIFY Hypercontent - issue

[Alex V. <al...@bi...>]

On Nov 1, 2006, at 10:20 PM, tom tom wrote:

> Hi Alex,
>
> If I need a staging area, cant I have the same
> Hypercontent server to final publishing rather than
> publishing it some other server. For example if I have
> project called my-project can't we have a staging area
> in the same project it self.

If you want a staging area, you can use HC as the web server, you  
just need to specify a separate filesystem for the build, as  
described here:

http://hypercontent.sourceforge.net/docs/manual/develop/filesystems.html

Note that this page is for 1.4; 2.0 no longer requires a preview  
filesystem at all, build and publish are optional, and you can  
actually mount any number of additional filesystems using a new  
configuration tag "<mount directory="/basedir/">" with a filesystem- 
def beneath it.

If you leave off the "base-url" attribute (which is used to point to  
an external web server), HC will serve the built content at URLs like

http://localhost:8080/hypercontent/project-name/build/index.html

>
> Is there any performance issues(when concurrent users
> goes up) if we select Hypercontent server as the final
> server to serve the content. Should we only consider
> Hypercontent for authers and publishers (limited
> users)

HyperContent should scale well up to a point, but publishing out  
static files to be served by apache will probably scale better.  You  
can also run HC on multiple servers behind a load balancer, and they  
will automatically distribute background processing chores like  
publishing between all the servers, as long as the repositories are  
located on a common mounted filesystem.

>
> Is there any sample demo to see the life cycle with
> some xml and stylesheet approach.

I just uploaded "portlet.zip" at

http://www.ja-sig.org/wiki/pages/viewpageattachments.action?pageId=12494

This contains the outdated contents of the CAS site and presents it  
in 7 different HTML outputs and 2 PDF outputs.  This will give you  
good starting points for building any number of possible displays;  
the XSL for generating the navigation structures is in a common file / 
config/skins/base.xsl which you can re-use in your custom designs.   
One of the forms of output contains portlet styles, so is appropriate  
for integrating into the portal.

>
> I observed some discrepancies while inserting some
> images just see following are bugs or not....
>
> I am using a war file approach rather than using HC
> inbuilt tomcat server. I created a war file called
> hypercontent.war and deployed on our existing tomcat.
>
> I have a very primitive projectdefinition.xml as
> listed below. When I tried to edit the html and insert
> an image using the editor, it does not inser the
> current relative path. it appends only /someimage.jpg
> but it should be idealy
> /hypercontent/my-project/someimage.jpg
> When I changed this file in the text mode it works.

Actually, /someimage.jpg is the appropriate path.  All links and  
images are stored as project-internal references, without including  
servlet or project mount points.  This way the projects are highly  
portable across environments.  The base.xsl file I mentioned above  
also has standard link and image re-writing logic that appends a  
relative base to the paths when they are rendered (e.g. ../../ 
someimage.jpg).  The WYSIWYG also knows how to interpret these  
project-internal paths.

Cheers,
	Alex