Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hotfix proper jms message charset #200

Open
wants to merge 2 commits into
base: next
Choose a base branch
from

Conversation

privettoli
Copy link

Use charset from the JMS message or UTF-8 but never use defaultCharset (on Windows it's Win1252) when converting a text to bytes before sending to a broker.
I've found out that bug when our testers created a bug that our app produce symbols like ????? on the places of charset-specific symbols like German and French.

@privettoli
Copy link
Author

@spindelmanne, @erikryverling, please, review

@spindelmanne
Copy link
Contributor

Thanks for your contribution! We will review it and get back to you shortly.

@spindelmanne spindelmanne self-assigned this Sep 23, 2015
@spindelmanne
Copy link
Contributor

I just noticed you haven't signed our Contributor license agreement yet. You can download it from here:

https://dl.dropboxusercontent.com/u/81603711/SmartBear_Contributor_License_Agreement.pdf

Could you sign it and send it to us? This is just to let us use your solution in our commercial version without any legal issues.

@privettoli
Copy link
Author

@spindelmanne where should I send it?

@spindelmanne
Copy link
Contributor

You can just email a photo of the signed agreement to manne dot fagerlind at smartbear dot com.

@joeljons
Copy link
Contributor

joeljons commented Oct 1, 2015

I think he just did. Replace the dot with . and at with @

@privettoli
Copy link
Author

@spindelmanne I've sent. Can you confirm?

@spindelmanne
Copy link
Contributor

Hello, finally looking at your PR. I have some issues with you replacing "UTF-8" with StandardCharsets.UTF8. I'm all for doing this (but I would static import it to make the code read better), but if so it should be done consistently in the project. There are currently 519 occurrences of the string "UTF-8", which is obviously technical debt that we should do something about, and you're only changing a couple of them.

Do you mind rolling back those changes? As far as I can see, the rest of the PR is good stuff!

@spindelmanne
Copy link
Contributor

Hey, @privettoli , did you see my comment?

@privettoli
Copy link
Author

@spindelmanne, I just was unavailable for these days. Okay, so, as you could see, changes from the hard coded Strings to the StandardCharset constant are in a separate commit, so yeah, we could do revert for these changes.

@privettoli
Copy link
Author

@spindelmanne, or I can replace all remaining hardcoded Strings with appropriate constants.

@spindelmanne
Copy link
Contributor

I prefer to do that as a separate change. It's such a huge code change (although it should not break anything, of course) that I need to do it in collaboration with the SoapUI OS dev team and QA. So just revert the commit for now, OK?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants