Java Software Development

Enabling remote access to JVM by JConsole JConsole password and access file configuration

Local debugging is automatically enabled, for remote debugging, you have to configure the application. -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n JBoss DEBUG_OPTS = -Xdebug -Xrunjdwp:transport= dt_socket,address=1044,server=y,suspend=n

There are three ways to create composit PK, see section 2.2.6 @Id and @Embeddable or @EmbeddedId or @IdClass

Alex Miller's Technical Blog

Java 7 Swing

To browse the JNDI contexts in JBoss Goto http://localhost:8080/jmx-console Under the 'jboss' section: click the link 'service=JNDIView' Under List of MBean Operations, java.lang.String list(): click the Invoke button Describes JNDI and how to connect to remote JNDI use the -b option with the run.bat or run.sh file When JBoss AS starts up, it binds to localhost by default. Older versions of JBoss would bind to the address 0.0.0.0. Because of this change, you can’t access JBoss AS locally by using your machine name or 0.0.0.0. For example, to verify the server is running, you can’t go to http://myhostname:8080; you have to go to http://localhost:8080 or http://127.0.0.1:8080. Properties props = new Properties(); props.setProperty("java.naming.provider.url", "jnp://server:1099"); props.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming"); props.setProperty("java.naming.factory.initial","org.jnp.interface...

Jar hell Java classloading

Monotechnology