-
1. Re: Leerzeichen in der EAR
jaikiran Oct 26, 2011 12:24 AM (in response to generic1)For those who are watching this thread but don't know German, here's what Google translates it to:
Hello,
I've taken ine larger project and in the EAR's are drinnnen spaces, eg: "applname Part1 EAR".
If I want to deploy on my JBoss 6.0 server, I get fiolgende error message:
java.net.URISyntaxException: Illegal character in the path at index x: file :/...
When I was in the path x character just to the left zählee ihc first come to the space.
The application is available on the JBoss 4.2 running perfectly, now with the JBoss 6.0 I get this same error.
Does anyone know how I can solve this without changing much need (eg modify the Projects -> I would like to avoid that)
Thank you,
Generic1
So it appears that you have .ear file whose name has space characters in it and you are running into deployment failures due to that, in JBoss AS 6.0.0.Final. Can you try this against the 6.1.0.Final which was released some time back? I think it was fixed in that, although I'm not really sure. Let us know how it goes.
P.S: Main language of communication in these forums is English. If possible, try and post in English so that it's a bit easier for others to understand
-
2. Re: Leerzeichen in der EAR
generic1 Oct 31, 2011 10:03 AM (in response to generic1)Hello,
sorry for the question in german, I thought that it is an german forum because I saw all in German.
I have downloaded JBoss 7.0.1 and it too can handle EAR's with a space in it. I get the Exception:
IllegalArgumentException: Invalid value specification ...
So JBoss v5 and higher can't handle EAR's with spaces -> Can I make this conclusion?
Thanks and all the best,
Hannes Weninger
-
3. Re: Leerzeichen in der EAR
jaikiran Oct 31, 2011 10:15 AM (in response to generic1)Hannes Weninger wrote:
I have downloaded JBoss 7.0.1 and it too can handle EAR's with a space in it. I get the Exception:
IllegalArgumentException: Invalid value specification ...
The latest available AS7 version is 7.0.2. If it still fails there, then it's a bug, in my opinion. Can you please post the entire exception stacktrace that you see on 7.0.2?