Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Received-SPF: pass (nike.apache.org: domain of lukas.vlcek@gmail.com
 designates 209.85.213.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1324210922.3776.57.camel@ubuntu>
References: 
 <CAO9cvUYdJjXRUtco1L6fMCCyrYByxx6MZu=+UhFeCbdV+g4Bxg@mail.gmail.com>
 <1323436816.21905.28.camel@ubuntu>
 <CAO9cvUbtNLgHO-1KN7jjfMs2dEXTEN1KqNiFjcgzGOJx1KwmoA@mail.gmail.com>
 <1323697054.3776.4.camel@ubuntu>
 <CAO9cvUaOVYvL9bfE7Y_GLsmfrL4=zJ=uc_KQGHiUfBCJXp10Hw@mail.gmail.com>
 <1323698968.3776.10.camel@ubuntu>
 <CAO9cvUYSEv2WcLqyME98to9kkcCKpqcUGrWjYe_P07kKUK_9aw@mail.gmail.com>
 <1323701915.3776.27.camel@ubuntu>
 <CAO9cvUYOvaxjmFo8kmUJV80c2o4_D08mhR-bz6TbndqwGpG5FA@mail.gmail.com>
 <1323703433.3776.28.camel@ubuntu>
 <CAO9cvUYtM-0BgQBGZaA9+0OO3wp4Jg3U+DeVbdudXWWLw3+Qsg@mail.gmail.com>
 <CAO9cvUYFPkKEsFNw2ypU3mGrgg0MOUzZ7DDwg+Ez8t36L8JxjA@mail.gmail.com>
 <1323951362.12084.8.camel@ubuntu>
 <CAO9cvUY0+a-tVLFuqdrxyms6tNkcSv4n=wVj=qaAxk6yORdxXQ@mail.gmail.com>
 <CAO9cvUau=fhL0GmrcCuJ1y=gDRXTfk_Uquv-FRfT87HKJ05RuQ@mail.gmail.com>
 <CAHVBJ+=h63VqQK1R+zevzUJ51L6MzXyAJ=XMTV0rgTfJ+HgEbQ@mail.gmail.com>
 <CAO9cvUYrLdGJQp7Jo8scJkPOV6pDuyOvMiN7_pv4M9GGQEWCwg@mail.gmail.com>
 <CAO9cvUb73SrdHK=UmmuEWTyQ3Y5e7h2LPiY3c5h6pae5pcaocQ@mail.gmail.com>
 <CAHVBJ+nPuvYwU3X7NNSE7HyNL30dLFucRO2tg3TncFjUALFh8A@mail.gmail.com>
 <CAO9cvUbip=TNQURYunBq+JPAtOD0U1_JAuL+ECPz7EEmE3x8vg@mail.gmail.com>
 <CAHVBJ+kZRvEXaMRLpn-VR6LjZyzs1nd6_c1h4Vr+N5DQgdZRGQ@mail.gmail.com>
 <1324126539.3776.40.camel@ubuntu>
 <CAO9cvUaPLjGb9-S078WeeQmwrUvaMWYYcZ50W2q2NO0Cr=sUPw@mail.gmail.com>
 <CAO9cvUZ4-ObzkX8L8CUMVPERMf55DYYhyUP2KXkba8gNU78Orw@mail.gmail.com>
 <CAHVBJ+neTOtUZ3qQGA-OhuH4JxeUqWgLj7gKSSJgZoZ0fTp_5g@mail.gmail.com>
 <1324210922.3776.57.camel@ubuntu>
From: =?UTF-8?B?THVrw6HFoSBWbMSNZWs=?= <lukas.vlcek@gmail.com>
Date: Mon, 19 Dec 2011 11:21:39 +0100
Message-ID: 
 <CAO9cvUbJpRSM44MfnzUQFh=EUmH9BdSmuqU_HtVTShqX5=k9Bw@mail.gmail.com>
Subject: Re: Switching from 0.6 to 0.7.1 - address parsing, CRLF issues
To: mime4j-dev@james.apache.org
Content-Type: multipart/alternative; boundary=20cf305639e932146704b46f523a

--20cf305639e932146704b46f523a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks,

this helped me.

Regards,
Lukas

On Sun, Dec 18, 2011 at 1:22 PM, Oleg Kalnichevski <olegk@apache.org> wrote=
:

> On Sun, 2011-12-18 at 12:57 +0100, Stefano Bagnara wrote:
> > 2011/12/18 Luk=C3=A1=C5=A1 Vl=C4=8Dek <lukas.vlcek@gmail.com>:
> > > Hi again,
> > >
> > > there is another difference between 0.6 and 0.7.1
> > >
> > > It happens when I need to parse message with weird charset 'x-gbk'.
> > >
> > > I added a new test case into my github repo for both 0.6 and 0.7.1
> versions.
> > > Basically the problem happens when I try to get Reader from the
> TextBody:
> > >
> > > Message message =3D getMessage(....);
> > > TextBody body =3D (TextBody) message.getBody();
> > > body.getReader(); // here the exception is fired
> > >
> > > It worked fine in 0.6 but it yields UnsupportedEncodingException in
> 0.7.1
> > > which is quite unfortunate because I do not see way how to extract bo=
dy
> > > content from it in this case (as I need to get the Reader first).
> > >
> > > Here are examples:
> > > 0.6
> > >
> https://github.com/lukas-vlcek/mime4j-test/blob/backto06/src/test/java/or=
g/mime4j/test/BasicTest.java#L134
> > > 0.7.1
> > >
> https://github.com/lukas-vlcek/mime4j-test/blob/workaround/src/test/java/=
org/mime4j/test/BasicTest.java#L134
> > >
> > > Any idea hot to deal with this situation?
> > >
> > > Note, I understand that 'x-gbk' is unknown charset for JVM but even i=
n
> such
> > > case I was able to extract the body content by forcing 'gbk' charset
> > > instead into my utility classes in 0.6, however, with 0.7.1 I am
> unable to
> > > do it because the very basic body.getReader call fails... is there an=
y
> > > workaround how to get the body Reader and not to get the exception?
> >
> > Please open a JIRA issue, attach your test case and the stack trace of
> > the exception you get.
> > I guess we can classify this as a bug because we want to give users a
> > way to deal with malformed stuff, so also unrecognized charsets.
> >
> > I don't know if we already have an existing workaround but the JIRA
> > issue will anyway help keeping track of the issue for future users.
> >
> > Stefano
>
>
> There's no need to raise a JIRA, because basically there is no issue.
> #getReader is merely a convenience method. One can always use
> #getInputStream() to get raw data stream and apply whatever charset
> encoding.
>
> Luk=C3=A1=C5=A1, what is wrong with that?
>
> ---
> Message message =3D
> ParserUtil.getMessage(getInputStream("mbox/jboss-as7-dev-01.mbox"));
>
> assertTrue(message.getBody() instanceof TextBody);
> TextBody body =3D (TextBody) message.getBody();
>
> String charset =3D message.getCharset();
> if (charset.equalsIgnoreCase("x-gbk")) {
>    charset =3D "gbk";
> }
> Reader reader =3D new InputStreamReader(body.getInputStream(), charset);
> ---
>
>
>

--20cf305639e932146704b46f523a--