[ 
https://issues.apache.org/jira/browse/AXIS2-2668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499765
 ] 

U. Suran Jayathilaka commented on AXIS2-2668:
---------------------------------------------

A trim() call is being made already where the actionMapping is processed. 
Although,  as of now, a trim() call while getting <parameter> text will not be 
added.(Since it's necessary to allow for parameters that do have meaningful 
whitespace.)

> CLONE -whitespaces are not trimmed in services.xml
> --------------------------------------------------
>
>                 Key: AXIS2-2668
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2668
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 1.0
>            Reporter: Antoni Jakubiak
>            Assignee: Deepal Jayasinghe
>
> If there are whitespaces used in services.xml such as <actionMapping> like:
>       <service name="FileService">
>                  ...
>               <operation ...>
>                       <actionMapping>
>                                  http://foo.com/FileService/upload
>                         </actionMapping>
>               </operation>
>       </service>
> Then those whitespaces will be included as the action URI. When the client 
> uses the URI without whitespaces as the WSA action, it will fail to look up 
> the service. Similar situations exist for other elements like <parameter>.
> I find that you're explicitly calling trim() at places where it's needed (eg, 
> trimming the ServiceClass parameter before loading the class). This is a very 
> dangerous practice. Isn't it possible to ignore all ignorable whitespaces? 
> For example, something like 
> http://www.jdom.org/pipermail/jdom-interest/2004-December/014464.html

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to