2008/11/19 jhomuth <[EMAIL PROTECTED]>:
> Hi for the third time,
>
> I've also no ideas. The only thing what I can image is that somewhere in the
> MyFaces implementation
> the magic methods
>
> FacesContext context = FacesContext.getCurrentInstance();
> Map<String, Object> requestScope =
> context.getExternalContext().getRequestMap();
>
>
> will be called. But I guess there will be no way to get around this
> issue?!?.
any filter that queries the request param could be the issue to.
however, you said you just added the extra cfg param to web.xml
>
>
> Matthias Wessendorf wrote:
>>
>> 2008/11/19 jhomuth <[EMAIL PROTECTED]>:
>>
>>>
>>> Hi again,
>>>
>>> I've to made some adds. I've taken out every
>>> requestScope.get("javax.servlet.error.whatEverIWantToHave");* stuff, but
>>> the error still occurs. As I said before if I take the <error-page>
>>> definitions out of the web.xml it will work again.
>>>
>>
>> interesting. I am over asked atm.
>>
>> sorry,
>> matthias
>>
>>
>>>
>>> -J
>>>
>>>
>>>
>>> jhomuth wrote:
>>>
>>>>
>>>> Hi again,
>>>>
>>>> I wanted to display the exception type of the http error code to the
>>>> user
>>>> and that why I queried
>>>> the request map in this way.
>>>>
>>>> FacesContext context = FacesContext.getCurrentInstance();
>>>> Map<String, Object> requestScope =
>>>> context.getExternalContext().getRequestMap();
>>>> try {
>>>> * errorCode = (Integer)
>>>> requestScope.get("javax.servlet.error.status_code");*
>>>> } catch (Exception exc) {
>>>> log = Logger.getLogger(ErrorController.class.getName());
>>>> ......
>>>> ......
>>>>
>>>> And because that crashed the pageencoding I've tried to get the
>>>> parameter
>>>> directly in my error page.
>>>>
>>>> <h:outputText styleClass="h3" value="#{fields.errorOccured}! Typ :
>>>> #{requestScope['javax.servlet.error.status_code']} "/>
>>>>
>>>> Both methods worked, but the pageencoding went wrong
>>>>
>>>> -J
>>>>
>>>>
>>>> Matthias Wessendorf wrote:
>>>>
>>>>>
>>>>> 2008/11/19 jhomuth <[EMAIL PROTECTED]>:
>>>>>
>>>>>
>>>>>>
>>>>>> Hi List,
>>>>>>
>>>>>> I have another strange stuff for you.
>>>>>> My Myfaces (V.1.1.6) application has a wrong page encoding since I
>>>>>> defined
>>>>>> error pages in the web.xml file.
>>>>>> Before defining the error pages I was able to show characters like
>>>>>> "ä,ö,ü,ß..." on my site. Now, since I've added
>>>>>> error pages, they will be shown in this way ä -> ä and ß -> ß. It's
>>>>>> really
>>>>>> strange. Furthermore I get always such a waring.
>>>>>>
>>>>>> PWC4011: Unable to set request character encoding to UTF-8 from
>>>>>> context
>>>>>> /<context-path>, because request parameters have already been read, or
>>>>>> ServletRequest.getReader() has already been called
>>>>>>
>>>>>> You might know this message, I saw many of them in a lot of forums,
>>>>>> but
>>>>>> now
>>>>>> usefully answer yet.
>>>>>>
>>>>>>
>>>>>
>>>>> when query params from the request parameter map it isn't possible to
>>>>> set the encoding
>>>>> afterwards. That's what the msg says. So q is now, why do you query ?
>>>>> Or your error page ?
>>>>>
>>>>> -M
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> If I comment out the error page definitions all will work again! Do
>>>>>> you
>>>>>> now
>>>>>> why the pageencoding is so strange and how to fix that????
>>>>>>
>>>>>> --
>>>>>> Johannes Homuth
>>>>>>
>>>>>> -----------------------------------
>>>>>> SOURCEPARK Gesellschaft
>>>>>> für Softwareentwicklung mbH
>>>>>>
>>>>>> Johannes Homuth
>>>>>> Helmholtzstr. 2-9 Gebäude M
>>>>>> 10587 Berlin Tel: +49 (0)30/398 068 316
>>>>>> Fax: +49 (0)30/398 068 39
>>>>>> e-mail: [EMAIL PROTECTED]
>>>>>> www: www.sourcepark.de
>>>>>> -----------------------------------
>>>>>> Sitz der Gesellschaft: Berlin
>>>>>> Handelsregister: Amtsgericht Berlin-Charlottenburg, HRB 80254
>>>>>> Geschäftsführer: Matthias Barmeier, Harald Dürr
>>>>>> -----------------------------------
>>>>>> Diese E-Mail kann vertrauliche und/oder rechtlich geschützte
>>>>>> Informationen enthalten. Wenn Sie nicht der richtige Adressat
>>>>>> sind oder diese E-Mail irrtümlich erhalten haben, informieren
>>>>>> Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
>>>>>> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
>>>>>> E-Mail ist nicht gestattet.
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>> --
>>> Johannes Homuth
>>>
>>> -----------------------------------
>>> SOURCEPARK Gesellschaft
>>> für Softwareentwicklung mbH
>>>
>>> Johannes Homuth
>>> Helmholtzstr. 2-9 Gebäude M
>>> 10587 Berlin Tel: +49 (0)30/398 068 316
>>> Fax: +49 (0)30/398 068 39
>>> e-mail: [EMAIL PROTECTED]
>>> www: www.sourcepark.de
>>> -----------------------------------
>>> Sitz der Gesellschaft: Berlin
>>> Handelsregister: Amtsgericht Berlin-Charlottenburg, HRB 80254
>>> Geschäftsführer: Matthias Barmeier, Harald Dürr
>>> -----------------------------------
>>> Diese E-Mail kann vertrauliche und/oder rechtlich geschützte
>>> Informationen enthalten. Wenn Sie nicht der richtige Adressat
>>> sind oder diese E-Mail irrtümlich erhalten haben, informieren
>>> Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
>>> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
>>> E-Mail ist nicht gestattet.
>>>
>>>
>>
>>
>>
>>
>
>
> --
> Johannes Homuth
>
> -----------------------------------
> SOURCEPARK Gesellschaft
> für Softwareentwicklung mbH
>
> Johannes Homuth
> Helmholtzstr. 2-9 Gebäude M
> 10587 Berlin Tel: +49 (0)30/398 068 316
> Fax: +49 (0)30/398 068 39
> e-mail: [EMAIL PROTECTED]
> www: www.sourcepark.de
> -----------------------------------
> Sitz der Gesellschaft: Berlin
> Handelsregister: Amtsgericht Berlin-Charlottenburg, HRB 80254
> Geschäftsführer: Matthias Barmeier, Harald Dürr
> -----------------------------------
> Diese E-Mail kann vertrauliche und/oder rechtlich geschützte
> Informationen enthalten. Wenn Sie nicht der richtige Adressat
> sind oder diese E-Mail irrtümlich erhalten haben, informieren
> Sie bitte sofort den Absender und vernichten Sie diese E-Mail.
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser
> E-Mail ist nicht gestattet.
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
