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 65546 - Why not support weblogic 8.1
Summary: Why not support weblogic 8.1
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-30 16:31 UTC by namanpatel
Modified: 2011-05-16 13:20 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 namanpatel 2005-09-30 16:31:22 UTC 
Guys,

This is just a sugestion but I guess it would be really bad not to support the
weblogic 8.1 app server. It is more widely used app server than the 9.0 version
of ther server.
Comment 1 rptmaestro 2006-08-16 04:23:30 UTC 
I've thoroughly gone through the weblogic9 module code and with only a few 
minor modifications, it can be made to support weblogic 8.1.
Comment 2 rptmaestro 2006-08-18 06:13:43 UTC 
A brief summary of what needs to be done to support WebLogic 8.1

1. For WebLogic 9.x, the module uses 
$WL_HOME/common/nodemanager/nodemanager.domains for finding the domains. This 
file is non-existent in the WebLogic 8.1 installation. The wizard will need to 
detect if a WebLogic 8.1 installation has been selected, and if so, populate 
the combo box with all domains in the $BEA_HOME/user_projects/domains 
directory. Additionally, the combo box should be editable and provide 
a "Browse..." button so the user can enter or browse for any domain that does 
not reside under this directory.

2. Within the domain directory, the module also expects to find init-
info/domain-info.xml (which the module never actually reads) and 
config/config.xml. WebLogic 8.1 keeps config.xml in the domain directory 
itself and uses an earlier DTD. So for WebLogic 8.1, config.xml will need to 
be read from the domain directory, using the earlier DTD and the module will 
need to exempt a WebLogic 8.1 domain from having init-info/domain-info.xml.

3. The domain startup script (startWebLogic.cmd or startWebLogic.sh) for 
WebLogic 8.1 must be executed from the domain directory or it will hang when 
executed.

4. The WebLogic 9.x weblogic.jar contains a DeploymentManager implementation 
that is used by the server plug-in. For WebLogic 8.1, we will need to provide 
our own DeploymentManager.

My initial phase of development will be to implement items 1 through 3 and 
provide a skeleton implementation of item 4. That will allow a user to add a 
WebLogic 8.1 server to the IDE and compile against it.
Comment 3 Vince Kraemer 2007-12-07 16:22:07 UTC 
please close this issue if you forgot to earlier.  If this issue is still open,
please change the target milestone to reflect the current commitment.
Comment 4 rptmaestro 2007-12-12 20:17:59 UTC 
Is 8.1 still needed?
Comment 5 satrul 2007-12-22 14:52:01 UTC 
Yes, it's needed. There are a lot of Weblogic 8.1 still alive and need development.
Comment 6 elishae 2008-03-07 07:28:30 UTC 
When would this issue be addressed?
Comment 7 elishae 2008-03-07 07:29:31 UTC 
Can we have this to be supported even in later versions of NB 6.0, 6.1 and beyond.
Comment 8 zaahirlaher 2008-04-14 13:50:32 UTC 
will this be in 6.1?
Comment 9 Petr Hejl 2011-05-16 13:20:57 UTC 
We won't support this.