Hello Warrell and Ross,

(ps I am done writing this mail, but before performing all the steps you
might want to read the end of the mail. While writing this mail, I
started to realize how much you are required to do manually if you want
to add it to the binary version. Perhaps we at Hippo should be able to
release a binary version with the hcamanager included...WDOT? )

I'll try to summarize all needed steps (though I did not run it
myself...hopefully I have all. Also note that IMHO building the cms
yourself is much easier, certainly because quite some properties need to
be set)

First of all the folder structure should look like:

hippo-cms-v6.05.01
|-- ...
|-- cocoon
|-- sites
|   |-- hippo-cms
|   `-- hippo-cms-hcamanager            
|-- ...
`-- ...

Now, you also need to do :

1) hippo-cms-v6.05.01/cocoon/WEB-INF/classes a file
persistence.properties. See [1] for this file, only without the values
filled in (this is normally done during a maven build from the
project.properties). You will need to fill in every property between '@'
and '@'

2) you need to add to hippo-cms-v6.05.01/cocoon/WEB-INF/spring the file
at [2] (properties do not need to be filled in, so exact copy is fine)

3) In hippo-cms-v6.05.01/cocoon/WEB-INF/cocoon.xconf you need to add at
the level '/cocoon/source-factories' an extra source-factory:

<component-instance
class="nl.hippo.cocoon.source.impl.ExtensionsSourceFactory"
name="hcamanager">
 
<cms-extensionspath>../hippo-cms-hcamanager/</cms-extensionspath>
</component-instance>

also at /cocoon/[EMAIL PROTECTED]'globalconstants'] add (or if
already present fill in correct value) :

<cms-hcamanagerpath>../hippo-cms-hcamanager/</cms-hcamanagerpath>

4) In hippo-cms-v6.05.01/cocoon/WEB-INF/lib : remove some jars according
maven.xml [3] from hcamanager:
        <ant:include name="geronimo-spec-activation-*.jar"/>
      <ant:include name="geronimo-spec-javamail-*.jar"/>
      <ant:include name="spring-mock-1.1.4.jar"/>
      <ant:include name="spring-1.1.4.jar"/>
      <ant:include name="jdo-1.0.1.jar"/>

and add some new ones: 
        hippo-community-app-2.01.01.jar 
        activation-1.1
        javamail-1.3.3.jar
        quartz-1.5.2.jar
        jpox-1.1.7.jar
        jpox-dbcp-1.1.7.jar
        jpox-springframework-1.1.3.jar
        jdo2-api-2.0.jar
        jta-1.0.1.jar
        spring-2.0.jar
        spring-dao-2.0.jar
        spring-jdo-2.0.jar
        spring-mock-2.0.jar

and probably some others as well, but you can find this back in the
project.xml [4] of the hcamanager:
                
5) Now, you should be able to add the parts to components.xml like 

<view
src="hcamanager://perspectives/dashboard/views/mailing-profiles/componen
t.xml"/>
<view
src="hcamanager://perspectives/dashboard/views/mailgroups/component.xml"
/> <!-- added in version 2.01.00 -->
<view
src="hcamanager://perspectives/dashboard/views/newslettertypes/component
.xml"/>
<view
src="hcamanager://perspectives/dashboard/views/mailings/component.xml"/>
<view
src="hcamanager://perspectives/dashboard/views/poll/component.xml"/>
<!-- added in version 2.01.00 -->


