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.
nbi build 070418 jdk1.5.0_10 JBoss 5 Beta 2 1) New Project -> Web -> Choose JBoss 5 -> Choose JavaEE5 -> Next 2) Choose Visual Web JSF framework -> Finish 3) Drag-n-drop Table component from Palette/Basic 4) Connect to sample database (app/app) 5) Drag-n-drop CUSTOMER table on Table in Page1.jsp (target header of Table, to choose table, not just a row) NPE is thrown and binding is then halway done (some changes in project are made, but database table isn't correctly binded)
Created attachment 41273 [details] messages log
Cannot reproduce using M9 visualweb please try again using a newer build
build 200704191800 vwp build 070419_10 It appears now randomly, but anyway when NPE doesn't pop up, it doesn't link database table with Table in jsp editor and IAE is thrown in log. So at the end this functionaly doesn't work for JEE5 and JBoss 5 anyway.
Created attachment 41341 [details] Part of log with error
I'm seeing an object on null I guess similar to an NPE, but different error from stack trace. I'm using the 070422 build. Attaching exception and will consult with J2EE team
Created attachment 41658 [details] JBoss 5 exception when creating datasource
visualweb passes to J2eeModuleProvider : jmp.createDatasource("jdbc/APP_ApacheDerby", "jdbc:derby://localhost:1527/sample", "app", "app", "org.apache.derby.jdbc.ClientDriver"); should be valid parameters unless JBoss doesn't like the '_'
To clarify, maybe JBoss doesn't consider a '_' as a valid character for the resource name
Oh, I see that JBoss 5.0 Beta 2 is not fully Java EE 5 compliant. This may be the reason for this error in creating a datasource.
I will mark as INCOMPLETE until JBoss comes out with a Java EE 5 compliant app server. If there's a more appropriate way to tag this issue, please do so.
Please, use INCOMPLETE only in case you need a feedback from reporter. This bug should be marked as WONTFIX when the issue is on JBoss. BTW, are you sure that JBoss isn't still JavaEE5 compliant? Can you explain what is the issue with datasource and JavaEE5 spec? Maybe, report the big for Jboss.
Marking the issue as WONTFIX resolves the issue. but I'm still not sure the cause. A resource name with '_' is not the issue Creating a datasource fails passing these parameters to J2eeModuleProvider jmp.createDatasource("jdbc/APPApacheDerby", "jdbc:derby://localhost:1527/sample", "app", "app", "org.apache.derby.jdbc.ClientDriver");
Fixed the NPE. Checking in DatasourceSupport.java; /cvs/serverplugins/jboss4/src/org/netbeans/modules/j2ee/jboss4/config/ds/DatasourceSupport.java,v <-- DatasourceSupport.java new revision: 1.3; previous revision: 1.2 done
serverplugin side appears to be fixed but visualweb's rowset code is choking attaching NPE
Created attachment 41799 [details] rowset bind error
Issue is reproducible on Jboss4 as well.
Release note added.
currently I'm blocked by 109710
Passing to j2ee for evaluation When target container is JBoss, requestedResource.getResource() returns "java:/jdbc/APP_ApacheDerby" whereas when Glassfish is the container, getResource() returns "jdbc/APP_ApacheDerby" for the resource name I expect getResource to return "jdbc/APP_ApacheDerby" visualweb has an extension of RequestedResource org.netbeans.modules.visualweb.api.j2ee.common.RequestedJdbcResource. RequestedJdbcResource doesn't override getResource() but neither does RequestedEjbResource
The issue seems to be in visualweb and it is also reproducible with WebLogic as a target server, see issue 108377. If you think this issue depends on some other issue, in some server plugin for example, you should file a separate issue for that.
*** Issue 108377 has been marked as a duplicate of this issue. ***
Reproducible on all the platforms
should be probably assigned to John
Fixed at design-time. Resource reference looks correct, but having trouble verifying runtime. 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.8; previous revision: 1.7 done Checking in visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/model/ProjectDataSourceManager.java; /cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/model/ProjectDataSourceManager.java,v <-- ProjectDataSourceManag er.java new revision: 1.3; previous revision: 1.2 done Checking in visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/project/datasource/ProjectDataSourceTracker.java; /cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/project/datasource/ProjectDataSourceTracker.java,v <-- ProjectDa taSourceTracker.java new revision: 1.11; previous revision: 1.10 done
Drag and drop has been fixed but the resource reference is created in the wrong file. See issue 112367 The workaround is to copy the resource reference section from the setup/jboss-ds.xml to the web/jboss-web.xml Also, another exception may occur. See issue 112372
Not completely fixed. Data source is now available but getting a new exception Caused by: javax.naming.NameNotFoundException: No object bound to name java:comp/env/jdbc/datasource1 at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:822) at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173) at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:337) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.sun.sql.rowset.internal.CachedRowSetXReader.connect(CachedRowSetXReader.java:344)
design-time works but runtime fails see issue 112367
Runtime now works also
Verified on: 1). JBoss 5.0.0 Beta2 JAVA: j2sdk 1.5.0_12-b04 2). Product Version: NetBeans IDE Dev (Build 200708160000) Java: 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04 System: Windows XP version 5.1 running on x86