Bug 724763 (BRMS-601)

Summary:	Add info about URIEncoding for multibyte characters WebDAV issue
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Toshiya Kobayashi <tkobayas>
Component:	Documentation	Assignee:	lcarlon <lcarlon>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Len DiMaggio <ldimaggi>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.1.0 GA	CC:	atangrin, lcarlon, lpetrovi, rwagner
Target Milestone:	---
Target Release:	BRMS 5.2.0.GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/BRMS-601
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-17 00:03:45 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Toshiya Kobayashi 2011-06-08 09:00:44 UTC

Affects: Documentation (Ref Guide, User Guide, etc.)
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007BhZE&sfdc.override=1
securitylevel_name: Public

Drools/Guvnor supports any UTF-8 character as part of rule name, but when using WebDAV access, the multibyte characters in the URL are decoded as ISO-8859-1 by default. It will end up with 404.

You can work around it by adding URIEncoding attribute in Connector settings in server.xml.

{noformat}
      <Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}" 
               connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" />
{noformat}

Here is a knowledgebase article for this issue.
https://access.redhat.com/kb/docs/DOC-57339

Our consultant requested to have this info in BRMS docs as well.

Comment 1 Toshiya Kobayashi 2011-06-08 09:09:37 UTC

Link: Added: This issue relates to BRMS-602

Comment 2 Toshiya Kobayashi 2011-06-08 09:09:38 UTC

Linked BRMS-602 which requests to have URIEncoding out-of-the-box

Comment 3 Anne-Louise Tangring 2011-08-01 15:20:46 UTC

Needs an update to JBDS.

Comment 4 Rick Wagner 2011-08-25 20:02:15 UTC

Note this BZ is associated with 2 SF cases.  Still, GSS prioritizes 'low'.

Comment 5 Rick Wagner 2011-08-25 20:07:21 UTC

(In reply to comment #4)
> Note this BZ is associated with 2 SF cases.  Still, GSS prioritizes 'low'.

Last comment is in error.  Actually, there are 2 BZs associated with a single SF case.  The case does not have a customer that is stuck, a workaround is documented, so 'low'.

The other BZ is 724764.

Comment 6 lcarlon 2011-08-29 03:19:18 UTC

The work around has been added to the User Guide and will be live on the internal doc stage shortly.

The content is in the form of a note that advises customers Red Hat does not recommend using special characters in rule names, and then goes on to provide the steps to enable unicode support.

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html-single/BRMS_User_Guide/index.html#sect-guvnor_connection_wizard

Comment 7 lcarlon 2011-09-05 05:01:06 UTC

Update.

I have removed the above content. The changes are now located in the webDAV section of the Integration chapter:

http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_BRMS_Platform/5/html/BRMS_User_Guide/ch08.html#WebDav_Unicode

Lee

Comment 8 Lukáš Petrovický 2011-09-30 09:51:42 UTC

Thanks, VERIFIED.