As described in
there should be a method in j2eeserver allowing a client to locate
DatabaseConnection's for a given Datasource.
Created attachment 38596 [details]
diff file of proposed changes to j2ee utilities projext.xml
To access DatasourceHelper.findDatabaseConnections(...,...), I think making
visualweb's dataconnectivity packages as friends is sufficient.
I'm attaching a diff of project.xml
Please let me know if this sounds ok.
It can be done as a temporary solution for M8, but that method will need to be
moved to j2eeserver in 6.0. I don't think adding those dependencies needs an API
review, so unless anyone on CC disagrees you can just commit. Please don't close
the issue, as it still needs to be addressed properly later.
If no objection, I'll make the change for M8, as indicated by the attached diff.
After M8, please suggest which class to move findDatabaseConnections(...) to
Should DatasourceHelper still be moved to another package?
If so, where is a good place?
Yes, I believe it should be moved somewhere else. j2eeserver is my best (well,
FYI, moving DatasourceHelper to j2eeserver is part of the API change which is
tracked by issue 89439. Setting the dependency...
89439 90209 are not dependencies, removing them from dependency list
Does the API still need to be moved to a new module and package ?
Yes. It shouldn't stay in j2ee/utilities because I want to avoid adding many
dependencies to that module.
ok, which package of j2eeserver is an appropriate place to move
DatasourceHelper, org.netbeans.modules.j2ee.deployment.common.api ?
No need to rush with this. The new location for this class will most likely be
the org.netbeans.modules.j2ee.deployment.common.api package, but the method
change, which was discussed in the issue 89439, needs to be done before or at
the same time when moving the class to j2eeserver.
John, is this issue blocking you? Do you need the tryRegister parameter that was
discussed in issue 89439?
This is not blocking me. I should remove my dependency, I have implemented a
similar way to find the connections, since I didn't want to wait for the
decision on where this api is to be moved. So, I'm just following up since
issue 90207 hadn't been resolved.
If that's the case then I gues you can just remove your dependency, but please
leave the issue opened. We need to improve this method, even if not sure if for
M10. No one has time to work on it now I think.
Obsolete milestone, please reevaluate