Jens, 1.1 has serious issues (see bug #17017) which are unfixed. I'm running into the same encoding issues in 1.1RC2, but can't upgrade because 1.1 doesn't work (and I can't release my software with alpha-quality dependencies). Is there a patch I can apply to 1.1RC2 to fix encoding issues? Better yet, I'd love to see someone fix the nested-beans problem once and for all so I can actually use the production level release of Axis. - Navneet
-----Original Message----- From: Jens Schumann [mailto:[EMAIL PROTECTED] Sent: Thursday, January 29, 2004 2:55 PM To: Axis User; Michael Serero Subject: Re: Character encoding 1.1 RC1 encoding is horribly broken. Please use at least 1.1, or better current 1.2 Alpha. Jens On 1/29/04 10:01 PM Michael Serero <[EMAIL PROTECTED]> wrote: > I found the release-note file in my axis installation. > I am using 1.1 RC1. > > I will try 1.2 Alpha. I am hesitant to upgrade to 1.2 because we are > finishing a QA cycle on our app. > > Michael > > -----Original Message----- > From: Michael Serero [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 29, 2004 12:39 PM > To: [EMAIL PROTECTED] > Subject: RE: Character encoding > > > Jens, > > I tend to aggree with you. That doesn't look like the right way of fixing > it. > However I am lucky because my app only reads/write XML files in UTF-8 > encoding. > > I have a silly question though: How do I check the version of my axis > installation. I use JBuilder and I did not explicitly performed the Axis > installation, JBuilder did. The directory name used does not give me any > clue about the version level. I could well be using axis 1.1 > > Michael > > -----Original Message----- > From: Jens Schumann [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 28, 2004 1:59 PM > To: Axis User > Subject: Re: Character encoding > > > On 1/28/04 8:57 PM Michael Serero <[EMAIL PROTECTED]> wrote: > >> Soniya, >> >> You are a star! You made my day! >> > > To be honest, this sounds like a dirty workaround and might introduce a lot > of other problems (while reading files which aren't UTF-8, because they were > written by non java applications). Do you guys use axis 1.1. or current 1.2? > The latter has fixed one encoding problem, and should not require your > workaround. > > Jens > >
