No, we shouldn't reject this issue.
There are two aspects to this
- us being able to consume an external WSDL which we do not control
- us being able to produce a WSDL for external use
The part which this issue refers to is the first, the part where BP is important (to us) is the second.
We need to be able to read external WSDLs in different character sets, irrespective of the BP, as these are not under our control and may not be under the control of whoever is using the ESB.
As far as working out the charset is concerned, I do not believe we can rely on that library (as appealing as it may be). It cannot guarantee to get the right result, just to make a 'best guess'. In essence we end up in the same position as we are now, after all we are 'guessing' at UTF-8, just with an algorithm providing the guess.
In my opinion we should be trying to determine the character set based by trusting whatever is specified on the input so, if it is something like http then we should be able to trust the content type. If this cannot be trusted, or if it does not exist (such as local wsdl), then we should assume UTF-8 *unless* the developer overrides the type.
Once we have it in a string representation then we are free to output this in UTF-8.
Kev