What is the reason to use remoting? Do you use EJBs?
What is the reason to migrate to a plain Tomcat?
I suppose the project is wired to some JBoss functionality and you can not use a 'plain' Tomcat.
I am using Jboss remoting for remote client server communication and data transfer (text data).
If I want to migrate to another open source application server then I am not able to migrate because
Jboss remoting code has dependencies on jboss-remoting.jar, Jboss-servic.xml (Jboss 4.2.2) / remoting-service.xml (Jboss 5.1.0)
In short it is completly dependen't on Jboss Application Server which I do not like and want to migrate to Tomcat
JBoss Remoting is a stand-alone project and can be used without all of JBoss AS, see: http://www.jboss.org/jbossremoting
Though, personally, I am perplexed as to why you would use remoting in a web application. I think that remoting would go against the servlet/JSP specs because you would have to fire off an alternate thread to handle requests. Or is the web app just a remote client?.
I refered documentation on Jboss Remoting 2 ,I think I pretty much figured out where all configuration file goes.
but In my Jboss-service.xml I have following <mbean> tag. I do not know where should I replace this in tomcat
display-name="SSL Servlet transport Connector">
I still need help over this issue MBean thing is complicated
Are you or any of your application using that MBean? If not, then why do you need it in Tomcat? If you are using that MBean, then you'll have to provide more details on how you are using it.
I'm having the same issue. I want to switch from a JBoss 4 to Tomcat 6.
I have a MBean declared like this :
<role name="guest" read="true" write="true"/>
<role name="publisher" read="true" write="true" create="false"/>
<role name="durpublisher" read="true" write="true" create="true"/>
And in my application, it's called like that :
<jee:jndi-lookup id="myJMSDestination" jndi-name="topic/topicSecurity">
Thanks a lot.