Re: [Hypercontent-users] Further doubts and clarifications needed

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

On Feb 20, 2007, at 9:23 PM, tom tom wrote:

> Hi,
>
> I got hypercontent working with apache2.2 with tomcat
> with the use of mod_jk, Hence am moving slowly towards
> the production setup.
>
> I got following doubts/questions which am not very
> clear.
>
>
> 1) What is the difference between build and publish as
> far as the HC life cycle is concerned. How build/build
> -all differ from publish

Build and publish represent a two-step publishing process: the first  
step renders the static output on a staging filesystem that can be  
used to review the content before it is copied to the publishing  
filesystem.  As it turns out, most people are perfectly happy with a  
one-step publishing workflow that renders the static output directly  
to the public web space.  To use this simpler approach, adjust the  
events in /config/workflow/publish.xml to something like this

	<event name="publish" permissions="publish">
		<variable name="publisher" value="${actor}"/>	
		<render path="${path}" destination="/publish/" force="false"  
delete="true"/>
		<nq who="${publisher}"/>
		<nq q="publishing"/>
	</event>
	
	<event name="publish-all" permissions="publish">
		<variable name="publisher" value="${actor}"/>	
		<render path="/" destination="/publish/" force="false" delete="true"/>
		<nq who="${publisher}"/>
		<nq q="publishing"/>
	</event>

Then you can remove /config/workflow/build.xml and any build  
filesystem.  "/publish/" refers to your publish filesystem in  / 
config/project-definition.xml

>
>
> 2) As I am running HC and apache in one machine(with
> mod_jk) should I use build and publish at all? Isnt
> author->preview->approve enough?
>
> Initialy I thought I dont want to use but later
> realize that if I dont use build and publish content
> will be served by tomcat (even with mod_jk). Due to
> shis reason
> I introduced the build-url and build and publish the
> content to apache docs folder so that static content
> will be served directly by apache. Please let me know
> we are on the correct track? If the build and publish
> not required align with our configuration pls do let
> us know?

I suggest

author->preview->approve->publish

if you drop the build step as outlined above

>
>
>
> 3) in the Approvals.xml it refers to the ${actor}
> variable and assign it to a variable called author
>
> Specially when sending reminders it sends the message
> with the uid not with the fullname.
> How to get the username/full name (assuming he/she has
> updated his/her profile) within the approvals.xml and
> send the mail accordinlgy instead of the uid(this is a
> numeric in our case) What is the variable that I
> should refer within the approvals.xml to get the users
> name.

This isn't supported at the moment, but you could implement it around  
line 57 of org.hypercontent.workflow.command.AbstractCommand  
following the pattern there to associate a variable name with the  
results of a VCard lookup, something like

else if(Strings.equals(name,"user-full-name")){
                         try {
                             var.set(0,event.getUser().getFullName()));
                         }
                         catch(IOException e) {
                             Logger.error(e);
                         }
                     }

Let me know if that works for you, and I can check it into CVS!


>
>
> 4) As far as the UI screens are concerned I need to
> change the name of the texts in some of the UIs
> specially workflow.
>
> I have seen references as follows
> $bundle.get("XXXXXXXXX")
> I just want to know where these screen text constants
> are kept, from which property file it get loaded to
> $bundle

The localization files are stored in the /l10n directory of the  
bootstrap repository.

Cheers,
	Alex