Noel Holshouser

Greenhorn
+ Follow
since Jan 26, 2000
Merit badge: grant badges
For More
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
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Noel Holshouser

I think that tar brushing the entire web for the page design flaws of some (most??) is a mite severe. The dot-com collapse had more to do with poor business/investment practices than any thing else. The major problem as I see it was that the graphic designers didn't and still don't have complete mastery of their medium (web page design); therefore, the design task fell to those who had at least a fair knowledge of the technical aspects of web page presentation. I don't think many will argue that most technically oriented folks have either the knowledge or mind set of a graphic artist. In the rush to get something on the web, good design principles and taste went by the wayside. The result was cluttered, confusing and sometimes useless web pages. Can anyone imagine international corporations allowing such a mess to represent them in a major publication's advertisement? Yet, we have all witnessed this sort of thing on the web.
This then beggars the further point of proper language usage. Offshore sourcing of page design by non-native speaking people will inevitably lead to poor language usage if not scrupulously and constantly monitored. How- ever, given the current state of education and emphasis on correct and understandable written English in this country, is it any wonder that proper usage has gone by the wayside. When you have to spend an inordinate amount of time deciphering posts or emails to get the meaning of a writer's message, can we really expect more?
Thanks Jesse and Mirko.
Just found this at: http://developer.java.sun.com/developer/community/chat/JavaLive/1997/jl0318.html
"We have to be really careful when we develop in native code. All Java built-in mechanisms on type safety and protection are no longer effective. Native methods essentially become part of the VM. The JNI is designed to minimize the number of mistakes you can make developing native methods. Still, you have to be really careful."
and
"The JNI has to be the last resort. If your application contains even one native method, the application is no longer 100% pure, and you'll lose many of the benefits of Java. However, if you absolutely need to access certain plaform-dependent features available in the standard Java library; or you have a large body of existing code in C and C++ that you do not want to throw away; or you are certain that you cannot get the performance you need with the current Java compilation technology; you may use native methods."
Seems that Jesse is more than right. You'd better be absolutely confident that the wrapped code is leak proof or suffer the probable undefined consequences.
------------------
23 years ago
Assumption: Legacy code (binary only available) that is called periodically which has a 16 char array to which 18 char are written (obviously not my code), predicably causing system crash.
Questions: If placed in a Java wrapper, what exception(s) if any is/are thrown on memory overwrite? When is exception thrown? Under EJB, will errant code be contained within the sandbox without harm to the rest of the code?
------------------
23 years ago

Originally posted by mitch tzonev:
Hey Guys,
What's the best IDE for developing EJBs?
Thanks
Mitch


Is there something wrong with Forte/Net Beans Developer?