This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Suggest Utilities.{,un}escapeForFilename | ||
|---|---|---|---|
| Product: | platform | Reporter: | Jesse Glick <jglick> |
| Component: | -- Other -- | Assignee: | issues@platform <issues> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | jtulach, mslama, pzavadsky, tor |
| Priority: | P3 | Keywords: | API |
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 8713, 16479 | ||
| Bug Blocks: | 27494 | ||
Target milestone -> 3.3.1. The code in WindowsUtil can disappear now, because InstanceDataObject has new method create (..., true) to ensure that new object will be really created. So the (un)escape might not be needed at all. But it's needed in many other places too. Last time I looked I found multiple places where code was trying to escape and unescape characters. And I need it for my own code (which writes XML and parses XML files). Having this code in a single place makes it more likely that it will work, since it's hard to know which meta characters need to be escaped across -all- OS's (I remember VMS had some surprising ones). Since the IDE has a heavy XML bent (with its layers etc.) I think it's important to provide methods to write arbitrary data to XML and read them back without worrying about errors. There also exist another copy of this escape method in ExJarFileSystem. Set target milestone to TBD Set target milestone to TBD passing to Radek. Peter just added this same code to org.netbeans.core.naming.Utils. IDO.escapeAndCut is apparently also used from window system. Yes PersistenceManager uses InstanceDataObject.escapeAndCut and unescape. Should be fixed as this issue is solved. Was just perusing the reflection code that does this (still) in the window system code. Any chance of addressing it? Reassigning to new module owner jskrivanek. |
Which would basically be the same as the current InstanceDataObject.{,un}escape but publically accessible. The code is already duped in core's WindowUtils and people have asked for it in other places too. There is a test written already.