Hi all,
Just wanted to have a short discussion on an issue that I wasted quite some
hours on. Let me first explain that I configured my cocoon block with
following two properties as per http://cocoon.apache.org/2.2/1366_1_1.html :
org.apache.cocoon.containerencoding=UTF-8
,
formEncoding);
return env;
}
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Wednesday, June 06, 2012 1:10 PM
To: dev@cocoon.apache.org; us...@cocoon.apache.org
Subject: issue with form encoding C2.2
Hi all,
Just wanted to have a short discussion on an issue
]
*Sent:* Wednesday, June 06, 2012 1:10 PM
*To:* dev@cocoon.apache.org; us...@cocoon.apache.org
*Subject:* issue with form encoding C2.2
** **
Hi all,
** **
Just wanted to have a short discussion on an issue that I wasted quite
some hours on. Let me first explain that I configured
the spring
configurator and I suspect this will confirm the issue. Will get back on this
today.
Robby
From: Javier Puerto [mailto:jpue...@gmail.com]
Sent: Wednesday, June 06, 2012 1:23 PM
To: dev@cocoon.apache.org
Subject: Re: issue with form encoding C2.2
Hi Robby,
Maybe it's helps
]
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Wednesday, June 06, 2012 1:27 PM
To: dev@cocoon.apache.org
Subject: RE: issue with form encoding C2.2
Hi Javier,
I read about default encoding for using GET, but I’m actually ‘posting’ the
form. I really am convinced that the only real
to quickly test a block using maven-jetty-plugin.
Robby
From: Robby Pelssers [mailto:robby.pelss...@nxp.com]
Sent: Wednesday, June 06, 2012 1:37 PM
To: dev@cocoon.apache.org
Subject: RE: issue with form encoding C2.2
One step closer to proving the issue:
The SettingsBeanFactoryPostProcessor.java preInit
