Craig Schwabl

Greenhorn
+ Follow
since Nov 20, 2001
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
(keep public parts private until JForum day)
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt
Moderation Tools

Recent posts by Craig Schwabl

"Connection refused" means that the database server actively refused the connections, which usually means that nothing is listening on the specified port. Are you sure that your SQL server is listening on port 1433? If so, are you positive that it is up and running?
Hey Kyle, nice presentation. I had a question relating to the PDF...specifically the slide on page 16 (the second one labeled "Project Organization best practices"). In this slide you show a single EAR file (ProjectA.ear) containing 2 WAR files (ProjectA.war and ProjectA'.war). Are you implying that the source code for both WAR files is located in the same CVS project, or are you implying that they are contained in separate CVS projects? The reason that I am asking is that our company develops many different web-based Java applications under Websphere/WSAD, but all of the application components rely on a set of core components including login, security, session management, user management, database access, etc. Most of these core componenets include Servlets, JSP, beans, and various miscellaneous web files. I am trying to organize our source control (CVS) so that the core components could be maintained in one project, and the application components could each reside in their own projects. The goal is that the core components could be deployed with any (or all) of the custom application modules to comprise a deployment. The challenge, however, is the fact that when separate projects are synchronized in WSAD and deployed to the test environment, they are deployed under separate contexts. This means that a user could not log into the "core components" project using one context root, and have seamless access to the application modules deployed using separate context roots. There is also a need to share session information between each project. I tried deploying both the core project and the application project under the same context root, however, it appears that this is not supported by Websphere (or even the J2EE spec). Anyway, do you have any suggestions on how I could accomplish this using WSAD 4.03 and CVS? I am trying to avoid using external build tools (i.e. Ant) if I don't have to.
Thanks.
I have been running CVSNT v1.11.1.2 on Win 2000 with WSAD (4.01 and 4.03) for several months without any problems. Your problems could be due to differences between v1.11.1.2 and v1.11.1.3.
Here is the latest information from IBM's web site here
"Planned Certification availability date for WebSphere Studio Application Developer V4.0 is April 15, 2002."

Unfortunately there were no additional details about it.
Craig
Try session.invalidate() to immediately remove the session, or session.setMaxInactiveInterval(int interval) to specify the timeout period.
15 years ago
1. This is not actually an error. Websphere is simply telling you that it doesn't recognize the driver as being a certified driver. This does not mean, that your connection will not work. Many 3rd-party JDBC drivers will work fine, even though this message will be displayed.
2. I do not know of any free SQL2000 JDBC drivers. Inet Software and Merant (now Data Direct) both make decent Type4 drivers that are certified by Sun. Unfortunately, you need to pay for them. Microsoft also has a Beta version of their type 4 driver for SQL server. I think you can download the beta version for free, but I would guarantee that it won't come with any support.
3. Did you install the Merant Server agent on the SQL server? This may be causing your error.
Hope this helps.
Craig
15 years ago
IBM has just made the Websphere Studio Application Developer 4.02 update available for download here
It now adds support for Windows XP users, as well as a bunch of bug fixes. Unfortunately, this upgrade is for registered customers and will not work with the Beta version.
Enjoy!
16 years ago