You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "John Kaputin (JIRA)" <ji...@apache.org> on 2007/03/29 15:56:26 UTC
[jira] Resolved: (WODEN-148) HTTPLocation not parsed correctly
[ https://issues.apache.org/jira/browse/WODEN-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Kaputin resolved WODEN-148.
--------------------------------
Resolution: Fixed
Fix Version/s: M8
HTTPLocation now parses valid location string correctly. I have opened a new JIRA WODEN-155 to implement the EBNF grammar that will correctly determine how to identify invalid location strings.
> HTTPLocation not parsed correctly
> ---------------------------------
>
> Key: WODEN-148
> URL: https://issues.apache.org/jira/browse/WODEN-148
> Project: Woden
> Issue Type: Bug
> Reporter: Keith Godwin Chapman
> Assigned To: John Kaputin
> Fix For: M8
>
> Attachments: diff.txt, diff.txt, patch.txt
>
>
> This occurn in RawParameterEndpoint of LocationTemplate-2G. I instantiated the HTTPLocation class with axis2/services/ProbeDataService.RawParameterEndpoint/RawParameter{!fragment} as the input parameter. But the httpLocation.getLocalNames(); returns an empty array. When the same argument is given with the ! mark removed it gives the expected result.
> Also it would be nice if HTTPLocation class can implement CR 117 too.
> Thanks,
> Keith.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org