Bug 724727 (BRMS-587) - BRMS allows creation of rulename that WebDav won't upload
Summary: BRMS allows creation of rulename that WebDav won't upload
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-587
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.1.0 GA
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-09 13:30 UTC by Rick Wagner
Modified: 2011-05-09 17:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
5.x BRMS
Last Closed: 2011-05-09 17:18:09 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-587 0 Minor Closed BRMS allows creation of rulename that WebDav won't upload 2012-10-09 01:17:42 UTC

Description Rick Wagner 2011-05-09 13:30:09 UTC
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000007AHUR&sfdc.override=1
Steps to Reproduce: Make a package with dots in the name.  Try to use WebDav to move something.
Workaround: Workaround Exists
Workaround Description: Don't use dots in package names.
securitylevel_name: Public

BRMS allows creation of package names that contain dots (.).  Example:  my.dotted.packagename.

WebDav will not transfer packages named in this way.

Please correct the inconsistency on one side or the other.  Note that we have at least one customer that prefers to use package names with dots in them.

Note:  Customer in referenced ticket (00456869) offers suggestions for remedies.

Comment 1 Tihomir Surdilovic 2011-05-09 13:51:39 UTC
In the Guvnor UI we can split the package String in the dot (.) and create nested packages if needed. I am not sure at all from reading the support case and this Jira info, how the customer is using the Guvnor Eclipse plugin at all. Seems they are using straight WebDav api with custom code so I am not sure what should/can be changed on our end? Please explain further.



Comment 2 Rick Wagner 2011-05-09 17:17:32 UTC
Thanks, Tiho.  I see what you're saying and agree, this is in the customer's use of the WebDav API.  I'll close the JIRA.


Note You need to log in before you can comment on or make changes to this bug.