The Java Platform Debugger Architecture (JPDA) API included in the JDK lets you connect to a Java debug session and receive debug events. This code allows you to do the same things you would normally do with jdb or an IDE debugger. This is useful if you want to write your own debug, diagnostics or metrics tools.
Unfortunately, there is no 100% foolproof process for determining how to validate an arbitrary XML document. If you are receiving a document, you should not leave choosing the validation mechanism to a remote party (e.g. downloading a DTD using its document-specified URI). Doing so opens your application to, at the very least, a potential denial-of-service attack. A validation mechanism may not even be specified in the document: W3 XML Schema (XSD) does not require it; RELAX NG does not seem to support such a mechanism. Then there are some XML documents that just don't have a schema of any form.
Nevertheless, there are times when you need to inspect a document to find out what it is. Most commonly, support is required for multiple versions of a document, where the structure and validation mechanisms change over time.
Note: when talking about validation, this post is not referring to whether the XML is well formed or not. Any XML parser should be able to check the syntax. This is about external constraints imposed on the document structure via a schema, DTD, etc.
Can you spot the problem with the following dialog?
I expect the developers of the Steam installer are making trade-offs for the benefit of younger users - providing visuals to help match them with their language. However, using flags in software products is generally a bad idea.
I spend quite a lot of time writing Java code. I got to thinking about the time I spent implementing, testing, maintaining and just paging over equals /hashCode implementations. These common building blocks tend to work much the same way in most classes and I wondered if there were a way to make them go away.
This article was written with Java 6 in mind.
Updated 2008/12/16.
/**
|
If you aren't careful with streams in Java, you end up with resource leaks. This article addresses some of the pitfalls of stream handling.
The examples that follow use implementations of OutputStream. Which output stream is not important - implementation details are encapsulated by the object and may change between Java versions. It is the developer's responsibility to honour the contract as per the documentation.
OutputStream.close(): Closes this output stream and releases any system resources associated with this stream. The general contract of close is that it closes the output stream. A closed stream cannot perform output operations and cannot be reopened.
New Java developers pick up pretty quickly that they have to close streams. Problems arise when they start thinking about how to do it.
It can be useful to automate deployment of enterprise applications to servers during development, either to automatically set up test builds or perform build verification during the kitting process. WebSphere Application Server (WAS) comes with a number of Ant tasks that can be used for this.
A quick HOWTO on setting up Rational Application Developer 7 as a Subversion client on Fedora 8.
Changes in the Java language have made the differences between
int
and
java.lang.Integer
less obvious but every Java developer should understand them.
Unless otherwise stated, Java 7 syntax and types are used.
Many of these issues apply to all the primitive types and their wrapper types.
This post has been rewritten in 2013. The original post was still generating comments (not the good kind) five years after it was written. This post is more detailed and provides better examples. Old comments have been deleted to avoid confusion - new criticism is welcome.
In Java, it is possible to get a String representation of a class by calling the Class.getName() method.
Since Java 1.5 (AKA Java 5), it has been possible to get the canonical name using Class.getCanonicalName().
#include <stdio.h>
int main() {
printf("Hello, World!\n");
return 0;
}
;syntax expected by NASM ;DOS, x86, 16bit org 100h ;start at address 100 mov ax,0200h ;AH=2 mov dx,0048h ;'H' int 21h ;int 21,2 (print char) mov dx,0065h ;'e' int 21h mov dx,006Ch ;'l' int 21h mov dx,006Ch ;'l' int 21h mov dx,006Fh ;'o' int 21h mov dx,002Ch ;',' int 21h mov dx,0020h ;' ' int 21h mov dx,0057h ;'W' int 21h mov dx,006Fh ;'o' int 21h mov dx,0072h ;'r' int 21h mov dx,006Ch ;'l' int 21h mov dx,0064h ;'d' int 21h mov dx,0021h ;'!' int 21h int 20h ;int 20 (terminate)
C:\WINDOWS\system32\debug.exe
C:\test>DEBUG -a 0C8A:0100 mov ax,0200 0C8A:0103 mov dx,0041 0C8A:0106 int 21 0C8A:0108 int 20 0C8A:010A -h 010A 0100 020A 000A -n PCHAR.COM -rcx CX 0000 :000A -w Writing 0000A bytes -q C:\test>PCHAR.COM A
mov ax,0200 mov dx,0048 int 21 mov dx,0065 int 21 mov dx,006C int 21 mov dx,006C int 21 mov dx,006F int 21 mov dx,002C int 21 mov dx,0020 int 21 mov dx,0057 int 21 mov dx,006F int 21 mov dx,0072 int 21 mov dx,006C int 21 mov dx,0064 int 21 mov dx,0021 int 21 int 20
using System;
public class HelloWorld {
public static void Main(String[] args) {
Console.WriteLine("Hello, World!");
}
}
Posts
All Comments
