Hi,
I'm having trouble deploying even the simplest EAR file through WSAD admin console. It throws an exception indicating "invalid binaries path".
Would anyone happen to know anything about it ?
The details:
1) Use WSAD to create a simple J2EE project called BEar, containing a single "helloWorld" Web Module.
2) Export it to an EAR file, somewhere on the file system.
3) On WSAD, create a new Server (Test Environment).
4) Run admin console. Use "install new applications" to install the EAR.
5) Still in admin console, start the new application.
This throws an excpetion, indicating "invalid binaries path".
What does "binaries path" mean ?
Is it related to the "binariesURL" property, in file "BEar/deployment.xml" (somewhere under Servers) ? I noticed that when you deploy through admin console, you get "binariesURL=${WS_EAR_BEar}". When deploying though WSAD ("Run on Server"), it becomes "binariesURL="$(APP_INSTALL_ROOT)/localhost/BEar.ear".
Does it help ?
Here's a shortened version of my stack trace. Note it mentions "application.xml" but I couldn't find anything wrong with it.
------------- shortened stack trace: ------------------
[23:45:10:578 IDT 19/04/05] 119130d9 ApplicationMg W WSVR0100W: An error occurred initializing, BEar
com.ibm.ws.exception.ConfigurationWarning: Failed to open D:\projects\wsad5.1\Servers\server2.wsc\cells\localhost\applications\BEar.ear\deployments\BEar
at com.ibm.ws.runtime.component.DeployedApplicationImpl.initialize(DeployedApplicationImpl.java:414)
...[ trimmed by solmyr]...
Caused by: com.ibm.etools.archive.exception.DeploymentDescriptorLoadException: META-INF/application.xml
at com.ibm.etools.commonarchive.impl.EARFileImpl.getDeploymentDescriptor(EARFileImpl.java:411)
com.ibm.etools.commonarchive.impl.EARFileImpl.initializeModuleExtensions(EARFileImpl.java:793)
...[ trimmed by solmyr]...
---- Begin backtrace for nested exception
com.ibm.etools.archive.exception.DeploymentDescriptorLoadException: META-INF/application.xml
Stack trace of nested exception:
com.ibm.etools.archive.exception.ArchiveRuntimeException: Invalid binaries path: D:\projects\wsad5.1/localhost/BEar.ear
at com.ibm.etools.archive.impl.LoadStrategyImpl.checkLoosePathsValid(LoadStrategyImpl.java:492)
...[ trimmed by solmyr]...
Thanks
I'm having trouble deploying even the simplest EAR file through WSAD admin console. It throws an exception indicating "invalid binaries path".
Would anyone happen to know anything about it ?
The details:
1) Use WSAD to create a simple J2EE project called BEar, containing a single "helloWorld" Web Module.
2) Export it to an EAR file, somewhere on the file system.
3) On WSAD, create a new Server (Test Environment).
4) Run admin console. Use "install new applications" to install the EAR.
5) Still in admin console, start the new application.
This throws an excpetion, indicating "invalid binaries path".
What does "binaries path" mean ?
Is it related to the "binariesURL" property, in file "BEar/deployment.xml" (somewhere under Servers) ? I noticed that when you deploy through admin console, you get "binariesURL=${WS_EAR_BEar}". When deploying though WSAD ("Run on Server"), it becomes "binariesURL="$(APP_INSTALL_ROOT)/localhost/BEar.ear".
Does it help ?
Here's a shortened version of my stack trace. Note it mentions "application.xml" but I couldn't find anything wrong with it.
------------- shortened stack trace: ------------------
[23:45:10:578 IDT 19/04/05] 119130d9 ApplicationMg W WSVR0100W: An error occurred initializing, BEar
com.ibm.ws.exception.ConfigurationWarning: Failed to open D:\projects\wsad5.1\Servers\server2.wsc\cells\localhost\applications\BEar.ear\deployments\BEar
at com.ibm.ws.runtime.component.DeployedApplicationImpl.initialize(DeployedApplicationImpl.java:414)
...[ trimmed by solmyr]...
Caused by: com.ibm.etools.archive.exception.DeploymentDescriptorLoadException: META-INF/application.xml
at com.ibm.etools.commonarchive.impl.EARFileImpl.getDeploymentDescriptor(EARFileImpl.java:411)
com.ibm.etools.commonarchive.impl.EARFileImpl.initializeModuleExtensions(EARFileImpl.java:793)
...[ trimmed by solmyr]...
---- Begin backtrace for nested exception
com.ibm.etools.archive.exception.DeploymentDescriptorLoadException: META-INF/application.xml
Stack trace of nested exception:
com.ibm.etools.archive.exception.ArchiveRuntimeException: Invalid binaries path: D:\projects\wsad5.1/localhost/BEar.ear
at com.ibm.etools.archive.impl.LoadStrategyImpl.checkLoosePathsValid(LoadStrategyImpl.java:492)
...[ trimmed by solmyr]...
Thanks