test

Re: Logging of AbstractSAXTransformer

On Wed, 2007-10-31 at 17:31 +0100, Grzegorz Kossakowski wrote:
> Thorsten Scherler pisze:
> >> Just go to the Cocoon's root directory and type:
> >> mvn clean install (or some variant of this command like with -P allblocks, etc)
> >>
> >> This will install all Cocoon's snapshot artifacts made from Cocoon's trunk to your local Maven
> >> repository. Then, when developing your application you just need to change version of Cocoon's
> >> dependencies to snapshosts, e.g. dependency on cocoon-core artifact should have 2.2.0-RC3-SNAPSHOT
> >> version.
> > 
> > That means (for other newbies) you need to edit your pom.xml and update
> > all dependencies versions. If you have followed the tutorial on
> > generating you own block you will need to change at least three
> > dependencies. 
> 
> Yep, and keep in mind that we increase version numbers of modules after releasing (first internally)
> our modules so in order to keep using trunk you will have to increase this numbers in your pom file too.
> 
> If you want to make sure that you are really using dependencies built from latest trunk you would
> follow these steps:
> 1. go to Cocoon's trunk directory and hit this command:
> mvn dependency:purge-local-repository -DresolutionFuzziness=groupId
> (this will remove all Cocoon artifacts from your local repository)
> 
> 2. Then:
> mvn clean install
> (this will install only latest snapshots of Cocoon artifacts to your local repository)
> 
> 3. go to your application directory and type:
> mvn clean install -o

[jira] Created: (COCOON-2143) Avalon less components

Avalon less components
----------------------

                 Key: COCOON-2143
                 URL: https://issues.apache.org/jira/browse/COCOON-2143
             Project: Cocoon
          Issue Type: Task
          Components: - Components: Avalon, - Documentation
            Reporter: Thorsten Scherler

When it comes to documentation, I think that document explaining how to develop Spring-based Cocoon
component wouldn't be complicated or very long. The effort should consist of searching mail archives
for all problems people had with developing Spring-based components up to date and collecting all
the hints in one place in a consistent way.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (COCOON-2143) Avalon less components

    [
https://issues.apache.org/jira/browse/COCOON-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539531
] 

Thorsten Scherler commented on COCOON-2143:
-------------------------------------------

Custom transformer:
http://marc.info/?t=119376535600001&r=1&w=2

Custom generator
http://www.mail-archive.com/users <at> cocoon.apache.org/msg39766.html

> Avalon less components
> ----------------------
>
>                 Key: COCOON-2143
>                 URL: https://issues.apache.org/jira/browse/COCOON-2143
>             Project: Cocoon
>          Issue Type: Task
>          Components: - Components: Avalon, - Documentation
>            Reporter: Thorsten Scherler
>
> When it comes to documentation, I think that document explaining how to develop Spring-based Cocoon
> component wouldn't be complicated or very long. The effort should consist of searching mail archives
> for all problems people had with developing Spring-based components up to date and collecting all
> the hints in one place in a consistent way.

--

-- 

[jira] Created: (COCOON-2144) SettingsInputModule.getAttributeNames(...) returns an empty iterator

SettingsInputModule.getAttributeNames(...) returns an empty iterator
--------------------------------------------------------------------

                 Key: COCOON-2144
                 URL: https://issues.apache.org/jira/browse/COCOON-2144
             Project: Cocoon
          Issue Type: Bug
          Components: - Components: Sitemap
            Reporter: Thorsten Scherler

http://marc.info/?l=xml-cocoon-users&m=119400082230384&w=2

The getAttributeNames(...) method should return an iterator of all properties.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (COCOON-2144) SettingsInputModule.getAttributeNames(...) returns an empty iterator

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

Thorsten Scherler updated COCOON-2144:
--------------------------------------

    Attachment: 2144.patch

Enabling iterator

