[JOB] Web application developer in Geneva

Swiss Exchange has an opening for a fulltime staff position as web
application developer in Geneva, Switzerland.  We are looking for an
experienced developer with a strong background in Java5 and OO design.

Additional assets are prior experience with other components of our
technology stack (Ant, Apache, Axis, Cocoon, C++, CSS, CVS, Dojo,
Eclipse, Findbugs, FOP, HTLM, JavaScript, JDBC, make, Oracle10g, Perl5,
POI, RelaxNG, Solaris10, SVG, Sybase12, Tomcat, XML, XSLT).

You will be working in a small team of developers who are in charge of
developing and maintaining the dynamic parts of http://www.swx.com and
other related websites.

The working language is English but a basic knowledge of German is a
plus.

If you are interested, please post your application to
http://www.swx.com/careers/description/g08msc_lsg01_en.html with
reference to this announcement.

Best regards,
Alfred Nathaniel
SWX e-Services

Re: svn commit: r689749 - /cocoon/whiteboard/corona/trunk/corona-sitemap/src/main/java/org/apache/cocoon/corona/sitemap/InvocationImpl.java

On 29.08.2008 07:45, Reinhard Pötz wrote:

>>> URL: http://svn.apache.org/viewvc?rev=689749&view=rev
>>> Log:
>>> improve error reporting: print the full stacktrace when the loglevel
>>> is set to INFO or below. Otherwise only print the first 5 lines.
>> Shouldn't these kind of things be left to the logging implementation and
>> configuration?
> 
> If I knew how to do this ... Log4j isn't really well documented.

I don't know either. I just "felt" wrong. Somebody else might know how 
to do it or implement his own formatter.

I saw you already removed it. Thanks :)

Joerg

[jira] Closed: (COCOON-2241) The commandline is not working since cocoon-1985

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

Thorsten Scherler closed COCOON-2241.
-------------------------------------

    Resolution: Fixed

> The commandline is not working since cocoon-1985
> ------------------------------------------------
>
>                 Key: COCOON-2241
>                 URL: https://issues.apache.org/jira/browse/COCOON-2241
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.1.12-dev (Current SVN)
>            Reporter: Thorsten Scherler
>             Fix For: 2.1.12-dev (Current SVN)
>
>         Attachments: COCOON-2241.txt, COCOON-2241.txt, COCOON-2241.txt
>
>
> Updating forrest to use cocoon-2.1.x, I found a problem in the
> AbstractCachingProcessingPipeline.
> I am not sure whether someone is using the cocoon cli ATM. Forrest is
> based around this component. 
> https://issues.apache.org/jira/browse/FOR-955?focusedCommentId=12624340#action_12624340
> I found that in

[jira] Commented: (COCOON-2241) The commandline is not working since cocoon-1985

    [
https://issues.apache.org/jira/browse/COCOON-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627631#action_12627631
] 

Thorsten Scherler commented on COCOON-2241:
-------------------------------------------

Committed revision 691199

Slight modification:
changed one line to be:

   this.objectModel.put(CLI_REQUEST_ID, new String(uri));

> The commandline is not working since cocoon-1985
> ------------------------------------------------
>
>                 Key: COCOON-2241
>                 URL: https://issues.apache.org/jira/browse/COCOON-2241
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>    Affects Versions: 2.1.12-dev (Current SVN)
>            Reporter: Thorsten Scherler
>             Fix For: 2.1.12-dev (Current SVN)
>
>         Attachments: COCOON-2241.txt, COCOON-2241.txt, COCOON-2241.txt
>
>

[jira] Subscription: COCOON-open-with-patch

Issue Subscription
Filter: COCOON-open-with-patch (108 issues)
Subscriber: cocoon

Key         Summary
COCOON-2233 Update archetypes to current trunk artifact versions
            https://issues.apache.org/jira/browse/COCOON-2233
COCOON-2222 Add SaxParser configuration properties
            https://issues.apache.org/jira/browse/COCOON-2222
COCOON-2217 HttpServletResponseBufferingWrapper throws NPE when response body is empty
            https://issues.apache.org/jira/browse/COCOON-2217
COCOON-2216 IncludeCacheManager can not perfom parallel includes
            https://issues.apache.org/jira/browse/COCOON-2216
COCOON-2212 jx:attribute does not check name is correct before proceeding
            https://issues.apache.org/jira/browse/COCOON-2212
COCOON-2211 Support for jx:element
            https://issues.apache.org/jira/browse/COCOON-2211
COCOON-2210 The field 'type' in GenerateNode in corona-sitemap should not be final
            https://issues.apache.org/jira/browse/COCOON-2210
COCOON-2197 Making the cocoon-auth-block acegi-security-sample work
            https://issues.apache.org/jira/browse/COCOON-2197
COCOON-2173 AbstractCachingProcessingPipeline: Two requests can deadlock each other
            https://issues.apache.org/jira/browse/COCOON-2173
