Re: Connecting 2 blocks with C3.0

Mansour Al Akeel <[email protected]>
Newsgroups gmane.text.xml.cocoon.user
Message-ID <CAFvvX=a9hU6PRMwVhTCv_24JgGnAZDtCGTCmHpOt3rcxaJ_x-w@mail.gmail.com>
I truly appreciate your help, and I agree with you that this needs to
be documented in a place where it's easy to find. It is taking me a
lot of time to try to figure out what is wrong.
I think it's related more to the running mode and the configurations.
For example when you declare a block as a dependency, its

resources/META-INF/cocoon/spring/dev/mysite-servlet-service.xml

has to have different name in the importing block, for example no two
blocks should have this:

resources/META-INF/cocoon/spring/block-servlet-service.xml

I am still investigating, and can not confirm that this is the issue.

Additionally


  <!-- A Cocoon-Sitemap based servlet-service. -->
  <bean id="com.mycompany.mysite.service"
class="org.apache.cocoon.servlet.XMLSitemapServlet">
    <servlet:context mount-path="/mysite"
context-path="jar:classpath:/COB-INF/"/>
  </bean>

in

https://github.com/ilgrosso/cocoon3EmptyProject/blob/COCOON3-105/mysite/src/main/resources/META-INF/cocoon/spring/dev/mysite-servlet-service.xml

needs a bit more clarification. Specifically

    <servlet:context mount-path="/mysite"
context-path="jar:classpath:/COB-INF/"/>

in development mode and this line in production:

    <servlet:context mount-path="/mysite"
context-path="jar:classpath:lib/${project.build.finalName}.jar!/COB-INF/"/>

It will be nice if this is documented with the scenarios where we
should use one of another.


Thank you.




On Sat, Feb 9, 2013 at 7:19 AM, Francesco Chicchiriccò
<[email protected]> wrote:
> On 09/02/2013 05:09, Mansour Al Akeel wrote:
>>
>> I am trying to follow this tutorial
>> http://cocoon.apache.org/2.2/1291_1_1.html
>> to connect 2 blocks. I was able to do this in the past easily with C2.1
>> and 2.2.
>>
>> With C3.0 as soon as I add the depency block to pom.xml I star getting an
>> error:
>>
>> [...]
>>
>>
>>
>> I have created the project from maven archetypes. Additionally, when
>> following the same tutorial, and I modify the rcl.properties to
>> include the classes for the first project, matchers stop matching on
>> any patterns.
>> Is there something I need to do to get this to work properly ??
>
>
> Hi,
> COCOON3-105 changed the way how blocks are deployed in a Cocoon webapp: this
> affects only C3 SNAPSHOTS of course, and even in this case you can restore
> the old (i.e. 2.2) way of connecting blocks.
>
> I've prepared a simple C3 project at [1] that shows how to deal with this:
> the README there should be enough to get it working and a quick look at
> sources can help in understanding what has changed "under the hood".
>
> More specifically, as you can see from [2], the block mysite2 can refer to
> block mysite1's resources as
>
> <map:read
> src="jar:classpath:lib/mysite-${project.version}.jar!/COB-INF/{map:1}.xsl"/>
>
> where ${project.version} is changed by Maven at build time into the version
> declared in pom.xml.
>
>
> We need of course to provide a proper documentation for how to get started
> with C3: I've opened COCOON3-119 for this.
> Hope this helps, in the meanwhile.
>
> Regards.
>
> [1] https://github.com/ilgrosso/cocoon3EmptyProject/tree/COCOON3-105
> [2]
> https://github.com/ilgrosso/cocoon3EmptyProject/blob/COCOON3-105/mysite2/src/main/resources/COB-INF/sitemap.xmap
> [3] http://cocoon.apache.org/2.2/1291_1_1.html
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.