| Summary: | REST binding browse button returns the wrong value | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Joseph Vincens <jvincens> |
| Component: | EDT | Assignee: | Tony Chen <chenzhh> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdlwuxin, chenzhh, jspadea |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Joseph Vincens
Joe - can the user specify anything they want (spaces, slashes, etc) for the bindingKey property of @Resource? If so then we should not prevent such characters from being manually entered. I think that we should only remove invalid identifier characters when we default the binding name (like with the SQL binding wizard). Justin is correct, if the user wants to use @Resource{bindingKey="mm nn%@/"} that is legal so we should not add any validation to this page, we should simply remove the button.
The browse button has been removed, and we also now validate that the binding name is not blank. Modified: NewWizardMessages.java NewWizardMessages.properties RestBindingWizardPage.java verified verified |