You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Enrico Ballarin Dolfin <eb...@innopark.ch> on 2004/07/28 11:07:08 UTC
Problem deploying a publication
Hi
Before using Lenya I have used cocoon for other web applications under tomcat
and generated a cocoon WAR file in the /root/build/cocoon/ directory. To
deploy cocoon I have put the WAR file in /usr/share/tomcat/webapps/ where
tomcat extracted it automatically.
Following the instructions of NewPublicationHowTo (version 2004-07-16) and
DeployPublicationHowTo I have set up following directories:
/root/build/cocoon/ # my original cocoon build
/root/build/cocoon-2.1.5.1/ # cocoon for lenya
/root/build/incubating-lenya-1.2-src/ # lenya
/root/build/publications/innopark/ # my test publication
After deploying my test publication 'innopark' I can find it in the
directory /usr/share/tomcat/webapps/lenya/lenya/pubs/innopark.
Changes to the publication are always stored in this directory and not
in /root/build/publications/innopark/, this means that if I try to deploy the
publication again as described in NewPublicationHowTo, I'm deployng again the
original and not the modified publication.
This is probably due to my settings in build.properties, but because I'm using
tomcat, I need to let know to tomcat where to find the lenya webapp.
In /usr/share/tomcat/webapps/cocoon/ I have my previous cocoon web
applications and in /usr/share/tomcat/webapps/lenya/ I'm deploying Lenya.
After deploying I have also changed the user and group for all the files
inside /usr/share/tomcat/webapps/lenya/ (recursively) from root:root to
tomcat:tomcat as I did for cocoon webapps.
- What did I wrong?
Here a few settings that I'm using from the file build.properties:
===========================================
# The root of the Cocoon source tree
cocoon.src.dir=../cocoon-2.1.5.1
#------------------------------------------------------------------------------------
# The original, unmodified and expanded cocoon webapp directory
cocoon.webapp.dir=${cocoon.src.dir}/build/webapp
#------------------------------------------------------------------------------------
# Root directories where publications are located
pubs.root.dirs=src/webapp/lenya/pubs:../publications
#pubs.root.dirs=src/webapp/lenya/pubs:../anotherproject/pubs:/home/user/my-pub
#------------------------------------------------------------------------------------
# Where the 'install' build target should put the webapp context
# WARNING: This has to be an absolute path! (FIXME: cocoon.xconf needs
absolute path (scr/targets/init-build.xml))
# NOTE: Do not use white spaces within the path
tomcat.home.dir=/usr/share/tomcat
#tomcat.home.dir=C:/build/tomcat
#------------------------------------------------------------------------------------
# Where the 'install' build target should put the webapp context
# NOTE: This path is not necessarily relative to tomcat.home.dir
tomcat.webapps.dir=${tomcat.home.dir}/webapps/lenya
#------------------------------------------------------------------------------------
# The server cache directory to be cleaned by the 'reset' target
# NOTE: This path is not necessarily relative to tomcat.home.dir
tomcat.cache.dir=${tomcat.home.dir}/work/Catalina/localhost/lenya
#------------------------------------------------------------------------------------
# Where the 'install' build target should copy the endorsed libraries
# NOTE: This path is not necessarily relative to tomcat.home.dir
tomcat.endorsed.dir=${tomcat.home.dir}/common/endorsed
===========================================
Thanks in advance
Enrico
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Andreas Hartmann <an...@apache.org>.
Enrico Ballarin Dolfin wrote:
> Thanks Andreas! Now it's clear!
>
> If you create or modify a publication (integration), then you need to make the
> changes in the source version (e.g. in /src/publications/innopark) and then
> to deploy the modified publication.
>
> If you use the CMS, the changes will be done by Lenya in the installed version
> (e.g. in /src/share/tomcat/webapps/lenya/lenya/pubs/innopark).
Yes.
> I was missing this information between the general Lenya overview and the
> detailed component documentation.
It is probably a little bit unusual, because you deal with
a CMF rather than a CMS. I'm about to make a picture to
illustrate these processes.
-- Andreas
>
> Enrico
>
> Am Mittwoch, 28. Juli 2004 18:12 schrieb Andreas Hartmann:
>
>>Enrico Ballarin Dolfin wrote:
>>
>>[...]
>>
>>
>>>>>2) Modify the publication in the tomcat webapps directory.
>>>>
>>>>You should modify *only* the source of the publication,
>>>>*not* the installed version.
>>>
>>>- Do you mean with "source" /src/publications/innopark/content/authoring/
>>>?
>>
>>No. I mean /src/publications/innopark
>>
>>
>>>- Do you mean with "installed
>>>version"
>>>/src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/ or
>>>/src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/live/ ?
>>
>>I mean /build/jakarta-tomcat-4.1.29/webapps/lenya/lenya/pubs/innopark
>>(or in your case /src/share/tomcat/webapps/lenya/lenya/pubs/innopark)
>>
>>
>>>If I modify something (e.g. with kupu) in the "innopark" publication, it
>>>will be changed in
>>>/src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/
>>>and not in /src/publications/innopark/content/authoring/
>>
>>Yes. But that does not mean modifying your publication, but
>>it means modifying content.
>>
>>These are two different things:
>>
>>1) Integration = Building a CMS (a set of publications)
>> using the Lenya CM framework
>>
>> - edit files in IDE
>> - done by integrators (developers)
>> - requires deployment
>>
>> Examples:
>> - changing sitemaps
>> - changing XSLTs
>> - changing configuration options
>> - ...
>>
>>2) Using the CMS
>>
>> - browser GUI
>> - done by administors and content authors
>> - does not require deployment
>>
>> Examples:
>> - adding users, groups, IP ranges
>> - setting policies
>> - add + manage content
>> - ...
>>
>>-- Andreas
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Enrico Ballarin Dolfin <eb...@innopark.ch>.
Thanks Andreas! Now it's clear!
If you create or modify a publication (integration), then you need to make the
changes in the source version (e.g. in /src/publications/innopark) and then
to deploy the modified publication.
If you use the CMS, the changes will be done by Lenya in the installed version
(e.g. in /src/share/tomcat/webapps/lenya/lenya/pubs/innopark).
I was missing this information between the general Lenya overview and the
detailed component documentation.
Enrico
Am Mittwoch, 28. Juli 2004 18:12 schrieb Andreas Hartmann:
> Enrico Ballarin Dolfin wrote:
>
> [...]
>
> >>>2) Modify the publication in the tomcat webapps directory.
> >>
> >>You should modify *only* the source of the publication,
> >>*not* the installed version.
> >
> > - Do you mean with "source" /src/publications/innopark/content/authoring/
> > ?
>
> No. I mean /src/publications/innopark
>
> > - Do you mean with "installed
> > version"
> > /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/ or
> > /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/live/ ?
>
> I mean /build/jakarta-tomcat-4.1.29/webapps/lenya/lenya/pubs/innopark
> (or in your case /src/share/tomcat/webapps/lenya/lenya/pubs/innopark)
>
> > If I modify something (e.g. with kupu) in the "innopark" publication, it
> > will be changed in
> > /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/
> > and not in /src/publications/innopark/content/authoring/
>
> Yes. But that does not mean modifying your publication, but
> it means modifying content.
>
> These are two different things:
>
> 1) Integration = Building a CMS (a set of publications)
> using the Lenya CM framework
>
> - edit files in IDE
> - done by integrators (developers)
> - requires deployment
>
> Examples:
> - changing sitemaps
> - changing XSLTs
> - changing configuration options
> - ...
>
> 2) Using the CMS
>
> - browser GUI
> - done by administors and content authors
> - does not require deployment
>
> Examples:
> - adding users, groups, IP ranges
> - setting policies
> - add + manage content
> - ...
>
> -- Andreas
>
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann wrote:
[..]
> 1) Integration = Building a CMS (a set of publications)
> using the Lenya CM framework
>
> - edit files in IDE
> - done by integrators (developers)
> - requires deployment
>
> Examples:
> - changing sitemaps
> - changing XSLTs
> - changing configuration options
> - ...
>
> 2) Using the CMS
>
> - browser GUI
> - done by administors and content authors
> - does not require deployment
>
> Examples:
> - adding users, groups, IP ranges
> - setting policies
> - add + manage content
> - ...
FYI: I made a little diagram to illustrate this:
http://wiki.apache.org/cocoon-lenya-data/attachments/NewPublicationHowTo/attachments/lenya-setup.pdf
(sorry, 1/2 MB - forgot to optimize :( )
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Andreas Hartmann <an...@apache.org>.
Enrico Ballarin Dolfin wrote:
[...]
>>>2) Modify the publication in the tomcat webapps directory.
>>
>>You should modify *only* the source of the publication,
>>*not* the installed version.
>>
>
> - Do you mean with "source" /src/publications/innopark/content/authoring/ ?
No. I mean /src/publications/innopark
> - Do you mean with "installed
> version" /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/
> or
> /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/live/ ?
I mean /build/jakarta-tomcat-4.1.29/webapps/lenya/lenya/pubs/innopark
(or in your case /src/share/tomcat/webapps/lenya/lenya/pubs/innopark)
> If I modify something (e.g. with kupu) in the "innopark" publication, it will
> be changed in
> /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/ and not
> in /src/publications/innopark/content/authoring/
Yes. But that does not mean modifying your publication, but
it means modifying content.
These are two different things:
1) Integration = Building a CMS (a set of publications)
using the Lenya CM framework
- edit files in IDE
- done by integrators (developers)
- requires deployment
Examples:
- changing sitemaps
- changing XSLTs
- changing configuration options
- ...
2) Using the CMS
- browser GUI
- done by administors and content authors
- does not require deployment
Examples:
- adding users, groups, IP ranges
- setting policies
- add + manage content
- ...
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Enrico Ballarin Dolfin <eb...@innopark.ch>.
Am Mittwoch, 28. Juli 2004 14:00 schrieb Andreas Hartmann:
> Enrico Ballarin Dolfin wrote:
> > Am Mittwoch, 28. Juli 2004 11:24 schrieb Andreas Hartmann:
> >>>Changes to the publication are always stored in this directory and not
> >>>in /root/build/publications/innopark/, this means that if I try to
> >>> deploy the publication again as described in NewPublicationHowTo, I'm
> >>> deployng again the original and not the modified publication.
> >>
> >>Yes, this is a known issue.
> >>You can avoid overwriting certain files using the
> >>target.install.excludes parameter in build.properties.
> >
> > For cocoon webapps was clear how to proceed:
> > 1) build a WAR file from the distribution sources in the "build"
> > directory and copy the WAR file to the tomcat webapps directory.
> >
> > 2) After that there was no more need of the "build" directory to develop
> > a webapp.
> >
> > In Lenya it's not so clear for me:
> > 1) Copy the default publication to your target publication in the "build"
> > directory and deploy it.
>
> Do you mean the source directory?
>
Yes
> Actually it is recommended to use the following structure
> (to make sure we're talking about the same things)
>
> /src/cocoon-lenya
> /src/publications/innopark
> /src/cocoon-2.1.5.1
> /build/jakarta-tomcat-4.1.29
>
I'll change my directory structure as you suggested.
> > 2) Modify the publication in the tomcat webapps directory.
>
> You should modify *only* the source of the publication,
> *not* the installed version.
>
- Do you mean with "source" /src/publications/innopark/content/authoring/ ?
- Do you mean with "installed
version" /src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/
or
/src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/live/ ?
If I modify something (e.g. with kupu) in the "innopark" publication, it will
be changed in
/src/share/tomcat/webapps/lenya/lenya/pubs/innopark/content/authoring/ and not
in /src/publications/innopark/content/authoring/
> > 3) Deploy again lenya???
>
> Yes.
>
> > - When do I need to deploy lenya again?
> >
> > Only when I add a new publication?
>
> No, not only.
>
> > Every time that I modify a publication?
>
> Yes.
>
Enrico
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Andreas Hartmann <an...@apache.org>.
Enrico Ballarin Dolfin wrote:
> Am Mittwoch, 28. Juli 2004 11:24 schrieb Andreas Hartmann:
>
>>>Changes to the publication are always stored in this directory and not
>>>in /root/build/publications/innopark/, this means that if I try to deploy
>>>the publication again as described in NewPublicationHowTo, I'm deployng
>>>again the original and not the modified publication.
>>
>>Yes, this is a known issue.
>>You can avoid overwriting certain files using the
>>target.install.excludes parameter in build.properties.
>>
>
>
> For cocoon webapps was clear how to proceed:
> 1) build a WAR file from the distribution sources in the "build" directory
> and copy the WAR file to the tomcat webapps directory.
> 2) After that there was no more need of the "build" directory to develop a
> webapp.
>
> In Lenya it's not so clear for me:
> 1) Copy the default publication to your target publication in the "build"
> directory and deploy it.
Do you mean the source directory?
Actually it is recommended to use the following structure
(to make sure we're talking about the same things)
/src/cocoon-lenya
/src/publications/innopark
/src/cocoon-2.1.5.1
/build/jakarta-tomcat-4.1.29
> 2) Modify the publication in the tomcat webapps directory.
You should modify *only* the source of the publication,
*not* the installed version.
> 3) Deploy again lenya???
Yes.
> - When do I need to deploy lenya again?
> Only when I add a new publication?
No, not only.
> Every time that I modify a publication?
Yes.
> - It seems that you need always the "build" directory of lenya for later
> working. Is this true?
You need the source directory of Lenya.
> - Cocoon is "self contained" in the sense that if you delete the "build"
> directory, your webapp continues to work and everything you need is included
> in the tomcat webapps directory "/usr/share/tomcat/webapps/cocoon".
> Can you say the same for lenya?
Yes. When your publication is finished (doesn't need further
modifications), the Lenya webapp is sufficient.
But as long as you want to modify your publication, you need
the Lenya sources.
> Is everything what you need included in
> "/usr/share/tomcat/webapps/lenya"?
As soon as your publication is finished, yes.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Enrico Ballarin Dolfin <eb...@innopark.ch>.
Am Mittwoch, 28. Juli 2004 11:24 schrieb Andreas Hartmann:
> >
> > Changes to the publication are always stored in this directory and not
> > in /root/build/publications/innopark/, this means that if I try to deploy
> > the publication again as described in NewPublicationHowTo, I'm deployng
> > again the original and not the modified publication.
>
> Yes, this is a known issue.
> You can avoid overwriting certain files using the
> target.install.excludes parameter in build.properties.
>
For cocoon webapps was clear how to proceed:
1) build a WAR file from the distribution sources in the "build" directory and
copy the WAR file to the tomcat webapps directory.
2) After that there was no more need of the "build" directory to develop a
webapp.
In Lenya it's not so clear for me:
1) Copy the default publication to your target publication in the "build"
directory and deploy it.
2) Modify the publication in the tomcat webapps directory.
3) Deploy again lenya???
- When do I need to deploy lenya again? Only when I add a new publication?
Every time that I modify a publication?
- It seems that you need always the "build" directory of lenya for later
working. Is this true?
- Cocoon is "self contained" in the sense that if you delete the "build"
directory, your webapp continues to work and everything you need is included
in the tomcat webapps directory "/usr/share/tomcat/webapps/cocoon".
Can you say the same for lenya? Is everything what you need included in
"/usr/share/tomcat/webapps/lenya"?
Thanks
Enrico
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org
Re: Problem deploying a publication
Posted by Andreas Hartmann <an...@apache.org>.
Enrico Ballarin Dolfin wrote:
> Hi
>
> Before using Lenya I have used cocoon for other web applications under tomcat
> and generated a cocoon WAR file in the /root/build/cocoon/ directory. To
> deploy cocoon I have put the WAR file in /usr/share/tomcat/webapps/ where
> tomcat extracted it automatically.
>
> Following the instructions of NewPublicationHowTo (version 2004-07-16) and
> DeployPublicationHowTo I have set up following directories:
>
> /root/build/cocoon/ # my original cocoon build
> /root/build/cocoon-2.1.5.1/ # cocoon for lenya
> /root/build/incubating-lenya-1.2-src/ # lenya
> /root/build/publications/innopark/ # my test publication
>
> After deploying my test publication 'innopark' I can find it in the
> directory /usr/share/tomcat/webapps/lenya/lenya/pubs/innopark.
>
> Changes to the publication are always stored in this directory and not
> in /root/build/publications/innopark/, this means that if I try to deploy the
> publication again as described in NewPublicationHowTo, I'm deployng again the
> original and not the modified publication.
Yes, this is a known issue.
You can avoid overwriting certain files using the
target.install.excludes parameter in build.properties.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-user-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-user-help@cocoon.apache.org