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.
When creating a Java DB db from the Services window, it should be clearer how to get the connection. I would expect that the connection would be made and listed with the other sample db connections. When I didn't see it there, I right-clicked Java DB to find a way to connect, but there was no option there. After a few minutes of being ticked off, it occurred to me to go one node up and look there. Bingo. But why does it have to be that hard. Best of all possible worlds: connection is created automatically and listed among the connected dbs. More tolerable than the current situation: make the connect command available on the Java DB node.
upping to P2 and marking as REGRESSION, because this was much simpler before (entry for (non)connection appeared and you mrely had to choose Connect, without entering parameters for connection)
I'm not sure what changed - I didn't change this logic at all. I'm not sure I follow what's not working for you. What do you mean by "go one node up?" Are you expecting the Java DB connections to be under the Java DB node? Is the connection there or not? Maybe you can explain step-by-step what you did and what happens, and explain the steps "the old way" that you believe is better. I want to make sure I get it, is all. Thanks for your time on this.
I'm not sure what changed - I didn't change this logic at all. I'm not sure I follow what's not working for you. What do you mean by "go one node up?" Are you expecting the Java DB connections to be under the Java DB node? Is the connection showing up under the Databases node or not? Maybe you can explain step-by-step what you did and what happens, and explain the steps "the old way" that you believe is better. I want to make sure I get it, is all. Thanks for your time on this.
Sorry about the duplicate, I had an Internet hiccup. The second revision is the one I think more clearly expresses what I'm trying to say..
Yes, I think the Connect action should also be available on the Java DB node. Now it's only available on the Databases node. It's not intuitive that you would create a database with one node (Java DB) and then have to go one level higher (Databases) to actually connect to that database.
We can put a connect action on the Java DB node, that seems reasonable. Also, when you create a new database, we should create a connection to it. I'm still not sure how this can be seen as a regression though, can you explain? It seems like a (very useful) enhancement, versus a regression/defect.
Reasons I consider the current behavior to a regression 1. Before when creating a db, a node for the db would appear. Even though there was no connection, there was a logical place to click and connect. 2. When you finally find the place to connect, you now have to enter the connection info manually. Before, you simply right-clicked the node for the db and chose Connect. 3. The current solution doesn't fully take advantage of the co-location of all of the features under Services. The fact that you have created a db and don't see it is counter-intuitive. Assuming you get past that, a next logical step is to look for the action on the Java DB menu. Once stymied there, you then start wondering whether you did something wrong or whether there is a bug. Going up to the Database node seems like going backwards (my action is getting more specific, not more general). I think this issue alone neutralizes the gain of moving all of the actions to the Services window.
*** This issue has been marked as a duplicate of 132037 ***