Seems lately as if almost every jar file I use throws this kind of nonsense into the log – every time it is invoked.
What possible use is this feature? I am not about to upgrade anything while developing. Even further, when in production, not going to see this noise pollution.
Even nicer is since quartz is on a timer it will politely trounce your logging while you are in the middle of a debugging session.
For some reason they thought this was a good idea – It isn’t.
Follow this post to turn it back on
Web Developer toolbar by Chris Pederick. If you are developing web apps – get it. Every web developer function I have ever seen in one FREE download.
If you have your site on a less than dedicated hosting package and you need to import a large MySql script you are typically up a creek. I tried all the usual ideas: using gzip, using bzip, split the file up, etc… Nothing worked.
One of the last searches had the simplest solution: use a small PHP program to load file and execute directly on server! Reference from the 1and1 q&a section but I am guessing the same method will work for any Linux host.
Best of all: it’s very fast.
I have a long term client with all of their sites hosted at one of the major vendors.
After tripping along for a while we decided to take up the host offer of adding multiple web sites/databases under one web hosting package.
Guess what? It doesn’t work. The sites (specialized job sites) are not generating any big volume at all. The host says our database queries need tuning (how bad could a single query an hour be?). I know though, come 2:00 PM, getting to the home page for any of the shared sites will fail.
The host must have some server side coding that notices traffic per package, compares to the price being received for that package and downgrades quality. I know, this sounds ridiculous – how could they be that cool and uncool at the same time?
Of course, taking one of the sites out into their own web package removes any of the performance problems whatsoever with that web site. (So, the supposed ‘database tuning’ wasn’t needed after all?)
I guess I don’t understand the point of advertising, promoting an offering that will not work. Even further, then once it starts to break tell subscriber that their code sucks.
I have been developing Hibernate coding for a couple of years, seeing hundreds of mapping files. I am guessing 1% of those required a full path to the class being referenced. From the few of those that I worked on it was never clear why Hibernate, Java, Spring, whatever couldn’t find the class definition in those cases.
Just ran across another odd ball that needed the full path to the object (even though there are several others in the same package that do not need the path).
Any ideas would be appreciated.
I think I have it: if there are multiple objects of the same name in the build path then you have to differentiate. For example, if you have a “package.one.Person” and a “package.two.Person” then when hibernate attempts to resolve your HQL “from Person” it will not know which Person object to attempt to locate.
I hope this is the answer – appears to make sense.
After trying several SQL statement queries I stumbled upon a built-in editor for CLOBs in SQL Developer:
In the last several jobs I have used tools on a daily basis that are no longer supported by anyone. Either the original company no longer exists or the original company came up with a ‘better’ idea and canned the old one.
The tools included:
Again, these were (and likely are) used on a daily basis by the companies involved, usually in a production environment. Yes, documentation is sparse. There are no online groups that discuss the product anymore. Usage tends to be something like “Look at the project Dave did last year and do the same thing”. And “Oh, yeah, Dave left the company six months ago.” Getting to the web wayback machine becomes a favorite.
The products do work. It has usually been pretty clear how to incorporate the product in the new, changed system. It is just scary as hell that one of the bullet items on your to do list is to get this neglected piece of code to behave. Just cross your fingers.
I have been developing Java apps for some time. Most of them have used Hibernate to database access. I think Hibernate is a pretty useful tool; very active user base; good, constant upgrades, fixes.
The last couple of companies I have worked at decided to hide Hibernate behind a homegrown facade. I have never understood what possible use this could be. The reasoning given was to:
Upgrade affects on applications? You mean when a Java library deprecates a bad idea, so the facade would mimic the old, bad idea? Or the application would not have access to the new, neato feature?
What other ORM for Java desktop apps? Are you seriously considering moving (backwards) to iBatis?
In both cases there has been a period of adjustment as you try to figure out what is really missing in the facade or what changes in behavior the facade introduces.
I can’t help but think it is really a case of ego, NIH. I wish I had a bug recorder hidden in the room when the senior development staff described their reasoning. On the other hand, maybe not – it might be too depressing to hear people rationalize such a bad idea.