Sumit | 2 Jan 2006 16:45

[2.2] Problems with JMX Support and Tomcat

I'm trying to get the latest 2.2 running in a standard tomcat 5.5.12

With the default webapp, the following class can't be found:

org.mortbay.log.LogFactory

So it seems that the jetty-jmx-5.1.8.jar does not contain all required

classes. Copying also jetty-5.1.8.jar into WEB-INF/lib of course solves

this problem.

Thanx,

Sumit Sanwal

PCS

 

Reinhard Poetz | 3 Jan 2006 06:59
Picon
Favicon

Re: [2.2] Problems with JMX Support and Tomcat

Sumit wrote:
> I'm trying to get the latest 2.2 running in a standard tomcat 5.5.12
> 
> With the default webapp, the following class can't be found:
> 
> org.mortbay.log.LogFactory
> 
> So it seems that the jetty-jmx-5.1.8.jar does not contain all required
> 
> classes. Copying also jetty-5.1.8.jar into WEB-INF/lib of course solves
> 
> this problem.

The problem has already been raised on cocoon-dev. AFAIU some developers are 
looking for solutions that avoid adding the complete jetty-5.1.8.jar.

--

-- 
Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}

                                        web(log): http://www.poetz.cc
--------------------------------------------------------------------
Victoria Vitaver | 3 Jan 2006 07:16
Picon
Favicon

RE: Error message handling in repeater rows

Hmmm .. that's funny. I also have error handling inside repeater rows and
its seems to work ok. Are you by any chance hiding rows(and hence the error
messages)?

Vica

-----Original Message-----
From: Derek Hohls [mailto:DHohls <at> csir.co.za]
Sent: Saturday, 31 December 2005 8:25 PM
To: users <at> cocoon.apache.org
Subject: Error message handling in repeater rows

I'd appreciate it if anyone could point to how to setup
handling of error messages for fields in repeater rows...
the method I am using does not seem to be working?

I have setup a new error message widget inside of the
repeater row, but it does not seem to receive a fail message
when, for example, an integer is out of range e.g.

<fd:form
 xmlns:fd="http://apache.org/cocoon/forms/1.0#definition"
 xmlns:i18n="http://apache.org/cocoon/i18n/2.1">

	<fd:widgets>

		<fd:field id="message" required="false"> <!-- message for outer widgets-->
			<fd:label></fd:label>
			<fd:datatype base="string">
			</fd:datatype>
		</fd:field>

		<fd:field id="GroupLabel" required="true">
			<fd:label>Label</fd:label>
			<fd:datatype base="string"/>
		</fd:field>

	<fd:repeater id="dsdata" size="5">
		<fd:widgets>

		<fd:field id="dsmessage" required="false">  <!-- message for repeater
widgets-->
			<fd:label></fd:label>
			<fd:datatype base="string"/>
		</fd:field>

		<fd:field id="dsYear">
			<fd:label>Year</fd:label>
			<fd:datatype base="integer"><fd:convertor type="plain"/></fd:datatype>
			<fd:validation>
  			<fd:range max="2100" min="1900">
				<fd:failmessage>Not in the required range (1900 to
2100)!</fd:failmessage>
			</fd:range>
			</fd:validation>
		</fd:field>

Thanks!
Derek

--
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.

CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html

CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html

For electronic copies of the CSIR Copyright, Terms and Conditions and the
CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
HelpDesk <at> csir.co.za.

This message has been scanned for viruses and dangerous content by
MailScanner,
and is believed to be clean.  MailScanner thanks Transtec Computers for
their support.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe <at> cocoon.apache.org
For additional commands, e-mail: users-help <at> cocoon.apache.org
Marcel Rouwenhorst | 3 Jan 2006 09:46
Picon
Favicon

Problem writing generator

Hi,

 

I have a problem writing a generator. I want to write a generator for exception handling. It should work something like the exception generator.

The generator should create an output that looks like this (simplified):

 

<exception xmlns:i18n="http://apache.org/cocoon/i18n/2.1">

<i18n:text i18n:key="some_key">test</i18n:text>

</exception>

 

I get everything right except I can’t create xmlns:i18n="http://apache.org/cocoon/i18n/2.1” in the exception tag or any other tag.

 

I use the org.xml.sax.ContentHandler to create the xml. In the same way as the exception generator does.

 

