Did you ever get a response to this? I'm interested in the same question.
This one is a pretty fundamental feature, it's difficult to get much into production without it given most firewall environments.
Will keep a lookout for 7.1Final.
Thank you for providing the following great feature of remote lookup in simplified manner in JBoss AS7 thunder.
But in production environments it is sometimes not possible to open a port like 4447. Usually we prfer HTTP Ports only specially when we have an Apache WebServer running in front of JBoss Thunder .... So is there any plans for supporting EJB/JMS Access over Http protocol?
1 of 1 people found this helpful
As far as JMS is concerned the port 4447 is only used for JNDI lookups. The actual JMS work is done on other ports. JBoss AS7.1.Final (i.e. Thunder) uses HornetQ as its JMS implementation and HornetQ can be configured to use HTTP or a Servlet. See this bit of documentation for more on that.
Also, if you wish to avoid the use of 4447 altogether with JMS then you can eschew the JNDI look-up and use the HornetQ "core" API to acquire references to the required JMS artifacts. I believe something like this will work:
Destination destination = HornetQJMSClient.createQueue("testQueue"); //this is NOT the JNDI name, it is the HornetQ name
HashMap<String, Object> connectionParams = new HashMap<String, Object>();
TransportConfiguration transportConfiguration = new TransportConfiguration("org.hornetq.core.remoting.impl.netty.NettyConnectorFactory", connectionParams);
ConnectionFactory connectionFactory = (ConnectionFactory) HornetQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration);
After this you can use the Destination and ConnectionFactory just like you would if you looked them up in JNDI.
Unfortunately I can't weigh in on EJB.
Wonderful Justin .... Justin++
My 50% problem is resolved by your answer on JMS part.