Return-Path: 
 <dev-return-104283-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
X-Original-To: apmail-cocoon-dev-archive@www.apache.org
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 93B06E542
	for <apmail-cocoon-dev-archive@www.apache.org>;
 Thu, 21 Feb 2013 04:36:17 +0000 (UTC)
Received: (qmail 361 invoked by uid 500); 21 Feb 2013 04:36:17 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 99673 invoked by uid 500); 21 Feb 2013 04:36:16 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 98991 invoked by uid 99); 21 Feb 2013 04:36:14 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Feb 2013 04:36:14 +0000
Date: Thu, 21 Feb 2013 04:36:14 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Message-ID: <JIRA.12633239.1361383444074.315419.1361421374048@arcas>
In-Reply-To: <JIRA.12633239.1361383444074@arcas>
References: <JIRA.12633239.1361383444074@arcas>
Subject: [jira] [Commented] (COCOON3-121) Create a generic generator that
 creates a root elemement and wraps the destination stream into it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/COCOON3-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582910#comment-13582910 ] 

Hudson commented on COCOON3-121:
--------------------------------

Integrated in Cocoon 3.0 #238 (See [https://builds.apache.org/job/Cocoon%203.0/238/])
    COCOON3-121
adding test for the generator (Revision 1448487)

     Result = SUCCESS
thorsten : http://svn.apache.org/viewvc/?view=rev&rev=1448487
Files : 
* /cocoon/cocoon3/trunk/cocoon-optional/src/test/java/org/apache/cocoon/optional/pipeline/components/sax/generator
* /cocoon/cocoon3/trunk/cocoon-optional/src/test/java/org/apache/cocoon/optional/pipeline/components/sax/generator/AddRootElementGeneratorTest.java
* /cocoon/cocoon3/trunk/cocoon-optional/src/test/resources/org/apache/cocoon/optional/pipeline/components/sax/generator
* /cocoon/cocoon3/trunk/cocoon-optional/src/test/resources/org/apache/cocoon/optional/pipeline/components/sax/generator/page.xml

                
> Create a generic generator that creates a root elemement and wraps the destination stream into it
> -------------------------------------------------------------------------------------------------
>
>                 Key: COCOON3-121
>                 URL: https://issues.apache.org/jira/browse/COCOON3-121
>             Project: Cocoon 3
>          Issue Type: Bug
>          Components: cocoon-optional
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Thorsten Scherler
>            Assignee: Thorsten Scherler
>             Fix For: 3.0.0-beta-1
>
>
> If you use something like ch.qos.logback.classic.log4j.XMLLayout you can create xml based log files. However the problem is that it does not add root element making the resulting file not well-formed. 
> You can activate the logging in your logback.xml like 
>    <appender name="FAILS" class="ch.qos.logback.core.FileAppender">
>         <file>${crawler.log.error}</file>
>         <append>false</append>
>         <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder">
>           <layout class="ch.qos.logback.classic.log4j.XMLLayout">
>             <locationInfo>true</locationInfo>
>           </layout>
>         </encoder>
>     </appender>
> The implemented solution has the following configuration in spring:
>   <bean name="generator:log4j" class="org.apache.cocoon.optional.pipeline.components.sax.generator.AddRootElementGenerator" scope="prototype">
>     <property name="encoding" value="UTF-8"/>
>     <property name="localName" value="events"/>
>     <property name="prefix" value="log4j"/>
>     <property name="namespace" value="http://jakarta.apache.org/log4j/"/>
>   </bean>
> and later parse the file that the appender gives like:
> <map:pipeline>
>       <map:match pattern="errorLogs">
>         <map:generate src="${crawler.log.error}" type="log4j"/>
>         <map:serialize type="xml" />
>       </map:match>
>     </map:pipeline>
> which will result in something like:
> <?xml version="1.0" encoding="UTF-8"?>
> <log4j:events xmlns:log4j="http://jakarta.apache.org/log4j/">
>   <log4j:event logger="org.apache.droids.exception.ExceptionHandler" timestamp="1361325224196" level="ERROR" thread="main">
>    <log4j:message><![CDATA[org.apache.droids.core.DroidsException: org.apache.droids.core.DroidsException: org.apache.droids.core.DroidsException: org.apache.http.client.HttpResponseException: Internal Server Error http://localhost:8888/xxx/details/xxx]]>
>   </log4j:message>
>   <log4j:locationInfo class="org.apache.droids.exception.ExceptionHandler" method="handleException" file="ExceptionHandler.java" line="23"/>
>  </log4j:event>
> </log4j:events>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira