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 114938 - NullPointerException arises by attempt to bound component to DB for WebLogic's project
Summary: NullPointerException arises by attempt to bound component to DB for WebLogic'...
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: John Baker
URL:
Keywords: RELNOTE
Depends on:
Blocks: 98366
  Show dependency tree
 
Reported: 2007-09-06 19:33 UTC by Roman Mostyka
Modified: 2007-09-07 10:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exception full stack trace (3.00 KB, text/plain)
2007-09-06 19:34 UTC, Roman Mostyka
Details
Screenshot (132.61 KB, image/jpeg)
2007-09-06 19:34 UTC, Roman Mostyka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2007-09-06 19:33:27 UTC
1. Add BEA WebLogic 9.2 application server to the IDE.
2. Add "Visual Web JSF Backwards Compatibility Kit" from UC.
3. Create J2EE 1.4 project for WebLogic.
4. Add Table component to the page.
5. Connect to Derby 'sample' DB.
6. Click CUSTOMER DB table and then click Table component on the page.

Result: Table component isn't bound to the db table, but CustomerDataProvider and Customer RowSet are created. And
NullPointerException arises (see in attach full stack trace).
Comment 1 Roman Mostyka 2007-09-06 19:34:10 UTC
Created attachment 48319 [details]
Exception full stack trace
Comment 2 Roman Mostyka 2007-09-06 19:34:45 UTC
Created attachment 48320 [details]
Screenshot
Comment 3 Winston Prakash 2007-09-06 19:39:26 UTC
Jim, can you take a look at this. The exception is coming from
com.sun.sql.rowset.CachedRowSetXImpl5.getConnection()
Comment 4 John Baker 2007-09-06 19:44:09 UTC
This might be a serverplugin issue again.

serverplugin APIs create the data source and JNDI name - there could be a problem here
Comment 5 _ jimdavidson 2007-09-06 19:54:33 UTC
Looks like the same serverplugin issue as before.  Investigating.
Comment 6 _ jimdavidson 2007-09-06 21:54:20 UTC
Looks like the same WebLogic problem as reported in Bug# 108377
("Cannot drag-n-drop a table to a visual table component for WebLogic").

Symptom is that creation of a datasource fails in ConfigSupportImpl.createDataSource().

The earlier bug was closed by Stepan as a duplicate of Bug# 101812, which was fixed by John Baker.
That bug dealt mainly with JBoss, but WebLogic was mentioned.

I have a feeling that the two bugs weren't duplicates, and that WebLogic has additional problems because the
serverplugin does not support creation of datasources (i.e., ConfigSupportImpl.isDatasourceCreationSupported() returns
false).

John, please take a look at this.  See if this should have been fixed by the fix for Bug 101812, or whether it can be
fixed now.  It may be that databinding for WebLogic is only supported if the user configures datasources by hand, which
is pretty much the same as no support IMO.

Comment 7 John Baker 2007-09-06 22:04:30 UTC
There shouldn't be a separate API for creating a resource reference for Weblogic

This is a serverplugin bug
Comment 8 Jayashri Visvanathan 2007-09-06 22:25:55 UTC
As far as I know databinding for WebLogic is only supported if the user configures datasources by hand.
I remember discussing this with Stepan and Petr Jiricka. But we should fail gracefully instead of throwing null ptr. 
This shouldn't be a P1.
Comment 9 John Baker 2007-09-06 23:02:01 UTC
Handling the NullPointer can be fixed but support for creating data sources out-of-the-box
will not be supported.

A sample server specific file for WebLogic can be added to an FAQ
Comment 10 John Baker 2007-09-06 23:11:47 UTC
will not be fixed for beta1
Comment 11 _ jimdavidson 2007-09-06 23:29:37 UTC
I agree that (a) we can't do much here if the serverplugin doesn't support datasources, (b) we should use
isDatasourceCreationSupported() to check and warn the user, rather than getting an NPE.

We should also update our release notes to note that WebLogic is only partially supported.  This will apply to both Beta
and FCS (assuming the serverplugin is not fixed).  As I noted above, telling users to configure datasources by hand
isn't an acceptable workaround.
Comment 12 John Baker 2007-09-07 01:03:41 UTC
Fix NPE, cancel the drop.
Still need to inform user - tracked by 98366

Checking in
visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/datasource/DataSourceResolver.java;
/cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/datasource/DataSourceResolver.java,v
 <--  DataSourceResolver.java

new revision: 1.16; previous revision: 1.15
done
Checking in
visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/model/DatasourceTransferManager.java;
/cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/model/DatasourceTransferManager.java,v
 <--  DatasourceTransferMan
ager.java
new revision: 1.17; previous revision: 1.16
done
Checking in visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/services/DesignTimeDataSourceService.java;
/cvs/visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/services/DesignTimeDataSourceService.java,v 
<--  DesignTimeDataSourceServic
e.java
new revision: 1.4; previous revision: 1.3
done
Checking in
visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/services/DesignTimeDataSourceServiceImpl.java;
/cvs/visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/services/DesignTimeDataSourceServiceImpl.java,v
 <--  DesignTimeDataSourceSe
rviceImpl.java
new revision: 1.13; previous revision: 1.12
done
Comment 13 Roman Mostyka 2007-09-07 10:38:56 UTC
Verified with build 070907.