> SettingsInputModule.getAttributeNames(...) returns an empty iterator
> --------------------------------------------------------------------
>
>                 Key: COCOON-2144
>                 URL: https://issues.apache.org/jira/browse/COCOON-2144
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>            Reporter: Thorsten Scherler
>         Attachments: 2144.patch
>
>
> http://marc.info/?l=xml-cocoon-users&m=119400082230384&w=2
> The getAttributeNames(...) method should return an iterator of all properties.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [jira] Updated: (COCOON-2144) SettingsInputModule.getAttributeNames(...) returns an empty iterator

Hi all,

I actually have commit access to cocoon since I am a lenya and forrest
committer.

If nobody objects I would like to help you and apply the patch myself. 

salu2

On Fri, 2007-11-02 at 04:00 -0700, Thorsten Scherler (JIRA) wrote:
> [
https://issues.apache.org/jira/browse/COCOON-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
> 
> Thorsten Scherler updated COCOON-2144:
> --------------------------------------
> 
>     Attachment: 2144.patch
> 
> Enabling iterator
> 
> > SettingsInputModule.getAttributeNames(...) returns an empty iterator
> > --------------------------------------------------------------------
> >
> >                 Key: COCOON-2144
> >                 URL: https://issues.apache.org/jira/browse/COCOON-2144
> >             Project: Cocoon
> >          Issue Type: Bug
> >          Components: - Components: Sitemap
> >            Reporter: Thorsten Scherler
> >         Attachments: 2144.patch

Re: [jira] Updated: (COCOON-2144) SettingsInputModule.getAttributeNames(...) returns an empty iterator

Thorsten Scherler pisze:
> Hi all,
> 
> I actually have commit access to cocoon since I am a lenya and forrest
> committer.
> 
> If nobody objects I would like to help you and apply the patch myself. 
> 
> salu2
> 

I reviewed your patch and it looks fine. While applying it don't forget 
to add information about your change to changes.xml of affected module.

--

-- 
Grzegorz Kossakowski

Abstract classes for Spring-based components (was: Logging of AbstractSAXTransformer)

Thorsten Scherler pisze:
>> AbstractSAXTransformer is not a component but just an abstract class assuming its descendants will
>> be Avalon-components. If you are extending such a class you must be careful because you must check
>> if your super class can work ok without assumption that Avalon-contracts are respected as they won't
>> be if your component is a Spring bean.
>>
>> For example, when extending AbstractSAXTransformer you may want to check why it implements
>> Serviceable interface. As you can see:
>>     public void service(ServiceManager aManager) throws ServiceException {
>>         this.manager = aManager;
>>     }
>>
>> It only stores a manager so you need to check if it is used somewhere. After bit of research you
>> figure out that manager is not used in AbstractSAXTransformer so this class can live without
>> ServiceManager at all. The same goes for other contracts.
> 
> Actually this is a very good example of some short comes in our current
> wrappers. The serviceable components are not initialized correctly. My
> custom transformer is using service(...) and had thrown a NPE. After
> debugging I found out that service(...) never got called. 
> 
> The solution is to implement:
> public void setManager(ServiceManager manager) throws ServiceException {
>   super.service(manager);
>   this.manager=manager;
> }
> 
> and add to your spring config:
> <property name="manager"
> ref="org.apache.avalon.framework.service.ServiceManager"/>

[jira] Closed: (COCOON-2144) SettingsInputModule.getAttributeNames(...) returns an empty iterator

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

Thorsten Scherler closed COCOON-2144.
-------------------------------------

    Resolution: Fixed

http://svn.apache.org/viewvc?view=rev&revision=591307

thanks Grzegorz for the review

> SettingsInputModule.getAttributeNames(...) returns an empty iterator
> --------------------------------------------------------------------
>
>                 Key: COCOON-2144
>                 URL: https://issues.apache.org/jira/browse/COCOON-2144
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Components: Sitemap
>            Reporter: Thorsten Scherler
>         Attachments: 2144.patch
>
>
> http://marc.info/?l=xml-cocoon-users&m=119400082230384&w=2
> The getAttributeNames(...) method should return an iterator of all properties.

--

-- 
This message is automatically generated by JIRA.