Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015675Openbravo ERP09. Financial managementpublic2011-01-17 09:472011-02-22 12:20
Reporterjonalegriaesarte 
Assigned Tojonalegriaesarte 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version2.50MP25 
Target Version2.50MP27Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0015675: In bank statement, create lines from the business partner selector does not work fine if you search for the character ñ
DescriptionIn bank statement, create lines from the business partner selector does not work fine if you search for the character ñ
Steps To Reproduce- Master Data Management || Business Partner
- Create a new business partner. The name must include the character ñ
- Financial Management || Receivables & Payables || Transactions || Bank Statement
- Create a new header
- Create lines from
- Search for ñ in the business partner selector
- Note that a strange character appears in the name field if you click the business partner selector button or in the value field if you press enter.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0016055 closed jpabloae Tomcat connector not properly configured 
blocks defect 0015936 closed jonalegriaesarte In bank statement, create lines from the business partner selector does not work fine if you search for the character ñ 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-01-17 09:47jonalegriaesarteNew Issue
2011-01-17 09:47jonalegriaesarteAssigned To => adrianromero
2011-01-17 09:47jonalegriaesarteModules => Core
2011-01-17 09:47jonalegriaesarteOBNetwork customer => Yes
2011-01-17 09:49jonalegriaesarteIssue Monitored: networkb
2011-02-09 12:17shuehnerIssue Monitored: shuehner
2011-02-09 13:27adrianromeroTarget Version2.50MP26 => 2.50MP27
2011-02-10 16:30adrianromeroStatusnew => scheduled
2011-02-10 16:30adrianromerofix_in_branch => pi
2011-02-10 16:31adrianromeroAssigned Toadrianromero => jonalegriaesarte
2011-02-10 16:31adrianromeroTypedefect => backport
2011-02-10 16:31adrianromerofix_in_branchpi =>
2011-02-10 16:31adrianromeroIssue cloned0015936
2011-02-10 16:31adrianromeroRelationship addedblocks 0015936
2011-02-22 12:20adrianromeroNote Added: 0034306
2011-02-22 12:20adrianromeroStatusscheduled => closed
2011-02-22 12:20adrianromeroResolutionopen => no change required
2011-02-22 12:23adrianromeroNote Edited: 0034306bug_revision_view_page.php?bugnote_id=0034306#r1516
2011-02-25 11:14adrianromeroRelationship addedrelated to 0016055

Notes
(0034306)
adrianromero   
2011-02-22 12:20   
(edited on: 2011-02-22 12:23)
This is a configuration problem of the Tomcat AJP/1.3 connector.

This issue is only reproducible when using the stack Apache + mod_jk + Tomcat and to fix it is needed to add the parameter:

 URIEncoding="utf-8"

To the Tomcat AJP/1.3 connector that is defined in the file conf/server.xml situado en CATALINA_BASE.

This way the connector definition should be similar to this:

    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" URIEncoding="utf-8"/>