That's what I would assume too, but why all of a sudden, does ldap complain. If I build with T3 instead of T4, ldap is fine.
This is a very weird problem that I've been banging my head over all day, and I'm stumped. We're about to put our migration plans on hold... Frank Russo Senior Developer FX Alliance, LLC > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Ron Piterman > Sent: Tuesday, December 13, 2005 4:20 PM > To: [email protected] > Subject: Re: Character Encoding on form submit > > > I doubt it, since, as far as I understand, encoding is just an issue > between the browser and the http server. if you debug, you > probably pass > some java strings to the LDAP, which are, afaik, encodingless. > > Frank Russo wrote: > > I have an application written in Tapestry 3. On a simple > form submit, > > we are creating a new user and putting that user into an LDAP store. > > > > I'm in the process of upgrading the app to T4, but > something weird is > > happening. When the form is submitted, I'm getting an LDAP > exception. > > None of the code has changed yet. I just upgraded to T4. I > changed a > > few components and other things that were complaining about being > > deprecated, but the LDAP code has not changed at all. The > error code > > is a bit cryptic, but it seems to mean that LDAP got > something that is > > wasn't expecting. > > > > The only thing I can think of is the character encoding. > What is the > > difference between T3 and T4? I know the default in T4 is UTF-8. I > > tried adding this to the .application file, which I found > in another > > post, but it didn't work: > > > > <meta key="org.apache.tapestry.template-encoding" > > value="ISO-8859-1"/> > > <meta key="org.apache.tapestry.output-encoding" > > value="ISO-8859-1"/> > > > > Any ideas? > > > > Thanks... > > Frank Russo > > Senior Developer > > FX Alliance, LLC > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