Help is appreciated

 

Marcel

 

Geert Josten | 3 Jan 2006 10:08
Picon

Re: Problem writing generator

Are you using startPrefixMapping and endPrefixMapping to register the i18n namespace?

Kind regards,
Geert

Marcel Rouwenhorst wrote:

> Hi,
> 
>  
> 
> I have a problem writing a generator. I want to write a generator for 
> exception handling. It should work something like the exception generator.
> 
> The generator should create an output that looks like this (simplified):
> 
>  
> 
> <exception xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> 
> <i18n:text i18n:key="some_key">test</i18n:text>
> 
> </exception>
> 
>  
> 
> I get everything right except I can’t create 
> xmlns:i18n="http://apache.org/cocoon/i18n/2.1” in the exception tag or 
> any other tag.
> 
>  
> 
> I use the org.xml.sax.ContentHandler to create the xml. In the same way 
> as the exception generator does.
> 
>  
> 
> Help is appreciated
> 
>  
> 
> Marcel
> 
>  
> 

--

-- 
Drs. G.P.H. Josten
Consultant

Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665  JZ  Bleiswijk
Tel: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl

De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is 
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken 
wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend.
Marcel Rouwenhorst | 3 Jan 2006 10:40
Picon
Favicon

RE: Problem writing generator

Thanks Geert for answering! 

I do use the startPrefixMapping and endPrefixMapping

This are the two source code examples I tried: 

1 ----------------------

handler.startPrefixMapping("i18n", I18nTransformer.I18N_NAMESPACE_URI);

AttributesImpl attr = new AttributesImpl();
attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "key",
"i18n:" + "key", "some_key");

handler.startElement(null, "exception", "exception", null);
handler.startElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
"i18n:text", attr);

handler.endElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
"i18n:text");
handler.endElement(null, "exception", "exception");

handler.endPrefixMapping("i18n");

This example creates the following xml:
<exception>
	<i18n:text i18n:key="some_key"/>
</exception>

2---------------------

If I change the following 2 lines 

handler.startPrefixMapping("xmlns", I18nTransformer.I18N_NAMESPACE_URI);

attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "i18n",
"xmlns:i18n", I18nTransformer.I18N_NAMESPACE_URI);

This example creates the following xml:
<exception>
	<i18n:text xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"/>
</exception>

You can see that there are 2 i18n:text
xmlns:i18n="http://apache.org/cocoon/i18n/2.1" 
I get an error "XML Parsing Error: duplicate attribute"

Thank you,
Marcel

-----Oorspronkelijk bericht-----
Van: Geert Josten [mailto:Geert.Josten <at> daidalos.nl] 
Verzonden: dinsdag 3 januari 2006 10:08
Aan: users <at> cocoon.apache.org
Onderwerp: Re: Problem writing generator

Are you using startPrefixMapping and endPrefixMapping to register the
i18n namespace?

Kind regards,
Geert

Marcel Rouwenhorst wrote:

> Hi,
> 
>  
> 
> I have a problem writing a generator. I want to write a generator for 
> exception handling. It should work something like the exception
generator.
> 
> The generator should create an output that looks like this
(simplified):
> 
>  
> 
> <exception xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
> 
> <i18n:text i18n:key="some_key">test</i18n:text>
> 
> </exception>
> 
>  
> 
> I get everything right except I can't create 
> xmlns:i18n="http://apache.org/cocoon/i18n/2.1" in the exception tag or

> any other tag.
> 
>  
> 
> I use the org.xml.sax.ContentHandler to create the xml. In the same
way 
> as the exception generator does.
> 
>  
> 
> Help is appreciated
> 
>  
> 
> Marcel
> 
>  
> 

-- 
Drs. G.P.H. Josten
Consultant

Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665  JZ  Bleiswijk
Tel: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl

De informatie - verzonden in of met dit emailbericht - is afkomstig van
Daidalos BV en is 
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onbedoeld hebt ontvangen, verzoeken 
wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden
ontleend.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe <at> cocoon.apache.org
For additional commands, e-mail: users-help <at> cocoon.apache.org
Stefan Ivanov | 3 Jan 2006 10:42
Picon
Gravatar

Build 2.1.8 with Java 1.5

Hi there

I'm trying to build cocoon 2.1.8 with no success.
I tried with 2.1.7 too.
I allways have some failure.
Here the message with the 2.1.8:

