Mr N

Windows Remote Desktop allows users to use a Windows computer while not sitting in front of it. This is ideal for remote support. For security this feature is not switched on in the standard installation and so must be explicitly activated. In order to use Remote Desktop you must have a password set up on your machine. Below is a simple guide to switching this feature on:

1. Load File Explorer
2. Right click on My Computer select Properties
3. Click the Remote tab
4. Check Allow users to connect remotely to this computer
   On Windows 2008: Allow connections from computers running any version of Remote Desktop (less secure)
5. Click Ok

The Apache Tomcat instructions on this are here but they are both worse than useless and totally acurate. It starts we the sentence:

This section of the documentation applies to procrun 1.0, and is now obsolete

Great! Now what. There is no link to the document that supersedes it, nor what procrun is! Typical open source documentation! As with all these thinks you have to go reading old mail archives to find the answer. Buried about half way down an archive page on a generalist open source support web site is the answer. procrun is a thin (’C') executable program that can run java classes. An extension of procrun is prunsrv which also knows how to register services with windows. Now, here is the gem of information that lets everything make sense. The vital piece of information that would save everyone who reads the Apache Tomcat Windows documentation 2 hours of searching for…. wait for it….. Tomcat has compiled up prunsrv.exe with the instructions for starting and stopping Tomcat and renamed it to tomcat6.exe. If you find your tomcat6.exe executable, right click it and select Properties. Go to the Version tab and select Original File name is says “prunsrv.exe". The original Tomcat documentation is actually correct, the documentation page is obsolete because you should be reading the prunsrv.exe documentation. But good luck finding that - only kidding it’s here!.

Seems like an obvious one, but I keep forgetting where the OutLook Express executable is. So as this is the brain extension, I’ll add it here for all time.

c:\program files\outlook express\msimn.exe

Once you have loaded it in, you can switch on (or off) the preview pane.

1. View->Layout
2. In the Preview pane section check (or uncheck) show preview pane

An interesting illusion with a checker board. Are those lines parallel? http://hcpcrew.at/pix/illu_003.gif The second one is a bit rude: http://hcpcrew.at/pix/chinese.jpg

Newer versions of ActiveMQ have support for XML name space schema declarations to allow easier configuration of container beans. Adding the following XMLNS declaration to the beans container will allow you to use ActiveMQ’s amq name space.

<beans xmlns="http://www.springframework.org/schema/beans"
 xmlns:amq="http://activemq.apache.org/schema/core"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.springframework.org/schema/beans
  http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.apache.org/schema/core
  http://activemq.apache.org/schema/core/activemq-core.xsd">

 <amq:broker start="true" brokerName="bs-localhost">
  <amq:networkConnectors>
   <!-- more configurations -->
  </amq:networkConnectors>
 </amq:broker>

</bean>

When the application is deployed (in Tomcat) it will work as expected, however if you try to run it under Eclipse the container fails to start with the message:

org.xml.sax.SAXParseException: schema_reference.4:
Failed to read schema document 'http://activemq.apache.org/schema/core/activemq-core.xsd',
because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not .

Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c:
The matching wildcard is strict,
but no declaration can be found for element 'amq:broker'. </xsd>

The amq:broker maybe replaced with amq:connectionFactory depending on which name elements you have actually used. In order for Eclipse to understand the amq name space you must add xbean support for ActiveMQ. This is achieved by adding xbean-spring-3.4.jar to your dynamic web project. According to the ActiveMQ website the XSD declaration will be automatically fished out of the jar and used to help Eclipse give you features like command completion for the XML schema. In fact what happens, is that Eclipse lights up like a Christmas tree moaning that it can’t find the schema declaration. Below is a set of instructions to tell Eclipse how to associate the activemq-core.xsd url with the activemq-core.xsd found in the jar file which is shipped as part of ActiveMQ.

1. Select Windows->Preferences from the Eclipse menu bar.
2. Select XML->XML Catalog from the left hand configuration tree.
3. Highlight User Specified Entries and select Add.
4. The Add XML Catalog Entry windows appears.
5. In the Location enter the path to the activemq-all jar, then add !/activemq.xsd to the end of the jar name. e.g. jar:file:C:/Java/libs/activemq/apache-activemq-5.2.0/activemq-all-5.2.0.jar!/activemq.xsd
6. Under KeyType enter Namespace Name
7. and under Key enter http://activemq.apache.org/schema/core
8. then click Ok.
9. Now we need to do the same for the other name space file, so hit Add again.
10. In the Location enter the path to the activemq-all jar, then add !/activemq.xsd to the end of the jar name. e.g. jar:file:C:/Java/libs/activemq/apache-activemq-5.2.0/activemq-all-5.2.0.jar!/activemq.xsd
11. Under KeyType enter Schema Location
12. and under Key enter http://activemq.apache.org/schema/core/activemq-core.xsd
13. Click Ok, Ok.

The Spring IDE should do its thing and the red error markers will disappear.