[
https://issues.apache.org/jira/browse/AXIS2-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719151#action_12719151
]
Glen Daniels commented on AXIS2-3084:
-------------------------------------
I can relate to your way of thinking, Andreas, but in this case I still think
doing a case-insensitive search would be better for our users. Clearly there
have already been at least a few occasions (even in some of our own stuff)
where we've stumbled across this, and it makes simple typing/memory errors when
editing config files much less egregious. Let me ask it another way - what's
the downside to allowing "<inflow>" as well as "<InFlow>"?
This is pretty much "be liberal in what you receive" except this time it's what
we're receiving from the config file rather than a wire message.
> Should make inflow/outflow (at least) case insensitive in module.xml
> --------------------------------------------------------------------
>
> Key: AXIS2-3084
> URL: https://issues.apache.org/jira/browse/AXIS2-3084
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Reporter: Glen Daniels
> Assignee: Glen Daniels
> Priority: Minor
>
> Currently the <InFlow> and <OutFlow> elements in module.xml must read EXACTLY
> that way - in particular <inflow> and <outflow> will not be recognized.
> We should make the read of these elements (ModuleBuilder:160 onwards)
> case-insensitive, IMO, to make things easier on the developer. <inflow> or
> <INFLOW> shouldn't fail silently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