...
cocoon-block-html-compile:
Compiling 3 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\html\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\html-block.jar

cocoon-block-jcr-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\jcr\dest

cocoon-block-jcr-compile:
Compiling 6 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\jcr\dest
Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo
n-2.1.8\blocks\jcr\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\jcr-block.jar

cocoon-block-linkrewriter-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\linkrewriter\dest

cocoon-block-linkrewriter-compile:
Compiling 4 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\linkrewriter\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\linkrewriter-block.jar

cocoon-block-lucene-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\lucene\dest

cocoon-block-lucene-compile:
Compiling 12 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\
build\cocoon-2.1.8\blocks\lucene\dest
Copied 1 empty directory to 1 empty directory under D:\_dev\pfh\modules\pfh-cms-
lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\blocks\lucene\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\lucene-block.jar

cocoon-block-naming-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\naming\dest

cocoon-block-naming-compile:
Compiling 3 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\naming\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\naming-block.jar

cocoon-block-profiler-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\profiler\dest

cocoon-block-profiler-compile:
Compiling 9 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\profiler\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\profiler-block.jar

cocoon-block-proxy-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\proxy\dest

cocoon-block-proxy-compile:
Compiling 4 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\proxy\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\proxy-block.jar

cocoon-block-querybean-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\querybean\dest

cocoon-block-querybean-compile:
Compiling 5 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\b
uild\cocoon-2.1.8\blocks\querybean\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\querybean-block.jar

cocoon-block-serializers-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\serializers\dest

cocoon-block-serializers-compile:
Compiling 19 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\
build\cocoon-2.1.8\blocks\serializers\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\serializers-block.jar

cocoon-block-validation-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\validation\dest

cocoon-block-validation-compile:
Compiling 23 source files to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\
build\cocoon-2.1.8\blocks\validation\dest
Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo
n-2.1.8\blocks\validation\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\validation-block.jar

cocoon-block-xsltal-prepare:
Created dir: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1
.8\blocks\xsltal\dest

cocoon-block-xsltal-compile:
Copying 1 file to D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoo
n-2.1.8\blocks\xsltal\dest
Building jar: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.
1.8\blocks\xsltal-block.jar

cocoon-block-forms-roles:
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-binding.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-cache.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-datatype.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-expression.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-form.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-selection-lists.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-validators.xroles
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\forms\
conf\forms-widgetlisteners.xroles
Writing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\c
lasses\org\apache\cocoon\cocoon.roles

cocoon-block-xsp-roles:
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\xsp\co
nf\xsp.xroles
Writing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\c
lasses\org\apache\cocoon\cocoon.roles

cocoon-block-session-fw-roles:
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\sessio
n-fw\conf\session.xroles
Writing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\c
lasses\org\apache\cocoon\cocoon.roles

cocoon-block-databases-roles:
Processing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\src\blocks\databa
ses\conf\db-modules.xroles
Writing: D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\c
lasses\org\apache\cocoon\cocoon.roles

BUILD FAILED
D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\tools\targets\compile-build.x
ml:254: The following error occurred while executing this line:
D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\temp\block
s-build.xml:1459: The following error occurred while executing this line:
D:\_dev\pfh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\temp\block
s-build.xml:172: FileNotFoundException: java.io.FileNotFoundException: D:\_dev\p
fh\modules\pfh-cms-lenya\src\cocoon-2.1.8\build\cocoon-2.1.8\classes\org\apache\
cocoon\cocoon.roles (The requested operation cannot be performed on a file with
a user-mapped section open)

Total time: 51 seconds

What am i missing?

10x for your help
Stefan
Giacomo Pati | 3 Jan 2006 12:01
Picon
Favicon

Re: [2.2] Problems with JMX Support and Tomcat


On Mon, 2 Jan 2006, Sumit wrote:

> Date: Mon, 2 Jan 2006 21:15:32 +0530
> From: Sumit <sumit.sanwal <at> patni.com>
> Reply-To: users <at> cocoon.apache.org, sumit.sanwal <at> patni.com
> To: users <at> cocoon.apache.org
> Subject: [2.2] Problems with JMX Support and Tomcat
> 
> I'm trying to get the latest 2.2 running in a standard tomcat 5.5.12
>
> With the default webapp, the following class can't be found:
>
> org.mortbay.log.LogFactory
>
> So it seems that the jetty-jmx-5.1.8.jar does not contain all required
>
> classes. Copying also jetty-5.1.8.jar into WEB-INF/lib of course solves
>
> this problem.

