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 108377 - Cannot drag-n-drop a table to a visual table component for WebLogic
Summary: Cannot drag-n-drop a table to a visual table component for WebLogic
Status: RESOLVED DUPLICATE of bug 101812
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: John Baker
URL:
Keywords:
: 109994 (view as bug list)
Depends on:
Blocks: 98366
  Show dependency tree
 
Reported: 2007-06-28 10:46 UTC by Sherold Dev
Modified: 2007-08-02 16:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
exception log (5.90 KB, text/plain)
2007-06-28 10:50 UTC, Sherold Dev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sherold Dev 2007-06-28 10:46:17 UTC
Product Version: NetBeans IDE Dev (Build 200706261800)
Java: 1.5.0_08; Java HotSpot(TM) Client VM 1.5.0_08-b03
System: Linux version 2.6.20-15-generic running on i386; UTF-8; en_US (nb)

1. Create a Visual Web Application
2. Add a Table component to the page
3. Try to drag and drop a DB table to the Table component
4. the attached exception will occur
Comment 1 Sherold Dev 2007-06-28 10:50:18 UTC
Created attachment 44507 [details]
exception log
Comment 2 _ jimdavidson 2007-06-28 22:48:43 UTC
This all looks fairly straightforward, except that the IDE is unable to get a connection to the database.

I tried it using a developer build from today, and everything worked fine.  

Configuration: MacOS X 10.4.10, Java 1.5.0_07, bundled Java DB.

What database are you using?  What driver?  Was the database already running?
Comment 3 Sherold Dev 2007-06-29 10:33:07 UTC
> What database are you using? 

I am using sample Derby DB that comes with GlassFish

jdbc:derby://localhost:1527/sample

> What driver?

org.apache.derby.jdbc.ClientDriver
version 10.1.1.0

> Was the database already running?

yes, the DB was running
Comment 4 _ alexpetrov 2007-06-29 12:58:35 UTC
Supported J2SDK 1.5.0_11 & 1.6.0 (see http://wiki.netbeans.org/wiki/view/NB6TestedPlatformsAndRuntimes).
I checked the described scenario on Linux Ubuntu + J2SDK1.6.0_1 - this bug is not reproduced: web-application was
deployed and web-page was displayed in a browser correctly.
May be, the problem is caused by Java: 1.5.0_08.
Comment 5 Sherold Dev 2007-07-11 17:13:39 UTC
Well, I just found out that this issue is not reproducible when the project is targeted to GlassFish. Please use 
WebLogic 9.0 as the project target server.

The issue is reproducible with the latest JDKs.

java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing)

java version "1.6.0_02"
Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
Java HotSpot(TM) Client VM (build 1.6.0_02-b05, mixed mode, sharing)

Removing the INCOMPLETE keyword
Comment 6 _ jimdavidson 2007-07-19 21:05:30 UTC
The problem seems to be specific to WebLogic, but independent of OS.   Updated the summary accordingly.

Until I investigate, can't say whether the problem lies in databinding or server plugin.  Should fix for 6.0.
Comment 7 _ jimdavidson 2007-07-30 03:24:57 UTC
Looks like a serverplugin issue.

The call config.getLookup().lookup(DatasourceConfiguration.class) returns null, which presumably means that the IDE
can't find a class to configure DataSources for WebLogic.

There's no IZ subcomponent for WebLogic10, so changing to WebLogic9.
Comment 8 _ jimdavidson 2007-07-30 03:25:49 UTC
*** Issue 109994 has been marked as a duplicate of this issue. ***
Comment 9 Sherold Dev 2007-07-30 12:24:47 UTC
Please note that the weblogic plugin does not support datasource configuration, it cannot be considered as a defect in
the plugin. There is no exception from the weblogic plugin in the attached log, so it does not seem that the problem is
there.

Reassigning the issue back to visualweb/databases for further evaluation.
Comment 10 _ jimdavidson 2007-07-31 03:20:41 UTC
Please explain what behavior you are expecting to see.

You are creating an application for a platform that apparently does not support datasources.   When you try to create a
datasource, what should happen?

The current VisualWeb code uses J2eeModuleProvider.getModuleDatasources() and J2eeModuleProvider.getServerDatasources().
 Should it be doing something different?    

Do we really not support datasources for WebLogic applications?   
Comment 11 Sherold Dev 2007-07-31 10:29:38 UTC
What should happen? Certainly, the exception should not occur, but I do not think I am the right person to answer this
question. The visualweb team should decide what is the right way to fix it.

There is nothing wrong on calling getModuleDatasources() and getServerDatasources() methods, but they will return empty
sets, I guess.

You should check J2eeModuleProvider.getConfigSupport().isDatasourceCreationSupported() method before trying to create a
new datasource.

No, there is no datasource support in WebLogic plugin.
Comment 12 _ jimdavidson 2007-07-31 19:52:51 UTC
Let me make sure that I understand this:

* There is no serverplugin support for datasources in WebLogic.

* As far as I can tell, that means that users cannot build WebLogic applications that use datasources.  (John Baker may
know more about this.)

* So, all we're discussing is how to handle the error that results.  That is, we should do something better than throw
an exception.

Based on that analysis, this can probably be downgraded to P3.  But, I'll assign it to John Baker, in case there's
something better that we can do even without support from the plugin.  At least we should add the appropriate checks
(e.g., isDatasourceCreationSupported()) to present a more appropriate explanation of the problem.
Comment 13 Sherold Dev 2007-08-01 09:20:51 UTC
Users can build WebLogic applications that use datasources, provided that they configure the datasources by hand.

The reason why this issue was filed as P2 was that the issue which depends on this issue is a P2. Even though that the
depending issue cannot be evaluated due to this issue, it looks like it has a work-around so I will downgrade it to P3.
Comment 14 _ jimdavidson 2007-08-01 17:41:37 UTC
Wait a minute!  There's a major difference between this issue and issue 98366, which is listed as depending on this one.

Issue 98366 was filed against NB 5.5.1.  Databinding and deployment to WebLogic works in 5.5.1; I just tested it. 

This issue has been filed against NB6.0.  Databinding and deployment to WebLogic do *not* work in NB6.0, because of the
datasource issues cited here.

Please clarify which version of the IDE this issue pertains to.
Comment 15 Sherold Dev 2007-08-01 18:23:17 UTC
OK, so then I can close the issue 98366.

This issue, however, still exists and it is reproducible in 6.0 as already mentioned in the description of the issue.

If I understood correctly, you were able to reproduce the issue as well, so I don't understand what information are you
missing.
Comment 16 Jayashri Visvanathan 2007-08-01 19:54:54 UTC
Stepan,
  According to http://serverplugins.netbeans.org/, Web Logic is supported. 
Am I missing something ? 
Comment 17 Sherold Dev 2007-08-02 09:02:14 UTC
Yes, WebLogic is supported, the plugin only lacks datasource support.

Note that each server plugin can have different level of support.

Removing the INCOMPLETE keyword since the issue is easily reproducible with the provided info.
Comment 18 Sherold Dev 2007-08-02 16:49:29 UTC
seems to be a duplicate of issue 101812

*** This issue has been marked as a duplicate of 101812 ***