headers
Grzegorz Kossakowski (aka g[R]eK) (JIRA | 1 Feb 02:19
Picon
Favicon

[jira] Created: (COCOON-1997) Configure servlet: links rewriting

Configure servlet: links rewriting
----------------------------------

                 Key: COCOON-1997
                 URL: https://issues.apache.org/jira/browse/COCOON-1997
             Project: Cocoon
          Issue Type: Sub-task
          Components: - Blocks Framework
    Affects Versions: 2.2-dev (Current SVN)
            Reporter: Grzegorz Kossakowski (aka g[R]eK)
             Fix For: 2.2-dev (Current SVN)

This issue is on configuring (or creating new) transformer that will take care of servlet: link rewriting.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Permalink | Reply | 5 comments |
headers
Grzegorz Kossakowski (aka g[R]eK) (JIRA | 1 Feb 02:23
Picon
Favicon

[jira] Updated: (COCOON-1997) Configure servlet: links rewriting


     [
https://issues.apache.org/jira/browse/COCOON-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grzegorz Kossakowski (aka g[R]eK) updated COCOON-1997:
------------------------------------------------------

    Attachment: cocoon-servlet-service-impl-linkrewriting-transformer-patch-1.txt

This patch configures LinkRewriterTransformer in order to rewrite properly servlet: links. It uses
block-path for this task. Currently only links in src and href attributes will get rewritten.

This patch affects cocoon-servlet-service-impl module only.
This patch adds dependency on cocoon-linkrewriter-impl module.

> Configure servlet: links rewriting
> ----------------------------------
>
>                 Key: COCOON-1997
>                 URL: https://issues.apache.org/jira/browse/COCOON-1997
>             Project: Cocoon
>          Issue Type: Sub-task
>          Components: - Blocks Framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski (aka g[R]eK)
>             Fix For: 2.2-dev (Current SVN)
>
>         Attachments: cocoon-servlet-service-impl-linkrewriting-transformer-patch-1.txt
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Grzegorz Kossakowski (aka g[R]eK) (JIRA | 1 Feb 02:25
Picon
Favicon

[jira] Updated: (COCOON-1997) Configure servlet: links rewriting


     [
https://issues.apache.org/jira/browse/COCOON-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grzegorz Kossakowski (aka g[R]eK) updated COCOON-1997:
------------------------------------------------------

    Attachment: cocoon-webapp-switch-to-servlet-service-patch-1.txt

This patch makes a switch to dispatcher servlet from cocoon-servlet-service-impl module. This is
required in order to get link rewriting work properly!

Affects cocoon-webapp module only.

> Configure servlet: links rewriting
> ----------------------------------
>
>                 Key: COCOON-1997
>                 URL: https://issues.apache.org/jira/browse/COCOON-1997
>             Project: Cocoon
>          Issue Type: Sub-task
>          Components: - Blocks Framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski (aka g[R]eK)
>             Fix For: 2.2-dev (Current SVN)
>
>         Attachments: cocoon-servlet-service-impl-linkrewriting-transformer-patch-1.txt, cocoon-webapp-switch-to-servlet-service-patch-1.txt
>
>
> This issue is on configuring (or creating new) transformer that will take care of servlet: link rewriting.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Grzegorz Kossakowski (aka g[R]eK) (JIRA | 1 Feb 02:34
Picon
Favicon

[jira] Updated: (COCOON-1992) Make Ajax resourced loaded directly from cocoon-ajax-impl


     [
https://issues.apache.org/jira/browse/COCOON-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grzegorz Kossakowski (aka g[R]eK) updated COCOON-1992:
------------------------------------------------------

    Attachment: cocoon-ajax-sample-patch-2.txt

cocoon-ajax-sample-patch-2.txt:

This patch makes use of servlet: link rewriting in Ajax sample. This was tested and is working in my env.

> Make Ajax resourced loaded directly from cocoon-ajax-impl
> ---------------------------------------------------------
>
>                 Key: COCOON-1992
>                 URL: https://issues.apache.org/jira/browse/COCOON-1992
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: Blocks: Ajax
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Grzegorz Kossakowski (aka g[R]eK)
>             Fix For: 2.2-dev (Current SVN)
>
>         Attachments: cocoon-ajax-impl-patch-1.txt, cocoon-ajax-sample-patch-1, cocoon-ajax-sample-patch-2.txt
>
>
> This task includes:
> 1. creating new sitemap in cocoon-ajax-impl and registering it as servlet in dispatcher from servelt-service-fw.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Schaefer | 1 Feb 02:48

list moved

This list has moved to

dev@...

The old address will still work,
but from this point forward you
should use the new one.

--

-- 
Joe Schaefer
Permalink | Reply | 0 comments |
headers
Ralph Goers | 1 Feb 06:02
Favicon

Re: OSGi blocks development?

You should probably add this to an FAQ somewhere.

Daniel Fagerstrom wrote:
> Neeme Praks skrev:
>> Hi,
>>
>> In spring of 2006 there was some heavy discussion going on about 
>> implementing OSGi based blocks system and refactoring things to use 
>> Spring container instead of ECM.
>>
>> After that, things seem to have become very quiet.
>> Last e-mail I see on the list is about the OSGi subject is from the 
>> beginning of September, 2006. After that - total silence.
>>
>> JIRA is just as quiet:
>> http://issues.apache.org/jira/browse/COCOON-1826
>> http://issues.apache.org/jira/browse/COCOON-1827
>> http://issues.apache.org/jira/browse/COCOON-1829
>> http://issues.apache.org/jira/browse/COCOON-1830
>>
>> Can someone shed some light on the status of OSGi integration in Cocoon?
>
> Although there are many people involved in Cocoon we are just a few 
> who work on the core and basic infrastructure. And we where spreading 
> ourselves to thin in the project by both working on moving to Spring, 
> moving to Maven and using OSGi at the same time. So we decided to 
> focus on Spring, Maven and getting a release of 2.2 before continuing 
> the work on moving to OSGi.
>
> Also it was a quite large work to integrate Spring and OSGi. And when
(Continue reading)

Permalink | Reply | 0 comments |
headers
Reinhard Poetz | 1 Feb 07:51
Picon
Favicon

Re: [graphics] Artwork for cocoon.apache.org - next steps

hepabolu wrote:
> Steven Noels said the following on 31/1/07 10:13:
>> On 31 Jan 2007, at 07:51, Reinhard Poetz wrote:
>>
>>> - Although I would like to have it, it is difficult for us to
>>>    maintain a "breadcrump navigation" like
>>>    Apache Cocoon > Cocoon Blocks > Cocoon Forms > [Introduction]
>>>    as we can't auto-generate them using existing (meta) data. As long 
>>> as we
>>>    don't have a good idea of how to do it, we should avoid having one.
>>
>> What's the (Daisy?) issue here? It sure is possible to have 
>> breadcrumbs + normal nav on one page - just a matter of processing the 
>> same navtree twice.
> 
> That's the caveat: if the page is not in the navtree, there is no 
> breadcrumb to be generated.
> 
> I'm working on it.

The problem is not Daisy specific but caused by the design of the export tool. 
Each artifact, that we produce, can have its own documentation. "Own 
documentation" means that it consists of one navigation tree document and 
documents that are linked from there.

For example, let's assume that we want to have a breadcrump navigation like
ASF > Apache Cocoon > Cocoon Blocks > Cocoon Forms > [Introduction]. When the 
"Introduction" document is exported, we have access to the document name 
"Introduction" and we know that it is part of the "Cocoon Forms" documentation. 
We also know that we are producing the "Apache Cocoon" documentation and that
(Continue reading)

Permalink | Reply | 0 comments |
headers
Woonsan Ko (JIRA | 1 Feb 08:51
Picon
Favicon

[jira] Created: (COCOON-1998) CocoonPortlet needs to allow overriding servlet-path parameter with preferences.

CocoonPortlet needs to allow overriding servlet-path parameter with preferences.
--------------------------------------------------------------------------------

                 Key: COCOON-1998
                 URL: https://issues.apache.org/jira/browse/COCOON-1998
             Project: Cocoon
          Issue Type: Improvement
          Components: Blocks: Portal
    Affects Versions: 2.1.11-dev (Current SVN)
            Reporter: Woonsan Ko
             Fix For: 2.1.11-dev (Current SVN)
         Attachments: servlet-path-pref-diff.txt

The CocoonPortlet in BRANCH_2_1_X does not allow overriding the *servlet-path* init parameter by preferences.
If the CocoonPortlet reads preferences to override the 'servlet-path', portal users can use manycoplet
fragments without tedious portlet tag additions.
FYI, some portals such as Jetspeed 2 allows inline preference settings, not allowed for end-users.

Without this feature, portal users have to add portlet tags in the portlet.xml whenever they need to use
another coplet in the portal site.

To test properly for the patch, you should add init-parameter in the cocoon/WEB-INF/portlet.xml like the
following:

  <portlet>
    <portlet-name>CocoonPortlet</portlet-name>
    ...
    <init-param>
      <name>allow-preferences</name>
      <value>true</value>
(Continue reading)

Permalink | Reply | 6 comments |
headers
Woonsan Ko (JIRA | 1 Feb 08:51
Picon
Favicon

[jira] Updated: (COCOON-1998) CocoonPortlet needs to allow overriding servlet-path parameter with preferences.


     [
https://issues.apache.org/jira/browse/COCOON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko updated COCOON-1998:
-------------------------------

    Attachment: servlet-path-pref-diff.txt

> CocoonPortlet needs to allow overriding servlet-path parameter with preferences.
> --------------------------------------------------------------------------------
>
>                 Key: COCOON-1998
>                 URL: https://issues.apache.org/jira/browse/COCOON-1998
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: Blocks: Portal
>    Affects Versions: 2.1.11-dev (Current SVN)
>            Reporter: Woonsan Ko
>             Fix For: 2.1.11-dev (Current SVN)
>
>         Attachments: servlet-path-pref-diff.txt
>
>
> The CocoonPortlet in BRANCH_2_1_X does not allow overriding the *servlet-path* init parameter by preferences.
> If the CocoonPortlet reads preferences to override the 'servlet-path', portal users can use manycoplet
fragments without tedious portlet tag additions.
> FYI, some portals such as Jetspeed 2 allows inline preference settings, not allowed for end-users.
> Without this feature, portal users have to add portlet tags in the portlet.xml whenever they need to use
another coplet in the portal site.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Woonsan Ko | 1 Feb 08:58
Picon
Favicon

Re: CocoonPortlet needs to allow overriding servlet-path parameter with preferences.

Hi Carsten,

Sorry it took so long to get back to you.
My INBOX became overloaded and now I finally caught up.

I just posted my patch to JIRA.
Thanks.

Regards,

Woonsan

--- Carsten Ziegeler <cziegeler <at> apache.org> wrote:

> Woon-San Ko wrote:
> > Hi, all.
> > 
> > The CocoonPortlet in BRANCH_2_1_X does not allow overriding the *servlet-path* init parameter
> by
> > preferences.
> > So, portal users have to add portlet tags in the portlet.xml whenever they need to use another
> > coplet in the portal site.
> > 
> > If the CocoonPortlet reads preferences to override the *servlet-path*, portal users can use
> many
> > coplet fragments without tedious portlet tag additions.
> > 
> Hi,
> 
> I think this is a good addition to the ManagedCocoonPortlet. Can you
(Continue reading)

Permalink | Reply | 2 comments |

Gmane