COCOON-2162 [PATCH] Fix for Paginator when accessing out of bounds Pagination page
            https://issues.apache.org/jira/browse/COCOON-2162
COCOON-2137 XSD Schemas for CForms Development
            https://issues.apache.org/jira/browse/COCOON-2137
COCOON-2114 fix sorting in TraversableGenerator
            https://issues.apache.org/jira/browse/COCOON-2114
COCOON-2108 xmodule:flow-attr Does not accept document objects

Bug in ContinuationManagerImpl

Re: Bug in ContinuationManagerImpl

On 03.09.2008 21:25, Gabriel Gruber wrote:

> just discovered an exception inside our freshly migrated cocoon 2.2 
> migration, thrown by the ContinuationManagerImpl:
> 
> Exception in thread "Timer-0" java.util.ConcurrentModificationException
>         at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
>         at java.util.HashMap$ValueIterator.next(Unknown Source)
>         at 
> org.apache.cocoon.components.flow.ContinuationsManagerImpl.invalidateContinuations(
> ContinuationsManagerImpl.java:390)
>         at 
> org.apache.cocoon.components.flow.ContinuationsManagerImpl$WebContinuationsHolder.valueUnbound(
> ContinuationsManagerImpl.java:548)
>         at 
> org.mortbay.jetty.servlet.AbstractSessionManager$Session.unbindValue(
> AbstractSessionManager.java:1125)

> Is this a new bug, or am I doing something wrong?

It's a new bug I introduced with [1]. Reviewing the changes I did I 
found that I "optimized" some code.  It's around line 390 [2]. I'll 
have a look on how to fix it. Sorry for the inconveniences.

Joerg

[1] http://svn.apache.org/viewvc?view=rev&revision=643752
[2] 
http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-sitemap/cocoon-sitemap-impl/src/main/java/org/apache/cocoon/components/flow/ContinuationsManagerImpl.java?r1=643716&r2=643752&diff_format=h

Re: Bug in ContinuationManagerImpl

On 03.09.2008 23:37, Joerg Heinicke wrote:

>> Exception in thread "Timer-0" java.util.ConcurrentModificationException
>>         at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
>>         at java.util.HashMap$ValueIterator.next(Unknown Source)
>>         at 
>> org.apache.cocoon.components.flow.ContinuationsManagerImpl.invalidateContinuations( 
>> ContinuationsManagerImpl.java:390)
>>         at 
>>
org.apache.cocoon.components.flow.ContinuationsManagerImpl$WebContinuationsHolder.valueUnbound( 
>> ContinuationsManagerImpl.java:548)
>>         at 
>> org.mortbay.jetty.servlet.AbstractSessionManager$Session.unbindValue(
>> AbstractSessionManager.java:1125)
> 
> It's a new bug I introduced with [1]. Reviewing the changes I did I 
> found that I "optimized" some code.  It's around line 390 [2]. I'll 
> have a look on how to fix it. Sorry for the inconveniences.

Two different proposals:
1. Reintroducing the original workaround using 
continuationsHolder.holder.values().toArray() in 
invalidateContinuations(..).

2. Adding iter.remove() directly after iter.next() in line 390. The 
later problematic call to remove the continuation from the map would 
just not do anything.

WDYT?

Joerg

> [1] http://svn.apache.org/viewvc?view=rev&revision=643752
> [2] 
>
http://svn.apache.org/viewvc/cocoon/trunk/core/cocoon-sitemap/cocoon-sitemap-impl/src/main/java/org/apache/cocoon/components/flow/ContinuationsManagerImpl.java?r1=643716&r2=643752&diff_format=h 

Re: Bug in ContinuationManagerImpl

> >> Exception in thread "Timer-0" java.util.ConcurrentModificationException
> >>         at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
> >>         at java.util.HashMap$ValueIterator.next(Unknown Source)
> >>         at
> >> org.apache.cocoon.components.flow.ContinuationsManagerImpl.
> invalidateContinuations(
> >> ContinuationsManagerImpl.java:390)
> >>         at
> >> org.apache.cocoon.components.flow.
> ContinuationsManagerImpl$WebContinuationsHolder.valueUnbound(
> >> ContinuationsManagerImpl.java:548)
> >>         at
> >> org.mortbay.jetty.servlet.AbstractSessionManager$Session.unbindValue(
> >> AbstractSessionManager.java:1125)
> >
> > It's a new bug I introduced with [1]. Reviewing the changes I did I
> > found that I "optimized" some code. It's around line 390 [2]. I'll
> > have a look on how to fix it. Sorry for the inconveniences.
>
> Two different proposals:
> 1. Reintroducing the original workaround using
> continuationsHolder.holder.values().toArray() in
> invalidateContinuations(..).
>
> 2. Adding iter.remove() directly after iter.next() in line 390. The
> later problematic call to remove the continuation from the map would
> just not do anything.
>
> WDYT?

+1 for first proposal) this seems much cleaner to me, than calling iter.next() and afterwards iter.remove()....

cheers,gabriel

Samples site