|
| Re: Publish to WebSphere6 fails due to backslash in directory name within WAR [message #177898 is a reply to message #177880] |
Fri, 25 August 2006 14:28  |
 Marko Topolnik
Messages: 42
Registered: July 2009 |
Member |
|
|
(Quoting myself...)
>I use WTP 1.5.0 with WebSphere 6. I have trouble deploying my application
>due to the following: in the WAR within the EAR, the names of the
>directories are, literally, \META-INF and \WEB-INF -- they start with a
>backslash! If I correct this, the resulting EAR deploys and runs with no
>problems. Am I doing something fundamentally wrong, since this looks like a
>very basic and generic problem? What can be done?
Let me be more specific: I've got a Dynamic Web Project and a corresponding
Enterprise Application Project. When I select "Run As | Run on Server" in
the context menu of the Dynamic Web Project, an EAR is generated in
..metadata/.plugins/org.eclipse.wst.server.core/tmp1. This EAR is corrupted
as explained above. The error message I get from WebSphere in Console View
is
com.ibm.etools.j2ee.commonarchivecore.exception.DeploymentDe scriptorLoadException:
IWAE0022E Exception occurred loading deployment descriptor for module
"MyWebApp.war" in EAR file "D:\Temp\app34442.ear"
(WebSphere obviously copied the EAR into my TEMP directory prior to opening
it)
The above mentioned directory (...tmp1) also contains the uncompressed
contents of the WAR and EAR. So, I recreate the EAR using a plain ZIP
archiver and manually deploy it using the command-line tool wsadmin, copying
from the console log the exact command that WTP used on it:
$AdminApp install
..../.metadata/.plugins/org.eclipse.wst.server.core/tmp1/MyW ebAppEAR.ear
{-appname MyWebAppEAR -deployejb -usedefaultbindings}
After that, the application runs fine.
Marko Topolnik
CROZ, Zagreb (Croatia)
|
|
|
Powered by
FUDForum. Page generated in 0.02442 seconds
] 
Search
Help
Register
Login
Home
