Hello Mr. John Stark, We actually met before, at LAJUG. I hope to see you there again. In fact, I tried to reach JBoss and invite them again, but I was not responded back to.
Thank you for informing me that JDK 1.2 hasn't been supported for 3 years. To me, it makes perfect sense that JBoss AS requires a modern JDK. But it really would be nice if legacy systems could communicate to the JBoss AS as clients. I was so close to integrating a JDK 1.2 JMS solution from Dynix. Fortunately, JMS 1.2 is compatible even on JDK 1.1 systems, which lend it very well to legacy systems. JMS also plays a role in the pivitol SOA. I think that the only aspect of JBoss that prevented this legacy integration was JNP's dependence on JDK 1.4 libraries. I perfectly understand the need for core of JBoss to be dependent on a modern JDK, but the ability for a client to connect with an older JDK and utilize a JDK 1.1-1.3 compatible API is quite persuasive. Regardless, I am very thankful for the excellent work that JBoss has provided to the community. I guess my best alternative is to use Client/Server sockets, or an HTTP post for this JMS message. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876864#3876864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876864 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user