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 73889 - Can't deploy EJB module on remote WebSphere
Summary: Can't deploy EJB module on remote WebSphere
Status: VERIFIED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebSphere (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Kirill Sorokin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-22 15:55 UTC by Alexander Kouznetsov
Modified: 2006-06-05 12:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
deploy output log (13.21 KB, text/plain)
2006-03-22 15:56 UTC, Alexander Kouznetsov 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2006-03-22 15:55:42 UTC 
Steps to reproduce:
- Register remote WebSphere instance
- Create New EJB Module targeted to the remote server
- Create New Session Bean in the EJB Module
- Deploy it
- RESULT: Build failed. You could easily deploy the generated ear file using
WebSphere Adminsitration Console.
Comment 1 Alexander Kouznetsov 2006-03-22 15:56:00 UTC 
Created attachment 29363 [details]
deploy output log
Comment 2 Kirill Sorokin 2006-05-29 09:08:01 UTC 
Upon a deeper investigation this turns out to be a limitation of the WebSphere
deployment engine. The resulting error code is ADMA0043E. What actually happens
is that the target server attempts to access the application archive using its
local path on the client machine. The WebSphere's native tools also suffer from
this misbehavior.
Comment 3 Alexander Kouznetsov 2006-06-05 12:39:47 UTC 
It is okay to remove this functionality.