But, to be honest, I really doubt wether I have been able to write down
every needed step, and building the hcamanager with cms from source is
really much easier then following these steps (because I doubt we get it
working easily, and....you would need to do it again for every deploy,
while creating a cms extension, and add the hcamanager and hippo-cms as
svn:external, you can reuse it every time, and when from the cms or
hcamanager a new release is done, you only need to update the
svn:external and run 'maven clean cocoon:deploy' or 'maven clean
cocoon:install' ). It is really not hard, see [5]. 

Hopefully I helped you out,

Regards Ard

[1]
http://svn.hippocms.org/repos/hippo/hippo-components/hippo-community-app
s/tags/Release-HCA-v2_01_01/cms-hcamanager/persistence/persistence.prope
rties

[2]
http://svn.hippocms.org/repos/hippo/hippo-components/hippo-community-app
s/tags/Release-HCA-v2_01_01/cms-hcamanager/persistence/persistenceApplic
ationContext.xml

[3]
http://svn.hippocms.org/repos/hippo/hippo-components/hippo-community-app
s/tags/Release-HCA-v2_01_01/cms-hcamanager/maven.xml

[4]
http://svn.hippocms.org/repos/hippo/hippo-components/hippo-community-app
s/tags/Release-HCA-v2_01_01/cms-hcamanager/project.xml

[5] http://www.hippocms.org/display/CMSSNDBX/08.+Extending+Hippo+CMS

> Thanks Ard,
> 
> Yep, you have summed up the situation very well. I have tried 
> putting in the dashboard redirects (for want of a better 
> phrase) but I get the same errors as when I first modified 
> the dashboard component.xml
> 
> I will give it another go now I know where hcamanager 'lives'
> 
> Cheers
> 
> On 28/01/2008, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
> >
> >
> > Hello Warrell and Ross,
> >
> > I think hcamanager folder would not end beneath the 
> hippo-cms folder, 
> > but next to it. I am not sure if you have experience with the 
> > 'extensions' folder to customize your cms, but the hcamanager works 
> > like the cms would in an extended cms (with svn external). 
> Normally, 
> > you would create your own cms project, and add the cms and 
> hcamanager 
> > as svn externals.
> >
> > But clearly, you want to use the binary dist of the cms. 
> Afterwards, I 
> > suppose you want to add parts like
> >
> > <view
> > 
> src="hcamanager://perspectives/dashboard/views/mailing-profiles/compon
> > en
> > t.xml"/>
> > <view
> > 
> src="hcamanager://perspectives/dashboard/views/mailgroups/comp
> onent.xml"
> > /> <!-- added in version 2.01.00 -->
> > <view
> > 
> src="hcamanager://perspectives/dashboard/views/newslettertypes/compone
> > nt
> > .xml"/>
> > <view
> > 
> src="hcamanager://perspectives/dashboard/views/mailings/component.xml"
> > />
> > <view
> > src="hcamanager://perspectives/dashboard/views/poll/component.xml"/>
> > <!-- added in version 2.01.00 -->
> >
> > see [1]
> >
> > >From the top of my head, I do not know the exact steps how 
> to achieve
> > this, but I'll try to find the steps to perform and let you 
> know the 
> > result (or if somebody has performed this operation before, 
> feel free 
> > to post the answer :-) )
> >
> > Regards Ard
> >
> > [1]
> > 
> http://www.hippocms.org/display/CMS/Community+apps+CMS+configuration+%
> > 28
> > general%29
> >
> > > Hi,
> > >
> > > I am trying to add Hippo Community Apps to a binary install.
> > > I asume that hcamanager cocoon webapp sits in the directory tree 
> > > beneath hippo-cms :-
> > >
> > > /hippo/hippo-cms-v6.05.01/sites/hippo-cms/hcamanager
> > >
> > > Unfortunately, the component.xml isn't found. I have a working 
> > > knowledge of how to modify the dashboard configuration 
> gained from 
> > > removing the permissions menu item for some users. The confidence 
> > > gained from that exercise has led me to try and 'bolt-on'  HCA. I 
> > > have built the maven projects for the java components and 
> am using a 
> > > MySql repository already so I was hoping it would be 
> possible (and 
> > > very educational) to add HCA to a running binary install.
> > >
> > > I have modified the component.xml to add in the view but 
> my install 
> > > can't resolve :-
> > >
> > > classSource="/hcamanager/js/mailingprofiles.js" although 
> I have put 
> > > the directory there. Do I need to modify one of the sitemaps. Any 
> > > help gratefully accepted.
> > >
> > > Regards
> > >
> > > Warrell
> > > ********************************************
> > > Hippocms-dev: Hippo CMS development public mailinglist
> > >
> > ********************************************
> > Hippocms-dev: Hippo CMS development public mailinglist
> >
> ********************************************
> Hippocms-dev: Hippo CMS development public mailinglist
> 
********************************************
Hippocms-dev: Hippo CMS development public mailinglist

Reply via email to