JBoss deploy problem

I have always built my exploded .ear/.war in a build directory in my
project.  For some reason, this has stopped working.  It will work with
an UNexploded .ear or .war.  I cleared caches, etc and no changes.

I noticed that it was saying that it could not find the file .....   The
spaces were encoded as %20.  I thought this may be a problem, so I built
the file in a location without spaces in the URL.

Does anyone know how to get it to work the old way?

In the attached log, I tried to deploy it with a directory with spaces,
then one with out, then one with, then one with out.

2 comments

Norris,

The problem is indeed that the spaces are encoded as %20. (The exception
you've got when deploying from a directory without spaces is caused by
an error inside your application.)

Please file a bug report here: http://www.jetbrains.net/jira/browse/JEEAS

Norris Shelton wrote:

I have always built my exploded .ear/.war in a build directory in my
project.  For some reason, this has stopped working.  It will work with
an UNexploded .ear or .war.  I cleared caches, etc and no changes.

I noticed that it was saying that it could not find the file .....   The
spaces were encoded as %20.  I thought this may be a problem, so I built
the file in a location without spaces in the URL.
Does anyone know how to get it to work the old way?

In the attached log, I tried to deploy it with a directory with spaces,
then one with out, then one with, then one with out.


--
Martin Fuhrer
Fuhrer Engineering AG
http://www.fuhrer.com

0

http://www.jetbrains.net/jira/browse/JEEAS-45

Martin Fuhrer wrote:

Norris,

>

The problem is indeed that the spaces are encoded as %20. (The
exception you've got when deploying from a directory without spaces is
caused by an error inside your application.)

>

Please file a bug report here: http://www.jetbrains.net/jira/browse/JEEAS

>

Norris Shelton wrote:

>> I have always built my exploded .ear/.war in a build directory in my
>> project.  For some reason, this has stopped working.  It will work
>> with an UNexploded .ear or .war.  I cleared caches, etc and no changes.
>>
>> I noticed that it was saying that it could not find the file .....  
>> The spaces were encoded as %20.  I thought this may be a problem, so
>> I built the file in a location without spaces in the URL.
>> Does anyone know how to get it to work the old way?
>>
>> In the attached log, I tried to deploy it with a directory with
>> spaces, then one with out, then one with, then one with out.
>

0

Please sign in to leave a comment.