I've seen you post here on several occasions, but I'm sorry that I've forgotten the environment you typically work in. I did find this discussion on the docker forums:
They say that Windows host running a Linux container may encounter this problem. For their issue, at least, the solution related to locale settings.
Thanks for your response. I'm running Docker on native Linux so I don't think I'm having the same issue.
If I bash into the image and do a cp foo.file fooåäö.file I also end up with the question marks. I'm trying to find if some LC_* environment vars could have an effect...
EDIT: for some strange reason, tab completion shows the åäö even if ls doesn't display them correctly.
The locale of the container may still actually be the issue. It looks like some people are seeing this behavior regardless of the host OS. That same discussion linked here:
The posts below that link discuss modifying the dockerfile in order to support the needed locale.
Thanks, I'll have a look. It can be simply reproduced with the official (CentOS based) WildFly docker image by doing a
docker run -it jboss/wildfly bash
and then in the wildfly directory doing a cp copyright.txt copyright.åäö
Without trying, I would be surprised if a WAR containing åäö in the FQCN would deploy in that OOTB.
It could be a case of Default to UTF-8 character encoding · Issue #29 · jboss-dockerfiles/wildfly · GitHub , I'll have a closer look
EDIT: Looks promising so far with the straight deployment, tomorrow I'll check if it helps with the arquillian issue I've been having