Bug 1062289 - Create new Package dialog displays no warning when using " in package name
Summary: Create new Package dialog displays no warning when using " in package name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BRMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ER2
: 6.0.1
Assignee: manstis
QA Contact: Jiri Locker
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-06 15:21 UTC by Zuzana Krejčová
Modified: 2016-08-01 01:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:58:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
New package popup warning when quote in name (20.81 KB, image/png)
2014-02-26 11:32 UTC, manstis
no flags Details
New package popup warning when slash in name (20.92 KB, image/png)
2014-02-26 11:33 UTC, manstis
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1006506 0 high CLOSED File name validation broken 2021-02-22 00:41:40 UTC

Internal Links: 1006506

Description Zuzana Krejčová 2014-02-06 15:21:36 UTC
Description of problem:
When creating a new package, the Create new Package dialog will not display any warning when using " in the package name. It does give warnings on other illegal characters though.
Although there is no warning, the package is not created and it seems as if simply nothing happened when clicking Ok.


Version-Release number of selected component (if applicable):
BPMS 6.0 CR2

Comment 1 Zuzana Krejčová 2014-02-07 09:59:04 UTC
Same thing happens with slash (\). Other invalid chars seem to produce a warning, as expected.

Comment 2 manstis 2014-02-26 11:32:41 UTC
Created attachment 867934 [details]
New package popup warning when quote in name

Comment 3 manstis 2014-02-26 11:33:03 UTC
Created attachment 867935 [details]
New package popup warning when slash in name

Comment 4 manstis 2014-02-26 11:33:59 UTC
Please see attached. I cannot replicate.

Can you please retest with next release (or advise if I've done something wrong).

Thanks,

Mike

Comment 5 Zuzana Krejčová 2014-02-28 13:07:34 UTC
(In reply to manstis from comment #4)
> Please see attached. I cannot replicate.
> 
> Can you please retest with next release (or advise if I've done something
> wrong).
> 
> Thanks,
> 
> Mike

Colleague came up with the probable reason for this - is it possible that the input is not escaped properly before being sent?

'a\b' works, 'a\\' as well, but e.g. 'a\s' does not. 'a\"' works as well.

For 'a"b', I get the following from error console in the browser:
uncaught exception: com.google.gwt.json.client.JSONException: Error parsing JSON: SyntaxError: JSON.parse: expected ':' after property name in object
And for 'a\s', I get this:
uncaught exception: com.google.gwt.json.client.JSONException: Error parsing JSON: SyntaxError: JSON.parse: bad escaped character


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