In the server console window when starting WLP 9.2.x there is a lot of logging that is both useless and slows down the start of your unit tests when developing. Here is how to get rid of that:
Go into your WebLogic Administration Console.
Under Environment on the left hand side navigation there is a node called Work Managers. Click on that and add a new Work Manager for the name:
weblogic.wsee.mdb.DispatchPolicy
Be sure to check the target server on the Next screen after adding the name.
Note: This tip came from Dev2Dev, which is sadly no longer.
Monday, August 31, 2009
Sunday, August 30, 2009
Whether to Use Open Source or Windows Development Platform
The following questions was on LinkedIn today:
Here is my response:
I started typing a couple of different responses, and then stopped as it occurred to me that the world of the operating system has turned upside in the last ten years, because your choice for OS is literally Mircrosoft or Open Source. All of the other vendors have either gone open source or are too small to consider as real choices anymore.
So from the OS point of view, it is a choice of who your support vendor is now.
Once you choose your operating system, then you need to choose your software packages. This is where in-house skill is a big part of the equation, because if you don't have people that will take complete ownership of both the framework and custom code, your open source options narrow. You have to look at which projects have the most solid team that will still be updating the product n years from now. Currently, those are products that either have vendor sponsorship (and you expect the vendor to be around n years from now) or are so wildly popular for so long that even if the current group gets rich and bored someone else will step in.
And, back to the Windows or something else question: For a web-based application, if software doesn't run on both (at least a version that runs on both), I wouldn't consider it.
But (as Dennis Miller used to say every week), that's just my opinion. I could be wrong.
How to decide whether to use Open Source or Windows development platform. we are working on creating a SAAS model for a payroll and HR software. The debate we currently having is to on what software to develop Open Source or Windows. Need some help to decide the parameters on which to compare so as to come up with a logical decision rather than the decision based on gut.
Here is my response:
I started typing a couple of different responses, and then stopped as it occurred to me that the world of the operating system has turned upside in the last ten years, because your choice for OS is literally Mircrosoft or Open Source. All of the other vendors have either gone open source or are too small to consider as real choices anymore.
So from the OS point of view, it is a choice of who your support vendor is now.
Once you choose your operating system, then you need to choose your software packages. This is where in-house skill is a big part of the equation, because if you don't have people that will take complete ownership of both the framework and custom code, your open source options narrow. You have to look at which projects have the most solid team that will still be updating the product n years from now. Currently, those are products that either have vendor sponsorship (and you expect the vendor to be around n years from now) or are so wildly popular for so long that even if the current group gets rich and bored someone else will step in.
And, back to the Windows or something else question: For a web-based application, if software doesn't run on both (at least a version that runs on both), I wouldn't consider it.
But (as Dennis Miller used to say every week), that's just my opinion. I could be wrong.
Saturday, August 29, 2009
Annotation Overrides in a Cluster
The original blog I referenced in my original blog (I recall someone laughing at the term "Legacy Web Application" back in 2000) is sadly gone. So, for those who may run into the following error:
Here is the closest reference still available to help you out: http://blogs.oracle.com/jamesbayer/2007/08/changing_weblogic_annotations.html
"javax.enterprise.deploy.model.exceptions.DDBeanCreateException: [J2EE Deployment SPI:260142]The descriptor at 'META-INF/annotation-manifest.xml' in module
Here is the closest reference still available to help you out: http://blogs.oracle.com/jamesbayer/2007/08/changing_weblogic_annotations.html
Sunday, August 23, 2009
Permission Error on Delete Directory for Java Projects on Windows
I wish I had take a screen shot of the error to make this easier for folks to say "oh, yeah, I have that problem". The thing is, when you build some J2EE applications from a project on the Desktop or My Documents (which I am only now starting to use out of convenience for back up programs that think that is where things should be stored) and then are done with them you find you can't delete them. You get this annoying warning that you might not have permission to do so, even though your are the administrator in Windows and the owner of the files.
This is because of a bug in Windows meant to annoy those of use who like having the directory structure match the namespace. The generated name spaces are often too long when combined with all that extra path crud that goes to My Documents or Desktop for the OS to handle. So, the simple solution is take the folder and drag it into the root of the drive and then delete it. Apparently, only delete is crippled by this bug and not move. Go figure.
And, yes, I know that Microsoft bashing is cheap and easy. So am I, which is why I do it. I am fully aware that if it were not for Microsoft I would most likely be living in a trailer wondering why a guy that likes and understands something as complex as programming is ignored by Corporate America and treated like a warehouse worker (the way it was before Bill was a Billionaire). Thank you Bill, for everything :)
PS: Microsoft bugs still piss me off.
This is because of a bug in Windows meant to annoy those of use who like having the directory structure match the namespace. The generated name spaces are often too long when combined with all that extra path crud that goes to My Documents or Desktop for the OS to handle. So, the simple solution is take the folder and drag it into the root of the drive and then delete it. Apparently, only delete is crippled by this bug and not move. Go figure.
And, yes, I know that Microsoft bashing is cheap and easy. So am I, which is why I do it. I am fully aware that if it were not for Microsoft I would most likely be living in a trailer wondering why a guy that likes and understands something as complex as programming is ignored by Corporate America and treated like a warehouse worker (the way it was before Bill was a Billionaire). Thank you Bill, for everything :)
PS: Microsoft bugs still piss me off.
Sunday, August 16, 2009
Scott Adams Nails it Again
This will be considered a classic. It is relevant at least every three years... (Click the post title to see properly until I get around to customizing this blog more)
My Session Has Fallen and I Can't Get Out
Ran across on question on LinkedIn today and thought the answer belonged here as well...
Q: (paraphrased for grammar) How to automatically redirect to the login page after a session time out?
A: Assuming that there is a security session that is separate from your server session, you can add a hidden AJAX component that checks every n seconds and redirects when the session is closed. When you do this, you need to include in your keep alive call an appended parameter that is incremented or changed randomly each time or else you may get a cached response from the browser and miss that magic time out moment.
If you need to know if the session of the same application on the same server has timed out, there is a chicken and egg paradox as any call to the server to check if the session is still alive will keep the session alive, so it will never time out. I've heard of applications that have worked around this, but have not had to research it out as the requirement always resolved to a security session timing out that lived on another server (as described in the first paragraph) or the that simply have the page go to the login page on the next click after the timeout was acceptable.
To go to the login page after the next click in a timed out session, simply fill in the security node of your web.xml completely and the web server will do the rest.
Q: (paraphrased for grammar) How to automatically redirect to the login page after a session time out?
A: Assuming that there is a security session that is separate from your server session, you can add a hidden AJAX component that checks every n seconds and redirects when the session is closed. When you do this, you need to include in your keep alive call an appended parameter that is incremented or changed randomly each time or else you may get a cached response from the browser and miss that magic time out moment.
If you need to know if the session of the same application on the same server has timed out, there is a chicken and egg paradox as any call to the server to check if the session is still alive will keep the session alive, so it will never time out. I've heard of applications that have worked around this, but have not had to research it out as the requirement always resolved to a security session timing out that lived on another server (as described in the first paragraph) or the that simply have the page go to the login page on the next click after the timeout was acceptable.
To go to the login page after the next click in a timed out session, simply fill in the security node of your web.xml completely and the web server will do the rest.
Friday, August 14, 2009
Work is the Curse of the Web Technologist
While it is very good to be busy in economic times such as these, it becomes easy to fall behind when keeping ahead. One obvious example is the fall off of my postings on this blog. The other is when a new spec right at the heart of my day-to-day livlihood is under construction for four months before it pops up on my radar.
In this case, I'm talking about HTML 5.
OTOH, web specifications seem to be totally outside of the whole "Internet speed" thing, because I'm still waiting for there to be more HTML 4 compliant pages on the web :)
In this case, I'm talking about HTML 5.
OTOH, web specifications seem to be totally outside of the whole "Internet speed" thing, because I'm still waiting for there to be more HTML 4 compliant pages on the web :)
Wednesday, August 12, 2009
Some Comments on Offshore and Outsourcing.
This question came up on Linked In today, and I thought I would post my response to it here for those that don't belong (and if you don't and you are reading this blog, you probably should):
I read the question as one about outsourcing, and I see many responses about off-shoring. I'll give my 2 cents on both, and you can owe me a nickle including tip.
Outsourcing is a way to mitigate risk for mission critical goals. The mitigation is in two forms. The first is, outsourcing to experts provides the perceived safety that the job will get done correctly. The perception is right about half the time (in my experience).
The other form of risk mitigation is the ability to place the blame for any failure on the vendor. As a vendor, I know that the likelihood of this being the reason for outsourcing increases with the number of people involved in the decision.
Off-shoring is a mixed bag. There are some companies that are really good, and some that are not. There are individuals within companies that are really good, and many that are not. In other words, on one level there is no difference between offshore and outsourcing.
On another level, there is the communication gap that is unavoidable due to both cultural and temporal differences. There are some companies that try to offset the temporal differences by having teams that work hours that coincide with US business hours. Anyone who has ever used 24 hour services knows that the best and brightest rarely work in the wee hours, and those that do are still not at the top of their game.
Off shoring works great for both parties far more often if the requirements are crystal clear and fairly static. Otherwise, your mileage will vary. Since the successes are a huge boost to ROI, they are well publicized and very motivating. The much more frequent failures are kept low key to protect careers.
And, as Dennis Miller often said: "But that's just my opinion...I could be wrong"
I read the question as one about outsourcing, and I see many responses about off-shoring. I'll give my 2 cents on both, and you can owe me a nickle including tip.
Outsourcing is a way to mitigate risk for mission critical goals. The mitigation is in two forms. The first is, outsourcing to experts provides the perceived safety that the job will get done correctly. The perception is right about half the time (in my experience).
The other form of risk mitigation is the ability to place the blame for any failure on the vendor. As a vendor, I know that the likelihood of this being the reason for outsourcing increases with the number of people involved in the decision.
Off-shoring is a mixed bag. There are some companies that are really good, and some that are not. There are individuals within companies that are really good, and many that are not. In other words, on one level there is no difference between offshore and outsourcing.
On another level, there is the communication gap that is unavoidable due to both cultural and temporal differences. There are some companies that try to offset the temporal differences by having teams that work hours that coincide with US business hours. Anyone who has ever used 24 hour services knows that the best and brightest rarely work in the wee hours, and those that do are still not at the top of their game.
Off shoring works great for both parties far more often if the requirements are crystal clear and fairly static. Otherwise, your mileage will vary. Since the successes are a huge boost to ROI, they are well publicized and very motivating. The much more frequent failures are kept low key to protect careers.
And, as Dennis Miller often said: "But that's just my opinion...I could be wrong"
Subscribe to:
Comments (Atom)