This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 79509 - Can't deploy Enterprise Application to WebSphere without server-specific DDs
Summary: Can't deploy Enterprise Application to WebSphere without server-specific DDs
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebSphere (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@serverplugins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-30 16:49 UTC by Alexander Kouznetsov
Modified: 2006-09-11 13:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample application (21.26 KB, application/x-compressed)
2006-07-06 15:00 UTC, Alexander Kouznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2006-06-30 16:49:28 UTC
Steps to reproduce:
- Create any arbitrary Enterprise Application targeted WebSphere server instance
- Do not create any server-specific DDs
- Try to deploy it to WebSphere using plugin
- RESULT: Deployment is failed due to absence of server-specific DDs

- Now deploy the EAR-genereted using WebSphere Administration Console. Check Generate Default Bindings box.
- RESULT: Deployment will be successfull and application will be working.

Note: Even if you provide some bindings that will allow application to be validated for WebSphere, it still will not work. The same time if you would deploy it using WebSphere Administration Console it would be working.
Comment 1 dlipin 2006-07-03 13:10:09 UTC
Try to export the application deployed through the plugin and the same 
application deployed through the Administration Console.

What is the difference in the .ear file contents?

Try to add missing parts to the appropriate DDs.


PS. When you say "Do not create any server-specific DDs" then it is now real 
truth - they created automatically with the default contents. I mean ibm-
application-{bnd,ext}.xmi
Comment 2 dlipin 2006-07-04 14:08:51 UTC
What do you mean when you say "arbitrary Enterprise Application" ?

I have performed the following:
1) I have created the Enterprise Application (EnterpriseApplication1) and have 
chosen to create WebModule inside it (EnterpriseApplication1-WebModule). I have 
chosen NOT to create EJBModule.
2) I have NOT modified any of the DDs
3) I have selected "Deploy" command from the context menu of 
EnterpriseApplication1 and the deploy process executed successfully.

ADMA5013I: Application EnterpriseApplication1 installed successfully.
ADMJ1018I: EnterpriseApplication1 is running.
BUILD SUCCESSFUL (total time: 30 seconds)


Do you mean exceptions that are thrown in messages log like the following one?
javax.enterprise.deploy.spi.exceptions.ConfigurationException: 
J2EEDeployInvalidModuleException: [AppDeploymentException: []
com.ibm.etools.j2ee.commonarchivecore.exception.OpenFailureException: IWAE0006E 
Archive is not a valid EAR File because the deployment descriptor can not be 
found (case sensitive): META-INF/application.xml
IWAE0006E Archive is not a valid EAR File because the deployment descriptor can 
not be found (case sensitive): META-INF/application.xml]
AppDeploymentException: []
com.ibm.etools.j2ee.commonarchivecore.exception.OpenFailureException: IWAE0006E 
Archive is not a valid EAR File because the deployment descriptor can not be 
found (case sensitive): META-INF/application.xml
[catch]IWAE0006E Archive is not a valid EAR File because the deployment 
descriptor can not be found (case sensitive): META-INF/application.xml
        at com.ibm.ws.management.application.j2ee.deploy.spi.
DeploymentConfigurationImpl.save(DeploymentConfigurationImpl.java:199)
        at com.ibm.ws.management.application.j2ee.deploy.spi.
DeploymentConfigurationImpl.save(DeploymentConfigurationImpl.java:178)
        at org.netbeans.modules.j2ee.websphere6.config.
WSDeploymentConfiguration.save(WSDeploymentConfiguration.java:238)
        at org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.
getDeploymentPlanFileForDistribution(ConfigSupportImpl.java:400)
        at org.netbeans.modules.j2ee.deployment.config.ConfigSupportImpl.
getConfigurationFile(ConfigSupportImpl.java:97)
        at org.netbeans.modules.j2ee.deployment.impl.projects.
DeploymentTargetImpl.getConfigurationFile(DeploymentTargetImpl.java:200)
        at org.netbeans.modules.j2ee.deployment.impl.TargetServer.
deploy(TargetServer.java:574)
        at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.
deploy(Deployment.java:96)
        at org.netbeans.modules.j2ee.ant.Deploy.execute(Deploy.java:76)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at org.apache.tools.ant.Task.perform(Task.java:364)
        at org.apache.tools.ant.Target.execute(Target.java:341)
        at org.apache.tools.ant.Target.performTasks(Target.java:369)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
        at org.apache.tools.ant.helper.DefaultExecutor.
executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
        at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.
java:234)
        at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.
java:287)
        at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:
125)
Comment 3 Alexander Kouznetsov 2006-07-06 15:00:50 UTC
Created attachment 31674 [details]
Sample application
Comment 4 Alexander Kouznetsov 2006-07-06 15:01:22 UTC
Sample Enterprise Application attached
Comment 5 dlipin 2006-08-30 18:48:02 UTC
Seems to be fixed during todays investigating.
Please verify on the next build.
If the issue is still reproducible then please clarify what do you mean by 
saying "any arbitrary Enterprise Application".

Thanks,
Dmitry
Comment 6 Alexander Kouznetsov 2006-09-11 13:58:06 UTC
This issue is partially fixed since server-specific DDs are constructed by the plugin for some of application items. Therefore I'm setting it to verified state. Verified with Coco 2006.08.31 build on WinXP.