You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Kamal Bhatt <kb...@tt.com.au> on 2008/04/10 05:36:01 UTC
More Cocoon 2.2 question
Hi,
Firstly, I would like to register my dissatisfaction on the structure of
the 2.2 website. It frustrates and confuses me and I know how to use
Cocoon. For example, I needed to get a description of how to write a
generator. To get to this information I had to click on the Core 2.2
link, then click the Core tag (which is described as "The
'*cocoon-core*' module is some kind of wrapper, that keeps all
dependencies together in order to make it easier to use Cocoon as web
application framework. For now the complete documentation of all core
modules can be found in Cocoon core."), then click Sitemap /Writing your
own components/Creating a Generator. What? Were it not for random
clicking on my part, I would not have found this information. Once you
get to this page, there are issues with the navigation on the left (some
parts cross over into the text). The old site was bad, but at least it
was navigable. Is there any hope of fixing the documentation any time
soon? This website is definitely not newbie friendly.
Anyway, now that I have got that off my chest, I have some questions:
1. I asked this before, but I did n't get a satisfactory answer. I know
that there is the new block structure, but I don't want to have to
bundle Cocoon classes with my sitemap, etc... for various reason
(including historical). As such, how do I point Cocoon to use a sitemap
outside the main Cocoon project?
2. Are there any instructions for deploying on different application
servers?
Thanks.
--
Kamal Bhatt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: More Cocoon 2.2 question
Posted by Kamal Bhatt <kb...@tt.com.au>.
Grzegorz Kossakowski wrote:
> Kamal Bhatt pisze:
>> Kamal Bhatt wrote:
>>> Hi,
>>> Firstly, I would like to register my dissatisfaction on the
>>> structure of the 2.2 website. It frustrates and confuses me and I
>>> know how to use Cocoon. For example, I needed to get a description
>>> of how to write a generator. To get to this information I had to
>>> click on the Core 2.2 link, then click the Core tag (which is
>>> described as "The '*cocoon-core*' module is some kind of wrapper,
>>> that keeps all dependencies together in order to make it easier to
>>> use Cocoon as web application framework. For now the complete
>>> documentation of all core modules can be found in Cocoon core."),
>>> then click Sitemap /Writing your own components/Creating a
>>> Generator. What? Were it not for random clicking on my part, I would
>>> not have found this information. Once you get to this page, there
>>> are issues with the navigation on the left (some parts cross over
>>> into the text). The old site was bad, but at least it was navigable.
>>> Is there any hope of fixing the documentation any time soon? This
>>> website is definitely not newbie friendly.
>
> Not sure what kind of comment I can give here. If you have some ideas
> how this could be changed I'm all open.
What I think is missing is a single place to get all the information
Organising a website on blocks may be convinient, but it hardly easy for
a newbie. IMHO, the Cocoon Core page should be the centre, and all other
pages should link off that page. Also, the term "Cocoon Core" isn't a
very good description of the content (not unless you have some
understanding of how Cocoon fits together, and even then it does not
cover all bases). Here is a page that has all the information you need,
but due to a bad description, it is impossible to find. From a code
perspective, it may make sense, but from a users perspective
(particularly a new one) it is nonsense.
>
>>>
>>> 1. I asked this before, but I did n't get a satisfactory answer. I
>>> know that there is the new block structure, but I don't want to have
>>> to bundle Cocoon classes with my sitemap, etc... for various reason
>>> (including historical). As such, how do I point Cocoon to use a
>>> sitemap outside the main Cocoon project?
>
> You can put your classes into one block and sitemap into another
> getting two different jars. Is it what you are looking for?
I would prefer not having jar files. The only JAR/WAR file I want is for
Cocoon. However, can I achieve this by using sitemap redirection? Would
that be inefficient?
>
>
>>>
>> Also, what is the replacement for cinclude?
>>
>
> I think that CInclude is still supported but I would advise using
> IncludeTransformer:
> http://cocoon.apache.org/2.2/core-modules/core/2.2/apidocs/org/apache/cocoon/transformation/IncludeTransformer.html
>
Is there a migration page for Cocoon? I would prefer not having to keep
asking about what is and isn't available in Cocoon 2.2.
--
Kamal Bhatt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: More Cocoon 2.2 question
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
Kamal Bhatt pisze:
> Kamal Bhatt wrote:
>> Hi,
>> Firstly, I would like to register my dissatisfaction on the structure
>> of the 2.2 website. It frustrates and confuses me and I know how to
>> use Cocoon. For example, I needed to get a description of how to write
>> a generator. To get to this information I had to click on the Core 2.2
>> link, then click the Core tag (which is described as "The
>> '*cocoon-core*' module is some kind of wrapper, that keeps all
>> dependencies together in order to make it easier to use Cocoon as web
>> application framework. For now the complete documentation of all core
>> modules can be found in Cocoon core."), then click Sitemap /Writing
>> your own components/Creating a Generator. What? Were it not for random
>> clicking on my part, I would not have found this information. Once you
>> get to this page, there are issues with the navigation on the left
>> (some parts cross over into the text). The old site was bad, but at
>> least it was navigable. Is there any hope of fixing the documentation
>> any time soon? This website is definitely not newbie friendly.
Not sure what kind of comment I can give here. If you have some ideas how this could be changed I'm
all open.
>> Anyway, now that I have got that off my chest, I have some questions:
>>
>> 1. I asked this before, but I did n't get a satisfactory answer. I
>> know that there is the new block structure, but I don't want to have
>> to bundle Cocoon classes with my sitemap, etc... for various reason
>> (including historical). As such, how do I point Cocoon to use a
>> sitemap outside the main Cocoon project?
You can put your classes into one block and sitemap into another getting two different jars. Is it
what you are looking for?
>> 2. Are there any instructions for deploying on different application
>> servers?
Have you followed this one:
http://cocoon.apache.org/2.2/1362_1_1.html
If you did, then go to myCocoonWebapp/target where you will find WAR file that you can deploy to any
servlet container you like.
>>
> Also, what is the replacement for cinclude?
>
I think that CInclude is still supported but I would advise using IncludeTransformer:
http://cocoon.apache.org/2.2/core-modules/core/2.2/apidocs/org/apache/cocoon/transformation/IncludeTransformer.html
--
Best regards,
Grzegorz Kossakowski
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: More Cocoon 2.2 question
Posted by Kamal Bhatt <kb...@tt.com.au>.
Kamal Bhatt wrote:
> Hi,
> Firstly, I would like to register my dissatisfaction on the structure
> of the 2.2 website. It frustrates and confuses me and I know how to
> use Cocoon. For example, I needed to get a description of how to write
> a generator. To get to this information I had to click on the Core 2.2
> link, then click the Core tag (which is described as "The
> '*cocoon-core*' module is some kind of wrapper, that keeps all
> dependencies together in order to make it easier to use Cocoon as web
> application framework. For now the complete documentation of all core
> modules can be found in Cocoon core."), then click Sitemap /Writing
> your own components/Creating a Generator. What? Were it not for random
> clicking on my part, I would not have found this information. Once you
> get to this page, there are issues with the navigation on the left
> (some parts cross over into the text). The old site was bad, but at
> least it was navigable. Is there any hope of fixing the documentation
> any time soon? This website is definitely not newbie friendly.
>
> Anyway, now that I have got that off my chest, I have some questions:
>
> 1. I asked this before, but I did n't get a satisfactory answer. I
> know that there is the new block structure, but I don't want to have
> to bundle Cocoon classes with my sitemap, etc... for various reason
> (including historical). As such, how do I point Cocoon to use a
> sitemap outside the main Cocoon project?
> 2. Are there any instructions for deploying on different application
> servers?
>
> Thanks.
>
Also, what is the replacement for cinclude?
--
Kamal Bhatt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: More Cocoon 2.2 question
Posted by Vadim Gritsenko <va...@reverycodes.com>.
On Apr 9, 2008, at 11:36 PM, Kamal Bhatt wrote:
> As such, how do I point Cocoon to use a sitemap outside the main
> Cocoon project?
Depends what you mean... If using 2.2 blocks, add a parameter to the
block servlet bean definition. Like this:
<bean name="org.apache.cocoon-welcome.block"
class="org.apache.cocoon.sitemap.SitemapServlet">
<servlet:init-params>
<entry key="sitemap-path" value="file:///path/to/sitemap.xmap"/>
</servlet:init-params>
<servlet:context mount-path="/" context-path="blockcontext:/
cocoon-welcome/">
<servlet:connections>
<entry key="style" value-
ref="org.apache.cocoon.samples.style.default.servlet"/>
</servlet:connections>
</servlet:context>
</bean>
If using classic mode, it is same as usual, <sitemap/> element in main
xconf file.
Vadim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org