Yes, the problem is known and JMX support is experimental and brand new. 
We are trying to solve this as soon as possible.

Sorry for the inconvenience.

--

-- 
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
Geert Josten | 3 Jan 2006 12:38
Picon

Re: Problem writing generator

What serializer are you using? Perhaps the problem is elsewhere. Your first code snippet looks okay 
to me...

Cheers,
Geert

Marcel Rouwenhorst wrote:
> Thanks Geert for answering! 
> 
> 
> I do use the startPrefixMapping and endPrefixMapping
> 
> This are the two source code examples I tried: 
> 
> 1 ----------------------
> 
> handler.startPrefixMapping("i18n", I18nTransformer.I18N_NAMESPACE_URI);
> 
> AttributesImpl attr = new AttributesImpl();
> attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "key",
> "i18n:" + "key", "some_key");
> 
> handler.startElement(null, "exception", "exception", null);
> handler.startElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
> "i18n:text", attr);
>         
> handler.endElement(I18nTransformer.I18N_NAMESPACE_URI, "text",
> "i18n:text");
> handler.endElement(null, "exception", "exception");
> 
> handler.endPrefixMapping("i18n");
> 
> This example creates the following xml:
> <exception>
> 	<i18n:text i18n:key="some_key"/>
> </exception>
> 
> 2---------------------
> 
> If I change the following 2 lines 
> 
> handler.startPrefixMapping("xmlns", I18nTransformer.I18N_NAMESPACE_URI);
> 
> attr.addCDATAAttribute(I18nTransformer.I18N_NAMESPACE_URI, "i18n",
> "xmlns:i18n", I18nTransformer.I18N_NAMESPACE_URI);
> 
> This example creates the following xml:
> <exception>
> 	<i18n:text xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"/>
> </exception>
> 
> You can see that there are 2 i18n:text
> xmlns:i18n="http://apache.org/cocoon/i18n/2.1" 
> I get an error "XML Parsing Error: duplicate attribute"
> 
> Thank you,
> Marcel
> 
> 
> -----Oorspronkelijk bericht-----
> Van: Geert Josten [mailto:Geert.Josten <at> daidalos.nl] 
> Verzonden: dinsdag 3 januari 2006 10:08
> Aan: users <at> cocoon.apache.org
> Onderwerp: Re: Problem writing generator
> 
> Are you using startPrefixMapping and endPrefixMapping to register the
> i18n namespace?
> 
> Kind regards,
> Geert
> 
> Marcel Rouwenhorst wrote:
> 
> 
>>Hi,
>>
>> 
>>
>>I have a problem writing a generator. I want to write a generator for 
>>exception handling. It should work something like the exception
> 
> generator.
> 
>>The generator should create an output that looks like this
> 
> (simplified):
> 
>> 
>>
>><exception xmlns:i18n="http://apache.org/cocoon/i18n/2.1">
>>
>><i18n:text i18n:key="some_key">test</i18n:text>
>>
>></exception>
>>
>> 
>>
>>I get everything right except I can't create 
>>xmlns:i18n="http://apache.org/cocoon/i18n/2.1" in the exception tag or
> 
> 
>>any other tag.
>>
>> 
>>
>>I use the org.xml.sax.ContentHandler to create the xml. In the same
> 
> way 
> 
>>as the exception generator does.
>>
>> 
>>
>>Help is appreciated
>>
>> 
>>
>>Marcel
Bertrand Delacretaz | 3 Jan 2006 12:46
Picon
Favicon
Gravatar

Re: Problem writing generator

Le 3 janv. 06, à 10:40, Marcel Rouwenhorst a écrit :

> ...This example creates the following xml:
> <exception>
> 	<i18n:text i18n:key="some_key"/>
> </exception>...

How are you looking at this? I think your code is correct, so maybe 
it's your view of the generated XML that is wrong?

Using the "view source" function of a browser might not show you the 
namespace declarations - saving the output with wget and looking at the 
saved file is more precise.

-Bertrand
Attachment (smime.p7s): application/pkcs7-signature, 2410 bytes

Gmane