jboss as 6 can be used by 64 or 32 bit jvm. Why are you thinking that the distribution should be different for 64bit architecture?
I have thought, that 64Bit-Machines need 64Bit-compiled code. So if Jboss AS Distribution were compiled using a 32-Bit-Machine, then it will not really 64-Bit-enabled. Is that false?
I want to setup a 64 bit machine with both jdk32Bit and jdk64Bit and want to use the JBOSS AS with jdk64Bit. So am I right to say that I do not need to setup anything (besides the path to the preferred jdk) ?
For example, in order to use Eclipse on 64Bit-Machine, I need to download the 64Bit-Version of Eclipse. Of course, I can use the 32Bit-Version of Eclipse on a 64Bit-Machine (am I right ??), but then it makes no use of 64-Bit-capabilities.
Are there any pittfalls?
If you need run any native code which is called from java, you need equivalent compiled code for the given architecture 32 or 64 bit. Eclipse is a such case.
If your java application is using only java APIs not native code calls, you need only select JVM to be architecture specific.
So java-projects without native code are 64-bit-treated, if using JDK64.
I do not need to compile my java code (which has no native code) against a jdk64-bit version to have a 64bit version of that java project. Am I right? Only the using of a jdk64bit is sufficient to treat the java app as a 64-bit-java-app.
right, Java bytecode is platform independent.
yes, indeed, java is plattform independent.
Therefore jboss as is also totally plattform-independent - jbossAS and all its included things (webcontainer, jars,...) does not make use of any plattform-dependent-source (dll or the like).