What do you think? ISO Tomcat guru.

Okay maybe not a 'guru'

I'm playing around with something on the side, the short version is that it needs to listen to a specific port and package a bytestream to a standard soap envolope (close enough anyway) which will be stuffed into a messege queue. Of course there is a catch, it has to run in tomcat and be easily intalled and managed by non geeks. The other minor cavete is that the messeging is being handled by MSSQLSERVER and there are currently no pools set up.

Option 1) bring in Axis and set it up as a web service that will handle all of the collection + transformation and then dump in on a JMS stack?

Option 2) write a seperate service(service/engine/connector/host/context) into tomcat that will run in paralel with Catalina and write a root level filter that will handle the collection, pass tranformation to a secondary library, then stuff the messege into the local datasource.

Option 3) custom write an olde skoole rmi server to monitor the desired port and then shovel things along behind the scenes

Obviously I lean towards op1, but with the vast majority of my webservice experience being in WebLogic, I'm not sure of the performance hits.

So what are your oppinions? I'm open to other ideas aswell.
-Thanks
-Mel